Product development is hypothesis testing. This is especially true in the early stages of a company when you need to confirm or reject your hypothe...
For further actions, you may consider blocking this person and/or reporting abuse
I’m so glad to see you recommending Next and TypeScript. Why not TypeScript on the backend too?
Honestly, mainly just due to our existing familiarity with Rails and its huge ecosystem. We knew we'd be carrying out a wide array of tasks on the server, and there's a gem for everything.
I know this is largely true for the Node/Typescript ecosystem as well, but I've personally found Rails to be more plug-and-play.
They’re probably about equal when it comes to availability of plug n’ play libraries. Note: a lot of teams find that they’re more productive when they can use the same language throughout the whole stack.
Great article!
Re everyone working on everything in a small team. I was a tech lead of a small team of five, and my observation is that natural code ownership happens organically even at this size. Typically a single part has up to two major contributors.
I can confirm that using the same language, along with a common style and best practices guide, helps peers access the code when needed.
Hmmm...I find it interesting that the bulk of your recommendations are Javascript based.
For me, I'm more of the camp of depending on the founding team for their tech side.
If the bulk of them has experience .Net, PHP or Python I would just go with those and slowly migrate my stack to cater for scale.
As long as my main goal is to get my products or services out there, the type of stack is not that important.
Sure I do have biases for Python-based stacks but my core is whatever works to deliver the products or services.