As the sibling pointed out, there are already plenty of laws about, for example, handling of personally identifiable data. Somehow there is a lack of awareness, perhaps what is needed is a couple of high-profile convictions (which can't be too far off).
One of the key functions of a professional body is to ensure all members are aware of existing and new laws, standards and codes of practice. And to ensure different grades of engineer are aware of different levels of the standards. And that sector-specific laws and standards are accredited accordingly.
High profile convictions are not a good way of dealing with this. Not in the short or long term. Sure they have an impact, and laws should be enforced, but that’s not a substitute for managing the industry properly.
Nothing would be more effective at killing open source and commercial software business that requiring everyone that writes and ships software to users, directly or indirectly (e.g. an open-source library) to have License To Program from Software Licensing Organization.
> aware of existing and new laws, standards and codes of practice
Yeah, because software business is not at all ruled by fads.
1997: you have to follow Extreme Programming (XP) or you don't get your license
2000: you now have to use XML for everything in XML or you don't get your license
2002: you now have to follow Agile or you don't get your license
2025: you now have to write everything in Rust or you don't get your license
A software engineering licensing body would require licensed individuals to understand things about security and accessibility, which would be a huge improvement. If you are responsible for a trivial security vulnerability you and the company should actually be liable for it.
Sysadmins/other adjacent roles should likely have the same requirements. An unmaintained/unsecured server can create a huge liability.
I know, through personal acquaintance, of at least one boutique accounting firm that is currently vibe-building their own CRM with Lovable. They have no technical staff. I can't begin to comprehend the disasters that are in store.
Generally why build your own CRM? ERP and other resource planning systems I get becouse you can tailor made those to your back office. But for CRM you need mostly reliability.
It's a commercial act, the 'punk' costumes carefully chosen for the right signalling, by a couple of middle class kids. What's with this idea that your taste in music must spring from the purest and rawest authenticity, preferably (in no particular order) poor, rebellious, substance abusing, ethnic, and so on. Leading to all these musical acts styling themselves like that.
The Ramones were sellouts and posers, just like most bands. Wearing them on a t-shirt to signal 'punk', the joke's on you. It's an "industry of cool", like Jack Black's character says in Almost Famous.
Was Jack Black in Almost Famous? Are you thinking of PSH. I've mixed them up in my head myself, and I have no clue why. I was a Tenacious D fan from day 1, so it's not like they're 2 actors I'm only vaguely familiar with. And they aren't super similar in many ways. Yet they're somehow interchangeable in my movie memories.
How delightfully cynical. Instead of thinking taste in music “must” spring from your cynical take on what authenticity us (which I agree is impossible to define and almost a useless term at this point), maybe people just… like the music, and it somehow speaks to them. Musical taste is famously subjective and entirely down to what music you heard before etc
Back in business school they used to tell the story of how makers of razor blades would put a good blade as the first and the last blade in the pack. I suspect the LLM services of doing something like that.
Nobody ever wanted to wire up RPC endpoints, in the form of Enterprise JavaBeans(tm), using XML files. That is one for the history books of ridiculous technology.
XML files are bad. Invisible magic is worse. The sensible way to wire up a bunch of RPC endpoints is, like the sensible way to do most things, plain old code.
Did everyone just agree to forget about Gradle? It was everywhere not too long ago. I think I even prefer it to Maven, in a choice between a rock and a hard place type of way.
That's what I am doing too, though I did have to drill out some wall to fit it, in some cases.
There is another option that I don't think many people are aware of: You can put a battery powered relay downstream of the (dumb) switch, and have it broadcast events when power comes on and off, to control other smart devices, which just have to listen for the events (via a broker like HA).
reply