Chris Headley

Today I used the term “brain vomit” in a meeting to describe what I’m doing in creating Copilot instruction files. I’ve used coding agents enough to know that while useful they have a tendency to use patterns I don’t immediately recognize and understand; or even like. I’m still just not comfortable giving agents large features to complete. I also personally find reusing common patterns and practices, whether solo or on a team, reduces overhead in reviewing, debugging, and making modifications. If you’ve ever had to work with many different teams with their own significantly different patterns and practices you’ll understand how much time gets wasted just trying to understand what you’re looking at. I’ve begun dumping (brain vomiting) my common preferred patterns and practices into instruction files. I structure my Lambda function files and the code within them in certain ways. I configure my DDB tables with a primary key named `pk` and sort key named `sk` while primary key values are prefixed with an item type. I almost never use the `Name` property on a resource in a CFN template. All of these are practices I developed for one reason or another and were often born out of lessons learned over time. To do this I started by using the Copilot CLI’s `/init` command in repos to generate instruction files based on the patterns the tool observes in my work. From there I’ve taken the instructions from the CLI’s output and used them to populate new instruction files targeted at specific technologies. (I prefer small topic based instruction files over large monolithic instruction files.) Next I’ve added more instructions based on memory or my own browsing through my projects. Finally I’ve been asking Copilot to suggest ways to simplify my instructions. My goal is to soon start creating coding agents with enough context that they are outputting code and building entire services in familiar looking ways. This lets me focus on evaluating how well the output functions and solves a problem rather than time spent figuring out how the output works and looking for subtle gotchas. Anyways, here’s the start of my collected patterns and practices. They’re mostly aimed at AWS serverless architectures. https://lnkd.in/esP6Jm5C #AWS #GitHub #Copilot

10

4 Comments

Don’t build features that nobody needs right now. Don’t write more specs than you can code. Don’t write more code than you can test. Don’t test more code than you can deploy.

1

Anyone else noticing a vast majority of the people heavily advocating for AI to replace software engineers aren't engineers themselves? Most I see are some form of business major or C-suite member pushing for the replacement of engineers. While AI and the tools built around it are getting pretty good, with even the ability to quickly prototype ideas, it's not replacing anyone yet. For a while now, I thought only the big tech FAANG companies were pushing this narrative, but no, it's business owners at all levels.

231

81 Comments

Finish this sentence: Advising teams who do not write tests when developing software to adopt Trunk Based Development is akin to ____________________

1

3 Comments