Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Some are good quick-and-dirty implementers, some are deep design thinkers, some are just good at reviewing and giving advice.

Fred Brooks has a chapter in Mythical Man Month where he mentions different programmers having different roles within "Surgical Software Team" but that never took off.

I wonder if updating that to 2020 would make more sense to have a group of people shipping features full-steam ahead, another reviewing the code for mistakes, and then having other folks refactoring the mess, behind both of them.

I would frankly enjoy being in just one the three positions, any of them, much more than the position I'm currently: having to be all three at the same time.



I've often thought about a similar idea.

I'm still relatively new to the industry (3 years programming, 1.5 professionally), but I've found that I'm a BIG fan of refactoring. To me, it's like writing or communicating ideas in general, which I really enjoy. I love taking a complicated idea and trying to explain it in the most simple and readable of terms. It also pushes me to really understand the intent behind the code/text.

To that extent, I enjoy editing and revision much more than creation. So, taking a role as a 'refactorer' actually sounds great!


This is an interesting idea. I've frequently found myself in the slow and methodical camp, but I admire the way in which one of the co-founders at my current job can just throw together some amazing proof of concepts in very little time. Of course, the code they write is in general littered with assumptions, missing error handling, and potential performance problems.

I hope I'll be able to learn that part of it too, but perhaps I am more naturally inclined towards writing the second version of their MVP instead.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: