Prompt engineering has become a fundamental skill for developers. There are different ways to approach it.
Some are more manual, some are way more automated with semi or fully autonomous agents.
So here’s the situation: our frontend team had this growing backlog of UI tweaks.
Buttons slightly off, wrong font sizes, missing translations, components that didn’t quite match what the designers put in Figma.
I was recently asked to help improve OpenAPI specs for a project where the documentation had gotten completely out of hand. Thousands of lines of OpenAPI specs scrambled in a few files.
Either you have prompt that was built based on some template or you have built it from scratch, sooner or later you will need to improve it.
So every time you use it produces better output for your recurring tasks.
There are many theories on how to build habits - some more complicated than others.
Over the years, I’ve tried a few different methods. What’s worked best for me is breaking big goals into tiny steps.
As you might have noticed by the title, Soft Skills by John Z. Sonmez is not a typical book for developers.
But is it?
Even though this book doesn’t talk about technical aspects like the structure of your code,
programming languages (though .NET is mentioned a few times), or what cloud (or no-cloud) provider you should use – over its 500+ pages, John dives into a wide range of topics you might be surprised to find in a book dedicated to developers.
