4 ms·
My comment is more about what to expect in the next 12 months. I've been using VSCode's Copilot with Claude Sonnet 4 and find it to be terrifyingly competent r
by dataviz1000 1y ago
My comment is more about what to expect in the next 12 months.
I've been using VSCode's Copilot with Claude Sonnet 4 and find it to be terrifyingly competent running 8 hours a day costing ~$10.
I am developing techniques to keep it moving forward producing code and fast. First, prompt engineering like "write clean, simple, and elegant code." Second, I use TypeScript very strictly which helps. Third, the models are amazing at producing very simple test units which will be important in the fifth. Fourth, I use techniques like "look for opportunities to refactor pure functions in the file and put them at the top of file" or "look for opportunities to refactor pure function and put them in shared utils.ts file." Fifth, every hour or so, I will have the agent simplify and clean the code and with complete test coverage both unit and integration as longs as they all pass .... good to go.
This is a process and it is the same every time. So now I'm thinking about how do I write code to automate these steps into an automated process. For example, I keep using the same pattern of steps to solve hard debugging problems which I'm going to leave out of this conversation now. If I can create a process in code, I'd be one step closer to complete automation coding.
The patterns are emerging. I strongly believe in 12 months these systems are going to be able to write extremely complicated programs with very little input from the human in the loop.
- i_love_retros 1y agoWhat are you building?
- dataviz1000 1y agoIn the past 3 weeks I ported Playwright to run completely inside a Chrome extension without Chrome DevTools Protocol (CDP) using purely DOM APIs and Chrome extension APIs, I ported a TypeScript port of Browser Use to run in a Chrome extension side panel using my port of Playwright, in 2 days I ported Selenium ChromeDriver to run inside a Chrome Extension using chrome.debugger APIs which I call ChromeExtensionDriver, and today I'm porting Stagehand to also run in a Chrome extension using the Playwright port. This is following using VSCode's core libraries in a Chrome extension and having them drive a Chrome extension instead of an electron app. I very heavily use the VSCode Copilot coding agents for all this. These are not trivial problems.
- oidar 1y agoWhat's your feelings on Claude Code? I mean you obviously chose VS Code, what wasn't hitting right using Claude Code?
- dataviz1000 1y agoI tried Claude Code because they gave 1 week free about a month ago. I didn't feel there was any advantage over Github Copilot which has been making huge strides trying to stay competitive in the past couple months. Maybe I should revisit Claud Code with this systematic process workflow that has been evolving.
- stillsut 1y agoYeah, I've been able to stack ~200 AI-generated commits on top of each other. Over 95% of the code is now AI generated. You can see each prompt and each commit that was generated here: https://github.com/sutt/agro/blob/master/docs/dev-summary-v1.md https://github.com/sutt/agro/blob/master/docs/dev-summary-v1... Since AI-Gen code is such a roll of the dice, the key is to roll the dice a lot - usually generate at least 3 potential solutions from at least two separate providers at the outset - and get good at quickly reviewing the offered solutions, or iterating on the prompt and regenerating.