952 karma · joined January 18, 2014
[1] https://en.wikipedia.org/wiki/Stanford_marshmallow_experimen...
On a similar note, as a Frenchman, I felt somewhat closer to the Japanese described in "The Chrysanthemum and the Sword" by Ruth Benedict than to the Americans, although the Japanese are the "aliens" from the point of view of that book.
For example, write a skill that finds some kind of code smell, say duplication, and generate a report. Give it some supporting scripts.
Then, use this report to file a few tickets. Then make the agent fix those tickets. Then, as you grow confident, automate more of this process.
It does not replace human supervision but it may enhance it. Especially in a team where people start generating PRs faster that anyone can review them.
Continue this improvement process long enough and you may find yourself with an AI Software Factory.
It is useful. It may be dangerous. It has an impact. I care about that.
Indeed I realized recently that, when we complain about LLMs producing slop, that's in part because we dont ask them to refactor.
Coding agents won't, on their own, make a big change the user did not ask for. And this is fine.
I am surprised this is not already the case.
Edit: or even better "this is not possible because X"
(Edit: assuming you are human)
What's the point of being human if we dont do human things but entirely rely on AI?
I believe this is more or less these mathematicians' argument.
Of course, it'd be better to not regulate, keep LLMs users reponsible and publicize this reponsibility in order to mitigate damage. But if this is not enough then we will have to move the needle somehow. Similarly to guns, drugs and so on.
Would they cool earth in such a way that it would offset carbon dioxide uniformly or would it lead to even more change ? Climate change is undesirable, wether or not Climate warming is invloved.
Surely it is reasonable, but also way more than our budget. Id like to compare.
The issue is, if he generates all of that without reviewing the code, he will always be far faster than us. And he can't review the code. No matter how he slices it.
Also, he is the CPO/CTO. So we can say no, but there is a natural incentive to go his way. He still doesn't feel confident enough to just bypass the programmers and he's probably right. But it'd nice to find a way to use my expertise to review this amount of code meaningfully, somehow.
What techno/service did you base your framework on? How long did it take to set it up? How many are you?
In our team, frontend work is vibe-coded by the PO and merged as-is without review. Backend is coded by developers, using AI but in a slower, more controlled way.
Recently, our PO has been trying his hand at vibe-coding the backend. I must say he is a smart guy, almost technical but not quite a developer. We've just been handed a burst of stacked PRs amounting for ~15k LOC backend. We do not quite know what do to about it.
I know we are not the only ones in the situation. What's your experience and context ? What do you do ? What works for you what doesn't ?
One might wonder (wrongly) why everyone should care about the special and expensive needs of a few (or old) people when designing public spaces.
But a majority will actually need to use these spaces with a baby stroller. Not a few. Baby strollers are a driving power of our society! Enable them!
And what if many lawnmowers started killing/injuring people ?
And what if this a known behavior detected during QA, but the robots are sold anyway with a disclosure ?
And consider your state of mind after the tech came over 6 times in a week, each time claiming to have fixed your HVAC but it keeps breaking.
When it is 40C max by day and 22C min by night, for example, the outside is still cooler than the inside at night. So ventilating will have a real impact.
With this you might reach 25-26C inside in the morning and 29C by the end of the afternoon. It is hot but generally OK with fans, depending on humidity.
Then you can turn the AC on during daytime on top of that, which makes more sense than relying only on it.