Join 📚 Siddish's Favorites
A batch of the best highlights from what Siddish's read, .
“One of the big barriers with computers today is certainly the physical interface, but this isn’t a technology problem,” he says. “The bigger part of it is just in finding the right ways of thinking, finding the right representations of abstractions, so people can think thoughts that they couldn’t think before.
“The example I like to give is back in the days of Roman numerals, basic multiplication was considered this incredibly technical concept that only official mathematicians could handle,” he continues. “But then once Arabic numerals came around, you could actually do arithmetic on paper, and we found that 7-year-olds can understand multiplication. It’s not that multiplication itself was difficult. It was just that the representation of numbers — the interface — was wrong.”
The Utopian UI Architect
John Pavlus
Now I very squarely identify as a *product engineer* when it comes to building software. What that means is I'm most interested in building things where the undefined variable is the user's needs and preferences (or call those requirements) and applying the right set of methods to meet the goal of *building the right thing* (this I would juxtapose with what might be considered more pure technical work aimed at *building the thing right* - "the thing" is much better defined at that point!)
Some Ideas on More Safely Prototyping LLM Products
daveguarino.com
• "...my main reasons for writing things down is because I want to find out if there is work I can safely avoid." - @Conaw
• "Another advantage of breaking down the steps into detailed and discreet chunks of work -- you don't have to do everything yourself." - @Conaw
THREAD: The Top 0.1% Of...
@george__mack on Twitter
...catch up on these, and many more highlights
Readwise