Hacker News new | past | comments | ask | show | jobs | submit login

You're really overstating how hard it is to learn to program.

I'm a woman who studied physics and astronomy at university. In my final year I taught myself programming in my spare time because I was interested in it, and knew the job prospects were better than in physics. I had other hobbies and an active dating life at the time, but I still managed to get a software job straight out of university, and it's evolving into a fruitful career.

Learning to program in no way requires 3 years of monastic devotion.




Function, parameters, modules, classes, objects, variables, interface, co and contravariance, structs, union... Functional programming, database (data normalization, SQL, no-sql), OS stuffs (process, scheduling, virtual memory), virtual machines, linkers and loaders, compilation, interpretation, compilers (language theory & implementation), HTML et al., networks (ip addressing, domain name, socket), software architecture, design patterns, security issues, memory management, IPC, containers, deployment, CI, encoding (Unicode, UTF8, ASCII), IO, various file formats... List, tree (binary, balanced, implementation), hashset, graph, stack, FIFO. Back-end, mobile, windowed app, game... etc, etc.

I see there is a lot of genius in this thread, having come across all these concepts and got a working understanding of all these things in a few weeks/months. I'm 10 years in and I still learn weekly. Either Dunning–Kruger is in full effect or you internalized so many thing you don't see them anymore.


Yeah, this is pretty much my thoughts as well. Even aside from the large range of topics out there, there's a massive gap from "can do something useful" to "can program well / in a maintainable way".

One of my dormmates in college was in some engineering degree, I forget what, and decided to learn some programming from us, since so many of us were in CS. It was a pretty short time before he could do useful things, actually helping him finish his projects faster, but all that took was some very basic concepts: arrays, loops, conditionals. I think on the order of a week to get the concepts down and be able to write a C program from scratch, and another week or two before he had the concepts embedded in his mind enough to use it with his own work.

Thing is, even that was far faster than I typically saw for those same concepts, as a Teacher's Assistant for the introductory CS courses. The engineering mindset seemed to give him some sort of foundation to pick it up faster, even having never done it before.

And his code was absolutely terrible, he had a long, long way to go if he ever wanted to even consider programming as a profession.




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

Search: