Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Sign in
Join
14
Likes
10
Comments
Your tech stack is not the product
by
@londoner
https://hoho.com/posts/your-stack-is-not-the-product/
So so true! I've done it myself. As dev's we tend to take pride in the tech stack we form for a project - at the end of the day the customer doesn't really care about it.
Thanks for sharing! I like the goals outlined for the technology team - "Ship the product. Frequently and reliably" and "Support growth" - are clear and concise.
Although, I think is hard to ensure that these goals are being met and that the technology decisions being made align with them. I wonder how to do it properly 🤔
Thank you for sharing this man!
BTW, I've checked your blog, your blog was born in 1996, and I born in 1996 😂
I think this is especially important for indie hackers to remember. When I was learning to code, it was easy to get lost in all of the discussions about the different tech stacks, but ultimately your users don't care.
I couldn’t agree more!
Unless you’re supplying something to a company whose own business is software, in my experience, customers could not care less about what technology is used. All they really care about is how what you provide to them meets their needs.
It doesn’t matter if you supply consumers or businesses. If you want to build a profitable business of your own, being obsessive about delighting customers is much, much more important than being obsessive about whatever technology stack you happen to have chosen.
At the end of the day, those who really care about the tech are the people who are using it on a regular basis - the developers.
The choice of the tech, therefore, should consider the developer first - if the development env suits the needs of the developer or the team, coding and ultimately the shipping will happen faster.
I know founders who decided to go for the ol' HTML- CSS- JS stack - no bundlers, no TS, no config and this works for them.
As I tried it myself, it was pure hell.
I need my frameworks and strong typing and all the fancy config around.
Without it, every simple feature or even a small task will take me much longer to develop
This is so true - I commonly see other fellow makers put a lot more emphasis and importance on their tech stack rather than the product itself.
Yeah, you're right! The goal is to keep delivering the promise and exceeding expectations. It becomes a matter of putting yourself in the shoes of the client. And also by not mentioning the tech stack it positions the product as a solution and not just another product or tool in the market.
Yup! See this all the time, and guilty of it myself. Hahaha.
Exactly! You always have to think of the end user/buyer - and none of them care how you built the product, they care how the final product helps them.
This comment was deleted 4 years ago