WorldEnder retweeted
Kind request every law maker in India to click the attached "BRICS News" post and read the thousands of disgusting comments degrading India and dehumanizing Indians.
Can we please talk about it for once in the parliament? And discuss as a nation what steps can be taken to counter this extreme genocidal hatred spread against India and Indians?
This is a multi-state sponsored, organized anti-India operation going on for too long that's affecting our exports, inbound tourism, economy, job opportunities for migrants, mental health of Indians, and physically putting them at risk of violence.
This is an issue that is beyond partisan politics affecting everyone of us and the country. IMO, this is a war that's being waged on India as serious as cross border terrorism and insurgency. So I humbly request law makers to start addressing this.
To those reading this, please repost tagging your known MP/MLAs requesting them to address this serious issue.
@PMOIndia @MEAIndia @HMOIndia @narendramodi @AmitShah @DrSJaishankar @nsitharaman @AshwiniVaishnaw @ShashiTharoor @Tejasvi_Surya
unavailable
Programming used to be like hard magic. Master the rules and you get to command the spirits of the machine to your will. The more skilled you got, the more power you had. It was fucking amazing!
Now its soft magic. 😮💨
I want witch hat not skyrim!
youtube.com/watch?v=ODc9oE9N…
I wonder if the number of people who started making software because they loved coding is very small. I personally got into it because I was fascinated by being able to program the computer do things. The computer was simply my favourite toy. Playing with the code was the point.
I would feel a lot better about using LLMs for work if there was more known about how prompts work. If there was a clear way to become more skilled at using these machines and an objective way to measure my success at using them. That wont be too far from programming.
Wrote this to explain expression parsing to myself.
jamungacch.com/blog/posts/pr…
WorldEnder retweeted
The easiest way to build an EV is to buy parts from a catalog and screw them together. We decided to do it the hard way.
This is what happens when you build an entire ecosystem from scratch. Over 100 granted patents working as one machine.
We at @Matter_India built our own dual cradle frame. We engineered a custom motor and gearbox. We designed active thermal cooling and a smart battery brain so performance never drops.
It took years of obsession to get this right. We didn’t assemble this machine. We engineered it.
WorldEnder retweeted
Same graphs are true for the code itself. A lot of people think that performant code is hard to maintain and work with, but the opposite is true, up to a point. Then, when you need to push past a certain performance boundary, the code does become harder to work with.
WorldEnder retweeted
Umm... I would like to talk to the manager to bring StackOverflow back.
I ran into some obscure error message when running an ansible playbook. Talked to GPT-5.2 (x-hi) and Opus 4.5, they were going around in circles.
Decided to Google it (gasp) as a last resort, and the first result was a StackOverflow post from 9 years ago...
There's no way an answer from 9 years ago is going to work with the latest version of ansible, I thought.
But nope, it actually worked.
I tried at least 10 different things that LLMs suggested before that.
But my good ol' stranger friend on StackOverflow solved it for me.
So yeah, can y'all please start posting questions and answers on SO?
Turns out, we can't survive without it.
WorldEnder retweeted
I took Opus 4.5 Max Mode for the ultimate test.
I asked it to search my code base for bugs
I took a lot of pride in this code, all hand rolled, by the sweat of my brow. It was mine and it was good.
Claude found 15 bugs
I was devastated
So I went to the first bug, and asked for a unit test. It produced a unit test in mere moments.
I ran the tests and saw it. A broken test. Property test of undefined. Rookie error
Ashamed, but determined I set forth to fix these bugs as penance. So I cracked open nvim getting ready to edit this typescript script
But... The code seemed correct. Weird.
So I checked the test, Claude faked bad data. The setup could never happen
Wtf
It's a lie, the whole thing.
I checked every bug Claude found. Every line item was not a bug. Everyone of them just some condition that cannot exist due to asserts or previous if statements
What an amazing $3s and 20 minutes spent
Normally when I waste time at least I learn something