Hour a Day: AI - Day 8 - Another perspective
I’m running off not much sleep as a bunch of severe weather came through my neighborhood last night. I have an event to go to in a few, and I’m not sure if I’ll be up for a full session when I return. So in the off chance I’m not a co-worker posted an insightful article, that while I may not totally agree with, is an interesting perspective on ai tooling.
Hour a Day: AI - Day 7 - The Power of Conventions
As a recap since there was a break yesterday: we’re focusing on starting to get tests written for our service.
Making Stubs Prompt:
I’d like you to create ut test stubs for the classes that I have (skipping the main entrypoint). Don’t fill out the implementations but ffeel free to create setup methods that setup up the needed dependencies. In general these are unit level tests so anything injected should be mocked.
Hour a Day: AI - Day 6 - Something a little different
Today is going to be a little different as my “hour” of ai was over a brownbag during lunch. Multiple people from work shared success and failure stories from their own personal ai adventures.
Mostly the things they said were things that were on my radar but it was good to hear some new ideas too. I’m planning on trying out some of those learnings into this series as well.
Hour a Day: AI - Day 5 - Total Failure
Today is going to be a little short on the prose department, I’m already over my hour starting to write this 馃槺
Create a test project Prompt:
Can you create a test project for llm-history-to-post.csproj
Response:
llm-history-to-post/llm-history-to-post.csproj
Add file to the chat? (Y)es/(N)o/(D)on’t ask again [Yes]: y
Okay, I will create a new xUnit test project named llm-history-to-post.Tests.
This involves creating a new project file llm-history-to-post.Tests/llm-history-to-post.Tests.csproj and a placeholder test file llm-history-to-post.
Hour a Day: AI - Day 4 - Something Functional
Yesterday we took a stab at having aider implement our history to blog post service based on the requirements doc that we had cleaned up on day 2. I ran out of time to talk about it, but it had a pretty big issue.
I was using aider’s architect mode to create the application. Which acts like a psuedo reasoning system where it uses the prompt entered into the cli to create another prompt to then feed into code generation.