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

The first (only?) comment on the blog hits on an important point: I know lots of technical people who don't code. These people build networks, configure racks of equipment, and generally keep data centers running smoothly ... and couldn't code their way out of a SIGTRAP. (Contrary to this, I've met plenty of non-technical people who "repair" PCs and know how to click the UI of the latest malware removal tool.)

I understand that the target audience is the MBA who thinks that since he bought a laptop last week, he's now "technical," but it's an important distinction when your story is read by a bunch of technical geeks.

<rant>Proofread your blog posts. This is why your blogging software allows you to create drafts - dump your rage into the editor and save the draft. Come back later after you've cooled down and fix your grammatical and spelling errors. Also, don't forget to pay some attention to organization.</rant>



It makes even less sense in other areas of engineering. I'm a computer scientist and can code, but it would be absurd for me to claim that, if I collaborate with a chemical engineer or mathematician who can't code, that person isn't "technical". It's getting increasingly useful to know how to do at least basic programming all across the sciences and engineering, but there are lots of other technical skills as well, mathematical skill being a big one. Even at tech companies, a statistics wizard who can write only basic code (say, simple R scripts) but knows the underlying theory and practice very deeply would certainly be a "technical" employee, for reasons other than their rudimentary coding ability.




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

Search: