4 ms·
Everywhere I've worked (including for MAANG companies), software engineering was best done by a combination of three things, listed in priority order: A) think
by christophilus 4y ago
Everywhere I've worked (including for MAANG companies), software engineering was best done by a combination of three things, listed in priority order:
A) thinking
B) programming
...
Z) meetings
The meetings contained something useful maybe 1/10th of the time, lasted maybe 4x longer than they should have, and involved maybe 20x more people than they should have. Those numbers skew higher the larger the organization.
Maybe that's a bit of an exaggeration, but not by much.
- kristjansson 4y agoMay we all be so fortunate to have tasks defined so specifically and selected so precisely that one can accomplish them only by thinking and programming, and find satisfaction in doing so.
- christophilus 4y agoHeh. I knew I’d get downvoted. I’ve generally been on the most productive teams in my segment of the business. The biggest differentiator seems to be that my teams had devs that knew when to ask questions and what questions to ask. This is probably the most important skill a dev can learn. The solution to ambiguous requirements is not meetings. At least, not in the usual sense. It’s knowing who and what to ask, and occasionally meeting with customers or knowledgeable stakeholders.