Agentic Coding – Part 2
In this final part I will share my experiences with custom instructions and custom prompts for refactoring and bug fixing
Tag: software engineering
Agentic Coding – Part 1
Since my first post on agentic refactoring and having attended O’Reilly Coding With AI seminar, I have learnt about a couple of techniques (more like still learning to get good at them), that have improved the results I have had with agentic coding somewhat
Lessons and Takeaways from O’Reilly “Coding With AI” Event
Last week I attended the O’Reilly “Coding With AI – The End of Software Development As We Know It”…so in this quick post I will share my bullet point takeaways, ideas and lessons from that event
Some Observations on AI/Agentic Refactoring
I have been reading, hearing a lot about how AI/vibe coding will make software engineers obsolete and that agentic coding is like magic…so I decided to give agentic refactoring a shot
Reflections on TDD and Software Design – Part 2
In part 1 I talked about the key aspects of my TDD practice from a workflow pov, in this final part I will talk about the more tricky aspects of TDD – scope and design.
Reflections on TDD and Software Design – Part 1
Having recently completed several weeks of pairing with a junior engineer on one of my teams, I came away with some reflections on the practice of TDD and its effect on design that I want to share.
Revisiting Essential Elements of the Ports and Adapters Architecture Style
I will attempt to define each element of the style a bit and also show some C# code examples to illustrate the points
How We Reorganised Engineering Teams at Coolblue for Better Ownership and Business Alignment
In this post, I will share my experiences leveraging Domain Driven Design strategies and Team Topologies to reorganise two product engineering teams in the Purchasing domain at Coolblue (one of the largest e-commerce companies in the Netherlands).
An Exercise in Domain Modeling Guided By Strategic Domain Driven Design – Part 2
In this final part, I will review the current domain model, explore alternatives and make some model improvements keeping in mind the outcome of the design level event storm. Finally I will end with some DDD takeaways that should be applicable generally
An Exercise in Domain Modeling Guided By Strategic Domain Driven Design – Part 1
A practice in domain (re)modeling using my pet project, guided by strategic and tactical DDD patterns.
Systems Thinking and Technical Debt
In this post I will try to use simplified Systems Thinking modelling language to put technical debt in the larger organisational context with the hope that it will make some sense to everyone.
On Software Architecture Decisions, Evolution and Engineering
Deliberate and thoughtful architectural decisions that solve real business problems and mitigate enough of the real risks, is the RIGHT and the MIDDLE PATH way to go.
Artineering 