I recently had a conversation with a new lead who insisted that his new website be created in C++. When a new lead, or a person that I’m having a conversation with about new work starts asking for a specific tech stack, I immediately ask, “Why do you need that technology” and “Are you open to suggestions on other tech stacks?”. The truth of the matter when choosing a tech stack for your startup, product or web application is really about two things in my opinion, search engine friendliness and overall popularity of a particular language. When you take the top few technology stacks used in web based applications, PHP, Ruby, Node.JS, Python and ASP (or other major windows based languages) and compare their effectiveness in terms of creating a web based software, it pretty much comes down to preference. A good PHP dev can recreate a Ruby or Python web application down to the letter and vice versa. The technology stack doesn’t have a lot to do with the particular language’s capabilities as much as it does preference.
Many years ago when we started 422 Studios, we had to choose a primary tech stack for our company. The tech we chose would be the basis for our client work, our hiring process and our sales process. We chose PHP based on the fact that it was and still remains, the most popular backend coding language. There were more jobs to be had, more talent to be hired and more resources to be consumed if we ran into a problem area or a difficult feature that we needed help building out. With that said, here are the top 3 things that we considered when making our choice, and that can be used to make an educated decision when choosing a tech stack for your next build.
These are our two most pressing questions when discussing a tech stack for a new build. Once you have answered both questions and found a competent developer, you should be set to go without worrying too much more about the stack that you chose. As with all web based endeavors the technology that is “the most popular” matters less than creating an amazing user experience with whatever tech stack you have adopted. Choosing a stack based on “what is cool” rather than trying to solve problems for your potential users and create a great experience is always the wrong way to go about it. As always, we hope this quick post helps in your daily grind, until next time, #hustleHard, make it happen, build your freedom every day.