Reason Based User Stories
In my previous post I described my feeling on why it is so critically important to develop a good user story. However I didn’t go into much detail on how that is done. I’m going to cover that in this post.
In my previous post I described my feeling on why it is so critically important to develop a good user story. However I didn’t go into much detail on how that is done. I’m going to cover that in this post.
I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.
du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.
One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.
Your existing team is buried in the complexity of your existing product. AI rewards the team with a blank slate. Most companies don't have one.