115,915 karma · joined July 27, 2010
Contact me at hn@jacek.zlydach.pl.
(I mean it. Don't hesitate, I'm always happy to continue interesting conversations after their HN thread disappears off the front page.)
Homepage: http://jacek.zlydach.pl. More: https://keybase.io/temporal_pl.
I do software nowadays, but I'm constantly looking for opportunities to do something actually useful for humanity. If you know of some, please let me know - especially if they involve biotech, cleantech or NewSpace industry.
(see also: http://jacek.zlydach.pl/blog/2018-01-06-going-far-going-small.html)
(Admittedly, I read it many years ago, my memory may be off, though I strongly doubt it.)
And then we raced ahead straight into materializing the x-risk everyone thought is still a few decades away, speedrunning through all the mistakes LW folks itemized and worried about over the past two decades.
With people "living in dirt", you can't pull that off because you'll jump ahead so far they'll immediately realize they can't possibly understand what you're selling right now, and shut the argument down. But they can get confused about things outside their direct area of direct experience.
Note: I'm not saying either is smarter or less smart. Rather, "living in symbols" get confused "higher up", while "living in dirt" get confused "low and to the sides", but they probably have more solid grounding.
On the other hand, Opus 5.5 cracked zero-shotting proper LCARS interfaces that near-perfectly adhere to the franchise "design language" even in tiny details, while simultaneously being 100% functional following my admonitions about Airbus cockpit design rules and nuclear reactor control room standards.
So yeah, why wouldn't I use it? It works spectacularly well.
Hell, half of my use of LLMs these days is bypassing around crap in software written by people[0].
The metric in question is not how it's built. It's whether it solves a problem. Particularly for single or sub-100-users software, what matters is whether it does the job the user(s) like, the exact way they like it.
Speculating here, but maybe I'm also hitting at a disconnect between perspectives: I look at a product as tool to solve a problem. But some look at it as something to sell for money or Internet fame. For the former, distribution doesn't matter. For the latter, distribution is everything, and then, perceived code quality/effort signals actually start making sense.
TL;DR: I don't mind using shoddy software, but I agree it's a bit harder to sell obviously shoddy software.
--
[0] - https://news.ycombinator.com/item?id=49875994 I started calling this "Bypass-Driven Development".
Or so it's better at the million other things LLMs are useful for?
Also if you aren't hitting capacity.
Off-work, I use LLMs regularly for both design/coding and non-technical work, but the volume is not enough to trip the weekly limits, and rarely enough to trip the daily limits. So I just go with whatever's current best SOTA available on my Claude & ChatGPT subscriptions and don't worry about limits. If I hit one, I do some household stuff or relax for a few hours (or just turn in for the day), and then the limit is refreshed.
But I agree in principle - the power wiring is there already, it's a matter of spamming cheap low-power outlets wherever cars tend to congregate for a rest.
Make cars work off power tools batteries.
Take e.g. Bosch AMP Share 18V 8.8 Ah bricks[0] or equivalents. Back-of-the-napkin, you'd need about one per 1km of range (+/- various factors). Put them in racks of 5, and allow people to swap out dead racks for charged ones at gas stations[1].
This would give regular people back their favorite experience of gas stations, while preserving environmental and economical benefits. For example:
- People riding short routes could run with only 20%-40% of the racks in. Means they won't need to carry as much mass around. This is like people today who always keep their gas tank half empty or even emptier, to not waste fuel on carrying fuel around.
- People riding long routes could take extra racks in their trunk to exchange range; people operating other equipment could get extra racks for it at the station, too -- same as people today do when coming with gas canisters to the station.
- In case you run out of power in the middle of the road, for some reason, someone else can help you by lending you their battery pack - even easier than lending you gasoline.
- No more worry about battery life degradation - you're constantly swapping out packs, never using the same ones for more than few days or weeks, and it's an activity you are doing regularly - so people would finally realize that batteries are replaceable and stop complaining about used EVs being as good as used iPhones.
- Overall preserves established economics of gas stations and attached restaurants and service centers; every driver born in the last 100 years understands that and will find it intuitive.
- Bonus - the "power tool batteries" was more of a joke establishing scale; actual implementation would be probably sealed "rack-sized" packs with different trade-offs, but on the off chance it is made power-tool compatible, so much extra utility opens - from charging at home, to powering power tools :).
(I think the mistake of the OG idea of swappable battery packs of yore was to optimize for swapping time and keep battery as a unit. Breaking it down into pieces that weigh 5kg or less means you can reuse existing infrastructure.)
--
[0] - Not an ad, I just have bunch of those and invent more and more silly ways to power things from them.
[1] - The new "battery passport" regulations around the world already solve some of the technical issues here.
If the rest of the car is fine, it should be one visit to a shop to swap out old battery for new (and the shop handling recycling/disposal of the old one), and off you go with car good as new.
Some of it, you are. At least for personal use. Our minds are our own jails here - we treat abstraction layers as more than suggestions, and vendor preferences as more than opinions. I recommend to try and challenge it.
https://news.ycombinator.com/item?id=49875994
LLMs, whatever you think of them, currently alter equation a lot when it comes to one-off work like this. I have the skills too (for some of these things), but I don't have time/energy/capacity to do the things necessary to bypass around the obstacles. LLMs do.
This is doubly ironic, because so, so many companies would be much more useful for the customers if delivered as a spreadsheet file for download.
I know, I worked for one too; said so in the meetings many times, especially watching the frontend side screwing up tables in SPA so they would choke rendering couple dozen rows of numbers.
So much time, effort and money is spent on designing subpar products and services, where spreadsheets would do better, simply because the value of using a spreadsheet goes 100% to users, and it cannot be that users reap all the value of their work, without a host of businesses capturing most of it along the way.
The whole point of replacing spreadsheets with a SaaS is usually to lock-in a specific "user journey" and force users to follow it, and this rarely if ever serves the user.
They have no other choice.
Tech is magic, it's near-pure supplier-driven market. Consumers don't understand it, barriers to entry are stupidly high[0], but the products/services are still necessary. Consumers are thus forced to choose from what's available on the market, not what would be actually useful. Companies know this very well.
This was true before computers, too - TVs, appliances - but is much stronger with computers (and every non-computer tech becoming a computer skeuomorphing as appliance).
That's why people "put up with this stuff voluntarily". They learn to cope, learn to not touch this if they can avoid it, and maybe silently complain to friends and family. That's why "can you fix my printer" is one of the most hated aspects of family life by computer people.
--
[0] - Hardware is pretty much impenetrable, because the easy parts are high-capital, and the important parts are supplier contracts, which everyone who matters has cornered already. Software-side is technically one of the lowest barriers-to-entry economic activities in history, and LLMs help a lot, but in practice, software is rarely the valuable part of software (!) - it's usually network effects (e.g. social media) or supplier contracts (Spotify, etc.), or such.
Humans still can't flap their hands and swim or fly.
You have people here in this thread - and in every other AI thread - seeing themselves as exploited for information for LLM companies to profit. This is such a backwards, scale-inverting perspective that it shouldn't be possible to hold in a rational mind, and yet.
- Those with safety training for this class of foot-pointed firearms, who know how dumb shit looks like and that they should not do it;
- Those with officer training who are able to recognize the higher-level categories, and take principled approach to safety - e.g. recognizing that "date", "timestamp, "duration", "time of day", "time of week", etc. are different concepts and should not be mixed.
Bypass-Driven Development: making progress by routing around obstructive abstractions instead of integrating on their preferred terms.
Motivating thought: often enough you already have all the pieces to solve your problem, and have legitimate right to use them, yet those pieces refuse to talk directly with each other because of a mix of technical and business reasons. API boundaries, OAuth walls that invite getting additional vendors (identity providers) involved for no good reason, platform purposefully preventing interoperability, enshittification, lack of "business need" to integrate - or worse, having a business need which means integration suddenly involves you being a third party to a contract between two service providers.
There's no technical limitation to prevent this, but I've noticed people started taking abstraction layers, API boundaries and "intended use" as holy writ, and assume you can't do something because "it's not how it's supposed to work".
BDD is my claim that an abstraction which obstructs a legitimate goal forfeits its right to be respected.
Subpattern of this, Bypass in Anger (BIA), when routing around becomes routing through. Evocative example: modern soldiers navigating dense urban environment by ignoring it entirely, and moving in straight lines, just blowing holes in any walls that are between them and their destination. That is my answer to when "the computer says no".
Kinda a pragmatic blend of Adversarial Interoperabiltiy/ComCom, "computational self-determination", good ol' hacker ethos, and a counterpoint to "security maximalist" doctrine that runs modern computing, with a hefty dose of defiant "you are not going to tell me what I can or cannot do with my data on my computer".