KJ

Likes to code. Creator of Hydro.

[Mitchell Hashimoto @mitchellh]

The problem with the "if it works who cares what the code looks like" mindset for agentic work is that it assumes the agent has a perfect understanding of "works." Realistically, things are underspecified, agents make bad assumptions, etc.

To be fair, agents are pretty good at unit test coverage. They're pretty bad at designing human experiences (API, CLI flags, etc.), especially cohesive ones for future roadmap plans they may not have visibility into (unless your backlog is perfect and vision fully laid out, which I doubt). They're bad at knowing where performance matters and what type (CPU vs memory tradeoffs). They're bad at where compatibility matters and where it doesn't (and tend to err on the side of preserving it without further guidance). Etc.

Unless you have this ALL specified, you can't possibly claim "it works" without taking a look and thinking about it.

[KJ @krjeske]

@ThePrimeagen Lol

[KJ @krjeske]

@stevensanderson There is even a fix for IE11 😉

[KJ @krjeske]

@theDiverDK @stevensanderson Azure Portal, at least when I checked last time

[KJ @krjeske]

@vyrotek @htmx_org @DamianEdwards Have you tried https://t.co/eEU4tnsbEp ?

[Vlad @vladquant]

Fun fact: We show Reddit/HN threads because that's where actual humans are discussing it.

Humanize the web!

[KJ @krjeske]

@Alicks14 Thank you

[KJ @krjeske]

@dhh @jarredsumner I wonder if dotnet will ever appear on this list. Would be lovely. :)

[KJ @krjeske]

@nickchapsas @davidfowl Isn't it just a matter of removing one folder?

[KJ @krjeske]

@DevLeaderCa 🚀

[KJ @krjeske]

@levelsio @pabloschz_ Is it one global app with one instance or multiple instances?

[KJ @krjeske]

@mjovanovictech From what I've seen, some devs know what asynchronous communication is, but they didn't know it's called that way.

[KJ @krjeske]

@davidfowl @dodyg @usehydro Good point, thanks. I'll fix it.

[dodyg @dodyg]

This is the first sample exploring the Hydro framework (@usehydro)

#aspnetcore

https://t.co/oQKhn803WN

[KJ @krjeske]

@mjovanovictech This is maybe not needed for registration as it can be maintained by the system administrator, but if the user has a feature to save and send an offer to the customer, then it's good to know if the email was actually sent.

[KJ @krjeske]

@mjovanovictech The outbox pattern is very useful but comes with additional considerations. Committing the transaction does not guarantee that all steps are complete. If the background job for sending the email fails, the system must notify the user and provide options for how to proceed.

[KJ @krjeske]

@davidfowl To me, the problem with the first one appears when you have more complex type with a longer name. Then usually I go with the third approach that wraps nicely.

[KJ @krjeske]

@thekitze I agree. The React component model is fantastic, but state management — and hooks in general — are horrible.

[KJ @krjeske]

@derrickbuyonje @dotnet ForEach is actually much less performant than regular foreach statement

[KJ @krjeske]

@Saadeghi Thank you for all the work you do