3 ms·
Do you want to put your career on the line deciding which features or bug-fixes to prioritize by the next release? If the stakes were that high, wouldn’t you ra
by PraetorianGourd 4y ago
Do you want to put your career on the line deciding which features or bug-fixes to prioritize by the next release? If the stakes were that high, wouldn’t you rather have an ally who has done at least a minimal amount of analysis to determine which features you should prioritize given a finite amount of resources? If you are comfortable with that responsibility while also deciding how to implement those features than by all means ignore your product manager.
- yrgulation 4y agoI do. Thats how i work. I feel like there are two tiers of software engineers: programmers and developers. Programmers implement spec sheets, while developers talk to stakeholders or even end users to understand what they need to build. I am the latter. I think good CS curricula should include product and project management and accounting basics. Otherwise software engineering is just conveyor belt work.
- PraetorianGourd 4y agoI respect that, but you still distilled an entire discipline to a couple semesters of course work. It is as absurd as an MBA saying they could be engineers because they took a few CS classes. It is incredibly valuable to understand the big picture of the industry but it is not sufficient to distill an entire discipline to a few classes.