You still can't trust AI to do what you expect, and the speed at which it can make changes means a death of a thousand cuts if you don't keep control.
From autocomplete to agents: a year of AI-assisted software delivery
Category: Coding
Assembly versioning, Nuget, and complexity.
Nuget packages can be tricky to update if you don't pay attention to your dependency chains.
Helpful.Hosting.WorkerService.Windows/Systemd
A simple but flexible package to turn your commandline project into either a Windows Service or a Linux systemd service.
Helpful.Aws.Sqs.Receiver
This is a very simple DotNet Standard 2.0 package for receiving messages from AWS SQS in as simple a manner as I think is possible. Source code is on github https://github.com/RokitSalad/Helpful.Aws.Sqs.Receiver The package is available on nuget.org: https://www.nuget.org/packages/Helpful.Aws.Sqs.Receiver The package provides a few useful features which you don't get by default when using the AWS … Continue reading Helpful.Aws.Sqs.Receiver
Technical Excellence
"Don't overengineer this. We need to move as fast as we can."Too many business representatives The Agile Manifesto is built on 12 pillars, the 9th of which (at the time of writing) is: Continuous attention to technical excellence and good design enhances agility. I regard the Agile Manifesto as a thing of truth. It has … Continue reading Technical Excellence
Where Patterns go to Die
An essay on why software patterns become anti-patterns and how to avoid pattern rot.
Don’t Stream JSON Data (Addendum)
Over the last few weeks, I've talked about how cool streaming JSON data can be and why maybe it might not always be the best idea. Have a read here: Large JSON Responses Don’t Stream JSON Data Don’t Stream JSON Data (Part 2) After the last instalment I thought that the code I listed for … Continue reading Don’t Stream JSON Data (Addendum)
Don’t Stream JSON Data (Part 2)
I've discussed the merits of JSON streaming in two prior posts: Large JSON Responses and Don’t Stream JSON Data, if you haven't read these yet then take a quick look first, they're not long reads. I'm attracted to the highly scalable proposition of scaling out the consumer, so many requests can be made individually rather than returning a … Continue reading Don’t Stream JSON Data (Part 2)
Don’t Stream JSON Data
I recently published a post about how to stream large JSON payloads from a webservice using a chunked response, before reading this post it's probably best to read that post here. Streaming is a fantastic method of sending large amounts of data with only a small memory overhead on the server, but for JSON data … Continue reading Don’t Stream JSON Data
Large JSON Responses
The long slog from a 15 year old legacy monolith system to an agile, microservice based system will almost inevitably include throwing some API's in front of a big old database. Building a cleaner view of the domain allows for some cleaner lines to be drawn between concerns, each with their own service. But inside … Continue reading Large JSON Responses
Coding Daddy Dobbs 