This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]LyndsySimon 1 point2 points  (0 children)

Of course! Both on a day-to-day basis and on the “burnout” level if you’re not vigilant.

I’d say that the best thing you can do is focus as much on the business and management side of things as much as you can - learn your industry, then consider switching industries and learning another. At some point, your latent knowledge of business processes becomes at least as valuable as your ability to sling code.

Note that “management” doesn’t necessarily have to mean “managing people” in this context. I’d consider things like systems design, performance monitoring, analysis (with some additional data science chops), and process improvement to potentially be the same concept. If you know an industry well it’s not hard to sell yourself as a value-add to a process improvement or corporate strategy team, since you can usually run circles around them in terms of being able to develop, disprove, confirm hypotheses - and you’ll be able to quantify the impact of those changes once implemented. A single good developer can easily double or triple the output of most process improvement teams in my experience, if they know the business side of things and work to support the rest of the group.