Like imagine if your hobby was cooking, but you hated the cleanup. If you buy a robot that automates the fun part at the cost of making twice the mess, that is not a good trade off no matter how many extra cookies you end up with.
We’re kind of at the fast food point: before LLMs, bring successful at all in software required some level of skill (witness all of the companies getting very expensive write-offs from off-shoring or big consultancies trying to save on payroll vs. staff), kind of like how the small cafe/bakery model needed to have at least some level of craft to have something people would buy before the option of making food at a factory and shipping it became an option.
The workers will see the fun evaporate but now they have to clean 10x cookie trays in the same 8 hours.
I'm lurking around the OpenBSD mailing list and it seems that code review is where collaboration starts. You send a patch, explain its purpose, people try it out and comment. If it's OK (various factors decide that), it's imported inside the codebase.
The main issue in corporate settings is that the author of the PR wants to browbeat you into accepting his/her changes. Either directly or by appealing to the manager. They don't want collaboration, they just see you as the blocker between them and the "Done" status on the ticket.
That’s an interesting framing. I’m not sure I agree with your strong conclusion but that’s mostly because I think there’s a second axis about maintenance – you can make a grand strategy game in a couple months but it’s harder to make it balanced, fun, and to keep shipping updates which players like. A prototype or hobby experiment doesn’t have that problem nearly as much and I think that’s where we see such bimodal reactions where some people think it’s a huge productivity boost and others see modest or even negative results.
An online community works when participants learn and share knowledge gained. Contests, with self or others, disrupt learning and sharing, hence by definition constitute "bad behavior". If it exists, the hyperwar you allude to will harm communities more than all LLMs combined could do.
It's hell for my ADHD, personally. It's an infinite rabbit hole generator and distraction machine. I have to use browser extensions to filter out stuff like Stack Exchange suggestions for interesting topics, too. I have had to block Wikipedia in the past to avoid rabbit holes there
I'm better now than I used to be but I am skeptical of people who claim to both be good at multi-tasking and also have ADHD. My experience with ADHD is that multi -tasking is not a strength, it's a sign of distraction
Interesting point of view from one who's been there. Intuitively the comment makes a lot of sense.
In a way human multitasking resembles how single-threaded computer programs work. That is, we focus on one task at a time but tasks can be interleaved to give an illusion of doing several tasks at the same time. Managing several tasks requires remembering the next step to do when leaving one task to attend to another.
That suggests ADHD people lose track of where they left off when performing several tasks. Distraction plays a role, but I think problematic working memory is the major issue. Among ADHD researchers there's a saying, "people with ADHD know what to do but don't do what they know." ADHD task performance may improve with proper treatment.
Not quite. At least not for me. My problem is hyperfocus. If I switch tasks I might go down a rabbit hole and forget to change back. It is similar to being distracted, except the distraction can still be legitimate work stuff. My focus is like a freight train, it's hard to change tracks
Which can seem like an attention problem when you're trying to change me from focused code mode to "jump on a call" mode
Agents let me complete things in parallel all the time.
They also let me build tools that manage all the attention-grabbing things in my life. Something I've been meaning to do "tomorrow" for a good decade.
I've already built custom notification tools for all the "I'll just quickly check hn/lobste.rs/tildes/whatever" so that they'll tell me if there's something actionable, closing down the rabbit hole for me. My email is pre-filtered by an agent that pings me if there's something urgent. My IRC client is custom-built for the specific way I use it etc etc.
Care to share it?
I still do start from bottom up to refactor everything into workspace members and this way, parallelism is way easier
> LLMs reward seeing forest instead of trees.
Not just forest. LLMs reward seeing structures and designs, and it still requires a lot of creativity to design it well. I have to do a lot of architect works for that, like package layout, testing strategies (BDD vs TDD vs E2E), setting up access to platforms and digging out what strategies to apply...etc.
> People focused on the trees will however lag behind as implementation details matter less and less.
Trees like demonstrations and example code are even more important. This is because those are literally post-training materials for the LLMs
> Specialists will be fed to the model weights
I don't think so. New labor laws are certainly going to be introduced by the politicans to tackle this.
> generalists will inherit the world.
Now the problem is how far do you want to stretch the systemic thinking, and you also get burned out quicker.
But I don't want to use AI to code, in large part because I iterate on ideas by working directly with code. Attempting to program through an LLM intermediary becomes like attempting to eat using soft silicone chopsticks.