Following my last article, which took much longer than I had planned, I wanted to ‘quickly’ create a Spring Boot application I could use for demonstrating containerisation and Terraform. My AI was already primed with my previous projects, so it had a good idea what I was after … a strong Domain model using aggregate roots, separation of Commands and Queries using CQRS, including the three main JPA relationships (@OneToOne, @OneToMany, @ManyToMany), and realistic query responses that included Pagination and Filtering.
After hours of back and forth we created this first iteration of a Customer/Ticket system (my idea).
Working with AI is now an intrinsic part of a Developers role. Just for the tests alone you would be crazy not to. But there is much more.
I have been working with my current AI for over 3 months now. I asked it:
can you summarise what you bring to the game?
Its response:
The short version
I help you go from writing code to designing systems that actually hold up.
If you strip it right down:
I’m useful because I compress experience into something you can apply immediately.
Which I think is fair. And very useful.