4 ms·

I disagree. Production code has to deal with anomalies and failure in a graceful way that allows recovery and identification of the fault. That's not somethin

I disagree. Production code has to deal with anomalies and failure in a graceful way that allows recovery and identification of the fault. That's not something that's taught in academia at any level, perversely. And it takes time to learn how to use software tools effectively in a standard way in a production environment that others can understand and extend and maintain. This isn't taught in academia either, and usually it takes several years in the real world for these skills to mature and integrate into the practice of writing good pro code. A PhD offers no advantage in this school of hard knocks.

stirfrykitty 8y ago
You said this better than I did below. You are right. I emerged from college an eager guy who went straight into a production environment. First gig? "Oh, we see you have Perl, awk, sed, Bash on your CV.. We need you to write some code to get this and that data from the server logs and then spit it out in this and that format, but we don't want this particular info." I about crapped myself the first day on the job. Fortunately, my team lead knew what he had asked for and coached me through how to be a useful nix admin. This led me to being more interested in coding than setting up nix boxes and getting them to talk to databases. I fell in love with regex stuff and still love it. Perl and Python are still my go-tos with regards to this. I still write small (25-30 line) programs in awk. Sadly, I have a job now where they all love PowerShell, so I've been "forced" to use it for certain Windows tooling tasks. Learning Go on my own now. I find R and F# fascinating and might take this on in time.
walshemj 8y ago
As opposed to some one fresh from a BSc who got through the interview by rote memorisation who will be just as clueless.
- umvi 8y ago
  Well at least with them you can pay them an entry level salary without looking bad.
deleted 8y ago
[deleted]

stirfrykitty 8y ago

You said this better than I did below. You are right. I emerged from college an eager guy who went straight into a production environment. First gig? "Oh, we see you have Perl, awk, sed, Bash on your CV.. We need you to write some code to get this and that data from the server logs and then spit it out in this and that format, but we don't want this particular info." I about crapped myself the first day on the job. Fortunately, my team lead knew what he had asked for and coached me through how to be a useful nix admin. This led me to being more interested in coding than setting up nix boxes and getting them to talk to databases. I fell in love with regex stuff and still love it. Perl and Python are still my go-tos with regards to this. I still write small (25-30 line) programs in awk. Sadly, I have a job now where they all love PowerShell, so I've been "forced" to use it for certain Windows tooling tasks. Learning Go on my own now. I find R and F# fascinating and might take this on in time.

walshemj 8y ago

As opposed to some one fresh from a BSc who got through the interview by rote memorisation who will be just as clueless.

umvi 8y ago
Well at least with them you can pay them an entry level salary without looking bad.

deleted 8y ago

[deleted]