|
It's pretty obvious that in a scientific field, without passion, rigor won't find itself. This article reeks of immaturity. And I'd rather have only passionate people in our field. Most coders who only go through a CS degree as oppose to elementary-highschool-life and beyond coders, there's just a huge wall of difference in terms of understanding down from the cpu to tcp networking, across to asm, endianess, etc etc. New coders just never really get it. It's like trying to learn chess at an older age, 90% of grandmasters were grandmasters by the age of around 13. I learned coding because I wanted to tear shit up as a somewhat dark child. And that's why I know pretty much everything from databases to reverse engineering to packet sniffing/editing to patching, injecting, loaders, class modification, obfuscation and deobfuscation, and XSRF, RCE, shellcode, buffer overflowing, the list goes on. Along with whatever it takes for an interesting programming job. New coders just don't get it, they are too far outside the scope of (played around with it as a child, because it was interesting.) Money isn't a good enough motivator to teach grubbers the real internals of a machine. |
I'm all for talented, experienced people in our field, but I think we also need a healthy work-life balance. If someone wants to work 60 hours a week then spend 20 hours a week on their open source side project because they're passionate about coding, that's their choice - but if someone else wants to work 40 hours a week then turn off the computer and spend time with their children, I don't see that as a problem or something they should be ashamed of.
And if my boss stopped paying me, you can bet I'd stop coming into work. If that means I'm in it for the money, then I'm in it for the money.