I’m teaching myself elixir/phoenix by building a SDLC tool inspired by Trac, the simplest tool that ever worked for me. But with CI/CD.
It has morphed in the offing into two tools. One a federated CI/CD tool and one a personal productivity tool with affordances for neurodivergent people.
Atlassian struggles with being a jack of all trades. Bamboo’s integrations make it harder for devs to create repeatable, reliable builds, not easier. I’ve seen Atlassian struggle to scale with dev count so I want something more federated. Jira is in constant danger of becoming a panopticon, using developer’s transparency as a weapon against them at review time, destroying psychological safety. Devs only use these tools if they see personal benefit or are harangued to do so. My thesis is that you need one tool for personal accountability and a separate one for team accountability both to fight Goodhart’s Law and for people with variability in their daily productivity. There are many little tools for doing bits of this but they don’t talk to each other, leaving the plate spinning up to the developer, many of whom plate spinning is onerous.
I’m hoping this will do for bug databases and possibly wikis what interactive rebase does for pull requests. Do what needs to get done, then make it make sense to others afterward.
It has morphed in the offing into two tools. One a federated CI/CD tool and one a personal productivity tool with affordances for neurodivergent people.
Atlassian struggles with being a jack of all trades. Bamboo’s integrations make it harder for devs to create repeatable, reliable builds, not easier. I’ve seen Atlassian struggle to scale with dev count so I want something more federated. Jira is in constant danger of becoming a panopticon, using developer’s transparency as a weapon against them at review time, destroying psychological safety. Devs only use these tools if they see personal benefit or are harangued to do so. My thesis is that you need one tool for personal accountability and a separate one for team accountability both to fight Goodhart’s Law and for people with variability in their daily productivity. There are many little tools for doing bits of this but they don’t talk to each other, leaving the plate spinning up to the developer, many of whom plate spinning is onerous.
I’m hoping this will do for bug databases and possibly wikis what interactive rebase does for pull requests. Do what needs to get done, then make it make sense to others afterward.