Dad, husband, agile dev desiring to deliver software better - both with process & design. Passion for solving technical problems. Building AI Biodiversity infra
If you claim the system failed because of human error, then you’re saying that your system requires error-free humans to function without failure.
If that’s the case, your problem isn’t the people, it’s that you have a fragile system.
What is the difference between the two urls?
one has an @ and one doesn't.
But also the first downloads version 15 of postgres from GitHub and the second one resolves to v15 dot zip domain which can also downloads a zip file that sure doesn't have postgres in it.
You see, URLs with @ in them are split into two parts, anything before @ is user info and anything after it is the host name, however this rule is broken if what comes before @ are forward slashes.
The second URL includes a character encoded like forward slash but isn't really the real forward slash, which URL parsers ignores making anything before the @ as user info and treating whatever comes after it as the real hostname.
While this can happen on any domain, the zip domains makes it more likely to happen. When you click on a link that ends in zip especially if it looks like from GitHub you won't think twice about it.
Read the full blog from Bobbyr below.
Want to work with #babashka while solving Infra + DevOps + Devex challenges?
I'm eager to share that our full-stack #clojure engineering team is looking for an Infrastructure Engineer!
https://t.co/E2PkqZr6T2
(Please RT for reach, thank you)
XP never had a story about scaling, which limited its reach. I get the feeling that there is a good story to be told about helping 1000s of folks coordinate their efforts & that story starts by reducing team dependencies.
https://t.co/lKYiIdoEgH
My protocol for speaking in a meeting I am not driving needs to fulfill two criteria:
1. I have something relevant to add AND
2. I perceive the topic as important.
This strategy has consistently resulted in folks giving me feedback that I should speak up more.
When you have a team that "feels understaffed", you might need to:
* stop making unrealistic promises
* get better at estimating and prototyping
* prioritize requests
* say no to more stuff
* fix any leaky sociotechnical systems
* finish the fucking migrations
Have you heard about CUPID? An alternative to the SOLID principles in software craftsmanship presented by Daniel Terhorst-North (@tastapod)
The CUPID acronym stands for:
• Composable
• Unix philosophy
• Predictable
• Idiomatic
• Domain-based
https://t.co/TKiZxrfylG
The recent WhatsApp accounts takeover is simple and genius.
This is how it works:
You're sleeping.
A "hacker" tries to login to your account via WhatsApp.
You get a text message with a pincode that says "Do not share this".
You don't share it, yet you still get hacked.
How?
Two once very literal expressions: a ‘backlog’ was a large log at the back of the fire that kept smouldering away while smaller wood came and went. And the original ‘deadline’ was a boundary around a prison: any inmate attempting to cross it was liable to be shot.
Most of what is wrong with OKRs these days is a lack of strategy. While planning can get too detailed and too removed from our ever moving reality, you still do need to know which direction to row in. You can’t set goals if you’re making it up as you go along.
Reversible vs irreversible. Some changes are easily reversed. Make these quickly & with confidence. Other changes have consequences for the larger system. Make these only after double checking. Converting irreversible changes (even partly) into reversible changes creates value.
idk how many times I need to key saying this but human performance is ecological. individual performance a) doesn't exist and b) couldn't be measured, even if it did. at best, AT BEST, you can vaguely understand someone's performance _in a specific and highly local context_.
Nowhere in the laws of physics is it required that a commit, push, or PR can only be for a fully completed feature. Some people made that up, and it is likely not a good choice for your org.
Try management for at least 2 years
But fewer than 5.
Swing back before you become unhirable as an engineer.
You get worse as engineering manager as your tech skills deteriorate.
@mipsytipsy#QConSF
– We don't write tests.
– Why?
– Because we don’t have time for it.
– Why?
– Because there is too much work and pressure.
– Why?
– Because we don’t move fast enough.
– Why?
– Because changing software has become difficult and risky.
– Why?
– Because we don’t write tests.