we need to stop judging dev tools on their day 1 experience (how easy it is to integrate), but on their day 200 experience instead
will this become tech debt and slow my team down more than anything?
UPDATE: The tweets by @TwitterSupport this morning, announcing a new policy banning linking to competing websites, have been deleted.
The policy itself was deleted from Twitter’s website.
From Jordan Martin at the elephant site.
"If you go to https://t.co/RPrbiTaUEW it is now a URL shortener that blocks the twitter user agent. That means you can share that link that will redirect to your Mastodon account without the pouty baby stopping you."
Reading about Lambda SnapStart (https://t.co/5iCnoBRT4n)… first thought was “cool, JVM for Lambda without the slow start”.
Second thought: “oh boy, ppl are gonna start using Spring in Lambdas, aren’t they?”
Rewatching “Solo: a Star Wars story” last night, and there’s a particular scene with a droid that had me thinking, “oh, that’s kinda dark”… apparently it’s even more horrific in the novelization (spoilers, of course): https://t.co/PaJBWuakpl
Don’t wait for PMs to “prioritize” tech debt. Make a technical roadmap, front loaded with mid/short term wins. Show you can make small impact in a month, medium in a quarter, before you ask for a year of refactoring. Break down milestones and measure if the work mattered.
Also, the irony is not lost on me that one of the reasons “is this unused?” is so hard to answer is because we also had a large round of layoffs at work a few months ago.
At the rate Elon is going, he’s going to decommission Twitter before I manage to decommission that random RDS cluster in us-west-1 that nobody seems to be able to say for certain is “unused”
After 20+ years of working, you figured you’d seem some shit but I don’t think I’ve come across the idea of “accidental layoffs”😬
Kidding aside, an org has to be pretty messed up to get to the point we’re people are so faceless that they are treated like they’re just line items