Opus cannot document the contract of interfaces if its life depended on it. It leaks implementation details. Every. Single. Time. Its comments could literally be used as an infinite example source of how to not write comments. I guess it must be a training artifact. @claudeai
@init7 used to be a good ISP. Not anymore. Our company has now been without a working internet connection since last Wednesday and Init7's current stance is that they will try do something about it the coming Friday. A "business" ISP product can't have 1.5 weeks downtime.
So much corporate red tape can be traced to a single anecdote where someone fucked up and their manager didn't have the balls to tell them directly. So they made a policy instead. Don't be that coward. Just tell Ben.
I recommend against using @goserverless for production applications. We used it in our startup, ran into a production-blocking bug, and filed an issue (including a PR with a fix). Crickets. Not even a "we're too busy to look at this".
https://t.co/gwVQ6Jp2Es
@goserverless 🧵It's quite clear what @goserverless's game is now. They're launching a non-OSS version and and want to force everyone to upgrade by refusing even trivial PRs, like the one-liner that adds Python 3.12 support: https://t.co/3Vab9sBBNm.
Delayed another 35m due to "airport constraints". At least not as bad as when @AirCanada drove the bridge into one of the engines, forcing us to change planes, and refusing to refund us for the delay, claiming "bad weather" as the cause of the delay.
Just got a message from @AirCanada that our flight is delayed due to extra time needed to tow the aircraft. The flight is in ~4 hours. How far do they need to tow the aircraft exactly?
@lufthansa Travel ID is a good example of how to not do a system migration. Despite not even being a Lufthansa customer (I'm with @FlySWISS) I now have several logins (https://t.co/jSyTBdGDyq, https://t.co/i1uv9l03Jx) and none of them work. 1/🧵