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

I very much enjoy working as a programmer, but, to be honest, there is constantly a little anxiety in the back of my mind that I do not get FP/docker/devops/insert-latest-buzzword-here enough not to look like a clueless coder in a watercooler-side chat with a fellow. So I really appreciated this article, it made me feel better about myself :-)


So what are you going to do about it?

I was formally educated to do low level development, did operating systems, hardware design, and communications for a living for 15 years. During that time I also learned and regularly used FP, data processing, windows GUI, full stack web development. Every year I pick a new tooling language so that I'm not completely tied to one language or paradigm. Every time I have an opportunity to use the right language or tool for the job I learn it and use it.

The whole point of my education process was not to learn C and Assembly, it was to motivate me to he constantly learning. When I wanted a new job I created a "real world problem" to solve, did actual design docs, took courses online, read books, etc. Was able to get a new job in a completely different field, doubling my pay and reducing my work load. That's all due to the fact that if I had a list of stuff I didnt know I'd be out there learning that stuff every waking minute.


Do not get me wrong, I am learning constantly and like it that way (now I go through a Haskell textbook and have a few MOOCs in my to-do list), but the thing is, I feel like I am still fighting a losing battle; there is just too many new information out there to understand everything. That is the source of anxiety for me.


It’s deeper than that - you won’t just look like a “clueless coder”, you’ll find yourself unemployable. I learned early on that it doesn’t matter what credentials you have or how much experience you have, never admit there’s anything you don’t know, or they’ll pass on you to hire somebody else who confidently insists that he does know absolutely every single thing there is to know. I feel bad for the author of this piece, because putting his name to this _will_ cost him employment at some point in the future.


This is honestly the most ridiculous thing I've ever heard. You think it's acceptable to never admit that you don't know something? You're advising people to pretend to know everything?

I would immediately try to get you fired for lying about your knowledge and qualifications.

One of the best possible things you can do is admit when you don't know something. That should always be safe to do at any GOOD employer.


Interview is over as soon as I find you pretending you know something you don't. Do you really think you're going to trick me when I have literally decades of programming experience? The person hiring you will often be your mentor. Start out on the right foot by trusting them and showing them you can be trusted.


The author created the key state management tool for one of the world's most used front end libraries - I think he's gonna be ok!


The idea of Dan Abramov having trouble finding employment is beyond comical.


Well, I hope so - the author of Homebrew ended up having trouble finding employment: https://twitter.com/mxcl/status/608682016205344768. Stranger things have happened.


Getting rejected from a single company does not constitute having trouble finding employment.


I've gotten hired or an offer several times admitting I don't know something. I don't think I'm an exception




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

Search: