You mean "went" right?
Top shelf phone I hope it holds on for awhile. I mainly love having an answering robot, but let me put my phone number on the internet for free!!! That way there's no point in buying my phone number from a data leak.. frankly the whole concept of phone numbers and gives me the ick for a lot of reasons.
Or pull your friends out while he pulls yours out
Getting old means all the famous people you grew up with just disappear like this one by one...
Waaaooww what a position
I'd want to disagree bc I know Nix and that feels declarative to me where as html just feels like actual drawing, like there's no conditional or iteration therefore how are you transforming information? HTML is a markup bc you need to render a UI and you don't know anything about the screen or keyboard&mouse so cope
This is a LinkedIn screenshot, sry if I cropped it too tight
A bunch of weeks ago the CTO of my company calls me up to ask about my prejudice against the useState hook, I'm guessing I've just been giving my team too much shit in code reviews about them using useState hooks and they went to complain to him and he asked me to explain what the value of the useReducer hook was.
His background is Java, Microsoft Java, C++, and not much else.
So I was able to explain to him the value of the useReducer hook is a lot like the common class object. In useReducer you're expected to write discreet state mutations and the state could potentially have more than 1 primitive field that gets mutated, and that's just what object classes are! In an object class you're writing methods for mutating the underlying state, the reason I think most people don't feel like these two things are the same is because of the functional appearance of the reducer function and how in object classes you have the this as a variable just like any other, so you're not returning a new state.
So just like in react where they're installing REDUX (like three generations of their families would be massacred if they didn't) just to write a switch case statement that puts the action in variables in the state. Bad programmers are just bad.
Only typescript is great. Raw JavaScript is like rawdogging someone (iykyk), you get STDs
A perfectly accurate statement when the set of all use cases for PHP has 0 things in it 👍👍👍👍👍👍👍👍👍👍 1000000000% agreed
I'm so heartbroken by the idea of unit tests. My first job was at a home automation startup and our primary product was a device that we would send ota firmware updates to. The device was based on an esp32, and because it received software updates from the app it had to be 100% robust and had full test coverage and the mono repo that would compile the firmware was gorgeous.
I'm a web developer and I've been wanting to replicate that exact experience ever since but I just can't get any team on board. It's gone to the point where if the llm writes a unit test I'll just commit it so I don't care.
I feel like useState and useEffect are 2 sides of the same coin
Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
cross-posted from: https://programming.dev/post/56563524
We're about to learn a painful lesson about delayed gratification in software engineering.
New data from China, 26,811 students tracked January 2023 through June 2025. Students using AI for homework saw their scores jump 20 percent. Completion time dropped nearly half. They aced the assignments.
Then exam season came. Those same students scored 20 to 40 percent worse when they couldn't use the tool.
The homework phase is over. The exam phase is coming.
We're doing this in software right now. Vibe coding feels incredible. Features ship fast. Nobody's asking what happens in Month 18 when the original dev has left and nobody understands the codebase.
Commercial pilots fly with autopilot for most of every flight. They're required to maintain manual flying proficiency regardless. If the system fails mid-air and the pilot can't take over, people die.
Most teams using AI right now have forgotten how to fly manually. They've become passengers in their own systems. The autopilot flies, nobody checks instruments, and the first sign of trouble will be a breach notice or outage.
Three rules:
- Command the mission. Define architecture before prompting. Ambiguity kills in code and in flight. Delegate selectively. Offload mechanical work. Keep design and security reviews human. Verify everything. Audit before production.
- Never trust the automation without checking instruments.
- Quick wins feel good. Sustainable engineering feels boring. Boring keeps systems standing.
Organisations surviving the next two years won't ship the fastest. They'll be the ones who remember how to fly without the aids.
people insisting that you actually be skilled, independently of your tools, doesn't make them Luddites. Rather, being unable to do so makes you a phony.
We're about to learn a painful lesson about delayed gratification in software engineering.
New data from China, 26,811 students tracked January 2023 through June 2025. Students using AI for homework saw their scores jump 20 percent. Completion time dropped nearly half. They aced the assignments.
Then exam season came. Those same students scored 20 to 40 percent worse when they couldn't use the tool.
The homework phase is over. The exam phase is coming.
We're doing this in software right now. Vibe coding feels incredible. Features ship fast. Nobody's asking what happens in Month 18 when the original dev has left and nobody understands the codebase.
Commercial pilots fly with autopilot for most of every flight. They're required to maintain manual flying proficiency regardless. If the system fails mid-air and the pilot can't take over, people die.
Most teams using AI right now have forgotten how to fly manually. They've become passengers in their own systems. The autopilot flies, nobody checks instruments, and the first sign of trouble will be a breach notice or outage.
Three rules:
- Command the mission. Define architecture before prompting. Ambiguity kills in code and in flight. Delegate selectively. Offload mechanical work. Keep design and security reviews human. Verify everything. Audit before production.
- Never trust the automation without checking instruments.
- Quick wins feel good. Sustainable engineering feels boring. Boring keeps systems standing.
Organisations surviving the next two years won't ship the fastest. They'll be the ones who remember how to fly without the aids.
people insisting that you actually be skilled, independently of your tools, doesn't make them Luddites. Rather, being unable to do so makes you a phony.
cross-posted from: https://programming.dev/post/55845570
After watching the Witch Hat Atelier anime I started getting tiktoks about it.. lots of AnimeNYC cosplayers running around in pointed caps all cute n shit. It showed me a tiktok about this old program from 2005 called Shimeji and this guy had brushbuddy hanging out on his screen. I fell into a rabbit hole, bc I've had oneko installed for so many years I was used to having screen pets around and I wanted this little guy too. My workstation is made so much brighter because of them
I opened this community to spread the word of the fun these little guys are!
After watching the Witch Hat Atelier anime I started getting tiktoks about it.. lots of AnimeNYC cosplayers running around in pointed caps all cute n shit. It showed me a tiktok about this old program from 2005 called Shimeji and this guy had brushbuddy hanging out on his screen. I fell into a rabbit hole, bc I've had oneko installed for so many years I was used to having screen pets around and I wanted this little guy too. My workstation is made so much brighter because of them
I opened this community to spread the word of the fun these little guys are!
cross-posted from: https://programming.dev/post/52191489
view more:
next ›