3 ms·
When reading these comments, I think it's worth remembering the HN crowd and what kinds of companies they tend to work for, especially the most vocal ones, when
by t-writescode 5y ago
When reading these comments, I think it's worth remembering the HN crowd and what kinds of companies they tend to work for, especially the most vocal ones, when taking their advice.
I've worked at a large company, a small and young company and small and very old companies.
You learn different things at different companies.
It's useful to learn how to be scrappy and fast as a young startup, to learn a little about a LOT of different technologies to push them out as quickly as possible.
It's useful to learn how to deep dive and improve features in a small company where you can make real impact, while still having the freedom and cash-flow to go slow and intentional and make big changes in small areas.
It's useful to work for a large, established company that has taken its scars and has long, established and hard-fought best practices in place, and where you can work with principal engineers that have made some awesome software.
Every kind of company has its benefits.
- DoingIsLearning 5y agoI would add Consultancy/Contracting as a must have experience in that list of 'work settings to try before you die'. If you do contracting work you will get a _huge_ variety of work in different problem domains. You really learn a lot in the costumer facing part of it, specially if you are more introvert and also the constant networking needed to have a steady stream of work and clients (You also learn that there is no money in the world that is worth putting up with some unhinged clients). One thing that is important to highlight is that although you can learn many things in all of these settings, they also carry different stress levels, I would rank from lowest to highest stress (highest to lowest Quality of Life): 1. Small old company 2. Large old company 3. Consultancy 4. Young Startup