17 ms·
How I learned to program
- burdalane 10y agoMy programming story: I started with BASIC on an old pocket computer. I typed in games from a manual without really understanding how the code worked. In eighth grade, I programmed a bit in QBASIC in an informal computer class. Then, for years, I didn't program much except for a formula on my TI-82. I never learned the TI-82 programming language well enough to do anything more complex. Towards the end of high school, I got Internet access and learned HTML to build a web page. I took AP Computer Science (in C++) in my senior year and scored 5 on the exam. I majored in computer science at a top math/science university that isn't as well-known for CS as some other schools. I turned down some of the higher ranked CS schools, which was probably a mistake, especially as I wasn't even that interested in the other sciences. I'm more into languages, and I was interested in CS because of its creative and entrepreneurial potential. Fast forward to now: I started programming early and majored in CS, and I can write classes, objects, and functions, but I still don't really "get" programming. My algorithms course in college was all math and proofs that I didn't really understand. I've since gone through algorithm MOOCs and implemented some algorithms, but I still can't really apply them. My work involves some programming, but more of it is Linux administration. (I also don't really get how to deal with hardware because of my problems with anything physical.)
- noelwelsh 10y agoThis was a lot more random than I expected. Very surprised to learn that Dan Luu nearly failed high school, for instance.
- Qworg 10y agoLots of very smart folks do - especially if they can't get courses that match their ability. You end up spending lots of time chasing other things.
- Retr0spectrum 10y agoTo improve readability: document.body.style.maxWidth = "768px"; document.body.style.margin = "auto"; document.body.style.fontSize = "20px"
- kgtm 10y agoI don't think your post was critical of the design, but I wanted to offer some perspective. What I like about sites like this, is that I can adjust them to my needs using a tool I have full control over. The browser allows me to: * Adjust window size or detach tab and resize * Use zoom judiciously * Use my preferred browser reading font Sure, it may not be beautiful, but is surely is functional. I'll also leave this here: http://motherfuckingwebsite.com/ http://motherfuckingwebsite.com/
- Retr0spectrum 10y agoI completely agree. The advantages of sites like these is that just 3 lines of code is enough to tweak it to my preferences. I doubt it would be so simple for sites with mountains of existing CSS. It's also worth noting that Firefox's "reader" mode works perfectly with this site.
- pvdebbe 10y agoThe page is very beautiful in its versatility. No fancy JS hacks to keep pages style: you can use Firefox' reader view for instance. I keep my browser windows around 1000x1000 pixels because the vast majority of sites would otherwise style me overlength lines of text. And it's fine, as long they scale properly and allow narrow browser views. The only criminals are the ones that force wide paragraphs... sometimes to a point I have to vertically scroll a paragraph.
- ZeroGravitas 10y agohttp://bettermotherfuckingwebsite.com/ http://bettermotherfuckingwebsite.com/
- palunon 10y ago
- guard-of-terra 10y ago> We tried BASIC, and could write some simple loops, use conditionals, and print to the screen, but never figured out how to do anything fun or useful. Luckily my BASIC books had most of their examples starting with SCREEN 1. Drawing images programmatically happened to be fun and useful, I learned the hard way by retyping examples and then somehow began modifying those. My own bummer was Windows epoch. I could do VB but never otherwise grasp Windows programming because any program will have so many IDE-generated boilerplate that was totally meaningless to me and I could not work with that. I could only resume when I learned proper WinAPI later as an University course, but then again I switched to Linux, which is a best IDE there is. UPD: meaningLESS
- Cyph0n 10y agoI'm also an EE starting my PhD doing research in hardware/software co-design and circuit design. I'm also heavily interested in CS in general, so I'm planning to take as many CS courses as possible. One thing I'm trying to do is keep myself current when it comes to software development. I think it's good to have a backup skill that I can fall back on in case my PhD doesn't work out. It's good to know that someone like Dan Luu went through ups and downs before getting to where he is now.
- deleted 10y ago[deleted]
- reachtarunhere 10y agoVery interesting read. Especially for someone like me who is on the verge of completing his undergraduate education. I have always feared that life might be too boring in the industry. This provides some fresh perspective. Also thank you for pointing out the downside of reading 50 Manning books. I wish wherever I end up working I manage to carve out time to continue reading and educating myself like you did.
- dcmininni 10y agoTL;DR Naturally talented, hardworking individual downplays everything he has ever done and tries to chock it all up to chance. I found this all very abrasive.
- phillmv 10y ago>Naturally talented is fairly consistent with >chock[s] it all up to chance A little humility does great for ego burns.
- dcmininni 10y agoTrue enough. Given the length of the post and how prevalent the theme of "luck" appears I still find it obnoxious. No doubt there is so much to learn in and around computers that everyone should feel humbled, but this guy should also recognize the mere mortals around him struggling even more so.
- phillmv 10y ago>the mere mortals around him I think I can empathize with your view, now. Your mileage may vary, but as a mere mortal I personally find it much more reassuring when the role of luck is recognized. Too many narratives are akin to: "Well, I worked very hard every day without stop and tho I struggled at first - with how hard I was working - eventually the fruits of my labour yielded this unbroken string of successes thereby reaping my just deserts"
- dcmininni 10y agoAgreed.
- pjc50 10y agoWhat kind of recognition do you want from him? I'm genuinely confused.
- Joof 10y agoMy experience in school seems similar except I didn't get nice math courses until very late on and I was miserably bad at the memorization-based Calculus work (and I still am, but I can do abstract math very well). By then I was pretty disillusioned by school in general. His luck probably helped quite a lot. Nobody really knows what they are good at or what they will enjoy until they do it. Even if it's 'harder' or 'easier'. Having a good mentor is difficult as well; they have to know their stuff, want to teach and mesh well with you.
- collyw 10y ago"I was hesitant about taking the job because the interview was the easiest interview I had at any company, which made me wonder if they had a low hiring bar, and therefore relatively weak engineers. It turns out that, on average, that’s the best group of people I’ve ever worked with." Maybe / quite probably they weren't filtering out ton of false negatives.
- 3pt14159 10y agoThe best people I've ever hired all looked the same: 1. Had a Github with actual code in it. 2. The code was clean, lightly commented, and brief without being terse; regardless of the paradigm. 3. They breezed through the interview because the questions tested their ability to actually build the thing they said they could build. No silly games. A light question that touches on data structures and O time, but nothing you'd need to crack open your old college books over. I feel bad for people starting out, but senior / intermediate devs are just such a better deal. You pay double and you get about four or five times the work.
- brogrammernot 10y agoIn my experience, this holds true as well. I would say though, that you have to keep an open mind when interviewing people just starting out or at that junior level cause there are some really talented, yet raw, developers that you can miss out on otherwise. This is of course assuming you have the bandwidth to help mentor these developers and/or you are okay with less output for the first 6-9 months while they begin to grok what is needed for the job. Overall, I've been bummed lately because I've interviewed CS majors and they have no/poor personal website, basic CS code in Github, and overall don't seem to have that passion that other non CS majors do have. I don't know if it's college that isn't preparing them well enough, but having a personal project or two in Github alongside a decent personal website goes a long way to at least indicate you actually enjoy programming.
- 3pt14159 10y agoYeah, I've learned I suck at managing / growing junior people. I want to be good at it, but I'm not patient enough and I don't like sitting on people. I'm good at the teaching part, I've taught two girlfriends how to code to the point where they are both earning serious money coding. And I'm good at the managing part, I could bring projects to completion that I was proud of and usually on time. But I can't seem to do these two things at the same time. And really, I have zero financial motive to learn how to do so because while you might get the rare wiz kid, usually you don't.
- sitkack 10y agoThis is a wonderful essay that 1) shows its messy work, 2) outlines the deep reward of metacognition. I have a very smart friend who is actually a great writer. But if she doesn't nail the first draft, she gives up saying, "I suck at writing". Writing is rewriting. And similarly, good learning is having grasp at the engine at your disposal through metacognition.
- barry-cotter 10y agoRC = Recurse Centre
- omni 10y agoWhile we're clarifying, it's Recurse Center (insert American flag emoji)
- gravypod 10y ago> The other thing I encountered for the first time at IBM was version control (CVS, unfortunately). Looking back, I find it a bit surprising that not only did I never use version control in any of my classes, but I’d never met any other students who were using version control. My IBM internship was between undergrad and grad school, so I managed to get a B.S. degree without ever using or seeing anyone use version control. I love this bit. This is extremely true even today. Most students at my university, and all of my university's classes, do not use or understand the benefits of a VCS systems. This is crazy on a different level. I hate to say this but it is in fact 2016 and it should not be a question that git or something should be used on every project no matter how small.
- baldfat 10y agoAlso all the time we hear projects lost months / years of code due to a lost laptop. Version control gives you VERSION CONTROL and a backup.
- ng12 10y agoI disagree, except maybe in a class specifically focused on real-world software engineering. Teaching somebody to use git takes an afternoon, teaching somebody to understand programming and computation takes years.
- Nursie 10y agoDevelopment process and software engineering should be part of any good course. At my university we had basic, ffirst year courses covering some practical coding, shell programming and various other sorts of usefuk stuff. I didn't appreciate why version control was so important until later, but at least I knew what it was. Now I consider a department with either no real vcs strategy, or an outdated, cumbersome one to be a huge red flag.
- Joof 10y agoHow would people merge code in a large codebase? Copy / Paste?
- itsmemattchung 10y ago> In retrospect, I should have taken the intro classes, but I didn’t, which left me with huge holes in my knowledge that I didn’t really fill in for nearly a decade After joining industry immediately after high school, I dismissed the value of formal education and selected a major with little consideration (I was unaware that CS even existed). I've recently joined a team where all my colleagues, many who received their degrees from prestigious institutions, majored in C.S. and imposter syndrome haunts me. Many though, are surprised, Although I have my B.S. in information systems, I'm debating whether to return to academia -- obtain a second B.S. in CS or a stretch for a masters in CS (self study the fundamentals, which I'm currently doing, prior to starting the program) -- or continue the self study route to fill the missing gaps in my knowledge.
- clappski 10y agoThe opposite where I work - literally no one has a CS degree, but there's plenty of people who've studied Humanities or the arts.
- retro64 10y agoand imposter syndrome haunts me You’ll get over it. However, you will forever be cursed with having to keep your wiz-kid credentials up to date as you will never have that degree to help wedge the door open for your next opportunity. Ultimately, if programming is what you do (yes, I know CS is not just about coding) it doesn’t really matter, because the rubber meets the road at some point, and either you can code, or you can’t.
- itsmemattchung 10y agoKeeping up with credentials, regardless of having a CS degree, is a life long commitment for everyone in the field - right?
- retro64 10y agoAbsolutely, but when you enter that room for an interview, there may be a bias already built up against you. Somehow you made it through the door, but now you have to overcome the skeptics, maybe a team member who refuses to believe anyone without a formal degree could possibly have the proper foundation for “real work”. You can’t be just good, you have to be outstanding. Even if you shine in the interview, you may still have to make it through an upper manager who did not bother to interview you. Twice I’ve been rejected because the upper management didn’t want anything to do with me, even though the technical team was excited. I was never told exactly why, but I suspected the lack of formal education (what else?). In one case I was offered the position about a month later but already had another job.
- esfandia 10y agoAmazing little essay. I love his intellectual honesty, and his lucid view of his career path. While he claims to have no takeway, I think one obvious one is that, barring disaster, you'll eventually end up where you belong no matter what path you take. You'll leave the bad jobs (maybe later than you should) and you'll get positive reinforcement for things you do well. Every time I've had "career envy", I've tried the alternate path only to discover why I'm really where I currently belong. But I'm glad for those alternate paths, as they gave me that reinforcement I needed. Crazy also how similar our path to learning programming was. Looking back, all those hours of fiddling with BASIC in high school, or with Pascal at school really didn't teach us all that much. Like him, my internships mostly taught me meta-lessons rather than actually valuable skills. Like him, in my education I followed the path of least resistance, or rather the path of "most options left to explore since I have no clue what I want to do", and I feel I'm lucky I ended up where I did. Like him, I fell in love with math way late when I finally saw it wasn't about rote application of arbitrary techniques (abstract algebra is what opened my eyes) like we're taught in school. This sentence, buried deep in the essay, is brilliant: "a common failure mode is that you’re given work that’s a bad fit, and then maybe you don’t do a great job because the work is a bad fit. If you ask for something that’s a better fit, that’s refused (why should you be rewarded with doing something you want when you’re not doing good work, instead you should be punished by having to do more of this thing you don’t like), which causes a spiral that ends in the person leaving or getting fired."
- daveloyall 10y ago> Tavish Armstrong has a great document where he describes > how and when he learned the programming skills he has. I > like this idea because I've found that the paths that > people take to get into programming are much more varied > than stereotypes give credit for, and I think it's useful > to see that there are many possible paths into programming. Okay. Yes that's useful. Let's see what path you took... > Luckily, the internet was relatively young [...] There ya go. Look no further! Mine own story is a little different... The author had local peers, I did not. The author made no mention of an old hand-me-down c64 nor Tandy 1000's in his kindergarten classroom... But, getting online in the mid-nineties? Check. That's huge. TCP/IP was explained to me by some random gamer in a chatroom, long before I ever thought to "google" it. (Speaking of paths... Lycos --> Altavista --> Still Altavista for a long time as I resisted the change to Google --> Google --> DDG)
- CodeMage 10y agoI was reading the "bad stuff" section and I stumbled upon what he said about the Joel Test: The Joel Test is now considered to be obsolete because it awards points for things like "Do you have testers?" and "Do you fix bugs before writing new code?", which aren’t considered best practices by most devs today. Can anyone explain why having testers isn't considered a best practice by most devs today?
- Nursie 10y agoDamn well should be! Lack of test resource is a huge red flag... Devs should be testing their own stuff too, of course.
- enraged_camel 10y ago>>Devs should be testing their own stuff too, of course. Only to check that it's actually working before sending it off to the testers. Unit tests can be a good way to do this. Make no mistake though: a good tester is worth their weight in gold because they will find many "real life" edge cases the developer would not have thought about, as well as UX issues if the feature being tested is user-facing.
- lukeasrodgers 10y agoNot sure, but I believe that part of XP is having devs do more/all of their own testing and getting rid of the developer vs. tester roles (note that this doesn't necessarily mean getting rid of QA), and this aspect of XP is increasingly common. I probably would be disinclined to hire a developer who wanted a different person to write/run their tests, unless it was for a very specialized role and said developer had exceptional talents.
- CodeMage 10y agoSo, it sounds like the only real change is that we don't call QA people "testers" anymore and have a fancier name for them? Kind of like it's gauche to call yourself a programmer nowadays and we're software development engineers instead?
- clifanatic 10y ago> no one’s going to stop you from spending time reading at work or spending time learning What? You've lived a truly blessed life, Dan Luu. I've observed the opposite, pretty consistently. I've been working as a programmer for 25 years and I've found, across nine separate employers (and lost-track-of-how-many different supervisors) that spending any appreciable time reading (even a book about Angular when you're supposed to be learning Angular) will become a management issue. Everywhere I've ever worked has expected learning to be on your own time. Don't believe me? Put "read three chapters of a book" on a status report and see how many levels of management show up at your desk to micromanage your time.
- vogt 10y agoWeird. I have found this to basically never be the case. Even some of the worst managers I've had have supported learning on the clock, through reading materials, tutorials, or otherwise. I've even had some jobs where learning time was a regularly slated part of my work week, and in some cases was allowed to take classes which cut into work a bit. My current employer has a library of technical books and educational material that any of us are free to rent and learn as we go.
- lfowles 10y agoSounds nice. I brought up the concern that learning on the job was frowned upon and was told "that is just keeping yourself marketable, you do that on your own time".
- Ensorceled 10y agoNot sure why you're being down voted since places like this exist ... I know because I've worked at them.
- lfowles 10y agoOT: How are you able to tell I'm being downvoted?
- iammyIP 10y agoOne way to learn to program is the urge to teach the machine some principle you might find nice to be realised by a machine. Some things are opposed to entropy, some things are there to create order (always with a net gain in entropy, but nonetheless). Therefore, the machines and us seem to be on the same side of nature. Even the whole ecosystem of the planet is a miraculous emergence of high level structure. So you learn to program, if you want to program some. Print that on the next calendar.