3 ms·
> In tech you are trying to make something no one has done before so you want the young hungry engineer. Alternatively, choose the older engineer with the expe
by Angostura 13y ago
> In tech you are trying to make something no one has done before so you want the young hungry engineer.
Alternatively, choose the older engineer with the experience to know: "You know what? Fundamentally, what we're building here is the same as this thing from 10 years ago".
- samfisher83 13y agoYes everything seems to go full circle from mainframe to PC to the cloud (Mainframes). It may be the same problem but someone younger might know how to tailor that solution to the younger generation. The other thing is all these founders are so young they may lack the experience or maturity to hire an older person.
- samfisher1906 13y agoI work at a software company that most likely will be bankrupt by year end due to a young developer's desire to rewrite our flagship product from the ground up using "new" technology. Three years later this new product has 40% of the functionality of the pervious version and has customers canceling contracts that have been with us for 10+ years.
- disbelief 13y agoExactly. Just because you're trying to accomplish something "no one has done yet" doesn't mean that you aren't going to be building on top of things (software, frameworks, paradigms) that have been around, at scale, for years. The older engineer is more likely to realize when a problem has already been solved, or during a crisis can connect the dots from previous experiences to find the solution.
- mason55 13y agoIt's funny. One of my friends lost his job in a round of layoffs recently and was lamenting that his skills were based way too much on their internal technology for him to ever find another job. I walked through it with him and explained that you don't realize how much stuff is the same anywhere. Communicating with customers & stakeholders is the same anywhere. Working with your coworkers is the same anywhere. Managing a project has the same steps in every company and if you're good at it it will translate. Likewise requirements gathering. Your knowledge of various domains that you pick up. Etc etc etc. MOST of what you're trying to do has been done before. All the day-to-day work that makes your business successful has been done thousands of times before. The only thing that's new is a few minor implementation details.