Anthony J Clink retweeted
60 years ago today, November 17, 1966, Al Bundy scored 4 touchdowns in a single game while playing for the Polk High Panthers in the city championship game.
Anthony J Clink retweeted
22 years ago today, Half-Life 2 dropped and the internet lost its mind — not entirely over the game.
November 16, 2004. Valve shipped the sequel to the most important shooter ever made, and it required Steam activation. Forums burned. Retailers grumbled. A generation of PC players discovered they'd bought a $50 license, not a disc.
Then they got to Ravenholm, and the argument was over.
The gravity gun. The striders. The airboat. Alyx Vance. City 17. Source engine facial animation that made every other 2004 release look like clay. HL2 walked so every storefront, every digital-only launch, every "why is this installing from the internet" complaint could run.
Two decades on, the weirdest thing about Half-Life 2 is how normal it all feels now.
Anthony J Clink retweeted
💡 Spring Boot: You can paginate with Pageable and Page<T>.
✅ Spring binds ?page=0&size=20 into a Pageable
✅ Page includes content + total count for the UI
Anthony J Clink retweeted
Every methodology eventually collapses into this one. The rest are just what we call it in the retro.
Anthony J Clink retweeted
Every codebase is legacy the moment someone else wrote it. Mine becomes legacy at the next commit.
Anthony J Clink retweeted
Exception handling rules I follow in Java:
• Never catch Exception and do nothing.
• Catch the most specific exception you can actually handle.
• If you can't handle it, let it go up.
• When you wrap an exception, pass the original as the cause.
• Log it once, where you handle it. Not at every level.
• Write clear messages: what failed and for which ID.
• Don't use exceptions for normal flow control.
• Create custom exceptions only when callers will treat them differently.
Good exception handling makes debugging so much less painful.
Anthony J Clink retweeted
The only generation that knows how computers work is also the most relaxed about AI:
Quit making canonical EDI models!
Canonical shipment models keep failing. Mapping libraries don't.
EDI guides don't agree on "returned." Companies burn millions on one status model. Amazon keeps a partner map. An LLM trained on every guide still guesses when codes overlap, and the next carrier writes a new take. Onboarding stays. The map is the product.
1
31
Anthony J Clink retweeted
Replying to @ahmedehab_01 @dhh
Well I don't know about the fallen mighty, but I agree completely that critical load bearing code may need increased amounts of scrutiny; up to, and including, line by line review.
On the other hand, using the helpful review of a new tool under development to signify that the mighty have fallen is a bit of a stretch.
































