Panagiotis Kanavos
banner
pkanavos.bsky.social
Panagiotis Kanavos
@pkanavos.bsky.social
53 followers 170 following 99 posts
Dad of 6. Moderator of DotNetZone, the Greek .NET User Group. Software engineer, aspiring architect, SharePoint Refugee. Not an MS MVP
Posts Media Videos Starter Packs
It told me to use the legacy cardinality estimator in a production reporting query, for 74% improvement.... That's a lot
So, that's why you need the R1...
This used to be the only way to survive a SharePoint troubleshooting... week
US customer enters 👍in you varchar Feedback field.....

German company importing Swedish sales data, realizing it ain't Latin1....
Then again, being able to run the formal spec without paying a gazillion for the spec parser is really nice
The trick is that LLMs make people *want* to write the formal specifications they never wanted to write in the 00s
And then Trash, @jameshoffmann.bsky.social with a manual Espresso machine I can't afford, Trash, trash, trash, @scott.hanselman.com again, trash, trash, more @jameshoffmann.bsky.social , trash, trash,...
I just opened it and got @scott.hanselman.com talking about how he added WiFi to his Commodore64!
As @migueldeicaza.bsky.social says every year this time "If it's good enough for Jesus, it's good enough for me"

No idea what that means, I can only afford Redmis
Cryptography "tutorials" and libraries around 2000 were as bad. Either fluff or useful only to academics.
Not sure he'd approve.

"Rickover's stringent standards are largely credited with being responsible for the U.S. Navy's continuing record of zero reactor accidents"
On the other hand, now you have the detailed Formal Specifications document you (or the product manager, customer, etc) didn't want to write
I see it and raise Ikarian melting cat Level 2.
Calling those stalagmites "scaling" is disrespectful.
Posts read like a troll. Why bother?
Sounds like the Great Depression tale about the speculator and the shoeshine boy
It was a comment about NRTs in general that should be blamed on Isaac Abrahams. Years ago he wrote that the way C# is, it's better to use NRTs with strict nullable checks than attempt to create Either<> or Optional<> constructs. I though that was extreme so I tried it and... He was right.
If we had DUs and exhaustive matching we wouldn't. Right now it's actually safer to treat warnings as errors and return T? instead of a custom Either<> or Optuinal<>.
I do it with bad recruiters all the time. If you don't even bother to read my profile, why should I bother responding to you?
I use Aeropress and Kingrinder P2 at both home and deserted islands. Small enough to put in a pouch, 6-kid proof and grinding is a great way to annoy the kids in the morning.

Check James Hoffman's YouTube channel too. A deeper rabbit-hole than functional, DDD and AI combined
Ahh, when all new TV stations used Scala.