Tom Oram retweeted
We are doing it, going live now!
The first live streamed Armakuni Friday Teaming Session with @tomphp and @thebddadvocate.
Watch us here: youtube.com/live/VIVKPRo4Rws…
#mobProgramming #ensembleProgramming
Tom Oram retweeted
On Friday @tomphp, @thebddadvocate, @abhisheksr_01 and I had a great time running the first @ArmakuniHQ Friday Teaming Session. We starting on the Conway's Game of Life kata.
Watch the recording here: youtube.com/watch?v=_8VrN8qD…
#python #tdd #mobProgramming #ensembleProgramming
Tom Oram retweeted
Dear programmers of all the apps I use: No I don't want to choose between DD/MM/YYYY and MM/DD/YYYY, I want the only sensible format which is YYYY-MM-DD.
Tom Oram retweeted
New financial year, new training budget?
Spend it wisely at @SoCraTes_UK training day, June 1st, 2023
Then continue to learn from them and others for the rest of the conference 2nd - 4th June.
buff.ly/2uITA1x
#softwarecrafts
Tom Oram retweeted
Don't miss out on @SoCraTes_UK, coming on 1st - 4th June!
🤩 Get involved!
📣 Tag your friends, colleagues, and organisations
🎟️ Get your ticket buff.ly/3DLFvkv
🫶 Become a sponsor buff.ly/3HBJK3b
#software #craft #openspace #unconference
Tom Oram retweeted
You should aim to remove as many shell scripts from your CI/CD and deployment models as possible.
Re-write them in code.
Tom Oram retweeted
When we choose TestAfter instead of TDD, what's the use of those tests? For whom?
They're useful IF we come back to that code, sometime LATER, possibly for someone ELSE. If and only IF they're good tests.
What's so great with TestAfter?
Tom Oram retweeted
Somewhat eye opening day. Test driven development was cutting edge circa 1999. It is the basis of modern development. I can't imagine not using it. Hearing companies that don't use it, is like hearing companies go "have you heard of this new thing called Linux?" ... wtf?
Tom Oram retweeted
Doing things right IS NOT an over-engineering.
Doing things "just in case" IS an over-engineering.
Tom Oram retweeted
Made a tool for identifying which files always appear in the same commits, so you can spot coupling github.com/PurpleBooth/git-m…
Tom Oram retweeted
Urgency breeds bad code.
When in a hurry less tests are written and less refactoring is done.
Eliminating urgency is a precondition to getting better code
Tom Oram retweeted
When is the best moment to improve some code?
Just before that code needs to be changed.
Tom Oram retweeted
I love using specdown, it's such a nice way of writing docs /cc @tomphp
Tom Oram retweeted
Kubernetes is a cunning plan to make Google’s rivals spend all their time debugging incorrectly indented YAML files instead of developing products.
Tom Oram retweeted
20 years ago today a bunch of people argued together on a mountain and put forth a website and it was used for some awesome things and some awful stuff and there was much ado about it
Happy anniversary
agilemanifesto.org/
Tom Oram retweeted
The most difficult part of TDD is to admit that we are limited and we need tests to help us overcome our shortcomings.
Tom Oram retweeted
One of the things I learned from @KentBeck years ago was to see cohesion in terms of divergent change rates. If you have a class and there's a set of methods that you tend to change together while leaving others alone, that set of methods could be a separate responsibility.


















