Climbs, codes, eats biscuits. In case you wondered, I earned the nickname before the other bright orange muppet became famous.
Sheffield
Joined July 2018
- Tweets1.7K
- Following103
- Followers21
- Likes699
BrightOrangeMuppet retweeted
🧵Next week, you will see people using something called Benford's Law to try to prove election fraud.
⛔️These people are wrong⛔️
I am a scientist who has published on Benford's Law. Let me tell you what it is and why what they are doing is mathematically incorrect. 1/
BrightOrangeMuppet retweeted
This doesn't mean that we all should go down to Assembler. As I said, that abstraction often makes us more productive.
But there are things where the efficiency and direct control of machine programming in assembly language are necessary.
BrightOrangeMuppet retweeted
Do you have a system of delivery or a Rube Goldberg machine?
System of delivery:
git commit && git push ⇒ runs tests, if they pass, deploys to pro
Everything signitifantly more complicated than that is possibly a Rube Goldberg machine.
#xp #ContinuousDelivery
BrightOrangeMuppet retweeted
Happy 23rd birthday Wayback Machine!
On October 24, 2001, The Internet Archive organization launched a free digital archive of websites for the general public called the Wayback Machine.
The oldest pages stored in the archive date back to 1996.
#InternetHistory
ALT Internet Archive website in 2001
BrightOrangeMuppet retweeted
Someone actually said this in a discussion and believes it:
"You should be able to plan a sprint that you can complete in time. If you can plan a sprint that you can complete in a two week period, then it naturally follows you can plan 2 sprints, or a quarter, with the same results."
I am 99% sure they have never written a line of code for an enterprise before.
I don't even let my family do that - and they're friendly and trustworthy. And at least arguably human.
BrightOrangeMuppet retweeted
Cookie banners.
Just visited a US website, from the US, that ships a 457.11kB (minified!) JS bundle of a GDPR "banner SDK" from a "trust" provider. Over 3x the size of React. It ships its very own version of jQuery inside.
Going to the "trust" provider website yields a 5.3s LCP (i.e.: 5s+ to load the first screen completely). 53% of visitors experience a similarly terrible loading experience. They couldn't care less.
This is the stuff that's silently destroying the web.
• For most users, these providers have gamified beyond belief your ability to actually block cookies. The primary buttons are always "Accept All", even when you "customize your preferences". More often than not, they're cheating you into accepting everything.
• The amount of JS they ship, downloading from a 3rd party website, is destroying the web's performance
• The aesthetics and function of websites is massively compromised. In the spirit of "privacy and trust", they're eroding the open web in favor of proprietary platforms.
• They undermine the product engineering teams' efforts. I've met so many amazing design engineers who spend countless hours honing experiences, only to have them destroyed by cookie junk.
Cookie banner slop has to stop.
EJB1 and EJB2 and AWT and Applets and JavaBeans and early RMI. Those still occasionally rise like Lovecraftian horrors in my head.
Almost as bad as Oracle 7 and Websphere.
It's a small thing in the world, but today reminded me @schumacher is the reason I now always wear a helmet when skiing or biking, and more often now wear a helmet when climbing. And never attach anything to those helmets.
Dunno if I fully agree, but I like the description and the concept. Sometimes waste, overhead and value depend where you're standing and when you ask the question.
"Value" is a technical term in Lean, from which Agile thinking derives. It means _direct_ value to the user. If it doesn't put user-perceived value into the customer's hands, it's waste (Muda). There is necessary Muda (overhead), and you need to perform overhead-related tasks, but it's not adding direct value. The question becomes one of time management. What percentage of your time do you spend providing user value, and what percentage do you spend on overhead? The answer depends on many factors: the maturity of the product, whether you're building market share, &c. Personally, I prefer to manage the overhead tasks independently, with their own Kanban board, &c., and a fixed percentage of my time allocated to them. Scrum, of course, munges everything into a single backlog, but I've found that practice to be suboptimal. It's useful to easily separate and manage value-add work from overhead work, and putting them both in the same pile doesn't help do that.
I agree the concepts are still very relevant. One nitpick I have is their gamification. E.g. I see the patterns used like pokemon "we haven't used facade yet".
I also bemoan the patterns books used as authority. Teams don't realise they can make their own patterns.
Design Patterns is a wonderful book. Yes, I know, it's thirty years old. Yes, I know it uses older languages. But it's still great.
Some folks have said that the concept of Design Patterns is out of date -- that those patterns were just workarounds for the bad languages of the day.
What a load of Dingoes Kidneys! The Patterns described in the book are timeless and well worth the effort to learn. They are crystalized applications of old and well worn principles.
You _will_ use them, one way or another, because they are common solutions to common problems. If you don't know them already, you'll work them out for yourself.
The benefit of learning the patterns from the book is that it gives those common solutions canonical names, and canonical forms. When others who know those names and forms see them in your code, they'll know exactly what to expect.
BrightOrangeMuppet retweeted
Instead of "when will this be done," ask "when can people start using this?"
They're not the same question. You can create a feature in one big-bang (waterfall-style) or you can create it in a number of "value drops" and collect feedback along the way.
BrightOrangeMuppet retweeted
Some engineer writes to me to object that my Go library is missing a key feature that it used to have.
Turns out that the library never had this feature, but ChatGPT thought so.
Actual email exchange:
BrightOrangeMuppet retweeted
telling all of my friends with small daughters that if they say "i wanna learn about dinosaurs and jump on a trampoline" this is in fact a perfectly fine career path
This Post is from an account that no longer exists. Learn more
Both really useful and really worrying.
🆕️🔥TruffleHog now scans DELETED & PRIVATE data on GitHub: trufflesecurity.com/blog/tru…
This data is not a part of any commit history.
To understand how substantial this TruffleHog feature is...
Here's a refresher from last week (1/5)👇
Turns out software industry isn't the first to have walked this path. Airline industry famous has a Just Culture as it's ideal method.
skybrary.aero/enhancing-safe…
Not saying it always works in practice (ahemBoeingahem), but it seems a sound goal to aim for.
So it turns out thorough testing is really important in memory unsafe languages.
And really, really important when those programs run in kernel space.
And really, really, really important when those programs are installed on business/safety critical machines.
Who knew?
