Great keynote from @KevlinHenney at #AOTB21, as usual packed full with interesting insights, only some of which I managed to capture...
"Agile" definition = "move quickly and easily"
...but agility is not about speed, it's about being able to respond to change.
There are two things that people hate: 1. Things changing, 2. Things staying the same.
(I feel duty bound at this point to mention this also came up during @KevlinHenney's ep on our podcast:
Velocity is not just speed - it is speed plus direction. It's no use going fast if you're doing it in the wrong direction.
There's a difference between faster and sooner.
It shouldn't be "move fast and break things", it should be "move slow and mend things."
When your job is to see things that others don't, you have to slow down enough to be able to look.
Decent architecture (inc. software) creates habitability - a place you can call home... A place where you can place your hand on anything without having to hunt it out.
Productivity is a function of codebase size. Developers are dramatically less productive on larger bodies of code. Rob Smallshire. @robsmallshire
Prioritising by business value is not physically possible, because you have no crystal ball and don't know, for instance, whether your innovation will sell. You can only prioritise by *estimated* business value.
Everyone you meet is fighting a battle you know nothing about. Be kind.
Always.
@aprilwensel, Compassionate Coding, has a lot of good things to say in this sphere.
Hillel Wayne: sleep quality and stress levels matter far more than anything else, including code quality. @hillelogram
I really enjoyed @EmilyBache’s talk about her Samman Technical Coaching technique (@CoachingSamman) yesterday at #AOTB21. Here are my notes.
Samman = Swedish, means "together".
An agile journey includes technical agile, and that's the part that the Samman technical coaching method focuses on.
Emily did a survey in the talk (using @Mentimeter) about what makes coding fun. The top choices were: 1. An end product that users care about, and 2. Code that is clear and easy to understand.
This is a really interesting thread. I totally get what you're saying, and it makes me really sad and mad that women encounter these situations in job interviews.
But the conclusions being drawn also make me sad.
I am a pathological question-asker, and I am aware that I have been judged for that, in some contexts (including interviews).
But, you know what? Sod them. The ability to ask decent questions is a core software development skill.
And it's not just about complex questions that are deliberately obscure. It's also a skill to be able to ask simple questions, and questions that are designed to increase simplicity. For senior technologists in front of less experienced colleagues, I believe it's an obligation.