Gregory Fisher retweeted
I worked with a group of engineers to create github/lever - a library of skills for automating boring work so that us humans can focus on the things we love.
We pooled our session history, mined it for the patterns that produce the best results, and turned them into low barrier skills.
For half the year the sickly sun is seen,
The other half thick night lies on the land,
A country bleaker than the polar strand;
No beasts, no brooks, nor any shred of green.
Gregory Fisher retweeted
time and time again i fall into the trap of designing a big piece of infra with an agent, only to find out that my context window is smaller than the agent's.
i keep forgetting things that were already discussed, while clanker mcclankerface knows all the things.
Gregory Fisher retweeted
Been a busy month.
Join the waitlist at zoah.com
Gregory Fisher retweeted
In the pre-agentic era my view was that the main purpose of the code was communication between team members. This doesn't really change for me in the agentic era, at least not yet. So I prefer the code to be clear and understandable, and that's not really that hard to achieve by following the ideas and principles of modularity, high cohesion, loose coupling, separation of concerns, good naming, right amount of engineering.
The problem in my view was that most folks went between two extremes. One were pre-agentic sloppers, and others were overcomplicating the code design for the sake of the design (often appealing to the authority of self-proclaimed relatives & such). The latter camp definitely made the code more complicated than needed.
But I disagree with the premise that a well-organized code has a cost. Code is information, and organizing that information is to me an essential part of my job.
