code-blooded
Joined 4 years ago
Joined 4 years ago
Authentication is happening where I live via electronic ID, but once you authenticate you could still use agents on your behalf to compare messages / request public services.
I still envision a deterioration of quality of responses we will be getting. At least in cases where we really need help not something that should have been a button in the first place.
It looks like a pretty bleak future to me ...
It's interesting how personal font choice (among many other things) is!
It's a difficult market though:
- Vast majority people use router provided by ISP. - Some unhappy with ISP hardware quality buy whatever they find online (in my country usually TP-Link devices) - Enthusiasts flash OpenWrt on cheap devices, home servers or buy MikroTik devices (or similar). - Non enthusiasts, but caring about quality and support still have some good (but more expensive) devices to pick from like Fritz!Box in Europe
People wanting pre-flashed OpenWrt will be fraction of a fraction of overall market, so you'd need to charge a lot, which puts you in direct competition with options above.
I thought people at work would be mad, but everybody adjusted instantly.
Next up I'd like to pre-plan blocks of focused work - an idea I got from the Deep Work book.
I wonder if true transaction cost even reaches the 0.2-0.3% or could be further lowered.
Personally, so far I got best results by carefully selecting a small number of apps and devices with good track record and community around them (think Emacs that's been around for decades, but also KOReader, Linux, AntennaPod on Android and many others) and supporting those in various ways. I might vibe code an extension or config for the apps, but then I still understand what it does and why.
AI is yet to change that. I use LLMs daily at work, but software maintenance remains problematic. Producing stable software in unstable times is actually what pays my bills.
Edit: And yes - if you fork, upstreaming is a problem. It's unfair for original software maintainer to need to review, test and integrate vibe coded code.
There's a big difference between putting money or time into a community of builders and learning in the process (myself or growing others) and maintaining a vibe coded project. That's why I want to know right away which projects are vibe coded so that I don't put any effort into them.
You're free to apply different criteria to software you use, but we're talking about having information to make an informed decision here.
Very bad battery life. Maybe 8hrs of reading with wifi off, BT off and only low screen backlight. I need to charge it daily or every other day at best.
Physical buttons are comically bad and often don't register presses.
Built-in book reading app is slow, lacks some critical features and hangs in many epub books. I replaced it with KOreader which finally made the device usable.
It's a great screen size though (9" would be even better).
It's not that vibe coding is bad on its own, but it makes me worried about project's future (ease come, easy go).
Some European banks including mine offer NFC payments via their app as well. You don't need Google services.