Eric Kennedy

Context Manager. Writing about software and AI. Intuit. Ethos Life. A few other places. Egg avatar until I find a picture of me less than 700kb.

[Eric Kennedy @EKeric13]

The reason why I think bad AI writing bugs people so much - it is genuinely disrespectful to ask someone to put effort into reading something you couldn’t be bothered to put an ounce of effort into writing...

[Eric Kennedy @EKeric13]

"Tech debt" is actually a great name because debt is not always bad. Sometimes it is good! We take on debt to buy a house, to buy a car, and in the most American tradition possible, sometimes we take on debt to ship software faster.

[Eric Kennedy @EKeric13]

@bcardarella As long as they are in the lead they get to. If their lead slipped they will have to be backwards compatible with other companies standards in order to win users.
Internet explorer use to do wacky shit until they lost market share for example.

[Eric Kennedy @EKeric13]

@IgorZIJ @swyx yes i have moved specific instructions into project scoped skills. and then globally useful instructions have moved to global skills.

there is a place for agents.md but it is slimmed down.

out of date agents.md/skills is another problem separate from the value of agents.md

[Eric Kennedy @EKeric13]

@HamelHusain just wrote about this actually - with the thesis of being it is just so disrespectful. the focus is more on the work place than on social media though

https://t.co/3FtcfzpYrv

[Eric Kennedy @EKeric13]

The reason why I think bad AI writing bugs people so much - it is genuinely disrespectful to ask someone to put effort into reading something you couldn’t be bothered to put an ounce of effort into writing...

[Eric Kennedy @EKeric13]

@NoemiTitarenco I really like project specific skills. Use those all the time. Have specific use case skills I toggle on and off if the use cases arises. For general skills I had up to 10 but down to like 3. As the models have improved I have needed less.

[Eric Kennedy @EKeric13]

Had they simply read the response before sending it, they would have realized the LLM was telling them they needed to do the tiniest bit of thinking themselves.

[Eric Kennedy @EKeric13]

The reason why I think bad AI writing bugs people so much - it is genuinely disrespectful to ask someone to put effort into reading something you couldn’t be bothered to put an ounce of effort into writing...

[Eric Kennedy @EKeric13]

```
The PR is well structured and handles X, Y, and Z effectively.
A few improvements could be made to Y by doing A or B.
The author is also asking for guidance on how to handle X. You'll still need to provide your own perspective on that.
```

[Eric Kennedy @EKeric13]

@iamdevloper Reading all of my own code but no longer all the code I review during PR review.

[Eric Kennedy @EKeric13]

@trikcode I think the best way is to just create artifacts as you go along. I get your point that it is hard to know when you will be rate limited.

I think the next best way might be to pull out your conversation history with one agent using another agent.

https://t.co/SeB9rTUa31

[Eric Kennedy @EKeric13]

@joshelman Wait is the new Siri good? If so they might need a rebrand honestly. The Siri name has turned into a punchline

[Eric Kennedy @EKeric13]

We have gone from GPU poor to token poor. Era of pay for play software arriving faster then I thought.

[Eric Kennedy @EKeric13]

That said, generally the right answer is probably still to cut features. haha.

[Eric Kennedy @EKeric13]

A software engineering truism that feels weaker now after AI codegen:

Brooks’s Law from The Mythical Man-Month - "Adding manpower to a late software project makes it later"

[Eric Kennedy @EKeric13]

no longer is the equation:
1. Cut features (generally the right answer)
2. Delay release

But now there is a valid third option:
3. Throw another engineer at the problem.

If they are skilled and you develop in an AI friendly manner they should slot right in.