3 ms·
Apart from the headline and a parenthetical reference, there isn't really any insight here about why returning to coding almost crushed him, which would have be
by altacc 6y ago
Apart from the headline and a parenthetical reference, there isn't really any insight here about why returning to coding almost crushed him, which would have been more interesting than yet another list of things common in modern development.
I have a similar switches between management and occasional development and there are a lot of "interesting" and frustrating challenges in returning to coding after a break of several years. Hearing other people's experiences helps dealing with the frustrations. There is a lot of tooling, frameworks, build processes, etc... which weren't widespread a decade ago which make starting a side project or jumping into code only occasionally an obstacle course for those who do not do it regularly. I'm ever grateful to those who write good how to guides for these things that I can refer to when I miss a crucial step in my setup.
- diydsp 6y agoI have my own rule for headlines. You can almost universally swap out the word 'How' for 'That'. e.g. "That Going Back to Coding After 10 years Almost Crushed Me."
- rbreaves 6y agoI feel this - there's been a definite shift in using some surprisingly large frameworks it seems like and it does take time to ramp up with them.
- bartvk 6y agoYup, I also couldn't find what exactly almost crushed them. That would've been the most interesting here.
- rob74 6y agoYeah... smells a bit clickbaity to me! If you decide to use such a title, you should at least expand on it in the article a little bit more than the "(although it almost crushed me)" at the very end...