Ask HN: In the age of AI, what's the most important thing a dev should learn?
13 comments
Welding, foraging, scavenging, hacking, repurposing old junk into shelter and transportation, hydroponics, stealing electricity, small scale farming, digging, ammo reloading, evading AI, creating improvised explosive devices, smuggling, ICE breaking, soldering / electronics fabrication and repair, firearms maintenance, diesel mechanics, broadcasting pirate radio and television...
What is ICE breaking?
> What is ICE breaking?
In this context: me being a little tongue in cheek.
In cyberpunk fiction "ICE" means "Intrusion Countermeasures Electronics"[1] and "breaking ICE" basically means something like "hacking through firewalls / network security". The term was made famous (if not outright introduced by) William Gibson's "Sprawl Trilogy" works, particularly Neuromancer. Amusingly enough the term - while fictional - has actually bled over into real-life usage a little bit.
[1]: https://en.wikipedia.org/wiki/Intrusion_Countermeasures_Elec...
In this context: me being a little tongue in cheek.
In cyberpunk fiction "ICE" means "Intrusion Countermeasures Electronics"[1] and "breaking ICE" basically means something like "hacking through firewalls / network security". The term was made famous (if not outright introduced by) William Gibson's "Sprawl Trilogy" works, particularly Neuromancer. Amusingly enough the term - while fictional - has actually bled over into real-life usage a little bit.
[1]: https://en.wikipedia.org/wiki/Intrusion_Countermeasures_Elec...
anything other than ai slop generation... with every muppet diving head first into llm group fap parties, all the real work still has to get done, especially as people are starting to properly understand that the inherent nature of these black boxes is to produce something that looks rational, but which is subtly woven with bugs that will take longer to fix than if you'd just written simple software from the start; forget "ai" taking your job - it's weeding out the useless "coders" and making those of us who treat coding as a craft even more valuable.
I kind of agree, but I would also argue that of those who treat coding as a craft many are in danger as well. Code in the end is just a tool. Deep understanding won't be replaced any time soon, but I have worked with software artisans who were really effective and ones that saw the code and system as an end in itself. If you're in the latter group I'd be worried.
who treat coding as a craft even more valuable
You probably think this of yourself. So do I.
You see, how do we know this isn't dunning kruger? If Dunning Kruger could talk, this is what it would sound like.
You probably think this of yourself. So do I.
You see, how do we know this isn't dunning kruger? If Dunning Kruger could talk, this is what it would sound like.
Networking, dealing with humans, and all the work involved in building reliable software that solves problems. In the end you still need to think about what you will build and make sure it solves someone’s problems. AI won’t do that for you.
There is no age of ai. Only a period of decent auto complete.
Nothing fundamentally changed in computer science since 20-40 years ago.
Nothing fundamentally changed in computer science since 20-40 years ago.
Compassion, decision making under uncertainty
Code review
Ethics.