adamzwasserman

6 ms·

61.
by adamzwasserman 9mo ago
Ironically, this article is itself selection pressure. Once 'excessive bold' becomes a known LLM tell, it gets trained out. We're in an arms race: identify a style marker, watch it disappear from the next model generation.
62.
by adamzwasserman 9mo ago
The author's framing is too generous to management. This isn't about AI at all. Amazon lost money in 2022, started cutting, then posted $30B, then $59B in profit while continuing to cut. Pinterest had one mildly bad year, then a r
63.
by adamzwasserman 10mo ago
Great questions, these are exactly where the mental model matters most. Where to draw the line? The answer is "further than you'd think." Validation errors? data-error attributes or aria-invalid on the input. Derived values?
64.
by adamzwasserman 10mo ago
"I also want my url to reflect the state of the page... It would have been great if the toggle action was implemented as a simple attribute something like toggle='element name'" Your wishlist (state in attributes, URLs r
65.
by adamzwasserman 10mo ago
This really resonates with something I've been working on. The article nails the core problem: we maintain JavaScript state that's just a shadow copy of what the DOM already knows. I built a library called stateless that takes thi
66.
by adamzwasserman 10mo ago
https://github.com/adamzwasserman/domx https://github.com/adamzwasserman/stateless https://github.com/adamzwasserman/genX https://github.com/adamzwasserman&#x
67.
by adamzwasserman 10mo ago
This has direct implications for my axiomatic prompting research ( https://osf.io/pcx2d ). We found that providing LLMs with explicit classification axioms improved LEDGAR accuracy by 10 to 22 percentage points across 7/
68.
by adamzwasserman 10mo ago
The Kolmogorov argument gets stronger in the age of LLM assisted coding. Tokenizers chunk camelCase unpredictably: "parseHTTPSURL" might become ["parse", "HTTP", "SUR", "L"] or worse, depend
69.
by adamzwasserman 10mo ago
You describe yourself as a materialist, so I'll engage on those terms. First: you're conflating the model with the chatbot. What you interact with is output filtered through RLHF, system prompts, and post-processing layers (much o
70.
by adamzwasserman 10mo ago
True, but it is not my code to that with. so... If I ever open source one of my backends I will try and remember to flag it in a reply here.
71.
by adamzwasserman 10mo ago
You are conflating all state into a big undifferentiated soup. I reason about state differently, Here are my axioms: 1. There is no such thing as "state".` There is user/ui state, there is cache state, there is db cursor stat
72.
by adamzwasserman 10mo ago
At the end of the day, personal preferences play a huge role. All programming is a compromise between tradeoffs. React has a lot going for it. It's simply that I prefer htmx; it feels cleaner to me.
73.
by adamzwasserman 10mo ago
hx-trigger in the response header would handle that cleanly. Fires an event client-side; one global handler shows the error. Similar to wvbdmp's approach but without needing the extension
74.
by adamzwasserman 10mo ago
I use nested templates the same way React uses nested components. The key is cascading the context (like props) down the hierarchy. Column order change? One edit in the table template; everything that includes it gets the update. The "
75.
by adamzwasserman 10mo ago
took the words out of my mouth!
76.
by adamzwasserman 10mo ago
my htmx apps have 0 cls. You just have to care enough to do something about it.
77.
by adamzwasserman 10mo ago
Read DATAOS.software for an in depth analysis of bundle sizes and impact on performance.
78.
by adamzwasserman 10mo ago
multicardz is heavy drag-drop ui. totally based on htmx (I still need to get data from a backend, I use htmx to do it for a number of reasons.)
79.
by adamzwasserman 10mo ago
that is why I wrote DATAOS.software. It is a paper/cookbook that answers that question.
80.
by adamzwasserman 10mo ago
Check out DecisionMe.com. 100 percent wizard pattern, htmx based nav and validation.
81.
by adamzwasserman 10mo ago
Not a problem with Jinja (or any server-side templating). Both the table and dropdown render from the same context variable in one template pass. One endpoint, one data fetch, two presentation formats. The "two endpoints" concern
82.
by adamzwasserman 10mo ago
I think you misunderstood me. I use htmx where most people would use fetch. I do not just use htmx willy nilly for no reason. I use pure front end manipulation to set state, then I send the state to the stateless back end with pure function
83.
by adamzwasserman 10mo ago
Honestly? I never think about it. I've never had to. What did you run into? Curious what the pain point was.
84.
by adamzwasserman 10mo ago
That is what DATAOS.software is all about. It is a manifesto of my proposed best practices somewhat like Hypermedia Systems, but more hands on, more of a cookbook.
85.
by adamzwasserman 10mo ago
The debugging question has a direct answer: when you capture User State from the DOM (via manifest) and send it to pure functions on the backend, you get a perfect event source pattern. Not only can I can tell you exactly who and what trigg
86.
by adamzwasserman 10mo ago
The state encapsulation concern is exactly what DATAOS addresses: dataos.software The premise is that React's "UI=f(state)" creates a synchronization problem that doesn't need to exist. If the DOM is the authority on sta
87.
by adamzwasserman 10mo ago
Declarative is the way.
88.
by adamzwasserman 10mo ago
Performance
89.
by adamzwasserman 10mo ago
I was able to find architectural patters that work smooth as glass. Here is what my htmx apps have: - Single-purpose endpoints: Each endpoint returns ONE thing (a card list, a tag cloud, a form fragment) - Optimistic UI: Preferences like f
90.
by adamzwasserman 10mo ago
multicards is almost purely client side interactivity. I STILL use htmx for a number of reasons: - No JSON serialization: HTMX sends form data natively no JSON.stringify() needed - Less JavaScript: Declarative hx-* attributes replace impera

More ›