AI Driven Development
Published: ....
Last modified: ....
Share this post on BlueskySee discussion on Bluesky
Over the past week or so I’ve taken some time off work (for a friends wedding) and found myself with a bit of free time - so I figured I’d work on a side project. The idea of project was still pretty fresh, and I figured that I’d try to lean into using ChatGPT to help me build it out.
Before digging in, I have been thinking more and more about AI as of late, I’m still really new to whats available and how it all works, but I’ve been trying to use the available integrations where I can. I pay for the upgraded version of Notion to use their AI integration (which I honestly haven’t really used all that much yet), I also pay for the upgraded version of Raycast with their AI version (which I’ve so far found to be really direct and straight to the point - I’ll talk a bit more about this later on in the post), and mainly I’ve been using ChatGPT.
I’ve formed some rough thoughts that I wanted to try and put them all into a post on this blog - I may revisit some of these in the future, but we’ll see!
Thoughts on AI in general:
It’s pretty decent, but I feel like I haven’t found a really solid fit for how it can wedge into my workflow. I don’t often need to write creative prose pieces which feels like where it really excels at the moment. However I do want to continue to give it a lot of thought and experimentation. There have definitely been many times where I’ve thought that different workflows that I do for work could be made more efficient, but it feels like no one is exploring them yet (at least not publicly).
A core example that comes to mind, and is also top of mind for me at the moment is an AI backlog assistant.
I want something that crawls our backlog, triages inbound requests, helps us to answer why we approached a problem in a specific way when looking back on it, and also helps us to better understand how we can tackle work.
I feel like this would greatly benefit from being integrated into not only our project tracker, but also Slack and GitHub where we have most conversations and where most of our work happens.
I’m sure I’ll have some more thoughts about AI use cases in general, but for now I want to dig into the focus of this post, which is how it works for web development.
Thoughts on AI for web development:
I’ve tried GitHub Copilot in the past for about a month or so (basically the free month that you can get from GitHub), and at the time I felt like it didn’t really fit into my workflow all that nicely. It felt like a slower version of the features/benefits that I got out of the TypeScript Language Server in VSCode[1]Jump to footnote.
This past week or so however I dug into a new project using Go lang and SQLite
leveraging only ChatGPT (v3.5, I haven’t purchased the 4.0 variant yet).
Overall, I enjoyed the setup quite a bit - it was nice to be able to talk to
someone something about the problem that I wanted to solve, and have it
work with me to write the code and implement changes.
There was definitely some friction - at best it felt like pairing with a junior engineer, but not a great pairing session in that. I often needed to ask the question two or three times for it to actually do what I wanted. Only about 4 or 5 times during the work of the project did I feel like I hit a wall and I just needed to implement the changes that I wanted to do manually.
Another point of friction for me was needing to go back and forth between my editor and my ChatGPT tab, including several times of pasting in the error / code I had to keep it up to date on what the code looked like after I made some changes. I think that GitHub Copilot now offers a chat like feature that knows about the state of the codebase, so i think that would improve the iteration cycles a bit more also.
In Summary
Overall, the experience was pretty neat - I definitely want to lean on ChatGPT more for working on more greenfield projects. I think the place where it really excelled was that I was fresh to the project as well - so I could discover the problem space and the eventual solutions as well while working with it. I feel like it would be relatively complex to dive into an existing large project and have it up and running and providing valuable feedback along the way. Maybe when it has a deeper integration into the codebase and the history of the project then it would be able to be a reliable assistant.
👆Back to reference I do wonder if that opinion would have changed had I start using it in a language that I don’t know as well, such as Go lang.
Tags:
Related Posts
Development
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
Is it a good or a bad thing to offload writing code to AI agents and Large Language Models?
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
How to generate a custom Ghostty theme based on any iterm2 theme!
Published: ....
A rough mental model for how you should be leveraging AI as a tool for your own growth
Published: ....
Even more thoughts on dogfooding!
Published: ....
The secret to excellent product teams is using your own product, and often!
Published: ....
(Ab)using Git as yet another tool for thought!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
webpack, and tools built on it like Next.js, don't support true dynamic imports, but I found a way to trick the system!
Published: ....
I've been using a variety of AI tools as of late, I figured I'd document the ones I'm primarily using!
Published: ....
I've started to use Cloudflare to manage my domains for several side projects, have had to jump through the same hooks multiple times that I figured I should document them here!
Published: ....
Revising my previous blog post on React Error Boundaries and my preferred go-to implementation!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
When did semver major changes become so scary?
Published: ....
No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few quick thoughts on burn out and taking a break
Web Development
Published: ....
Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
A brief overview on how we launched The Bikeshed Podcast, including a deep dive in our recording and distribution workflows!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Some rough thoughts on building a file-system routing based web application
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
A quick way to handle resetting internal state in components when a parent form is submitted!
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
A quick look at a small but powerful pattern I've been leveraging as of late!
Published: ....
A proposal for a minimal variant of TypeScript!
Published: ....
Sharing a few core recommendations when working within monorepos to make your life easier!
Published: ....
This is a quick post noting that Next.js should now work with Deno v2!
Published: ....
React components have a fundamental contract that is often unstated in their implementation, and you should know about it!
Published: ....
Replace that old useState and useEffect combo for a new and better option!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
Proposing a solution for sharing core "business" logic across services!
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.
Published: ....
When did semver major changes become so scary?
Published: ....
Leveraging service monitors properly to improve service observability.
Published: ....
A brief recap of how Wayfair changed it's CSS approach not once but twice in the span of 5 years!
Published: ....
A deep dive into one of my recent side projects; microfibre - a minimal text posting application
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few thoughts on using Suspense with GraphQL to optimize application data loading
Published: ....
A few thoughts on what to do after you launch a new project
Published: ....
A few quick thoughts on burn out and taking a break
Published: ....
A few thoughts on managing complex UI component state within React
Published: ....
A quick overview of the new lifecycle methods introduced in React 16.3
Published: ....
A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions
Published: ....
A few thoughts on the redesign of my personal site, adopting Next.js and deploying via Now
Published: ....
A few weird things about JavaScript
Published: ....
Building a calendar web application
AI
Published: ....
A quick look at combining Cursor with Obsidian to ask questions of your notes!
Published: ....
Is it a good or a bad thing to offload writing code to AI agents and Large Language Models?
Published: ....
A rough mental model for how you should be leveraging AI as a tool for your own growth
Published: ....
I've been using a variety of AI tools as of late, I figured I'd document the ones I'm primarily using!