321–330 of 515 posts
Earlier quoted context omitted.
In the future Claude will keep a tight ship on dissenters. If your monthly quota doesn't exceed the 10k worth of tokens your employer will be notified and you will be flagged as a "dissenter". Your lease will be cancelled, because who would trust someone ignorant enough to not use LLMs in their daily life, and you'll be vetoed from the field for life, for clanker companies will proclaim that anyone who doesn't use LL…
ai skeptic fanfic evolves in fascinating ways every day
Earlier quoted context omitted.
Maybe I’m just getting extremely lucky, but I don’t use AI to code at work and I’m still keeping up with my peers who are all Clauded up. I do a lot of green field network appliance design and implementation and have not felt really felt the pressure in that space. I do use Claude code at home maybe a couple hours a week, mostly for code base exploration. Still haven’t figured out how to fully vibe code: the generate…
> the generated code just annoys me and the agents are too chatty I’ve eyerolled way less with Codex CLI and the GPT models than with Claude.
Earlier quoted context omitted.
This is going to catch some heat, but what if the most important professional “developer skill” to learn or improve is how to effectively use coding agents? I saw something similar in ML when neural nets came around. The whole “stack moar layerz” thing is a meme, but it was a real sentiment about newer entrants into the field not learning anything about ML theory or best practices. As it turns out, neural nets “won”…
> what if the most important professional “developer skill” to learn or improve is how to effectively use coding agents? Well, it's not. There's a small moat around that right now because the UX is still being ironed out, but in a short while able to use coding agents will be the new able to use Excel . What will remain are the things that already differentiate a good developer from a bad one: - Able to review the ou…
Earlier quoted context omitted.
Perhaps the lack of investment in their skills was the cause for the commenter’s job hopping, not the effect.
It's all so vague. "lack of investment in their skill". You just spent $250k and 5 years in college learning stuff. You get hired to do a job for money. What "investment" do you expect company to do? Give me number of weeks and amount of dollars per year and tell me how it stacks against $250k and 5 years that you just spent? If you want to learn on the job, shouldn't YOU be paying the company for teaching you, like…
Earlier quoted context omitted.
I imagine it being a "does anybody know COBOL?!" but much sooner than sixty years rom now.
COBOL also came to mind. The COBOL thing seems to be working out just fine last I heard. Today a small number of people get paid well to know COBOL's depths and legacy platforms/software. The world moved on, where possible, to lower cost labor and tools. Arguably, that outcome was the right creative destruction. Market economics doesn't long-term incentivize any other outcomes. We'll see the arc of COBOL play out aga…
The salaries were ok but not good for COBOL.
Here's an anecdotal Reddit thread about it. https://www.reddit.com/r/developpeurs/comments/1ixfpsx/le_sa...
Earlier quoted context omitted.
> Just because they invented cars doesn't mean you stop jogging. They literally made it a crime to walk down the street.
across the street, no? It's also a crime to jog on the railroad tracks.
If a wagon or trolley hit someone that was considered the fault of the driver, every time.
When cars started arriving and being driven around by people who were wreckless and bad at it, you started getting manufacturers and "motorists" lobbying for the concept and laws around jay-walking. Even the word was a way to delegitimize what used to be normal. "Jay" was negative slang for country-person (think red-neck). The idea was "modern city people stay out of the streets!"
Improving developer skills is not valuable to your company. They don't tell a customer how many person-hours of engineering talent improvement their contract is responsible for. They just want a solved problem. Some companies comprehend how short-sighted this is and invest in professional development in one way or another. They want better engineers so that their operations run better. It's an investment and arguably…
This is going to catch some heat, but what if the most important professional “developer skill” to learn or improve is how to effectively use coding agents? I saw something similar in ML when neural nets came around. The whole “stack moar layerz” thing is a meme, but it was a real sentiment about newer entrants into the field not learning anything about ML theory or best practices. As it turns out, neural nets “won”…
Doing so will effectively force a (potentially unwanted) career change for many people and will lead to the end of software engineering (and software as a career), assuming AI continues to improve.
"Effectively" using agents means that you're writing specs and reading code (in batches through change diffs) instead of writing code directly. This requires the ability to write well (or well enough to get what you want from the agent) and clearly communicate intent (in your language of choice, not code; very different IMO).
The way that you read code is different with agents as well. Agents can produce a smattering of tests alongside implementation in a single turn. This is usually a lot of code. Thus, instead of red-green-refactor'ing a single change that you can cumulatively map in your head, you're prompt-build-executing entire features all at once and focusing on the result.
Code itself loses its importance as a result. See also: projects that are moving towards agentic-first development using agents for maintenance and PR review. Some maintainers don't even read their codebases anymore. They have no idea what the software is actually doing. Need security? Have an agent that does nothing but security look at it. DevOps? Use a DevOps agent.
This isn't too far off from what I was doing as a business analyst a little over 20 years ago (and what some technical product managers do now for spikes/prototypes). I wrote FRDs [^0] describing what the software should do. Architects would create TRDs [^1] from those FRDs. These got sent off to developers to get developed, then to QA to get bugs hammered out, then back to my team for UAT.
If agents existed back then, there would've been way fewer developers/QA in the middle. Architects would probably do a lot of what they would've done. I foresee that this is the direction we're heading in, but with agents powered by staff engineers/Enterprise Architects in the middle.
> Edit: as an aside, I have learned plenty from reviewing coding agent generated implementations of various algorithms or methods.
People learn differently. I (and others) learn from doing. Typing code from Stack Overflow/Expertsexchange/etc instead of pasting it, then modifying it is how I learned to code. Some can learn from reading alone.
[^0]: https://www.modernanalyst.com/Resources/Articles/tabid/115/I...