3 ms·

The problem with this question is it is akin to those people on photography forums and elsewhere asking "what camera / lens / ISO /shutter speed / aperture" did

The problem with this question is it is akin to those people on photography forums and elsewhere asking "what camera / lens / ISO /shutter speed / aperture" did you use ? As if somehow having the same combination will give them the same results. Surely the correct and only answer is "the right tech stack for the job". Trying to shoehorn everything into one chosen stack is only likely to end in dismal failure. Switching stacks just because flavour of the month cool stack is code written in Foo with Bar library with a Foobar cloud backend is also only likely to end in dismal failure. If a graph database is suitable for a project ... then use it. If cloud is suitable for a project... then use it. etc. etc. Don't be a "Jack of all trades, master of none", jumping around programming languages and libraries just because its the cool thing to do. The trouble is I see too many people over-egg the pudding on tech stacks. Perhaps especially when it comes to cloud services where they architect everything as if they were getting billions of hits per second and feel the need to justify using all cool cloud services buzz words like horizontal scaled event-driven, serverless computing platform. Sometimes its better just to follow the KISS principle (Keep It Simple Stupid).

siculars 5y ago
My takeaway from the ask is what can you get done as a “solopreneur” and which tools do you use to do it. It looks like there are many answers and no single “right” answer. I’m particularly interested to know why people pick the tools that they pick.
ebiester 5y ago
One of the components of "right tech stack" is "how many people does it take to support it?" For example, K8s might be the right tool for many things, but unless you have explicit K8s experience it probably is wrong for a solopreneur today. Thus, seeing what others are using with those constraints can be constructive.
Zababa 5y ago
> Surely the correct and only answer is "the right tech stack for the job". That is assuming that there is a "right" stack in the first place. That thread is mostly proving the opposite, that the stack doesn't really matter. "use the right tool for the right job", "don't focus on the flavor of the month", "focus on getting users before scalability" and "KISS" all have been said a thousand times. Saying that again leads to no new insight.
- traceroute66 5y ago
  > Saying that again leads to no new insight. I would throw that one right back at you by saying.... What great insight does 200 people posting about 200 different variations of stacks provide insight about ? Diversity in stacks ? And, erm .... not much else ? Sure I guess you could try to aggregate it and look for patterns, but would that really be useful ? I'm not sure the sample of 200 or so would be big enough for it to be more than a subjective extrapolation of random answers and you certainly couldn't claim to see trends etc. in such a small sample.

siculars 5y ago

My takeaway from the ask is what can you get done as a “solopreneur” and which tools do you use to do it. It looks like there are many answers and no single “right” answer. I’m particularly interested to know why people pick the tools that they pick.

ebiester 5y ago

One of the components of "right tech stack" is "how many people does it take to support it?" For example, K8s might be the right tool for many things, but unless you have explicit K8s experience it probably is wrong for a solopreneur today. Thus, seeing what others are using with those constraints can be constructive.

Zababa 5y ago

> Surely the correct and only answer is "the right tech stack for the job". That is assuming that there is a "right" stack in the first place. That thread is mostly proving the opposite, that the stack doesn't really matter. "use the right tool for the right job", "don't focus on the flavor of the month", "focus on getting users before scalability" and "KISS" all have been said a thousand times. Saying that again leads to no new insight.

traceroute66 5y ago
> Saying that again leads to no new insight. I would throw that one right back at you by saying.... What great insight does 200 people posting about 200 different variations of stacks provide insight about ? Diversity in stacks ? And, erm .... not much else ? Sure I guess you could try to aggregate it and look for patterns, but would that really be useful ? I'm not sure the sample of 200 or so would be big enough for it to be more than a subjective extrapolation of random answers and you certainly couldn't claim to see trends etc. in such a small sample.