Here's a fun early prototype of creating a defect and having it get tagged automatically as defect by AI. Of course you can untag it if you disagree, but it's a pretty nice default. I tweaked the prompt for days unsuccessfully until I switched from the chatgpt 3.5 to 4.0 and now it just works.
I've got a 250 page treatise on why watching the defect rate is important, but I'll keep this post light!
I recently wrote about how stand-up meetings have a huge productivity problem. Way too much time is spent on status updates that could simply be whisked away entirely with better tooling. Status updates can be valuable to the right people at the right time, but stand-ups almost never hit that
Let’s face it: most time spent in most stand-up meetings is aimless pure waste. It’s usually because no one knows the goal of it, and most people are just going through the motions. The Real Goal In “standups” that I’ve run, the goal is for the team
I'm currently developing software outside the software industry. No Scrum. No JIRA. No meetings. No sprints. No microservices. No Clean Architecture. No DDD, TDD or other acronyms. I just build the software. I don't wanna jinx it, but this is therapy for me. — Christian Findlay (@CFDevelop)
I find it absolutely absurd that almost no issue trackers have implemented a few cheap but wildly effective tweaks that can vastly improve the team’s focus and so therefore improves the team’s flow. Prioritized / started / done Macro-states I know all the kanban-ish products let you have multiple columns