The All Blacks against the Springboks. Over 103 years and 106 games, rugby's biggest rivalry has shaped nations, changed governments, affected law, created communities, and provided more outstanding matches than any other. We dug into a game like no other-
https://t.co/j0OCJLd7RQ
So many of the comments I hear about estimation boil down to "but we have to plan and meet our goals." That's a deep failure to grasp the concept (of agile ways of working). We plan strategically, and our goals are strategic. The details of what we have to build to meet those strategic goals are discovered incrementally by releasing small bits of valuable software and getting feedback on it. We defer details, in other words, to the last responsible moment. Defining those details too early doesn't really work because the customers themselves won't know what they need until they have something in their hands. The details are invariably wrong. Too-early focus on details also often leads to building things nobody wants or needs.
There are occasional exceptions, of course, in the corners of the program where regulations, or the actual behavior of actual hardware, or necessary algorithms apply, but those bits comprising the entire system are exceedingly rare.
BSides Cape Town 2024 Tickets are now Live!
Early Bird has Sold out (50 Tickets)
We have released the Standard, Corporate and Student Tickets
Get your tickets here
https://t.co/T1yocGAwBI
@shanselman OPL was BASIC with the power of C and what I preferred. Oval was VB6 clone that allowed anybody get up and running quick.
When Psion partnered with Erikson in the first days of Symbian, I vividly remember getting a box of 4 massive tomes of C++ references and it was over.
@shanselman The robustness of the hardware coupled with standard customer replaceable battery tech like the AA and the 9V DCs meant Psion sold the hardware once and that was all the money they made.
The programming was also ahead of it's time with OPL/Oval before Symbian became a thing.
i can tell no one has ever let you be responsible for anything when you think hiring is ever a good answer
you wake up trying to do work and you get a DM like “hey the new hire said something kinda racist in front of joe and it wasn’t AT joe but joe is still kinda upset”
New blog post by @__AlexMonahan__:
Benchmarking Ourselves over Time at DuckDB
The DuckDB team's philosophy is to first ensure correctness, then iterate and optimize to improve performance. This blog explores how this happened over the last three years, when DuckDB became approximately 3-25x faster and 10x more scalable.
Read more at https://t.co/pdSVJCj88C
A common notion👇. That last bit is the hard one. I don’t think I’ve ever seen a Scrum shop move past Scrum to something better. You can do Scrum perfectly without being the least bit agile as well. If Agile is a 0-100 scale, Scrum gets you from 0 to 1. I suppose that’s better than SAFe, which gets you from zero to 0.1.