| |
 |
gax
|
|
| Total Posts: 22 |
| Joined: Apr 2011 |
| |
|
| The main skill a good programmer needs is the ability to narrow in on exactly where you need to make that one line change in a 500K+ line code base. And then be 100% sure you haven't messed anything up. |
|
|
 |
AB12358
|
|
| Total Posts: 63 |
| Joined: Apr 2014 |
| |
|
Oh man.
I once spent 200+ hours digging through a mix of 40 year old Fortran and C looking for a bug, only for it to be a single character typo in what I'd thought was an unrelated part of the code (Yb instead of Ya or somesuch). Typo was causing an overflow in Yb, leading to intermittent errors in part of the code that relied on the next bit of shared memory.
The main trait a professional programmer needs to have is pragmatism, the main skill is writing readable code with helpful comments. |
|
|
|
|
sigterm
|
|
| Total Posts: 10 |
| Joined: Jul 2017 |
| |
|
"Answering my own question: compilers, operating systems, and network programming. Not SICP, FP, OOP, or monads."
The SICP/FP people have a good claim on the compiler territory. Filter out the too theoretical and they are enlightening.
As for operating systems, I'm going to shill for xv6: https://pdos.csail.mit.edu/6.828/2012/xv6.html .
Programming Pearls by Jon Bentley could pass for an ancestor to aosabook.org. |
|
|
|
