4 ms·
In theory, theory and practice are the same, but in practice they're not. Your list is good, but I'd add that he should pick one suitable language/framework an
by swombat 16y ago
In theory, theory and practice are the same, but in practice they're not.
Your list is good, but I'd add that he should pick one suitable language/framework and actually build something with it, so he has a better gut understanding of what it's like to build software. This will earn him essential respect from his team and allow him to sniff out a lot of the bullshit that would otherwise pass him by (eg "adding a button is really hard").
- hga 16y agoExactly. Either he needs real "bare metal" experience (whatever that means in this domain :-) or the ability to pick and then absolutely trust one person who does. Without one of those two no one is likely to end up happy.
- scorpioxy 16y agoSeconded. The list is fine, but to me it doesn't mean anything if the PM wasn't a previous programmer and knows nothing about pulling all-nighters chasing some obscure bug. If your friend really wants to get into a tech PM role, then he has to pay his dues just like we all do. So swombat's advice is right on. He should learn a language/framework and build something with it(not a small script, a real actual application).