7 ms·
Completely disagree. > full teams can and have built huge java projects just by using the intellij project wizard and maybe a tiny bit of Gradle from stack ove
by kelnos 5y ago
Completely disagree.
> full teams can and have built huge java projects just by using the intellij project wizard and maybe a tiny bit of Gradle from stack overflow.
I would not ever want to work with anyone from those types of teams. They are the kind of programmers who have a very narrow range of abilities, and whenever they see a problem outside those abilities, they get completely lost.
> But this is stuff that should come in later classes, particularly for students who are interested in those details. Not everyone needs to know it.
Yes, they do. They absolutely do. There seems to be this mindset that's starting to infect software development that pushes the idea that people can be good at programming computers without actually knowing anything about how those computers work. I just do not understand how anyone could seriously believe that. My experience over the past 20+ years tells me that people who avoid learning about these topics are generally just not good at their jobs, or at best can do a decent job of things, but then completely freeze when they encounter something outside of their narrow comfort zone.
> In fact my experience is that some colleges have the exact opposite problem: they teach students old tools and techniques
That's lame, but has nothing to do with the point you're trying to make.
- einpoklum 5y ago> > In fact my experience is that some colleges have the exact opposite problem: they teach students old tools and techniques > > That's lame It's not lame, it's fine. It is just fine, and usually better, to teach basic concepts using a simple tool - even if it is not fashionable or up-to-date.
- kelnos 5y agoI think the parent's point was that some people teach using old tools that no one uses anymore, while teaching with the current-generation tools would be just as easy to teach, but would be much more useful. Agree that teaching old techniques can be useful in the cases where the current techniques build on what came before.
- tomohawk 5y agoVery much agree. IDEs can be great, but in the hands of someone just learning they encourage a cargo cult style that becomes a barrier to actually knowing what you're doing. I've had to work with people who are still stuck cargo culting thing 15+ years into their careers. Not fun. Relatedly, they can also assist people who to get just enough success (in the cargo cult sense) to get a degree, when they would be much better off in a different field. It does them (and their future team mates) a disservice.
- JeremyNT 5y agoThis article is in the context of computer science education, though - not real world programming. Undergrad CS students aren't learning software development first and foremost. They're learning logic and math, data structures and algorithms. They need a low friction environment so they can learn the academic stuff without wasting their (or their TA's) time. So while I agree that many "real world" programming jobs require dealing with the kind of boring minutia that IDEs try to abstract, this stuff shouldn't necessarily be a prerequisite for students on a CS track. There's plenty of time for the real world later :)
- Rd6n6 5y agoWhen I learned programming with eclipse years ago I spent so much time worrying about the magic behind the scenes that it left me with no confidence in my programming. When I finally learned to write my own make files and compile on my own, I went back to using ides and like them, but you shouldn’t learn with them
- Ekaros 5y agoSo should we teach the students how to write make files before we allow them to write first line of code?
- jcelerier 5y ago> I would not ever want to work with anyone from those types of teams. They are the kind of programmers who have a very narrow range of abilities, and whenever they see a problem outside those abilities, they get completely lost. Okay but what matters is not who you want or do not want to work with, but "can it make a business that works". That's the only metric. The first job I was in the owner did "code" pretty much everything on a visual programming language (Max/MSP). Was it pretty ? No. Did it allow him to start a business and sell things ? Definitely, and that's the only thing that matters
- kelnos 5y agoMaybe "can it make a business that works" is the only thing that matters to you, but it's not to me. If I have to spend my days dealing with developers who can't think outside of a tiny box, I will be miserable. I don't care how much money the business makes; that's not how I want to live my life. And what happens after you get that business running and bringing in some revenue, but you need to start tackling harder problems in order to keep your current customers happy and attract new customers? You're stuck with a bunch of developers poorly suited to solving those problems, and a bunch of infrastructure that wasn't designed with this sort of feature expansion in mind. So you hire some new people who have to rewrite a bunch of things, or who have to spend months or quarters untangling the mess. You could even miss your market opportunity. Even if you don't, you've still wasted a lot of time and money.
- jcelerier 5y ago> Maybe "can it make a business that works" is the only thing that matters to you, but it's not to me. What I want doesn't matter any more than what you want regarding this. What matters is what the society as a whole wants, and the current situation is in big part the manifestation of it. > And what happens after you get that business running and bringing in some revenue, but you need to start tackling harder problems in order to keep your current customers happy and attract new customers? You're stuck with a bunch of developers poorly suited to solving those problems, and a bunch of infrastructure that wasn't designed with this sort of feature expansion in mind. you're assuming that you would even have gotten the first customers if things were "done right". My experience seeing entire businesses held by 1kloc of "academic" (I'm not saying this as a compliment) python scripts with 20% of it being globals succeeding says otherwise.
- brtkdotse 5y ago> They are the kind of programmers who have a very narrow range of abilities, and whenever they see a problem outside those abilities, they get completely lost. The vast, VAST majority of programming is of the type OP described. It ugly and has warts, but is good enough to deliver business value. I’ve seen it first hand. The truth is that developers working on projects like that outnumber everyone else probably 10-1. See https://www.hanselman.com/blog/dark-matter-developers-the-unseen-99 https://www.hanselman.com/blog/dark-matter-developers-the-un...
- kelnos 5y agoWhile that may be true, programmers working on these types of projects will end up being better at doing them (they will build it faster, write fewer bugs, and have an easier time fixing the bugs they do write) if they understand more about computers, operating systems, and the tooling around their chosen language and IDE. Sure, maybe they can still get things done without that knowledge, and it'll work, but that's not really the point.
- Sankozi 5y ago>> full teams can and have built huge java projects just by using the intellij project wizard and maybe a tiny bit of Gradle from stack overflow. > They are the kind of programmers who have a very narrow range of abilities, and whenever they see a problem outside those abilities, they get completely lost. How does one follow the other? How does not learninging unnecessary skills hinders ability to solve new problems? If skill is really needed later one person from the team can learn it and share most important bits of knowledge. If skill is not needed now why learn it? YAGNI can also be applied when learning things. I find that not understanding how compilers works or how to use them in low level tasks is minor problem when developing. I never met developer who had problem like that. Much bigger problem during developing is not listening to and understanding your users and IDE will not help you with that. This is much better skill to learn than compiler CLI.
- kaba0 5y agoA great rule of thumb I’ve read on HN is that a great developer is one who understands at least one layer of abstraction below where he/she works (but 2 is better). That doesn’t compiler intrinsics if you are programming in high level languages, but it does include in my opinion the general tooling of the language, its way of execution, etc.
- vishnugupta 5y agoI call it n-1 rule and IMO it can be generalized to any creative/craft profession. A great driver understands how engines work. A great wood carpenter understands about different kinds of Timbers and their properties.
- kelnos 5y ago> YAGNI can also be applied when learning things. I don't think that's true. I think learning things that are related to your work will almost always make you better at your work, even if you don't use that specific knowledge directly. Human brains are big pattern matching machines, and the more data you can feed it, the better it will be at looking at problems and truly understanding them. > I find that not understanding how compilers works or how to use them in low level tasks is minor problem when developing. I'm not saying that you need to understand enough to build your own toy compiler (though that can also be very useful in understanding how to write better programs). But at least understanding it from a basic level, like "javac takes in my source code, turns it into some kind of machine-readable intermediate representation, does optimizations, and outputs bytecode" is something that I expect every Java programmer to know.
- _pmf_ 5y ago> I would not ever want to work with anyone from those types of teams. They are the kind of programmers who have a very narrow range of abilities, and whenever they see a problem outside those abilities, they get completely lost. The thing is, they are the ones least likely to cause difficult to debug build issues due to "very clever" features and using the latest version features of build tools in the first place.
- marcellus23 5y agoIt’s true that clever code can only be written by knowledgeable engineers, but that doesn’t mean that knowledgeable engineers all write clever code.
- kelnos 5y agoThey're also the kinds of people who will use the same version of their tools long after they've stopped being supported, and then when you need one of those new features, or run into a problem that you can't work around, you have to drag all that stuff into the present, which is always a huge pain in the ass. And the kind of developers who got you in that situation in the first place will be the least well-suited to help get you out. Regardless, I don't think "I don't want knowledgeable people because they might write something 'too clever' that causes problems in the future" is a particularly winning strategy. You're basically saying you want dumb people because they will never try to be too smart for their own good.
- jdbernard 5y agoThey are absolutely the ones to create hard-to-debug issues because they layered a whole bunch of complex things incorrectly or unknowingly. For example, recently I spent more time than I'd like finding out that we linked two incompatible versions of a library. All the visible dependencies were correct, but at some point someone bundled an old version in a fat jar and that got included transitively via another dependency. If you understand the details you know why you don't distribute libraries as fat jars. But if you're just following some guide it's easier to fat jar it than correctly specify your dependency tree. If your education was really effective you recognize this is just the static/dynamic linking problem again in new clothes.
- duckmysick 5y ago> They are the kind of programmers who have a very narrow range of abilities, and whenever they see a problem outside those abilities, they get completely lost. Interesting. In other fields, like surgery, narrow specialization is desirable.
- kelnos 5y agoA surgeon still spent many years studying medicine at a broad level before moving into training for that specialty, though. And many developers I know do end up specializing in particular sub-fields (ML, databases, whatever), but they already have a wide breadth of knowledge and experience to serve as a foundation underneath that. In contrast, I also know some developers who didn't take that route, and jumped into specialization early, and who are completely useless at productionizing their work.
- andrew_eit 5y agoA surgeon is still a doctor who spent years studying medicine though.
- rowanG077 5y agoYou generally specialize after you have learned the basics. All oncologists are doctors, all architects that design very large buildings are capable of designing houses etc. It's seems obvious that the basics for a developer includes how a machine works.
- simonh 5y agoYou only like to work with experienced engineers, who are already experienced with the specific tooling you use on your projects fine. Students by definition are not experienced engineers. They’re in a given class to learn the topic for that class, and hopefully that class with be a challenging program of learning. In CS often the fact they’re even working in Java is incidental, they’re not even there to learn Java, but generalisable CS concepts. I’ve got no problem teaching students practical software engineering skills, sure, that can be very valuable. It should be on a course on that topic though.
- karma_fountain 5y agoI agree and also feel like Students new to computer programming shouldn't be using Eclipse. They should be learning the fundamental concepts and their implementation, and having to learn a whole very complex IDE as well would just add to that difficulty.
- J-Kuhn 5y agoWhat fundamental concepts? if, while, and other programming concepts? I'd agree on that. But the article suggests learning about files, file formats and other low level stuff. So maybe they should first learn how a filesystem works, how it keeps internal consistency, and how the bytes are mapped into some physical storage. That's pretty fundamental too, right? What we have here are "leaky abstractions"[1]. If the abstraction an IDE provides is not good enough that students can work with it without knowing about the lower layer, then the abstraction is leaky. And that is the problem. Not "should I teach them with an IDE or without". [1]: https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/ https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...
- Jensson 5y ago> What we have here are "leaky abstractions"[1]. If the abstraction an IDE provides is not good enough that students can work with it without knowing about the lower layer, then the abstraction is leaky. Do you suggest teachers fix Eclipse so it no longer has leaky abstractions rather than just teach students how to work in a modern file system?