5 ms·

> It really saddens me to see some developers talk about literally quitting their careers over AI, right when the benefits of existing deep technical experience

by miyoji 5mo ago

> It really saddens me to see some developers talk about literally quitting their careers over AI, right when the benefits of existing deep technical experience have never been more valuable. 1. Because the experience of interacting with AI is miserable. I like writing code. I don't like finding the magic incantation that gets the machine to write the correct code. I don't like correcting the machine when it gets things wrong. I don't like any of this, it's awful and I would never have gone into this field if someone had told me that it would be like this one day. 2. I cannot condone the means by which these tools were created, which is, as far as I am concerned, theft. I think it's unethical to use them at all, because they were created unethically. I dislike using stolen work, I think it's wrong, and I think everyone who uses it is making the world worse and normalizing theft. If continuing in my career means that I have to compromise my ethics, I wouldn't do it even if I loved this stuff, and see point (1). 3. Is anyone going to pay me more for my "more valuable" skills? Doesn't seem like it, engineering salaries on the whole are going down right now. You can believe they'll go up eventually if you like, but there's no evidence that will happen, or that it's happening. If my employer captures all the value, why should I care whether I'm creating more of it?

echelon 5mo ago
> Because the experience of interacting with AI is miserable. I like writing code. I'm your exact opposite. I've felt like code is 1960's punch card tech my entire career. I've always wanted to do more. So much of coding is plumbing. Or paying attention to tiny little details. Or hunting down stupid bugs. Or changing requirements and refactoring. That shit sucks. All of it. I've never had so much fun with software. It's starting to feel like magic. And because we possess deep understanding, we are uniquely positioned to take advantage of this. The AST is not the objective. The finished product is. Our DNA is by all accounts filled with garbage. Let your feelings about code purity and sanctity go. It's the job to be done that matters. Code is not holy. In 100 years people will look at our ephemeral artifacts as silly little things. Treat it that way today. Means to an end.
- customguy 5mo ago
  "the sand doesn't matter, only the beach does"? Makes no sense. Perfection is achieved when there is nothing left to take away. > In 100 years people will look at our ephemeral artifacts as silly little things Whereas they'll totally admire the hamster wheels in which people shoveled product? Well, I don't care either way. Craftsmanship and care have their own rewards, and shape the person engaging in them for the better.
  - echelon 5mo ago
    > Perfection is achieved when there is nothing left to take away. Perfection in glue and plumbing? That's what 99% of software is. Even active-active distributed systems are glue and exist only to bridge ephemeral infrastructure. Everything will eventually be thrown out and rewritten. Nobody lauds the half-century old banking code written in COBOL. They want it ripped out and replaced. Nothing is "perfect". Not even close. > "the sand doesn't matter, only the beach does"? Makes no sense. The code isn't the sand, it's the sandcastle. > > In 100 years people will look at our ephemeral artifacts as silly little things > Whereas they'll totally admire the hamster wheels in which people shoveled product? They'll hear about "You Tube" and "Face Book", I'm sure. But none of the code that runs either of those things will likely be running or capable of running.
    - customguy 5mo ago
      > That's what 99% of software is. Even active-active distributed systems are glue and exist only to bridge ephemeral infrastructure. Everything will eventually be thrown out and rewritten. > Nobody lauds the half-century old banking code written in COBOL. They want it ripped out and replaced. So? That's true for actual plumbing, too. That changes nothing about the fundamental fact that a pipe that achieves a specific thing with N gram of materials and N meters of pipe length is better than something that is 100x times heavier and goes around the block several times just because why not. > The code isn't the sand, it's the sandcastle. Same difference. It makes just as little sense to say "the sand the sandcastle is made of doesn't matter, only the sandcastle does." > But none of the code that runs either of those things will likely be running or capable of running. Obviously. Who claimed otherwise?

by miyoji 5mo ago

echelon 5mo ago

> Because the experience of interacting with AI is miserable. I like writing code. I'm your exact opposite. I've felt like code is 1960's punch card tech my entire career. I've always wanted to do more. So much of coding is plumbing. Or paying attention to tiny little details. Or hunting down stupid bugs. Or changing requirements and refactoring. That shit sucks. All of it. I've never had so much fun with software. It's starting to feel like magic. And because we possess deep understanding, we are uniquely positioned to take advantage of this. The AST is not the objective. The finished product is. Our DNA is by all accounts filled with garbage. Let your feelings about code purity and sanctity go. It's the job to be done that matters. Code is not holy. In 100 years people will look at our ephemeral artifacts as silly little things. Treat it that way today. Means to an end.

customguy 5mo ago
"the sand doesn't matter, only the beach does"? Makes no sense. Perfection is achieved when there is nothing left to take away. > In 100 years people will look at our ephemeral artifacts as silly little things Whereas they'll totally admire the hamster wheels in which people shoveled product? Well, I don't care either way. Craftsmanship and care have their own rewards, and shape the person engaging in them for the better.
- echelon 5mo ago
  > Perfection is achieved when there is nothing left to take away. Perfection in glue and plumbing? That's what 99% of software is. Even active-active distributed systems are glue and exist only to bridge ephemeral infrastructure. Everything will eventually be thrown out and rewritten. Nobody lauds the half-century old banking code written in COBOL. They want it ripped out and replaced. Nothing is "perfect". Not even close. > "the sand doesn't matter, only the beach does"? Makes no sense. The code isn't the sand, it's the sandcastle. > > In 100 years people will look at our ephemeral artifacts as silly little things > Whereas they'll totally admire the hamster wheels in which people shoveled product? They'll hear about "You Tube" and "Face Book", I'm sure. But none of the code that runs either of those things will likely be running or capable of running.
  - customguy 5mo ago
    > That's what 99% of software is. Even active-active distributed systems are glue and exist only to bridge ephemeral infrastructure. Everything will eventually be thrown out and rewritten. > Nobody lauds the half-century old banking code written in COBOL. They want it ripped out and replaced. So? That's true for actual plumbing, too. That changes nothing about the fundamental fact that a pipe that achieves a specific thing with N gram of materials and N meters of pipe length is better than something that is 100x times heavier and goes around the block several times just because why not. > The code isn't the sand, it's the sandcastle. Same difference. It makes just as little sense to say "the sand the sandcastle is made of doesn't matter, only the sandcastle does." > But none of the code that runs either of those things will likely be running or capable of running. Obviously. Who claimed otherwise?