Software architect and developer with a passion for simple, effective solutions.
Focus on software design and backend development.
Tech: #typescript #kotlin #java
| Web page | https://henko.net/ |
| Blog | https://henko.net/blog/ |
AI promises to make us all 10x programmers, but if you stop reading the code, you arenât speeding up; youâre creating instant legacy code.
Once the agents have written the code, the code becomes the ground truth. Either you understand the code well enough to verify and adjust it, or you rely on the AI to safely modify it. The latter means outsourcing correctness to a non-deterministic system with unknown failure modes.
Read more on my blog.
https://henko.net/blog/are-you-using-ai-to-generate-instant-legacy-code/
Good point by @jasongorman.
> Itâs quite clear that the factors that make code easier for us to wrap our heads around also make LLM performance on it better (less unreliable).
This means that even if you think you will be able to vibe code your way to success without ever reading the source cdoe, it is _still_ important that the generated code is understandable by a human. đ
I really hate sitting in traffic. If I can keep moving, Iâd rather take a long detour than be stuck in a jam, even if the detour ends up taking more time.
I've found I can get the same feeling waiting for an #AI #agent like #claude. It may reach a finished solution faster than I would typing it by hand, but it is so boring to do nothing while it works.
Theoretically, I could be doing some other valuable task while waiting (yay, multitasking) but I often end up doom scrolling instead.
Just realized that `docker debug` (which is now free to use) allows access to _stopped_ containers as well! Very nice!
On the blog: Think for Yourself
"In using Gen AI, many developers have unintentionally taken a back seat with both their knowledge and their destiny. By skimming past the friction necessary for learning, the pursuit of convenience can end up deskilling rather than enhancing skills."
https://kevlinhenney.medium.com/think-for-yourself-7d129aa959e3
The goal of software architecture isnât to specify all the details, but to describe a solution space in which teams are free to move.
It is similar to how a nautical chart provides sailors with the information needed to navigate safely toward their destination, showing the safe channel and hazardous areas to avoid.
Read my latest blog post for more on how architecture can effectively guide teams.
https://henko.net/blog/software-architecture-as-a-nautical-chart/
I've been planning to take a look at Cursor, just to understand it better. Felt a bit bad that I haven't taken time to do so yet.
Then I stumbled upon my personal notes from March 2023 saying:
> Quickly tested Cursor as a development environment. It is a bit rough, but it still seems promising.
So apparently I already have. đ
Tanya Janca | SheHacksPurple 
Kevlin Henney
Rob Ricci