Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What Does Your Tech Stack Optimise For? 💭 #148

Open
nelsonic opened this issue Aug 30, 2024 · 0 comments
Open

What Does Your Tech Stack Optimise For? 💭 #148

nelsonic opened this issue Aug 30, 2024 · 0 comments
Labels
discuss Share your constructive thoughts on how to make progress with this issue T25m Time Estimate 25 Minutes technical A technical issue that requires understanding of the code, infrastructure or dependencies

Comments

@nelsonic
Copy link
Member

There are many variables to consider when selecting a Technology Stack here are our Top 10:

  1. Customer Satisfaction - do the people using your product/service love or hate using it?
  2. Time to Market - time between ideas and delivering useable features; shorter is better.
  3. Total Cost of Ownership - how much does it cost to develop, deploy, run and maintain the app?
  4. Reliability / Availability - does your App perform reliably with the required service level e.g: 99.99% uptime?
  5. Developer Experience - Happiness and effectiveness at delivering features reliably.
  6. Ecosystem - are there good packages/modules available to extend the tech if needed?
  7. Scalability - does the technology need to serve just one person, millions or even billions of people?
  8. Hiring - availability of competent/experienced people who are available for the price you want to pay.
  9. Maintainability - how easy/difficult is it to maintain the tech over its useful life?
  10. Performance - the amount of useful work accomplished by a computer system. Relevant to conserve/maximise computing resources.

Note: the order in which your company/team place these competing priorities
will inform your selection of technology. ⬇️

Performance often becomes a "my language is faster than yours" pointless debate and loses track of other important factors.
If your server is ultra-fast but frontend has horrible UX or uptime and nobody uses it, you are just wasting time/money.

Other factors we consider as "given" are Security, Privacy and Standards: nelsonic/nelsonic.github.io#54 (comment)

@nelsonic nelsonic added discuss Share your constructive thoughts on how to make progress with this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies T25m Time Estimate 25 Minutes labels Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Share your constructive thoughts on how to make progress with this issue T25m Time Estimate 25 Minutes technical A technical issue that requires understanding of the code, infrastructure or dependencies
Projects
None yet
Development

No branches or pull requests

1 participant