21–30 of 31 posts
And I still enjoy the process actually. It's a different process indeed. But times change, and you can't always do the same thing forever.
This asynchronous engineering progress has allowed me to do more householding in between. It maybe sounds crazy, but I feel it helps me organise my life better. For me it won't cause any burnout anyway.
Earlier quoted context omitted.
"Writing code was slow but you understood what you built. " Yes. Definitely. I never did try and error with code snippets from the internet until something sort of worked. I never hacked things together like this till the sun rose and had no idea 2 weeks later who wrote that hacky mess and why like this. Or well, years later. And as the code piled up and side problems took over, I certainly did not reimplemented the…
You do realise this is your experience, and just outs you as a mediocre engineer and doesn't prove that slow and steady doesn't win the race, right? Or did you write your comment with an intentional self-demeaning note, and not a sarcastic tone?
And this doesn't cover the scenario of code reviews. If, in the example, Ben and Alice are reviewing each other's code - Ben now has twice as much code to review as Alice does, so her AI usage also affects him negatively.
Earlier quoted context omitted.
You do realise this is your experience, and just outs you as a mediocre engineer and doesn't prove that slow and steady doesn't win the race, right? Or did you write your comment with an intentional self-demeaning note, and not a sarcastic tone?
Since we out here doing ad hominems: if you don't think the code you wrote a few months ago is shit, you're already cooked, and judging by that comment, I'm betting you're crispy. Even the best code I've ever written rots, not because it changes but because I get better. Now... I know thinking out of the box is hard... but one can get better a lot of different ways, and call me an optimist, but I'm betting folks can…
My only thought is take your time to actually review what the LLM/Agent generates... ensure that you understand and can follow it. Give feedback and iterate as necessary. I've used this analogy a lot, but it's really a lot like managing remote development teams in a lot of ways... and even though you can also use agents for planning, it becomes a critical step as part of the communication loop when you aren't sharing…
Charming praise for Anthropic’s low rate limits. It’s a selling point over codex I hadn’t thought of.
I'm not running a bunch of agents in parallel as I actually review/track most of what is getting done while it's happening.. sometimes I'll stop/rollback and rerun with updated instructions. I can't imagine anyone actually doing meaningful reviews of code generated by a half dozen agents running in parallel for example/contrast.
That said, I mostly stand by my statement... at least in how I've been using AI lately.
Personally, I experienced something different. Before AI, it was the managers who gradually took away the joy and tried to fundamentally alter the profession... AI brought much of the joy back. Until some upstream roles discovered AI and used it as leverage to send larger volumes of bullshit downstream. I got away, sadly some people could not.
Earlier quoted context omitted.
Since we out here doing ad hominems: if you don't think the code you wrote a few months ago is shit, you're already cooked, and judging by that comment, I'm betting you're crispy. Even the best code I've ever written rots, not because it changes but because I get better. Now... I know thinking out of the box is hard... but one can get better a lot of different ways, and call me an optimist, but I'm betting folks can…
The code I write is pretty good, and it stays good throughout the years because it was already good. If you're frequently finding month old code to be shit, your code is just shit to begin with.
Earlier quoted context omitted.
The code I write is pretty good, and it stays good throughout the years because it was already good. If you're frequently finding month old code to be shit, your code is just shit to begin with.
Or .. you are working in an unstable environment. If the system you take as a base changes frequently(like the web), your code becomes bad, outdated code, no matter how shiny it was before. But if it was good, migration and maintaining it is easier.
Earlier quoted context omitted.
Or .. you are working in an unstable environment. If the system you take as a base changes frequently(like the web), your code becomes bad, outdated code, no matter how shiny it was before. But if it was good, migration and maintaining it is easier.
React is 13 years old
Are you implying I should have switched to react 13 years ago, when it was just another framework who come and go?
And then my experience would have been stable?
(I kind of doubt it, when my unstable web experience was caused by changes into how canvas works, webrtc, indexeddb, webgl, webgpu. I don't make simple UI's)
Or well, just that "let" was introduced makes all my beautiful old code with only "var" bad code by modern standards.
Earlier quoted context omitted.
React is 13 years old
So? Are you implying I should have switched to react 13 years ago, when it was just another framework who come and go? And then my experience would have been stable? (I kind of doubt it, when my unstable web experience was caused by changes into how canvas works, webrtc, indexeddb, webgl, webgpu. I don't make simple UI's) Or well, just that "let" was introduced makes all my beautiful old code with only "var" bad code…
My point is that the web is not really an unstable platform anymore, it's just something people say that used to be true. Also using var and other superceded constructions doesn't make the code bad; that's not what bad code is. I think you know this.