Hasnain says:

This had some fascinating history but I cannot help but laugh at this part unfortunately

“Yoga, al-Munajjid preaches, is a form of idolatry ‘based on lies and charlatanry’ that may appeal ‘to simple minded people who are weak in faith’. Some yoga postures imitating animals detract from human dignity including ‘adopting nakedness and resting on all fours’. He has also criticised the tendency of yoga practitioners to encourage a vegetarian diet ‘for which Allah has not revealed any authority’.”

Hasnain says:

“I’ll finish this rant with a related observation: I keep seeing people say “if I have to review every line of code an LLM writes, it would have been faster to write it myself!”

Those people are loudly declaring that they have under-invested in the crucial skills of reading, understanding and reviewing code written by other people. I suggest getting some more practice in. Reviewing code written for you by LLMs is a great way to do that.”

Hasnain says:

I generally say I add negative value to any project if I am involved UI work but I like to think I’d still avoid this one somehow.

Hasnain says:

“That was another rathole, and the answer was also a thing to behold: I couldn't see it in the checked-in source code because it had been fixed. Some other engineer on a completely unrelated project had tripped over it, figured it out, and sent a fix to the team which owned that program. They had committed it, so the source code looked fine.

[ Another side note: this person who fixed a bug in some code that wasn't their actual "job" was the kind of excellent behavior that used to be lionized there - "nothing at FB is someone else's problem". That credo died a long time ago. ]”

Hasnain says:

“In the end, it took me probably less than an hour to find, diagnose and fix this bug, so it wasn’t that bad, as far as bughunting stories go. But I found the bug to be sort of beautiful, so I wanted to share it anyway.

I hope that you found this bughunt case interesting, and that you perhaps also learnt something new along the way.”

Hasnain says:

Coolest math fact I’ve learned in a while.

“One may claim this is cheating, but it seems to be in line with the rules of the puzzle! Note that the entity n doesn't actually appear anywhere - it's just a helper to count the number of repeated square roots.”

Hasnain says:

“So why did I say getaddrinfo sucks? It's because it was designed for POSIX. Do one thing, and do it well. And in that sense it succeeded without a doubt. Could it be better, more flexible and more extensible? Sure. But if that were the case it would also probably be more buggy, and have a bunch more differences across platforms. But what of the other APIs we looked at today? Well, these are the results of each platform doing their own thing. Some had a common starting point - see res_query - but slowly diverged to accommodate the specific requirements of their users and platform. What we now have is a buffet of choices, each with their quirks and buggy implementations.”

Hasnain says:

“"We are not going to fix this problem without better regulation and actual, real, serious consequences for delivering ads that fund horrific companies and activities," Edelson says. "It's too profitable to just ignore this. It's going to be impossible to solve without changing those incentives."”

Hasnain says:

20 years. Life goals.

“I financed PerfectTablePlan out of my own savings and it has been profitable every year since version 1 was launched. I could have taken on employees and grown the business, but I preferred to keep it as a lifestyle business. My wife does the accounts and proof reading and I do nearly everything else, with a bit of help from my accountant, web designers and a few other contractors. I don’t regret that decision. 20 years without meetings, ties or alarm clocks. My son was born 18 months after PerfectTablePlan was launched and it has been great to have the flexibility to be fully present as a Dad.”

Hasnain says:

Loved this one because deterministic thread scheduling for testing is vastly underrated

“Not all heroes wear capes

Yes, it's cliche – but it's true.

Concurrent program debugging is incredibly important. These tricky concurrency bugs take an inordinate amount of time to debug and work through. While new languages like Rust have built in mechanisms to help prevent race conditions like this, the majority of software in the world is already written, and written in something other than Rust. Java, even after all these years, is still one of the most used languages. Improving debugging on JVM based languages makes the software engineering world better. And given how some folks think that code will be written by Large Language Models, maybe our jobs as engineers will eventually just be debugging bad LLM code instead of just our own bad code. But, no matter the future of software engineering, concurrent program debugging will remain critical for maintaining and building software.

Thank you Ao Li and his colleagues from the PASTA Lab for making it that much better.”