TonyAlicea10

6 ms·

61.
by TonyAlicea10 4mo ago
Yes I said “many” because if I didn’t qualify it someone would mention Rust.
62.
by TonyAlicea10 4mo ago
Thanks! It's all stored locally on your device. No login, database, or trackers.
63.
Show HN: 0llm is a small app to help you spend time away from AI(0llm.tonyalicea.dev)
1 points by TonyAlicea10 4mo ago|2 comments
64.
by TonyAlicea10 4mo ago
Many browser rendering engines are built in C++, so C++ is parsing the HTML. My general point is that many web/internet techs that web devs interact with have C++ one abstraction level below for actual implementation.
65.
by TonyAlicea10 4mo ago
I always tell web developers I teach that the language of the internet isn’t JavaScript it’s C++. Web devs are just users playing in a C++ dev’s program. ;)
66.
by TonyAlicea10 4mo ago
Relational model too, yes. But the biggest "aha" moments I've had mentoring devs on thinking in SQL came when they understood that the result of a query is itself a set. So you can join two selects, join that result with anot
67.
by TonyAlicea10 4mo ago
I’d say the most impactful thing is not to learn SQL, but set theory. Well-written SQL is about thinking in sets. I cannot tell you how many poorly written procedural stored procedures I’ve replaced with a single performant SQL query over t
68.
by TonyAlicea10 4mo ago
Gmail’s summaries are both intrusive and poor quality. They actively make the email experience worse. This is all a solution looking for a problem, pretending that people don’t have time to read or write their own email. With both Google se
69.
by TonyAlicea10 4mo ago
Lots of slop indicators in this article. That’s why I didn’t finish reading it. If the author doesn’t have the time or care to write it, why should have the time or care to read it?
70.
by TonyAlicea10 4mo ago
Beware the Cumulonimbus.
71.
by TonyAlicea10 5mo ago
This is in many ways what user experience designers might call "the five whys". People don't express their problem in the form of a problem, but a solution they've thought of. They don't say "I'm hungry, f
72.
by TonyAlicea10 5mo ago
> You want a change to a part of text? Span. You haven’t read the HTML spec. There are an incredible amount of elements, including for changing just a piece of text (b, i, strong, em, and many more). Plus elements for visual aspects like
73.
by TonyAlicea10 5mo ago
I can do a lot of layout without divs. Adding aria to divs is an anti-pattern and likely a worse experience than semantic elements. You might need some extra divs for layout sure. But I guarantee less than most people are using if they mark
74.
by TonyAlicea10 5mo ago
This is ironic to me because Tailwind’s paid templates are absolutely terrible div soup.
75.
by TonyAlicea10 5mo ago
The HTML spec says divs are the element of last resort. This issue isn’t that they’re bad. The issue is they are reached for far too quickly. Also if you think massive numbers of nested divs don’t have a performance impact in the DOM when r
76.
by TonyAlicea10 5mo ago
I disagree. With Tailwind you think in nested classes which ergonomically encourages “I need a div for this class”. Very similar to early React where every component had to return a single real parent element (now you can return a fragment)
77.
by TonyAlicea10 5mo ago
Who said inherent. The design loop of “I need a div for my CSS class” is an ergonomic problem not a concession.
78.
by TonyAlicea10 5mo ago
Folks in this thread keep conflating “forces to” and “ergonomically encourages”. If a power tool is poorly designed it may not force me to hurt myself but if it makes it easier that’s a problem.
79.
by TonyAlicea10 5mo ago
It’s not Tailwind the tech, it’s the ergonomics of the tool. Tailwind’s design loop encourages “let me add a div so I have a place for my CSS class”. I’ve usability tested and performed user research with many users needing assistive tools
80.
by TonyAlicea10 5mo ago
I mentioned blind but there’s lots of others. Folks sitting a desk whose eyesight are getting worse and are scared to say so for fear of losing their job, for example. This happens. Side note: if you aren’t deliberately choosing semantic el
81.
by TonyAlicea10 5mo ago
React encouraged this for years by requiring a single parent element being returned from all components. They also showed a div as the option of choice. They fixed this later with Fragments but the damage was done.
82.
by TonyAlicea10 5mo ago
If a tool’s design makes it easy to cut myself, the response is not “people have been cutting themselves for years”. There is such a thing as the ergonomics of the tool. Yes div soup has been around a long time. But also yes, Tailwind makes
83.
by TonyAlicea10 5mo ago
This isn't about "purity/correctness" it's about the real experience of a blind person. Accessibility means caring about the HTML. Your comment only mentions developers as the audience of HTML authoring, as opposed
84.
by TonyAlicea10 5mo ago
The "open a different file" reasoning piece is a common pro-Tailwind statement and I do see the upsides. I think that upside became more prevalent in the reusable components era, whereas previously CSS was targeting an entire HTML
85.
by TonyAlicea10 5mo ago
> I got curious about what writing more semantic HTML would feel like. I've been teaching semantic HTML / accessible markup for a long time, and have worked extensively on sites and apps designed for screen readers. The biggest
86.
by TonyAlicea10 5mo ago
When designing AI-based user experiences I refer to this as provenance. It’s a vital aspect of trust, reliability, compliance and more. If a software system includes LLM output like this but doesn’t surface the provenance of its output for
87.
by TonyAlicea10 5mo ago
At the core this is recreating the right click via voice. Interesting but not “reimagining” anything. I think the real story here is how vibe coding now enables flashy demo sites like this to be built for a concept that hasn’t yet earned it
88.
by TonyAlicea10 6mo ago
“Money was never the constraint. Knowledge was.” The irony is how difficult it is to read this obviously AI-generated article due to its unnatural prose and choppy flow full of LLM-isms. The ability to write is also a skill that atrophies.
89.
by TonyAlicea10 6mo ago
I wouldn’t go that far. It was pretty clear a long time ago that humans spending so much time filling the internet with content was going to eventually enable neural networks to pretend to communicate. The advancements required to arrive at
90.
The Evaluability Gap: Designing for Scalable Human Review of AI Output(tonyalicea.dev)
1 points by TonyAlicea10 6mo ago|0 comments

More ›