11 ms·
How to become a programmer, or the art of Googling well
- devnonymous 12y agoThis, for me was a bit surreal and strange, because it took a long while for me to arrive at the same conclusion but from the complete opposite end. I came to computers from electronics and for me, Data Structures and Algorithms was (to an extent, still is) black magic with Don Knuth the presiding head wizard. For me, compilers, filesystems and OS internals were all sort of deep dark places that I wasn't equipped to handle. On the other hand, banging out a shell script, spewing perl, or reciting python was just a matter of figuring out the right set of incantations ...not really hard. I learned html, css, js, a lot of python and was (/am) happy to just 'get-things-done' with these skills. I looked at people who could talk about BigO, concurrency, monads and the rest as the 'privileged' -- I could never be /that/ good. And yes, I thought all of this was relevant to software engineering (as opposed to science) and that I would never get there. Fortunately, I no longer think this. Thanks to all the resources available online these days, the limits, I know now, are not inherent nor are imposed by ability to understand, they are imposed simply by time for learning and practice. So, I am still learning and yes, in that sense, the art of googling well can make you a better programmer -- irrespective of what you know today.
- meowface 12y agoI'm in a similar boat. I majored in "Information Systems" which was practically a glorified business degree with some IT, networking, and a tiny bit of programming thrown in. I was able to pick up comp sci fundamentals from various awesome online tutorials and even just good old Wikipedia.
- sanxiyn 12y agoThis is very true, but it's a bit more complicated than that. "I'd come to understand that the answer was out there, somewhere." The answer is out there, but so is the wrong answer. Recognizing the right answer is the hard part. I also must point out that the answer is out there if you know English. Knowing English is a strong privilege. Success rate plummets if you Google programming questions in a language other than English.
- yen223 12y agoThis is something I've always wondered - how do programmers who don't natively speak, read, or write English cope with the sheer amount of literature they have to parse to have a career programming?
- sanxiyn 12y agoI don't natively speak, read, or write English. Speaking for myself, you cope by studying English. Blood, toil, tears, and sweat are involved.
- yen223 12y agoFor what it's worth, your English is pretty good.
- aerovistae 12y ago...uh...seems to have paid off well for you.
- bdcravens 12y agoBased on the limited sample, you write it better than many "native" speakers.
- gone35 12y agoI don't natively speak, read, or write English. Damn. I wish I could show your comment to people like John Searle.
- Tehnix 12y agoVery easily. But that might be because in Denmark, it's rather the exception than the norm that people don't know english. Of course with varying degrees of proficiency.
- rdeboo 12y agoIn my country (Netherlands) people speak English quite well. My entire (CS) master was in English. So that means literature, class, assignments, exams, everything. I must say it did feel kind of awkward sometimes if you sit in a class where every single student and the teacher is native Dutch speaker, and still the course has to be done in English. But I think in the end it is worth it, because you learn all the terminology in English. Actually it is funny, I only realized while reading this discussion that I always google my programming questions in English. It never occurred to me do google them in Dutch. I will try it today to see the results :)
- ayrx 12y agoI'll argue that good programmers need to have a working understanding of algorithms, databases, compilers and all that. Sure, it's not something you will use day-to-day in a software engineering job but it's important to know how all the low level pieces of your stack fit together in order to write good code. There's nothing worse than a programmer that fits together code snippets from Stackoverflow and similar sites without understanding what it is actually doing.
- bdcravens 12y agoI think it's fair to say that you can be effective without necessarily being good and vice versa. I think the some of the best developers are those who are smart enough to have gotten a CS degree but skipped a bit of the academics. (A bit self serving: I graduated high school in 1996, had my first intro IT job by the fall of 1998, and had my first real programming job in January 2000, while my contemporaries were still in college)
- jjoonathan 12y agoEveryone overvalues education similar to their own and undervalues education dissimilar to their own.
- outrightfree 12y agoEveryone generalises too much.
- tux3 12y agoBest 4 words I've read today.
- nevergotenglish 12y agoThe general conclusion is that you haven't read much today.
- grecy 12y agoI currently work with a bunch of people who are "business majors" or whatever and are similarly self-taught in the Tech/IT/Programming space. It's interesting to watch how they work and the kinds of outputs they produce. Quite a lot of the stuff works... mostly... It's entirely untestable, not repeatable, undocumented and just stuck together with flaky glue code. Sure, if you aiming to "make it work" you can do that. If you're aiming to do well... I suggest learning proper technique.
- bdcravens 12y agoI think it's a mindset thing; either you have the mind of a developer or you don't, degree or not. I'm self-taught, and early on I had a inferiority complex when it came to those with CS degrees. Didn't take long for that to wear off as reality exposed gaps in their ability/knowledge.
- grecy 12y agoFair enough. I have a Software Engineering degree (certified Engineer), so I already have a superiority complex anyway ;)
- Tehnix 12y agoExcept for maybe Haskell[0] and Lisp[0], I've begun to feel like there isn't any language that I can't quickly learn with how I'm able to google at the moment. For example, I'm currently helping some fellow students with their F# assignments, even though I don't do F# at all. I just know what to google, because I know the concepts that I need translated to the specific syntax. [0] Maybe Lisp, but Haskell is way too different from other languages in the way to programme. I'm currently learning it, but it's by far the language that has taken me the longest.
- brudgers 12y agoTake a look at APL. There will be three.
- checker659 12y agoProlog, and there'll most likely be four.
- aerique 12y agoI think there's only two and Lisp doesn't need to be on that list, but maybe I say that because I've been using Common Lisp for so long. Lisp ought to be easy since all you basically have to learn is: "(function parameter1 ... parameterN)". Coming from Lisp I've been trying to learn some Haskell and holy cow syntax[1]! There's a lot to parse and know (compared to Lisp) before being able to write a small program. [1] I know it is not literally syntax but mostly function calls, it's still a lot of extra special characters one needs to know about.
- girvo 12y agoOr J, and related languages. Crazy stuff, but apparently super productive once you're used to them.
- jeffwass 12y agoCurious if you've also tried Forth?
- 12y ago
- Kenji 12y ago"But I’d never even heard of the words front-end developer or full-stack. What was Heroku? Never heard of Xcode. Wasn’t git just the thing you used to make sure your partner had access to the code you’d written? Frameworks? Didn’t you just need HTML and Javascript? What the hell was an API?!" If you literally never heard about any of those during your computer science courses, you attended a sad, sad university.
- deleted 12y ago[deleted]
- eru 12y agoOr you went to university a decade or two earlier?
- Wilya 12y agoApart from HTML/Javascript, which is usually taught in a web development course, most of these aren't taught in usual computer science courses because they have nothing to do with computer science. They are software engineering concepts.
- Kenji 12y agoI am well aware of that, being a CS student myself. However, those things are expected to be learned alongside. There won't be lectures about it but hand-on exercises will be impossible without them.
- joslin01 12y agoLol that's not true either. How would hands-on exercises be impossible without Heroku? Haha. You know what I did in my CS classes? Wrote my own server in C. That's real CS, which is very focused on deep understanding -- not domain knowledge in software tools. You should ditch the attitude. Your first comment wasn't even necessary. You were just looking to feel good about yourself.
- 12y ago
- mapcars 12y ago>Some Small Advice: if you’re just beginning to program, I’d suggest starting with JavaScript/HTML/CSS because there is a plethora of help out there. What a terrible advice.
- sanxiyn 12y agoWhy is it a terrible advice?
- stonewhite 12y agoBecause programming != web programming, and sure as hell HTML/CSS is not programming. About javascript(vanilla js), nobody even wants touch it anymore. Almost anybody who interacts with javascript code does it with a 5 foot stick(coffescript, clojurescript), and/or behind huge frameworks that protects you from its perils. Something that is more usable and understandable in its barebones state like python makes more sense for beginners.
- sehr 12y agoI think you're severely overestimating the number of people who use a compile to language
- stonewhite 12y agoI do agree it was a hyperbole.
- BonsaiDen 12y agoVanilla JS is perfectly fine and there are a ton of people out there who are using it every day on a highly professional level. There is a huge amount of tooling these days and specially the Node.js community and ecosystem are flourishing. Code coverage, static analysis, test frameworks for every use case imaginable, you name it. Coffeescript and its brethren are a "solution" for people who are not interested in JavaScript and don't care about performance / maintainability in the long term. The additional compile step and the resulting problems with not being able to know exactly what it ends up generating become a huge burden in the long run. If you're really good in JS, you know what we'll be JIT'ted and what not, just like a really good C++ developer knows what the compiler will eventually optimize away and what not. Seriously, building your cool, new library in <Insert Fancy New Compile to JS Language here> is like writing the latest addition to Boost in C89. Nobody wants to depend on it in the long run. From what I have seen, the people who are mainly using things like Coffeescript are coming from Ruby or Python and want their cool-aid back. If you don't want to learn a language, don't use it and if that means you won't be able to do stuff on the web, well I'm totally fine with that. I've seen enough code that looked like a J2EE developer just started coding C the other day.
- bpizzi 12y agoMy 2cents. Don't be fooled by this false sense of know-how when you just start being able to write some html/js stuff. Googling a problem is a reflex when you start coding, and yes, good or bad googling abilities could be the difference between you still being in the industry in 5 years or not. But, still, this is only a first step on your path, and stopping there will also stop you from being a real hacker. There are things that just can't be resolved with a single search: "How to center a div in CSS" is not like "How to share load across different servers", because a big question must be divided into a lot a smaller ones, and there comes the difference between you and your "code-god compatriot". So the real path looks more like this: 1- read good literature (CS, functionnal programming, network, etc), 2- exercise, 3- read good code, 4- exercise, 5- goto 1. Anyhow, best of luck at Google ;)
- collyw 12y agoI started learning in 2000, before Google was big and Stack Oveflow didn't exist. I think every new programmer gets a false sense of how easy everything is. 14 years of learning later, I now realize how little I know.
- coldcode 12y agoI started coding in high school in 1973 and professionally in 1981 with no benefit of any classes (other than the one in high school). Believe me I prefer to live in the modern age where your knowledge is expanded by the world's collective brains. In the "old days" you only had your own brain and limited library books and periodicals and maybe a good buddy. It was much harder than today to do anything you didn't already know but we didn't know any other way. Today it's much easier to find information, get ideas and opinions. I even use Google to find method names in iOS documentation (Xcode's sucks). But you still need to be able to understand what you read, decide if it is relevant, and how to apply it. Those things you can't just learn from Google fu, it takes experience, trial and error, and a willingness to recognize when you are wrong.
- JacksonGariety 12y agoLearning to “google well” has become the fundamental skill to replace reading/writing well in life. Scary.
- fhadley 12y agoI found that one particular phrase,"technically privileged", both hilarious and utterly horrifying. Hilarious because I suppose I never paused to consider that the folks in my major who were both curious and motivated enough to be involved in the field outside of class to be particularly "privileged". I suppose I should have given greater thought to how unfair it was that read API documents and I didn't! Like I said though, it wasn't just good times and passive aggressive complaining about first world problems while I read this. I can't even begin to fathom the miserable, pathetic, and generally small, unexamined existence that would lead one to believe that h(s)e is somehow the victim of deep injustice at the hands of those people with their prejudiced technical abilities and natural curiosity! How dare they not level the playing field just because she never bothered to explore the use of code outside the classroom; clearly everyone missed that she's the subjugated one, with a comfortable liberal arts education and regular internet access. But still, we should all take a moment to recognize the plight of the comfortable, generally satisfactory lives of those among us struggling silently with the burden of "technical un-privilege."
- cushychicken 12y agoWhat an uncharitable response to someone who had a legitimate revelation and used it as a catalyst for personal growth! Software development is intimidating to outsiders - of course it's a privilege to be on the inside. (Or at least it appears that way.) This isn't a complaint about an unlevel playing field - it's an awakening on how to get better at doing something you love.
- penprog 12y agoWhat does it even mean to be on the inside? Nobody in my family had any experience with computers. My first programming book was a gift for me when I was ten that I asked for (it was a learn C++ in 24 hours book). You can imagine how that turned out with nobody there to help me. I didn't understand what variables were let alone how to add the compiler to the path on windows. The only help I had was that my dad bought me the book and I had a family computer in the living room. Am I on the inside?
- CmonDev 12y agoGoogle is your remote long term memory. Why wouldn't you use your long term memory? Sooner or later our brains will be modified to make the round-trip of entering request and getting a result much shorter and the difference will disappear.
- russgray 12y agoOver time I have come to the conclusion that one of the best ways to identify a really interesting problem is when your attempts to google a solution come up blank. Google doesn't have all the answers, and if it becomes literally your only mechanism for moving forward you will hit a wall sooner or later.
- touristtam 12y agothis just reminds me of the Expert Beginner: http://www.daedtech.com/how-developers-stop-learning-rise-of-the-expert-beginner http://www.daedtech.com/how-developers-stop-learning-rise-of...
- WBrentWilliams 12y agoThis was fun to read. What I saw was someone say that they were panicking because they needed time to understand how all the things that go into learning to be a researcher goes into learning how to be a professional programmer. I'm quite sure his mind will be blown once he realizes that creating things, while incredibly rewarding, is only half the work. The other half is getting someone else to use your widget. Also (bad at math joke), there's an extra 50% involved in getting attribution. My take? I'm biased because I was educated as a researcher. I can name-drop three famous professors at my alma mater (and yes, I did study under all three), but what really pushed me was getting a job, on campus, writing software to support PhD candidates in another discipline. I quickly made the jump from researcher to practicum precisely because I was trained as a researcher, then applied those skills to understanding what my customers needed. Seems to me this guy found his own "push". And yet, he's still a researcher.
- sanxiyn 12y agoFYI, the author is not male.
- enraged_camel 12y ago>>but what really pushed me was getting a job, on campus, writing software to support PhD candidates in another discipline. I quickly made the jump from researcher to practicum precisely because I was trained as a researcher, then applied those skills to understanding what my customers needed. I think what allowed you to make that jump was that you were inherently familiar with the problem domain; even though your customers did research in another discipline, at the end of the day they were still researchers. I was the lead trainer at my company, and the training materials (hundreds of pages of them) used to be on Word documents. I got fed up with it, taught myself Rails, developed and deployed a learning management system, and migrated the content there. It was very successful because as the lead trainer, I knew exactly what features would be needed and how they should work. It was kind of funny actually because when I gave a demo to the trainers in other teams, they basically said, "wow, this is exactly what we need -- when can we start using it?" Which is music to any programmer's ears.
- atmosx 12y agoHm this can go the other way around too: You don't realise how hard is something and how far and away some people are, until you start programming[1]. Same goes for other sciences/sports/whatever. http://xkcd.com/1425/ http://xkcd.com/1425/
- gtirloni 12y ago* But a liberal arts CS major prepares you for a career in computer science research, which is completely different from, say, software engineering. It’s like comparing a physical therapist with an athlete Kind of funny that software engineering is compared to an athlete. In the current situation, I'd compare it with a headless chicken.
- elemenofi 12y agoI feel the opposite. I am a self-taught full stack programmer and yet I wish I had some sort of degree to pursue research as a career.
- unclesaamm 12y agoIt seems like the skill in question isn't necessarily about becoming a programmer as it is about becoming a hacker. It's a fine line, but I think the skills you learn at Google will be much more programmer-esque, like code review, unit testing, and doodling on whiteboards :). Whereas I see deploying APIs in weekends to get things off Craigslist to be in the domain of hacker-ish things, what someone else already called "hobbyist". I think that's an important and subtle flag for career prospects, so the line isn't that clear, though. Another point I get from this is both a critique and praise for CS learned in a liberal arts college. You felt unqualified for getting a software engineering job, which is something that really needs to be addressed in small LACs. On the other hand, academic rigor probably prepared you well for cutting through bullshit that surrounds fashionable technologies. For example, you may not have heard of Heroku, but you may have learned about networking protocols and virtualization, which I think is the harder part to learn. I think you struck a good community by choosing web development (a bit biased), but I'd like to amend that with a word for the road not taken, which is that back-end programming is becoming really, really accessible as well. Tutorials for Flask, Node, and Rails are just as prevalent (and potentially misleading) as HTML tutorials of yore. Now anyone with a mac (and even windows! would you believe that!) can set up a server and push "hello world" to heroku. Anyway, I'm looking forward to seeing "How to become a Googler, or the art of ????? well". I don't know what ???? is but I imagine it involves a lot of frustrated inability to Google things :)
- dobbsbob 12y agoOr google 'what books should I read to become a programmer' http://matt.might.net/articles/what-cs-majors-should-know/ http://matt.might.net/articles/what-cs-majors-should-know/
- thisjepisje 12y agoIn my mind I am pronouncing the italicized words with an Italian accent.
- jchmura 12y agoI thought this was going to be something bashing programmers by the nature of the title. Glad I was wrong. Great story and something that all aspiring programmers should stick to.
- sbierwagen 12y agoThe first time I met him, he was in the middle of writing a script to scrape Craigslist of all its free furniture listings (which is illegal, btw). It's a violation of the Craigslist TOS, a contract between two citizens, so it would be covered under civil law, not criminal. A creative prosecutors could try to spin it as a crime under the CFAA, (http://en.wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act http://en.wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act) and there in fact have been CFAA prosecutions for scraping Craigslist listings, (http://en.wikipedia.org/wiki/Craigslist_v._3Taps http://en.wikipedia.org/wiki/Craigslist_v._3Taps) but I doubt there's much a case here.
- jElais 12y agoThis would fall under US v Drew (http://www.dmlp.org/threats/united-states-v-drew http://www.dmlp.org/threats/united-states-v-drew). A case where someone violated the MySpace TOS and then was charged under the CFAA. The Judge ruled this was not a violation citing the void-for-vaguness doctrine and not wanting to give the power to right federal laws to websites.
- plicense 12y agoSo the OP used Google to get a job at well, Google.
- rpdillon 12y agoGoogling well is very helpful in filling in gaps in your knowledge that are widely known by others. For most (?) software engineering jobs, that's probably enough. Writing some code that works, though, doesn't forward the state of the art. I was lucky enough to take AP computer science in high school. I remember arguing with the teacher when she criticized my code in front of the class. I said something along the lines of "Well, it runs and produces the right output!" She then lit into me, explaining that the structure of the code, its readability and maintainability were at least as important as its output. I've carried that lesson with me in the 19 years since, and had in reinforced multiple times over. The art of "Googling well" won't teach you good abstraction and maintainability, and yet I would argue it is one difference between junior engineers and (good) senior engineers. We talk about learning all these frameworks, but that's not nearly as useful as developing the skills to create the next powerful abstraction to make a class of hard or time-consuming problems easier or faster to solve. You won't learn how to do that on Stack Overflow.
- fibbery 12y agoDo you have any thoughts on how a junior engineer can improve their ability to write maintainable code? This is the main problem I struggle with as a self-taught developer. I can write code that works for the most part thanks to googling all the things, but my projects tend to turn to spaghetti the longer I work on them, and are greek to me when I return to them in 6 months. Part of the issue is that it's much more rewarding to add a new shiny feature than it is to refactor the existing mess, but another part is I'm not really sure what goes where. Most online courses targeted at inexperienced programmers teach x feature of y programming language, instead of practical software engineering... as a result I feel like I've learned how to build a fancy stained glass door for a house that has an unstable foundation. I've often thought I'd like to hire a senior dev to sit with me and help me work through building an app the 'correct' way... but short of that I'd love to know of any books or web resources that would help.
- yid 12y ago> Do you have any thoughts on how a junior engineer can improve their ability to write maintainable code? Think of your code like an essay. Write comments on the motivation for decisions you make, not just what the codes does. Think of the exercise not as trying to just produce writing code, but to make the next person reading the code feel like they were with you the whole way, making decisions together, working out problems on a whiteboard. While doing this, don't be afraid of honesty, don't be afraid of verbosity, and always have empathy for the next person reading your code.
- mattfrommars 12y agoWow, the guy is exactly me when he graduated college and in winter he started panicking. Pretty good in Googling too lol Graduated with a degree in Mechanical Engineering this year summer and unemployed since. Winter now, panicking. Learning web Development in hope of getting into something. Strange how similar his and my path are up to winter. Time will tell where I end up.