That makes sense. Software engineers have gone from being artists (because yes, software architecture is an art) to becoming AI managers. It’s demoralising.
I believe open-source software will continue to provide a refuge for artists.
Yup. I’m watching my artform die in real time. Not only will my career no longer exist in the form I enjoy it, but the art form itself will die. Nobody is going to appreciate artisan code like they do other forms of art.
I wholeheartedly agree with you that code can be art but I was never able to express myself on that level at my corporate jobs. I was always limited to writing code that aligned with the company’s rigid style guide, and never allowed to implement new design patterns that would’ve improved things but deviated from the way things were done in the existing codebase.
Thus, I’m not too miffed about being forced to use coding agents at work because writing corporate-sanitary code already felt like a robotic process before LLMs existed. Personal hobby projects and open source contributions are where we can express ourselves freely and create our art the way we want to. They’ll never be able to take that from us.
You worked places with style guides? Did… Did you have a real testing environment that wasn’t prod too?
I got taken off a project recently for being too direct about how the rest of the team was just spray and praying entirely AI generated code with no standards or review whatsoever, and they were charging ahead like it was a race to implement features we hadn’t even discussed if we wanted/needed.
If you can’t tell me how it works, you can’t confirm that we actually need it, you can’t tell me the upstream and downstream effects (or confirm they don’t exist), and you can’t even confirm that we even want it to do the thing it only supposedly does, then we have better things to do than go on a wild goose chase trying to debug it when there’s a looming deadline for things that legitimately do not work that we need. Stop vibe coding and actually review the existing shit for fucks sake. If the requirements have never been clear, solve that instead of generating more slop. Maybe update some of the existing documentation instead of having AI wholesale hallucinate entirely new not quite right ones over and over.
Anyway, please tell me more happy development bedtime stories. I need to chase away the nightmares.
You worked places with style guides? Did… Did you have a real testing environment that wasn’t prod too?
Yes, and the style guides reached far beyond things like “use camel case”. I’m talking guidelines for how whole blocks of code should be formatted. Also weren’t allowed to throw exceptions at all even though we were using up-to-date modern C++. Some guidelines had good intentions and others were just put in by OCD control freaks that no one felt like opposing.
And yes, we had a testing environment, although we mostly depended on manual QA rather than software tests. Medical devices can’t test in prod, fortunately
There are many C++ features that make the language worse. Exceptions is one of them. It’s not strange to have them banned.
Critical systems often only allow you to use a subset of the language. Dynamic (heap) allocations, recursive functions, exceptions are features that are often banned. In medical devices, safety is critical, so it makes sense. Otherwise you could get a Therac-like scenario due to an unhandled exception.
for the last three years and a bit, silicon valley has promised eradication of everything from writer to filmmaker as a career. after all this i don’t think that devs get to hitch their wagon to artists for sympathy points
That makes sense. Software engineers have gone from being artists (because yes, software architecture is an art) to becoming AI managers. It’s demoralising.
I believe open-source software will continue to provide a refuge for artists.
Yup. I’m watching my artform die in real time. Not only will my career no longer exist in the form I enjoy it, but the art form itself will die. Nobody is going to appreciate artisan code like they do other forms of art.
Yes. My work is open source, and pretty unchanged. We get some AI pull requests now that take longer to review than doing the work ourselves.
I think a key difference is that there was never any tolerance for bullshit in my team’s code base.
We don’t have thousands of points of boilerplate, or a big pile of “not invented here” crap code.
So we don’t have somewhere for the AI to really shine.
I wholeheartedly agree with you that code can be art but I was never able to express myself on that level at my corporate jobs. I was always limited to writing code that aligned with the company’s rigid style guide, and never allowed to implement new design patterns that would’ve improved things but deviated from the way things were done in the existing codebase.
Thus, I’m not too miffed about being forced to use coding agents at work because writing corporate-sanitary code already felt like a robotic process before LLMs existed. Personal hobby projects and open source contributions are where we can express ourselves freely and create our art the way we want to. They’ll never be able to take that from us.
You worked places with style guides? Did… Did you have a real testing environment that wasn’t prod too?
I got taken off a project recently for being too direct about how the rest of the team was just spray and praying entirely AI generated code with no standards or review whatsoever, and they were charging ahead like it was a race to implement features we hadn’t even discussed if we wanted/needed.
If you can’t tell me how it works, you can’t confirm that we actually need it, you can’t tell me the upstream and downstream effects (or confirm they don’t exist), and you can’t even confirm that we even want it to do the thing it only supposedly does, then we have better things to do than go on a wild goose chase trying to debug it when there’s a looming deadline for things that legitimately do not work that we need. Stop vibe coding and actually review the existing shit for fucks sake. If the requirements have never been clear, solve that instead of generating more slop. Maybe update some of the existing documentation instead of having AI wholesale hallucinate entirely new not quite right ones over and over.
Anyway, please tell me more happy development bedtime stories. I need to chase away the nightmares.
Yes, and the style guides reached far beyond things like “use camel case”. I’m talking guidelines for how whole blocks of code should be formatted. Also weren’t allowed to throw exceptions at all even though we were using up-to-date modern C++. Some guidelines had good intentions and others were just put in by OCD control freaks that no one felt like opposing.
And yes, we had a testing environment, although we mostly depended on manual QA rather than software tests. Medical devices can’t test in prod, fortunately
There are many C++ features that make the language worse. Exceptions is one of them. It’s not strange to have them banned.
Critical systems often only allow you to use a subset of the language. Dynamic (heap) allocations, recursive functions, exceptions are features that are often banned. In medical devices, safety is critical, so it makes sense. Otherwise you could get a Therac-like scenario due to an unhandled exception.
That’s a great story. https://ethicsunwrapped.utexas.edu/case-study/therac-25
for the last three years and a bit, silicon valley has promised eradication of everything from writer to filmmaker as a career. after all this i don’t think that devs get to hitch their wagon to artists for sympathy points