You should of course practice solving the kind of problem you want to solve or enjoy solving.
If you’re optimizing for an IC career at a large company, then you should of course practice that kind of work (and get mentored and get depth and everything the article says).
If you’re an engineer trying to transition to building businesses or being an investor, then you should of course NOT do what the article suggests. You should instead practice startup problems (probably at startups or by starting your own), like prioritization and resource allocation and networking.
And if that’s the goal, then you can easily find business mentors or startup mentors that will make an impact on your career, and what the article pejoratively calls “breadth” in software problems will actually turn out to be depth in business or startup problems (like prioritization and resource allocation and networking).
tl;dr – Sure, find mentorship and get experience, but make sure you articulate your goals first.
You should of course practice solving the kind of problem you want to solve or enjoy solving.
If you’re optimizing for an IC career at a large company, then you should of course practice that kind of work (and get mentored and get depth and everything the article says).
If you’re an engineer trying to transition to building businesses or being an investor, then you should of course NOT do what the article suggests. You should instead practice startup problems (probably at startups or by starting your own), like prioritization and resource allocation and networking.
And if that’s the goal, then you can easily find business mentors or startup mentors that will make an impact on your career, and what the article pejoratively calls “breadth” in software problems will actually turn out to be depth in business or startup problems (like prioritization and resource allocation and networking).
tl;dr – Sure, find mentorship and get experience, but make sure you articulate your goals first.