wangsg

@thunkoid @plainionist scrum came before agile, no ?

@plainionist I think the simple Agile manifesto is great. I think Scrum turned it into something else entirely. The best engineers I know don’t work in Scrum. They work in small teams, with agency. Getting work done is self evident. It doesn’t help that so many orgs “do it wrong”

Serious question: In your experience, has Scrum created stronger or weaker engineers?

@Ngnghm there you go...bigger problem :)

@quangsg Alan and I disagree on what exactly to call "Object-Oriented Programming" quora.com/How-much-did-D…

If Simula was OO, why does nobody use the "concatenation semantics" of Simula (and Beta, its successor, also universally unused, because frankly unusable, and incomprehensible), but everyone uses the method resolution semantics of KRL and Smalltalk?

@Ngnghm Trygve, MVC creator, tried to solve it with DCI

@quangsg They did, starting with Smalltalk-76.

@Ngnghm object interaction was not solved yet

@Ngnghm around 1:04:53

@crutchcorn @hellonehha who calls the update when one of them changes :)

@quangsg @hellonehha Except that it's not a blackbox and is explicit?? Like????

no. If the products and bigger products are breaking due to useEffect then it is 💯 a bad API design.

@hellonehha @crutchcorn cyclic blackbox dependency list :)

@crutchcorn i still don’t agree with this. If it would be about 1 product then 💯 this could be an issue but last year we saw what was happening. Either their is lack of awareness , docs are not enough , guidance is not great job

@big_chocky trickle down :)

When the government tells you: “We’re in the same boat”

@fhinkel not 10x profit?

Vibe Coding makes you 10x faster at making 10x more technical debt.

@vidamrr universal reaction: skill issue :)

Después de leer el post puedo concluir que el problema no es usar useEffect, sino que hay gente que no sabe cómo usarlo y por lo tanto lo usan de la peor manera posible. Si de verdad fuera tan malo ya lo hubieran deprecado. Mejor enseñen a esos developers que no es navaja suiza ni la vieja confiable cuando no sabes manejar estado.

@dev_maims open vs closed

What's the difference?

@crutchcorn @DavidKPiano github.com/day8/re-frame :)

@quangsg @DavidKPiano Point to a better one.

useEffect isn't a bad or poorly designed API; it's a primitive on which to build your own APIs on top of. The educational and tooling corrections towards avoiding usage is broadly a net positive, but the cultural misinformation that it's a "bad design" is a net negative.

@mrdoob meta found missing piece for metaverse

DLSS 5 OFF / DLSS 5 ON

@sahill_og good, you have 2h-builder team :)

Job interviews in 2026 should just be: "Open your laptop. Build something in 2 hours. We'll watch." No leetcode. No "tell me about yourself." No "where do you see yourself in 5 years." Just build. That's the whole interview.

@EthanHe_42 yes, lazily scale :)

Intelligence scales with compute. And compute scales with energy.

@thesayannayak I stored my cache in database :)

Interviewer: If cache is faster than a database, why isn’t everything stored in cache ?

@BlackHC I predict the usage of software to to zero eventually :)

A while back, Andrej Karpathy said the app store will be replaced by generated, disposable software," and Amjad Masad predicted that the value of all application software will go to zero I think this "ephemeral software hypothesis" is wrong, though, and I want to explain why:

@zg_dev @rahulj51 what is the adoption rate of TDD in the industry .. dont confuse TDD and tests :)

I agree. I can see an argument for TDD and using that as your spec, but I have never been able to retroactively read through prompts and have any clue what the end product may have become. This narrative seems to be gaining traction among a lot of smart people so I tread lightly here, but I just can’t see how TDD and real code could ever become inferior to a markdown document or set of prompts.

I don't know. Hard for me to agree with the spec-is-code argument. Specs are low fidelity. They aren't a common shared DSL. Have very low signal to noise. Not verifiable or deterministic. They don't encourage iterative work. Almost always written by an agent, thus prone to more slop. Lose their inherent value as soon as they are converted to code. Specs are throwaway. They are a way to temporarily express behavior intent - an agent translates that to a version of code. That's the thing that lives forever. If you are convinced that spec is code then you should be able to confidently delete all code and regenerate from specs.