Programmer @TerribleAaron@hachyderm.io
Portland, OR
Joined August 2011
- Tweets624
- Following179
- Followers84
- Likes966
Aaron Bruce retweeted
I've never worked on a piece of design-up-front software where the design didn't have to change radically based on things we learned as we developed. Death-march projects usually start with a fixed up-front design. Time spent on detailed up-front design is time wasted, IMO.
I'm a big fan of TDD, but I never liked the claim that it FORCED good design. I think that sends the wrong message to newcomers.
aaronbruce.com/posts/tests-d…
Same. "Semantic drift" and cargo culting in our industry leads us into these situations where we can't use the words that describe our profession anymore.
DevOps and to a lesser extent Continuous Delivery have suffered the same.
Aaron Bruce retweeted
Cost of unfinished work is one of the biggest problems in software development teams.
Aaron Bruce retweeted
How we plan & prioritise work has a big impact on its quality. Do you create technical stories in addition to user stories?
In this #GOTO x @davefarley77 collab ep, Dave talks about why technical stories fall short as a valuable method for planning work
youtu.be/4drvdaZcd0Y?list=PL…
In this piece I talk about one aspect of the cost associated with "working large" and provide some simple examples with math to explain the mechanism.
Stop asking "Should this be smaller?" and start asking "How can we make this smaller?"
aaronbruce.com/posts/cost-of…
Aaron Bruce retweeted
I just got back from @fintechdevcon in Austin. It was a super fun trip (notwithstanding the 105 degree air 🥵).
I gave a new talk while I was there, on why compliance and regulatory standards are ✨not✨ incompatible with modern development best practices.
Engineering leaders must take responsibility for the quality of their software systems. They operate at the intersection between development and business, and are the best to understand the tradeoffs associated with quality investments.
aaronbruce.com/posts/debt-bu…
I talk about the value of working in small steps a lot. System stability is just one of the many great things that comes from working small. Here's how that happens
aaronbruce.com/posts/small-s…
Halfway through year three of being fully remote I'm thinking more and more about how effective documentation might need to help fill some of the gaps caused by lows of proximity
aaronbruce.com/posts/documen…
Aaron Bruce retweeted
What you're probably getting wrong with "smaller steps": A step can be one action or many, but to be a step it has to take us from ready to ready.
buff.ly/45z2gn4
Good quote from Release It! by @mtnygard
"Adaptability doesn’t happen by accident. If there’s a natural order to software, it’s the Big Ball of Mud."
Aaron Bruce retweeted
I find that discussions surrounding how to make stories smaller, are much more useful than discussions surrounding estimation. For one thing, the latter is focused on implementation, not customer value.