23 ms·
The grief factor of learning to code is on a different scale to every other major. One missing semicolon will take your whole tower down, and you realise this i
by lordnacho 9y ago
The grief factor of learning to code is on a different scale to every other major. One missing semicolon will take your whole tower down, and you realise this in the first day of practical exercises.
Even if you are of the opinion that CS is math, and coding doesn't come into it, you will hit a coding wall early on.
In fact, every exercise in CS has this problem. You add a new thing (eg inheritance), and it breaks. But not only that, it might be broken because of a banal little syntax problem.
And that's just what you consider code. If you put in the wrong compiler flags, it breaks. If you can't link because something needed rebuilding, it breaks. Want to avoid it? Learn how make works. Huge number of options, which you won't understand, because you're a novice.
Oh and learn git, too. And Linux. Just so you can hand in the homework.
Compare this to the rest of university. I'll use my own experience.
- Engineering subjects tend to revolve around a small number of vignettes. Here's an aircraft engine in thermo. Draw some boundaries, apply some equations. If you get it wrong, your tutor can still see if you were going the right way. Once you've learned the relevant points, it's not hard doing some rearrangements and plugging in some numbers.
- Economics essays are basically bullet points. Miss one out, you still have an essay. Which you can hand in without knowing git.
- adrianratnapala 9y agoAll this is true, and yet when I was a young'un, Engineering had a plenty high dropout rate. Higher than CS I think.
- madengr 9y agoYep, 66% or more dropped out.
- Kenji 9y agoFor me, maths was a much bigger stepping stone than programming. When I came to uni, I was basically already equipped with most of the programming knowledge I needed to enter the workforce. I learned it quickly and easily. But maths - man, that's a different monster. It's one thing to see that you missed a semicolon, another to understand what singular value decomposition and principal component analysis and Stoke's theorem mean.
- plafl 9y agoAnd my own experience is that I learned coding and using Linux on my free time several years before entering college, where I studied engineering, which required no little effort. Programming is hard, I'm not denying it, but so is everything else if you plan to get paid doing it.
- kutkloon7 9y agoIn my experience it is much more stressful and hard to learn these things for a course, because you're not interested in them but HAVE to use them in order to do something (e.g. hand in your assignment with git). Now I'm looking at git again in my free time it's a pretty nice tool, and I can't imagine that I loathed it so much when I had to use it for a course.
- ooqr 9y agoIt's great that this was part of an assignment. Git is a fantastic, incredible tool. Along with testing, it's one of the skills I figure is just as important as the things you learn in university, but which typically isn't taught there.
- kutkloon7 9y agoNo, everybody hated it. I didn't learn git. There was a weekly assignment, and I ended up mailing the TA every other week at the day of the deadline because I broke the repository again (thankfully, he was very understanding and helpful). Maybe this is a consequence of how the assignments were structured. I don't remember exactly, but there was no introduction and the workflow was not the typical add, commit, push one.
- erikbye 9y agoIt's incredulous how people can find git daunting; especially the simple usage most make of it. Yet, I constantly see people refer to such simple and easy to use CLI tools as an obstactle in CS courses, not a helpful tool. Welcome to the fulfilled prophecy of the movie Idiocracy. This is why MIT had to stop teaching SICP and why many courses uses Java instead of C... Good luck learning pointers and assembly then. Good luck ever knowing how to create and manipulate data structures, how to create a filesystem, database, OS, scheduler, etc; or how to develop/improve and implement algorithms used in ML and AI (to be fair, this is math... and which is why programmers need to stop avoiding math, it's another issue, but related. stop avoiding complexity, because it's a fucking big and scary monster lurking beneath everything you're working with, just waiting in the dark...) What we need is people who understand the complexity we constantly throw more shit on top of; it's only going to get worse the more data points and networking we have to deal with. Pretty soon we're going to have a massive network of autonomous vehicles on physical, country-spanning networks of roads. For this we need systems people. Not front-end developers. The sad thing is that most programmers are absolutely useless when shit hits the fan.
- watwut 9y ago> The grief factor of learning to code is on a different scale to every other major. One missing semicolon will take your whole tower down, and you realise this in the first day of practical exercises. I would say that this basically screams "badly taught programming". Missing semicolon does not take down work, it just needs to be put back in and ide should help you. "Even if you are of the opinion that CS is math, and coding doesn't come into it, you will hit a coding wall early on." I mean it seriously, programming is easier then math. I am telling that as someone who always liked math. "And that's just what you consider code. If you put in the wrong compiler flags, it breaks. If you can't link because something needed rebuilding, it breaks. Want to avoid it? Learn how make works. Huge number of options, which you won't understand, because you're a novice." This is not something novice should be dealing with. "Oh and learn git, too. And Linux. Just so you can hand in the homework." As I told, badly taught programming that takes in people who know nothing and then proceed as if they already learned stuff in the past.
- Legion 9y ago> I would say that this basically screams "badly taught programming". Missing semicolon does not take down work, it just needs to be put back in and ide should help you. The point is that the incidental complexity is there, and that it's something that has to be dealt with, to even begin to get to the fundamental part of the problem. That you have to be using the right IDE (and learn how to use it, and learn to recognize it's attempts at helping you with the problem) does not refute the point, it's a perfect illustration of it. CS isn't harder. CS has high incidental complexity, the crap you have to deal with just to be able to work on the problem within a real world environment.
- jrochkind1 9y agoAnd yet I had zero problem learning Logo when I was like 10 years old. Neither did _most_ of the other 10-year-olds in the class. They didn't all take to it as much as I did, but the majority of the class was not stopped by the frustration of syntax errors. If you can teach programming to 10-year-olds without it being too frustrating... on the other hand, I suppose you could argue that younger people will have an _easier_ time, for the same reasons (human) language acquisition is easier for children. I dunno. I'm not sure how it relates, but what I think was _really_ an immense aid to people of any age learning programming in the 80s was that computers and software were _simpler_, meaning that you could very quickly approach the level (at least at first glance) of 'real' software with what today seems like 'toy' software. The text adventure games I started writing as a child weren't actually _fun_ for anyone to play but me, but they _looked_ like a real text adventure game that other people played, they had the same form. Or the ascii-graphic blackjack game. There was gratification with a pretty low bar. I have no idea how I'd become a programmer today. It's an entirely different path. People ask for me for advice, and in my head, I'm like, well, first be a child in the 80s with an Apple IIe, then start writing for the web when all you need to know is HTML and you write it in Perl cgi-bin... I have no useful advice. I do have a CS degree, which I got in the 90s.
- elsombrero 9y ago>The grief factor of learning to code is on a different scale to every other major. One missing semicolon will take your whole tower down, and you realise this in the first day of practical exercises >In fact, every exercise in CS has this problem. You add a new thing (eg inheritance), and it breaks. But not only that, it might be broken because of a banal little syntax problem. That can be said for math as well, switch a + for a - at any point and the whole solution crumbles down, or use the wrong method of resolution and you are in for a world of pain. >Oh and learn git, too. And Linux. Just so you can hand in the homework. Again, comparing that to math, learn all the different notations used just to understand what the problem asks of you. Point being that any scientific course require a part of self study to get what you are doing. Although I can certainly agree that the way CS is taught now interwines many basic things that should be on their own course and could do with some reorganization, even though it's hard for universities to keep up with the way most of current day tech advances.
- SamReidHughes 9y agoThe difference with math is, you can get partial credit.
- deleted 9y ago[deleted]
- alistairSH 9y agoThere's no reason you can't receive partial credit in CS. If assignments are being graded solely on whether or not the output is correct, I'd say it's a flaw in the curriculum. FWIW, I do not remember this being the case when I studied CS in the mid-90s.
- toomanybeersies 9y agoIt was a combination for me, depending on the lecturer. I had some papers where up to 15% of the paper purely depended on output being 100% correct (you lost percentages each time it failed, and got 0% if it didn't work in the end). I also had some papers where your grade was based around functionality, where there were several milestones, so as long as you got it partially right, you got some marks. For instance, in one paper, we had to implement RIPv2, but we got partial marks if we only got parts of the spec working. Then there were papers where you had a final goal, but even if your code didn't even compile, they'd take a look at it and if you were on track, you'd get partial marks. For example, we had a paper where we had to control a helicopter reading data from a rotary encoder and other inputs, and use PID control. We had our PID control backwards so the thing wouldn't even fly, but the code was otherwise correct.
- noobermin 9y agoI think you are significantly under appreciating the difficulty and need for precision in many other fields, like mathematics and physics. For example, compare "missing a semicolon" to "missing a minus sign" in physics or making precision errors in chemistry. Alright, so both the hard sciences and CS have less traffic than say business, but then physical science has been growing and CS has not, and so we've solved nothing.
- kbenson 9y agoBeing a software engineer is often about the merging of the discipline of CS and the art of programming. I think most software engineers are strong in one and get by in varying degrees in the other. The few that are strong in both end up being the "very good" programmers we all know or have heard about. For some, that semicolon is a nagging reminder of their mistakes. For others, it's a small detail they zoom past as they get on with the laying down of code. I find those strong in programming may be prolific in what they write, but often have to rewrite portions as they encounter problems with their design. A more probe and prod sort of solution to the problem, where you feel your way through. I often do this. On the other hand, I have known people that take quite a bit more time up-front to think about problem areas, and end up programming generally what they thought in the beginning (with some delays as they stop to reexamine problems as they come up, but generally before too much time has been wasted on an incorrect solution). I strive for this. Being able to do both at roughly the same time, so you come up with a good model that you quickly get implemented, is what I think makes a good programmer. I think a great programmer is someone that does that but also sees interesting new paths that others often miss, leading to more elegant solutions more often.
- scaryspooky 9y agoYou start saying 'software engineer' and end with programmer. Clarify your terms. There is a huge difference between willing to take on liability for your faults versus slinging code.
- kbenson 9y ago> You start saying 'software engineer' and end with programmer. Clarify your terms. Eh, it snuck in there. I specifically changed programmer to software engineer in multiple spots to disambiguate it because I was talking about "programming" as an act distinct from applied CS. I missed doing so at the end. > There is a huge difference between willing to take on liability for your faults versus slinging code. Based on your assumption of what I meant, it sounds like you have something you wish to express on this point. Perhaps you should do so in more detail?
- flexie 9y agoThe premise of the article is wrong. From 2009 and until 2015, the number of CS grads almost doubled and any of those economics majors could have seen that in the graph, even if their essays are "basically bullet points" and their field is dead simple. They could also have told the blogger that causality might go the other way; Salaries are high precisely because demand is bigger than supply. If (or when) high salaries cause more people to study CS, salaries will drop unless demand rises even more. So we have a huge increase in CS majors in just 6 years. What could be the explanation for that? I would say that CS has become both more rewarding and more accessible in the last decade. More rewarding because with better browsers, and with smartphones, you can simply do more stuff. And those who graduated in 2009 started studying just before iPhone, before Google Chrome, HTML5. Long before Tesla and SpaceX were household names, long before we again believed in AI and robots. The field has simply become more and more interesting. More accessible because of Codecademy, Udacity, Udemy and the rest of the bunch. 10 years ago, learning to code meant reading books that were already outdated when you bought them and spending days in frustration trying to install whatever language you had decided on. Before you did as much as a hello world. Unless your friends knew how to code or you were enrolled at an educational institution you didn't have access to tutors. Today, you can get great tutorials online, and you can learn JS, python and many other languages without the hassle of installing anything. And once you are up and running, there are a plethora of libraries, modules, frameworks and ways of deploying which mean that you can do in weeks what before could take years.
- gms7777 9y agoYes, I'm sure there are other factors but the graph tells a pretty simple story. Numbers declined from 2005-2009, which means students that entered college around 2001-2005 -- students that were in high school during the dotcom bubble burst and aftermath. CS may not have seemed like an attractive field at the time. Over time the state of the field has recovered, and as you point out continued to grow and get more interesting, and growth in graduates returned.
- deleted 9y ago[deleted]
- 9y ago
- deleted 9y ago[deleted]
- ashark 9y agoI don't think it's even the programming that's the problem. There's a ton of Stupid Computer Shit we all know, mostly from messing around on our own time, that makes programming or doing anything else with computers much easier. A set of skills for navigating and troubleshooting issues, and a hard-earned intuition for where and how to look for answers. My CS program was really easy and I still don't know how people who hadn't put hundreds to thousands of hours into picking up that stuff in the years before college made it through. Many didn't, I guess. With some programming background on top of that it was pretty much a cakewalk for me, but the poor n00bs....
- ikeyany 9y agoI believe that being in the "engineering mindset" is at odds with what many people are used to. I think it's the culture that some see and get scared away from, even if that perception isn't 100% accurate. People interested in fixing CS "inclusivity" should address this first.
- na85 9y agoGiven that computer science isn't engineering (they are distinct but different disciplines), can you elaborate on what you mean by the engineering mindset?
- throwaway7645 9y agoCan't speak for OP, but the engineering mindset usually comes from those of us who go into the program that tend to be very mathematical and logical, while being obsessed with figuring out how things work. When a group of engineers sits down at a table to eat lunch, they could spend an hour arguing about how the restaurant could be more efficient...etc. These kids are often used to independent problem solving and don't need to have their hands held. We had an economics teacher in college who was famous for asking the engineers to stand up on the first day of class and then stating that they would be excused from the finals as they would all have above a 95 and not have to take it. The only majors that get the math exposure we do are well mathematics and physics. The difference is we also have to do a lot of concrete things like fabrication, CAD, circuit design, and almost every other class gets some level of programming, so your entire world resolves around fixing things and applying problem solving techniques. They parody this in Dilbert, but engineers are weird birds. Comp Sci is similar in a way when you have a student coding for 12 hours straight as they're in the zone and coding an elegant solution. They aren't entirely dissimilar, but engineers often have a more formal math background and will attempt to approach a problem from that side. Someone with a PhD in math will be so far ahead of me, that I'll barely be able to catch a glimpse at the kinds of problems they solve. We do more practical things like design engines and stealth technology, while they work on things like the millennium problems. I once attended a lecture by a notable math professor on the Riemann Hypothesis basics. 1 hour in and I still didn't hear the problem properly stated. He said "the reason the riemann hypothesis is important is because it is the reimann hypothesis" wtf?!? Anyway, although it is somewhat stereotypical, each major seems to have a kind on niche person that is attracted to it.
- peter303 9y agoIf you regularly experience grief in a subject, theN YOU SHOULD NOT CHOOSE THAT FOR A CAREER. You could be doing it for 30-40 years. Why make life miserable if you have a choice.
- Guyag 9y agoI agree with you that people should probably choose a career in something they're good at, but I think that's separate to the issue of making life easier for people entering the subject from nothing. The CS courses I've seen are different from those in other subjects in that they assume a whole lot more background knowledge, which is a pretty exclusionary assumption to make. Stopping this is no bad thing.
- Bakary 9y agoI've often heard people make "sensible" choices like these in undergrad. In their minds, it's a few years of toil that will yield an abstract form of an easy/successful life because "3. ??? 4. Profit", but for some reason they don't come to terms with the fact that their reward will be more of the stuff they hate, with longer hours and more pressure.
- azakai 9y agoOne of my professors actually made the opposite point: that in CS, the compiler will give you an error. You can fix it and move on to the next. While in math (he was a math prof), the paper doesn't object to your writing nonsense. If you have an error early on in your work, all the rest might be nonsense, and you only find out much later after a human grades it. tl;dr at least in CS you get immediate negative feedback
- lazyasciiart 9y agoUntil you're working on something that can segfault/fail to null terminate a string/fail to sanitize user input, etc. And the compiler won't tell you if the semantics of your program is garbage either.
- rjprins 9y agoIndeed very often the problems people encounter are described well in the error message and/or stacktrace that is printed. But many, many people find it very hard to correctly read and understand those and it's because that is also a hard skill to learn.
- douche 9y agoPeople will actively refuse to read error messages[1]. I don't know how many times I've been trying to fix something with somebody, and an error dialog comes up, and they dismiss it instantly, before whatever content it might hold has a chance to flash across their retinas. Then I have to get them to do whatever it was four or five more times, before they calm the hell down and let me read what the error message is telling them. [1] https://www.joelonsoftware.com/2000/04/26/designing-for-people-who-have-better-things-to-do-with-their-lives/ https://www.joelonsoftware.com/2000/04/26/designing-for-peop...
- sodabeest 9y agoi sometimes wonder if a single line of code I wrote was ever run/checked by a TA or professor
- 9y ago
- eternalban 9y ago> One missing semicolon will take your whole tower down That is not true. You do not put your "whole tower" back together again when you move cursor and type the missing [';']. [edit]
- pcthrowaway 9y agoI guess GP was thinking of programming in punch card languages, where one incorrect hole punch could mean you'd have to redo the whole thing.
- lostboys67 9y agoPunch cards easy try toggling in a program using the front panel switches which I have had to do a couple of times on PDP/11's
- flukus 9y ago> Oh and learn git, too. And Linux. Just so you can hand in the homework. They should know linux/unix/gnu before they start on anything cs related.Are you really suggesting the people that don't know anything about computers should be taking cs? Git would have made debugging the missing semi colon a lot simpler because it makes the divide/conquer approach simpler.
- pmorici 9y ago"One missing semicolon will take your whole tower down, and you realize this in the first day of practical exercises." Isn't that what makes CS easier? You get immediate feedback. You know if it will be right or wrong before you even turn it in.
- exolymph 9y agoDepends on your personality.
- kd0amg 9y agoYou know if it will be right or wrong before you even turn it in. Most student-written test suites I've seen are not nearly this thorough.
- pmorici 9y agoSure, but that is all about attention to detail. It isn't really about how smart you are rather how much effort you put in.
- rhino369 9y agoYes and no. You can understand a concept 100% and execute it 99% and still have the program fail. In other engineering disciplines, that gets you a good grade. In CS classes it's a fail. So you have to sit there and make sure it actually works. I'm not a programmer, but I took CS courses. Debugging your homework is fucking awful. I understand it's a skill necessary for programming, but it's awful. Especially when the bug is a mistake that is unrelated to the topic of the homework. I remember pulling an all nighter trying to figure out why my problem set didn't diff correctly. I must have spent 20 hours on a single bug.
- lordnacho 9y agoA missing semicolon tells you only one thing; In all likelihood, there are many things wrong with your code. In most other subjects, there are ways to get most of the feedback in one go.
- ransom1538 9y agoAgreed. I learned this in our new student orientation. "If you can't recompile a linux kernel by the time you graduate, you have learned nothing. Oh, yeah, also, we wont teach you that - it's just something you will run into. " -- Professor Norman S. Matloff
- ams6110 9y agoCompiling a linux kernel is just following a set of instructions. You don't need to know anything about computer science to do that.
- jstimpfle 9y agoThe thing with instructions is always this: The first instant something goes wrong while following them you have to give up if you don't know quite a bit about what you're doing anyway.
- TheSpiceIsLife 9y agoI believe I'm not the only one who, when something goes wrong, I become more determined and think "I might learn something here" followed by searching the internet for things related to what went wrong.
- taphangum 9y agoThis is basically how I learned to program.
- afarrell 9y agoRight, but that takes it from "just following instructions" to a thing that requires you to build a mental model of the system you're working with. It also requires you to have confidence that you will find the answer in bounded time.
- erikbye 9y agoAnyone who talks about compiling the Linux kernel as a measure of difficulty or knowledge obviously knows nothing. I could teach my 9-year-old nephew how to do that.
- dghughes 9y agoUgh. That was me. At age 14 I used to copy BASIC into my Atari 600XL, QBASIC into my old 5150 and 486 PC, some HTML in the 90s, some Python, Perl others here and there. So I tried to go for CS about ten years out of school and Java got me. My brain just doesn't seem to like programming.
- throwaway7645 9y agoNothing against comp Sci, but engineering is its own set of problems as you have to take a lot more advanced math classes than comp Sci, while taking all your calculus based engineering problems. Some you use techniques to convert to simple algebra problems...that end up being 2-3 pages long. All while having to learn CAD, robotics, practice circuits, design trusses, and yes, quite a few programming languages (basic, C, assembly, VHDL, Matlab, and PLC (ladder logic))to name a few. Each one of those has its own set of problems from the install to the OS to the awful assignments...etc. Then each class itself is often taught really harshly. I often had multiple choice tests...sounds good right? Not great when you make 1 sign error on an entire page of calculations and get 0/10 points. I had a design project once that I spent weeks on and went above and beyond everyone else in class. 30 pages on the design with pages of equations and optimizations. 1 page had a minor error that carried to another, but overall not too bad. 70/100. Not to sound overly dark, but engineering school was extremely difficult and by far the worst 4 years of my life. I graduated with a good GPA, but I studied pretty much non-stop those 4 years. Some people manage to make great grades with very little effort, but it is rare. Again, nothing against comp Sci. Any program that focuses on logical problem solving is A-ok in my book, I just don't want anyone to get the idea that engineering is in any way easy. It is often a cruel and harsh mistress.
- skookumchuck 9y ago> It is often a cruel and harsh mistress. If your engineering project doesn't work, there's no pretending that it does. It's the ultimate in fairness :-)
- CamperBob2 9y agoIf your engineering project doesn't work, there's no pretending that it does. Yeah, that's marketing's job.
- lostboys67 9y agoNah that bridge that fell of its supports it was the contractors fault honest guv :-)
- PretzelFisch 9y agoyes, I still remember never getting fortran to do anything. C++ was easy to pick up. funny how picking one bad class can kill a subject for you.
- wonnage 9y agoIn practice, you don't have to know any of these things to be (or at least pass for) a programmer. Work at a large company, someone else takes care of the build. Use a git GUI app/IDE to take care of source control. Don't use anything new. Of course, you probably won't progress very far career-wise (or maybe you'll become a manager...) if you never venture out of the little box. But the amount of effort you'll have to invest to reap a solidly upper-middle class income is pretty minimal. If you spend 2-3 years in industry and don't get fired, you probably know how to code well enough to satisfy your employer. And at that point you're probably gonna get more (career) value working on soft skills like planning projects, managing expectations, navigating bureaucracies, etc.
- panda88888 9y agoTBH CSE has some of the best toolset available to the general public. It also has one of the lowest cost of entry as well. Compare a misplaced semicolon that throws a compiler error to, say a miswired electronic component, which most likely kills the chip and possibly other chips connected to it... and the fact that a breadboard offer no "syntax checks" to make sure signal input is not connected to power signal... I say CS/SWE has probably the best toolset out of all engineering disciplines.
- deleted 9y ago[deleted]
- anothercomment 9y agoHm, I wonder if there is a inverse correlation between number of JavaScript frameworks and enrollment numbers :-)
- ma2rten 9y agoThere is another problem. Computer Science just doesn't sound that interesting. Say you could learn to build aircraft engines, understand how the economy works (which has a huge influence on people's lives) or learn how to make a computer print "hello world" on a terminal screen and how to efficiently store data. Most people wouldn't choose the latter. It's actually quite hard to describe what computer science is and why it is a science.
- douche 9y agoThe problem with pure computer science is that it isn't even that interesting to the uninitiated. Who the hell wants to grow up to balance binary trees, derive proofs around number theory, and poke and prod at heaps of linear algebra? Or the other end of the spectrum, where you are a cube-dweller, who shuffles endlessly to Scrum meetings, does email, enter garbage into JIRA, and once in a blue moon gets to write a little code that might possibly be executed as part of some faceless, soulless enterprise monstrosity.
- Double_a_92 9y agoSay you could learn to build sites like facebook or google, understand how the internet works (which has a huge influence on people's lives) or learn how forces bend metal and how to calculate some break even point. Most people wouldn't choose the latter...
- amelius 9y agoYes, for most people CS == IT. And IT doesn't sound very exciting. Also, in the end, big companies like Google and Facebook are IT companies, or advertisement companies, and they are after your private data. I guess most people would rather choose a more noble goal in life. And finally, tools created by big companies such as Google docs perform worse than wordprocessors of the 90s. Yes, they allow collaboration now, but still, they are perceived as slow. In people's minds, IT is not progressing much.
- SomeCollegeBro 9y agoIt's interesting you say that too, because a lot of those "flashy" jobs end up being very similar to a computer science job anyways. There are typically thousands of people designing a jet engine, and individual teams and people are assigned minute tasks of the process (especially engineers). The work goes from "designing a jet engine" to "sourcing proper bolts for a small part of the jet engine".
- nostrademons 9y ago> The grief factor of learning to code is on a different scale to every other major. 'Cept physics. Misalign a mirror or shake the table and all your experimental data is bogus, and you don't find that out until you've analyzed your data and realize it's nonsensical. I suspect other hard sciences (chemistry, biology) have similar issues, but am not familiar enough to judge. I started out as a physics major and switched to CS in my last semester...CS is hard, but not nearly as hard as the hard pure sciences.
- InclinedPlane 9y agoAn example from chemistry: get a mixture of different chemicals in a lab class that you are tasked with separating and identifying. Screw up one separation step and lose one or more of the chemicals, you aren't getting it back. If you're lucky maybe you can take the NMR spectrum of the whole sample, isolate out the contributions from the other chemicals you were able to separate and then possibly be able to identify the missing one, but you're not going to be able to turn in an isolated sample of it so that'll at best cost you a bit. An example from math: you make one tiny logic error while composing a proof and miss it until you start rereading, then you might have to start all over again from scratch.
- ghaff 9y agoMany engineering fields (including CS in some contexts) have a huge dependency on experimental setups that are "temperamental" at best much of the time and/or dependent on someone else's experimental work and other hardware that doesn't always perform according to spec, etc. As someone with degrees in non-CS engineering fields, I mostly find the idea that programming on a stable computer has a high frustration/grief factor to be pretty funny.
- gozur88 9y agoThat was my reaction too. You don't know frustration as an undergrad until your correctly designed circuit is behaving oddly because one of your components is damaged in a nonobvious way. I found the CS classes to be relaxing by comparison. Works every time as long as I get the code right? Sign me up.
- InclinedPlane 9y agoHah, seriously? This is a very bizarre perspective. Sure, CS is a lot of work but I would hardly describe it as more difficult than any other STEM field. I was effectively a triple major in college (graduated, went back for a double major post-bac degree in different fields) and against Chemistry and Mathematics I'd describe Computer Science as the easiest of the three. As for git, that only takes a few days at most to learn to the level you need to use it in school, at least if you're even remotely technically minded. In undergrad CS courses I learned about, oh, databases, algorithms, data structures, inheritance, and so on. In undergrad math courses I learned vector calculus, abstract algebra, linear algebra, numerical analysis, differential equations, etc. In science courses I learned organic, physical, and inorganic chemistry, some of quantum mechanics, how to use instruments ranging from: mass spectrometers, gas chromatagraphs, infrared spectrometers, UV-Vis spectrometers, flame emission spectrometers, Nuclear Magnetic Resonance spectrometers, as well as cramming "free time" during the weeks/weekends with lab time. If anyone came up to me and asked "so, do you think studying computer science is more difficult than vector calculus or quantum mechanics" I'd laugh in their face. No, CS is not uniquely difficult among college majors. I'd say there are a few major factors why CS majors haven't grown at the same pace as others. One is that the number of CS majors ballooned in the '90s when the industry started blowing up, and it's been a bit inflated since then. Another is that a CS education is treated as a necessary and sufficient pre-requisite for becoming a software developer and it's really ill-suited for that. Software dev. is not scientific work, a lot of what they teach in CS programs is not hugely applicable to being a good developer, and a lot of what you need to be a good developer isn't taught in Universities. Parallel to that, you can jump into the industry "running" if you just start coding and getting experience and learning while doing. That is often a superior way to build your skillset, build your network of colleagues, build your resume, and start making money instead of digging yourself into student debt. So a lot of people who enter the industry go that route. That also has it's problems but on balance it's probably the better route for most people.
- kbart 9y agoI don't agree with that. Just an anecdote, but programming was always the easy part for me. Boring, abstract and arcane concepts, algorithms (that you probably will never have to program by hand outside of university anyway) was the reason I've chosen engineering instead. Also, downplaying difficulty of the other disciplines only shows the lack of knowledge in them.
- Emp202 9y agoNot sure what universities you went to but that view is as far from the truth as it can be, at least for where i'm at (germany). I majored in CS myself but had a lot of friends in mechanical and electrical engineering. To say their fields revolve around a small number of vignettes is downright bizarre. I was never bad at math, but i gotta admit it got hard in CS along the way. However, the math the did in EE in the higher semesters to me was completely arcane. Like several steps above what we had to do in CS. The grief factor of coding? Seriously? Load up a halfway decent IDE and have immediate feedback when you did something wrong, then tinker until it works and you can hand it in? It doesn't get any easier. Compare that to "drawing some boundaries and applying some equations" (over 10 sheets of paper), then noticing you made a mistake on page one and your results don't make sense... I'll take the "code grief" any day. I don't mean to be snarky but you sound like a frustrated CS undergrad student that hasn't had to much exposure to the other fields you devalue so easily.
- lr4444lr 9y agoSuddenly it makes sense to me why so many programs are switching over to Python for every course they can that is not domain-specific, like graphics or architecture.
- ForHackernews 9y ago> The grief factor of learning to code is on a different scale to every other major. One missing semicolon will take your whole tower down, and you realise this in the first day of practical exercises. Only somebody with zero experience with wet lab chemistry or biology could ever write the above with a straight face. At least you can fix a missing semicolon. If you screw up a long-running organic synthesis, or you kill your bacterial colony around generation 2,000 all you can do is start the whole thing over.
- linkregister 9y agoYou will not be screwing up an organic synthesis or killing a bacterial colony in your 100- or 200-level biology course. The author's point was that the early unforgiving nature of programming could possibly be a factor in the potential lack of growth in the field.
- ForHackernews 9y agoSpeak for yourself. I definitely goofed up syntheses and badly botched biology labs in first- and second-year chem and bio courses.
- microcolonel 9y agoIf you think the programming tools are the hard point, I have a proof assistant and program extractor to show you.
- Shorel 9y agoIMO the difference with math is, you are the compiler, the linter, and everything else as well. With programming, you have plenty of tools that detect errors for you. With maths you sometimes will only see the error after somebody else (like the tutor) point it for you. Therefore you can be much more efficient when programming than when doing proofs and other maths stuff. Except with economics, as you point out :)
- quicknir 9y agoHonestly CS major is typically a joke compared to math (real math, not "CS is math" math), or physics. Comparing the hardest CS classes you'll do in undergrad to the likes of PDEs, Complex & Real Analysis, advanced QM, General Relativity, etc, it's just no comparison. I took ML in person at UIUC 4th year / graduate cross-listed level, and the 3rd year Stanford algos course on Coursera (supposed to be identical to the material in the actual course, yes yes though feel free to laugh b/c it's Coursera). These classes were interesting, but about as challenging as typical second year math/physics classes. They are peanuts compared to senior math/physics classes. That said I still think CS is more challenging than most majors, it's just that the "few" is much more highlighted because there is very high demand. Certainly way higher demand than math/physics, and more demand than other fields that are still reasonably challenging like engineering, pre-med, etc. It's definitely the field where some reasonable increasing function on both demand and difficulty is maximum.
- jcranberry 9y agoPerhaps you have never seen the trails of broken dreams leading out of introductory proof-based math classes.