What software engineers can learn from the rapid collapse of Fast

Re:What software engineers can learn from the rapid collapse... by wnevets on Thursday April 07, 2022 @05:56PM (#30950814)

> Sounds like the engineers were just entertaining themselves with shiny toys rather than solving the problems they actually had.

Programmers love to add the latest tech to their resume then move on to a new position within ~18 months

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by CoastalCoder on Thursday April 07, 2022 @06:18PM (#30950999)

That may be specific to early-mid career focus

If/when a developer builds deep knowledge of a problem domain, things like framework-of-the-month may become an unwelcome distraction.

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by teaearlgraycold on Thursday April 07, 2022 @08:06PM (#30951842)

Seeing someone using nothing but tried and true tech to solve new problems is a resume green flag.

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by Nextgrid on Friday April 08, 2022 @05:02AM (#30954853)

Is there a place where such "green flags" would net me money? It seems like as a software engineering employee, the roles that require me to waste time reinventing the wheel and battling self-inflicted complexity pay significantly more than those who require solving actual problems with boring tech.

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by teaearlgraycold on Friday April 08, 2022 @10:07AM (#30956924)

> Is there a place where such "green flags" would net me money?

Well the best way to reap the benefits of your experience is to run your own company. Not screwing yourself over with BS tech is a competitive market advantage. However you might need to hire people so you can’t pick something too old.

Working for other people it’ll mostly net you less on call headaches.

[ Parent | on HN ]