1,161 karma · joined June 29, 2011
Or, is this "people watching broadcast content on devices", or "you'll get YouTube TV for free"?
Of course there are great reasons for using pointers also. I'd say this is mostly a preference, I'm sure you are extremely effective using your own methods. I have maybe two dozen terminals open atm, and I can tell you what each of them is for - but put a phone bill or a bank statement in front of me and it might as well be Greek.
It’s a lose/lose proposition for every software company with more than three management layers. We're frozen in place.
You need to be an an org who is able to deliver directly to your consumer, who needs to be defect-tolerant with the expectation of quick iteration. That customer will have access to advanced tools that its competition is unwilling to adopt. Many will fail.
There are many verticals for which this does not work at all - but this is unlikely to be the permanent state. The new model will work its way through the market, and companies will fall as fast-moving competitors find a willing customer segment they can target, make that segment out-compete the others using their access to tools with superior abilities but higher defect rates. The customer base will eventually adopt, having become accustomed to this, and so slowly expectations will change, and so will our field.
I for one welcome our slop overlords.
Some motherfucker today suggested we should use Haiku for all coding tasks, and this guy is a Sr Director of real humans.
In my professional life however, we are NOT producing more software ($bigco). We are on the edge of it maybe. My experience is we've been on the razors edge - just enough staff to meet the business needs - and so every AI iteration sped up some process, which exposed some limit in a dependent process, which we tried to free up with a reorg, which cut capacity somewhere else, and the snake eats its tail. We've had enough iterations to get to a place where an increase in developer output probably won't cause the whole thing to fall over. I hope.
But anyway, I spend a lot of time exploring new dev tools, it's sort of a hobby of mine; I like to understand the state of "what's out there" and this has helped me professionally. This has recently become impossible do the sheer mass of llm productivity, while at the same time more fun than ever; the amount of crazy interesting and seemingly mature brand-new things (in the dev space) has astounded me. I found Swamp Club recently, like wtf where did this come from? It's like five dudes with LLMs.
Currently, learning programming is the lever to unlock architecture understanding. We will need a few new layers of abstraction before this changes.
They are working on a cli agent; I tried it, but it silently injected hooks into all my other cli agents to re-target JB inference APIs, which caused me to burn through my JB tokens in like two minutes and b0rked all my running agent sessions.
They are working on a spec-driven thing, which I attempted to try but getting burned by the cli thing I abandoned it. It looks really interesting - it's a meta-harness, built and shipped with one of the Spec-Something frameworks, where you define your own specs for your projects, kinda like snake-eating-it-own-tail-of-specs. If spec-driven is The Future, they are at least trying.
There have been a few other things I can't recall, but my observation is that they are taking generative AI seriously as an existential threat, and probably (as another poster here put it) "heating the office burning tokens".
In this proposed world where this static software is replaced with dynamic software ("AI will build it JIT"), doesn't that destroy the value proposition?
And in the world where normal software becomes AI-integrated ("software has intelligence "), isn't this tantamount to very very high hosting costs - where each execution now costs centi-dollars instead of nano-dollars?
Seems like the only use case where the cost model is equal or better is "AI writes the software".
There have been a few very good harnesses - like Amp, which is excellent - which made this same choice and just haven't had the adoption they deserve.
Is there a middle ground , like where the "main" agent uses an API, but delegates using provider mechanisms (claude -p et al)? I don't mind paying for intelligence, but coding agents are expensive and at this time I am nearly exclusively using subscriptions for them, until the math (inevitably) changes.
Her and the Apple Lady talk quite a lot. It's really useful, and we barely use the phone anymore (light switch is even rarer).
For a workflow where you are also display switching (kvm etc), Synergy doesn't work well. You can technically use it when hosts are coming on/off display, but it's not designed for it. If you use a kvm-like workflow and have a Magic Touchpad, there's no easy solution without re-pairing, and I hope OPs tool works for this.
It's not beyond reason to guess that you stumbled into some niche ad targeting group, like "US grape juice drinkers who've visited Germany", and your old email identity was transitively linked somehow. Maybe ten years ago that email was about grape juice?
Something like IR emitters, infinite-crawl QR Codes, IR-only nsfw content, lidar to damage sensors but not eyes, something fun.
This might've made a better argument ca. 2005 wrt a 20-something Austrian's minimalist wsgi framework. Heck, I'll bet you could even find said argument somewhere in the Archive :)
I overused Astra in order to drain my weekly, figuring I'd have the reset. (not wastefully, I did get more work done)
I've wondered why I haven't seen this everywhere.
If so, you could target any number of render backends, keeping the same simple interface for your agent, avoiding the bazillion problems rendering engines face to work well across the ecosystem.