5 ms·
Not from a modern developer. You need to jump down the rabbit hole of the history of solid and proven solutions. Indeed. I've noticed an increasing number of p
by userbinator 3y ago
Not from a modern developer. You need to jump down the rabbit hole of the history of solid and proven solutions.
Indeed. I've noticed an increasing number of people who call themselves "developers" and appear to create software, but all they can do is follow step-by-step tutorials to glue together some massively bloated thing that they have absolutely no understanding of, much less the skills to debug it when something doesn't work perfectly as expected.
- gofreddygo 3y ago> but all they can do is follow step-by-step tutorials Lego's dream has come true.
- keyle 3y agoAt some point, the plane flew so high above the clouds, and it hasn't seen the ground for so long, the passengers might think the clouds is the ground.
- turtleyacht 3y agoWhen "Hello World" is a cloud instance spun up and billed on your tuition. That won't really happen, right? No Computer Science (CS) professor would designate special cloud Interactive Development Environments (IDEs) to students. On the other hand, it would really resolve a lot of "doesn't work on my machine" issues.
- samarthr1 3y agoI think that would be a great way to make a weeder course? Setup some obscure software, with poor documentation, build something nice on top of it, then rewrite it because some fundamental assumption is broken, sounds like this kind of first year of cs course we should have. The idea being weeding out those not as passionate about computers.
- dllthomas 3y agoIt's been a while, but when I was in school I think things had to work on the campus ultrasparc systems.
- kjs3 3y agoGood way to catch unaligned access errors. I seem to recall a similar "you can develop on whatever you want, but to turn it in it needs to work on the Dept systems" back in my college days. Intro to CS was in pascal, and a bunch of us started with Turbo Pascal on our PCs, and figured out pretty quick the Pascal on the AT&T SVR3 boxen was a very different beast.
- WorldMaker 3y agoAzure and AWS both have academic/educational resource buckets and discounts. GitHub has said one of the largest growing areas for Codespaces (cloud IDE) usage is Education. It's already happening. It does resolve a lot of "doesn't work on my machine" issues; it does leave some questions about how much students see of the "ground" below the Clouds.
- geek_at 3y ago> glue together some massively bloated thing that they have absolutely no understanding of Welcome to the world of npm and supply-chain hell
- busterarm 3y agoJava and Golang aren't any different.
- quectophoton 3y agoTo be fair, I would also say the mainstream IDEs have contributed to this situation to a certain extent, since they lower barrier of entry. That's a very good thing, but also sometimes bad. Here's what I mean. There's a difference between: * Using an IDE knowing what you want to do but you just like the convenience. You know what the IDE is doing for you, but you want your tool to do it for you quickly and get out of the way. If the IDE does something you don't know, you try to learn what this was. * Using an IDE because you literally can't work without one. Not knowing your programming language and depending 100% on autocomplete to do most stuff. Not even knowing how to write the files that the IDE automatically updates when doing certain things. It's a subtle difference, but the former is more likely to leave better comments in a web-based code review ("pull request") than the latter. And if a project consists only of the latter type, it's unlikely that there will be comments like: * "Use this other class with the same name but different package because this one is buffered" (because depending on autocomplete without knowing the language prevented them from even caring about which import to use, or the difference between those, as long as it works). * "Would this change affect this other file that's not in the PR but calls this function a thousand times per request?" (because not knowing their own projects general structure due to depending on their IDE for navigation, so they're more likely to NOT notice a file that's not mentioned in the PR). So if a project has only people that depend on an IDE (instead of using an IDE for convenience), it's easy to end up with stuff that technically works, but copies 40MB of strings around multiple times, and thrashes your performance due to reading one character at a time without buffering. Granted, this technically is not related to IDEs, but in my experience (emphasis on "my"), most of the people I've worked with that use an IDE, are of the "can't program without it" type, and not the "I use it because it's convenient" type. Not all of them. But most. Even if there's a learning curve at play here, I'd say there's usually overlap between "use IDE because convenient" and "actually bothering to put an effort into learning". I understand this is an inevitable consequence of lowering the barrier of entry and making programming more accessible, and it doesn't matter if we're talking about npm, IDEs, programming languages, or anything.
- sfvisser 3y agoYou might not want them in your team maybe, but isn’t it really cool we reached a state where you can actually do this? Democratization of software engineering is a great good!
- marginalia_nu 3y agoDunno if it actually is democratizing software engineering. Looks more like a cargo cult to me. You get a second class of developers that don't quite get it. Not because they aren't capable, but because nobody shared the secrets with them and they had to piece together everything from flotsam.
- toast0 3y agoCargo cult programming is a starting point. Plenty of people won't go any further, but when what you're putting together is all source code, it's mostly transparent boxes you're putting together. You can look inside and see the secrets whenever you want, if you ever want. Sure, maybe there's some design principles to share that aren't obvious. But it's hard to share and teach those before someone has experience with at least putting stuff together. Also, it's not like there are principles that are universally accepted or universally applied by trained software engineers.
- marginalia_nu 3y agoI'd say it's more the opposite. What characterizes cargo cult development is having too many principles and rules, rather than lacking them, they're rules without any real understanding of why they exist and what they're for or when they're applicable. As long as you adhere to the strictures, good code emerges somehow. The way to bring a cargo cult developer into the light typically involves debunking or contextualizing a whole bunch of weird ideas.
- toast0 3y agoMaybe you and I have a different definition of cargo cult developers than I do. I'm thinking cut and paste from stack overflow (or now chatGPT) without much understanding or consistency. Knowing how to apply design principles and rules despite not fully understanding them is a different level, in my mind.
- nousermane 3y ago> glue together some massively bloated thing that they have absolutely no understanding of Relevant: https://xkcd.com/1988/ https://xkcd.com/1988/
- pikseladam 3y agoexactly that. I couldn't describe better.
- VoodooJuJu 3y agoThen how are these people getting jobs but not my more competent friend? Asking for friend.
- msla 3y agoWelcome to the world of programming on an OS.
- intelVISA 3y agoTurn back, nothing but pain and disappointment if you continue this dangerous line of thought.