4mitkumar
Joined 10 years ago
Joined 10 years ago
But learned a bunch about bosons, fermions, QCD, gluons, Kugelblitz, composite bosons and finally Noether’s Theorem on symmetry. Was a wild ride
I have moved away to Jekyll again but there's always something alluring about single file things - single file webapps, single file LLMs (llamafile) and others
Sometimes, I' get excited by an idea, may be even write a bit about it. Then turn to LLMs to explore it a bit more. An hour later, I feel drained. Like I have explored it from so many angles and nuance that it starts to feel tiresome.
And within that span of couple of hours, the idea goes from "Aha! Let's talk to others about it!" to "Meh.."
EDIT: I do agree with this framing from the article though: "Once an idea is written down, it becomes easier to work with..... This is not new. Writing has always done this for me."
Like the author says - fleet-tracking system, a bus-ticketing platform or IoT platform share some basically similar requirements. And this is what those SAP types offer - standardised templated versions of workflows.
But slowly, as they get more and more standardised, they start feeling like calcified systems that the end users start hating. Because they are now forced to work as per the templates.
And then the need for customization. And move beyond IKEA-like standardization.
But I see the allure of the idea.
They also have a voice input only version if you still would like to keep your typing keyboard: https://voiceinput.futo.org/
I wonder that's a new corporate strategy - charge randomly till someone goes through the pain of IVR and spends 15 mins with support. Must generate quite an upside for them if it is indeed a strategy.
I suppose this is one interesting pattern for that.
_1: (explored a bit here at https://world.hey.com/akumar/software-s-blog-era-2812c56c)_
I made this primarily for myself – I'm someone who gets stuck between "I should be productive" and "I literally cannot decide what to do right now." The pattern I noticed: starting anything small breaks the spell, then I can think about actual goals.
The (optional) AI suggestions are deliberately constrained to be actionable (15-60 minutes tasks that ladder up to your goal) rather than generic productivity advice.
Would love to hear if this resonates with anyone else, or if you have thoughts on the approach.
It is a crisis and the risk of A(G)I is real. But almost all this while in the history of automation, we have blamed implementation of automation when things go wrong. Instead of attributing morality, intent and so many other things that we do with LLMs.
Without having to go in to the philosophical validity of these concepts applied to AI, I feel it's much more useful to focus on the implementation of automation here as well - what risks were opened, how was the env hardened, what was the observability like - how was it being observed anyway, and more.
Done poorly, that can be catastrophic enough. But that sounds mundane. And does not help the hype.