Also being a nerd doesn't mean playing at work. I'm not sure why you push my view as a lack of discipline or being lax.
> I never said anything about reinventing the wheel.
You did not indeed, yet this is what I have observed 100% of all nerds I ever knew in my life doing over and over again. Sorry, I am a bit jaded but also quite justified in my opinion if you take my life + career in mind.
> I'm not sure why you push my view as a lack of discipline or being lax.
Interpreting your words, nothing more. If you feel I did it wrongly feel free to elaborate. I'd be interested to read it.
You're on! Okay, I will need
- the make and model number of this unit, and whatever documentation is available describing the glitch: what to look for under what conditions; steps to reproduce and such;
- the hardware itself: some contact person who will send it to me;
- SDK for the thing, and firmware codebase, with some documentation: how to build, flash;
- contact information for where to send fixes and have a related conversation;
- all of the above free: I will fix the problem, but I'm not paying for anything.
Until I have these things, I'm working on my pet project with what I have available.
>- the make and model number of this unit, and whatever documentation is available describing the glitch: what to look for under what conditions; steps to reproduce and such;
With just that and the allegation of a particular glitch harming a person, you can report it to the manufacturer and they're legally compelled to treat it as Serious Business (I don't think that's actually the FDA's term for it), though that doesn't strictly speaking guarantee a timely fix.
...Though not sure how well are the SDKs documented...
A lot of simple and correct things were built by passionate people, and play is a necessary prerequisite to nurture passion.
As to the amount of play to be encouraged in a work setting, I don't have a strong opinion yet.
Python gets plenty of criticism, you might have just made sure you're never going to hear it.
If you are comfortable with Python I can somewhat envy you -- you likely have a cushy job and not much changes. Enjoy it while it lasts because take my word for it, it's a turbulent world outside of your bubble.
But in my eyes people with your mindset are enabled through their privileged position and thus become complacent.
It's OK to disagree. I also thought I'll share how I view you (in addition) and will bow out.
And its main selling point nowadays, ML/DL? I hear Rust's Polars is catching up. Python should enjoy its place while it lasts because I am seeing a good amount of effort for it to be displaced, from many directions.
I am not making anyone believe me though. Most programmers feel easily threatened when their favorite language is criticized and I've come to accept that defect in human thinking. But I won't be pretending to believe in a mass illusion. I moved on, long ago, and I've seen increases in productivity and correctness and [machine + development] speed.
Regulated industries should produce high quality output, agree. But the moment that approach leaks into the rest of software I’m out for good, and I imagine many others along with me. The “real” and certified™ big boys can take over all the work for all I care, but there’d be substantially less output across the industry. (Some backwards people would call that a win)
Note that I specifically left a much more regulated industry to be in software. Also note that I care about correctness and quality a lot still, it’s one of my favourite CS subtopics (memory safety, business logic in the type system, (fuzz, property, unit, integration, e2e) testing, …).
Damn. I want such a programming job.
It kinda reminds me of the "passport bros". You want to MAKE me do housekeeping, and there's NO way to get someone else to do it? I'm just gonna leave, and have fun suckers.
You're really smug about "certified™ big boys", but you're just the counterpoint to them. The "certified™ real deal developers", chime in to talk about how they'd never accept oversight, but yet there's very little substance here.
I hope you have some reason. You feel that this is a waste of time and too much effort gets spent on CYA and BS, that the "real process", and things that really keep the system safe and secure get ignored (like having super smart certified™ real deal developers), and the checks and balances (like in the process) do nothing to help... maybe this isn't your pitch, but I imagine there's something; yet you haven't shared these ideas.
In any case, I think you're wrong. We don't have enough regulations, especially in safety and security critical applications. We need discipline and standardized methods in software, as well as regulations in important areas.
Even if you were making real points, we'd have to doubt your motives, but at least you're not sneaky enough to hide them.
Then why do you keep mocking the idea of a professional certification?
1. Except, the millionth LISP interpreter is almost definitely a hobby project, so their claim that people are screwing around at work is bogus.
2. What drives people to work on problems (in industry) isn't "what the nerds find cool", it's money. That's a capitalism problem, not a "this industry isn't controlled enough by me" problem.
3. The software industry isn't uniform. Medical devices ARE regulated under the medical industry, commercial airplanes ARE regulated under the aviation industry.
Has there been recent disasters in those industries due to software? Yes, and regulation gets updated. Regulation gets written with blood.
You might argue that software feels like they're the most prominent, but I argue it's because
1. Software is relatively new
2. We are software engineers, so we take notice of software more.
Mechanical and civil engineers are not immune to mistakes. Think of the last car recall due to mechanical failure (heck, there's one this year due to brake manufacturing issues: https://www.caranddriver.com/news/a44475030/honda-acura-brak...). Or the O-ring failure in the space shuttle Challenger that caused it to explode mid-launch.
> The most lucrative jobs are in enterprise SaaS and ads companies, do you think engineers flock there because that sounds fun?
It's not even specific to these industries! HN has a very myopic view of the world. This is true for a number of engineering disciplines.
How many people are REALLY passionate about making trash (basically a job I held as an EE)? They pick up these manufacturing jobs, because they're reliable money makers. What was I doing? Taking a machine and creating a copy right next to it (with modifications).
Now I'm working in software and largely doing similar things. Integrations, design, architecture... basically accounting work with templates for code. I do a fair amount of embedded system design, but the software design pretty much decided.
> 3. The software industry isn't uniform. Medical devices ARE regulated under the medical industry, commercial airplanes ARE regulated under the aviation industry.
There are software safety standards, but they can be treated as suggestions.
What happens to me if I simply decide not to follow regulations? There's very little. It's comparable to legal, accounting, and other engineering work that has real consequences attached to it for doing it wrong. Loss of profession or jail time.
In Europe, more stuff requires a stamp. I work in an industry where we have these conversations. The "real developers" and the "big boy serious developers". I'm just shocked he can have such short-sighted interpretation.
The serious big boy developers have their problems too. People just have to choose either extreme side of a spectrum.
Hear hear. The last 10 years of my career I was surrounded by this attitude (about Python); there was literally no possibility of putting a dent in the groupthink and cult-think surrounding Python (because after all, wasn't it "the most popular programming language in the galaxy"?), which eventually became the corporate-ly mandated language for all software development (and that was that). Yet when I retired in late 2021, my employer's minions were still developing almost entirely in Python 2, having half-heartedly put forth multiple parallel Python 3 migration initiatives which had largely come to naught.
/rant
> Like I ranted recently here in HN, can we stop with the millionth LISP interpreter already?
Except, the millionth LISP interpreter is a hobby project, that people are making on their own time, not during work? I get it's annoying to see something you've seen before, but you know, you can ignore it.
Play is an important part in learning. The millionth LISP interpreter, game engine, whatever is fine. From my experience, the people building these things gain a lot more valuable experience than just doing college or even just having a prior job.
> We have people dying in hospitals because the software of the heart monitor glitched or misread a sensor. Can we get on those problems instead?
Do you have any idea how current problems actually get decided for in industry (not only software, but in general)? It's not "this problem gets tackled because it's cool", it's because of money. Do you think bright software engineers love working on Microsoft Word or better AdSense because they think it's fun?
Also, this sounds really stupid to say, but this seems to be what you're implying when you say "keep play out of work": do you really think the same people working on embedded systems for heart monitors are the ones writing LISP interpreters...somehow...at work?
> Except, the millionth LISP interpreter is a hobby project, that people are making on their own time, not during work?
You are likely correct though I still have my doubts, I've encountered pretty privileged individuals around here, commanding $250k - $400k a year with practically zero supervision. So I do wonder still.
> Play is an important part in learning. The millionth LISP interpreter, game engine, whatever is fine. From my experience, the people building these things gain a lot more valuable experience than just doing college or even just having a prior job.
True, I am simply jaded that everyone is always "learning" and I don't see much progress in almost any area in programming. We still tip-toe around outdated concepts and implementation that people are too afraid to touch and start revising. It has gotten infuriating as I get older and older.
> It's not "this problem gets tackled because it's cool", it's because of money.
Oh I know, believe me, and here I am not faulting the programmers, I am faulting the completely broken system that is so detached from the problems that this race needs solved that they might as well live in an adjacent solar system...
> Do you think bright software engineers love working on Microsoft Word or better AdSense because they think it's fun?
You haven't seen the long diatribes of people working there who build a mental labyrinth and go out of the other side they are doing good. I wish I could forget seeing these comments, that day my faith in humanity has plummeted, like a lot.
So yes some of them not only see it as fun but also as a good thing to do.
History will judge them but sadly they won't be alive at that time.
> Also, this sounds really stupid to say, but this seems to be what you're implying when you say "keep play out of work": do you really think the same people working on embedded systems for heart monitors are the ones writing LISP interpreters...somehow...at work?
See above. I am sure some do.
> There's also something that plagues HN and it's that they think the software industry is somehow uniform.
I hear you, it's a common defect in human thinking when we get frustrated and I am not an exception, sadly. I am mostly commenting on the usual state of affairs and the most visible parts. Otherwise you are right and I agree with you.
--
All in all, my comment upthread was borne out of long-bottled frustration. I can't see almost any progress in almost any software venue, people are too happy to keep tinkering in their own miniature corner and then emerge on some forum and claim superiority (reference: KDE vs. GNOME forum threads, one of the ugliest human discourse I've ever seen), and in the meantime the entire computing industry is sitting on ancient implementations that only get drivers added (like the Linux kernel; an amazing project that I feel is a shining light of the free software movement... but to this day security is not their priority).
I can go on and on. But the TL;DR is: I really hoped we as a collective area will have more balls. Seems like we're just tame nerds that only do what they're told.
Shame. That's breaking my heart. Hence the frustration.
I hope not. We need more structured approaches, I personally vote with all hands the amount of "play" we do to be drastically reduced, enforced by revoking a professional license even (if our industry ever gets regulated).
I am sick or nerds reinventing wheels because they are privileged and bored. Like I ranted recently here in HN, can we stop with the millionth LISP interpreter already? We have people dying in hospitals because the software of the heart monitor glitched or misread a sensor. Can we get on those problems instead? Like, before the 41th century for example? When will we get to do something genuinely useful that actually, [gasps], helps people?
[takes a deep breath]
First order of business: rework our interaction with the OS the command line, stop all the legacy lunacy of TTY and many others, and figure out one way of doing things. Do it on Linux. If Windows and macOS don't want to play along then too bad, the devs working there will have a miserable time, and that will introduce pressure from them to Microsoft and Apple to play ball.
Let's go. No more nerds. Let's be correctness + simplicity fanatics, I say.
> I hope that this industry turns it around
It will never do that. Let's not forget we are workers paid to produce value. Let's also not forget that IT is always viewed as an undesired cost center -- I hate it as much as every programmer but it's how people view us and curiously enough, that perception is very persistent.
Many people understood we need to "play" to gain more knowledge but these times are mostly over, at least in popular development categories like web and mobile. Most people there -- myself included -- are paid to assemble IKEA furniture, at least 90% of the time. Creative tasks are few and far between, sadly.
> The paragraphs about git were interesting, in the sense that the author themselves suffer from the industry's "I'm right and you're wrong" motto that is the reason, by the looks, that they've left. There is some unresolved conflict there.
As a guy who started 20+ years ago -- like you alluded to these times being more lax (which I haven't observed but then again I never lived in the USA) -- I stand with OP here; appealing to popularity and cult of personalities are sins I didn't imagine the programming area will suffer from, yet it happens every day. Try criticizing one of Python's many obvious pitfalls (no, I will not elaborate, they have been described a million times, including here on HN) and you'll be buried under a mountain of "millions are using it successfully every day, have you considered that you are the problem?". As if the amount of supporters of a thing ever had any correlation at all with quality but hey, don't tell them that (tidbit: burning the "witches" in the middle ages; I bet 99% of the time somebody had a beef with the neighbor lady and they set her up as a "witch" to get rid of her).
--
I share your nostalgia about how things were done long ago but I really hope we emerge more disciplined, structured, and much less bikeshedd-y out of the whole thing.
Play on your own time, not during work.