Anything that compromises the bottom line or puts the next executive bonus at risk is considered a waste of time.
From their POV quality, privacy and security are not worth investing in. Unless the government forces their hand, and even then they'll find ways around it.
It kinda makes sense from a cynical business point of view. A company increases its revenue by acquiring customers and/or raising prices. It makes sense to spend resources on adding features (increasing the customer base and justifying price increases) instead of on fixing bugs/issues because the existing customers are already willing to pay for the somewhat broken product. But absent other info I think it is pretty harsh to fire an employee for not viewing things in this way, it could be an opportunity to teach instead of punish.
> I know someone who was essentially fired because he spent too much time solving customer issues instead of shipping new features.
Me too! Very smart guy, well mannered, easy to work with so support kept reaching out to him and the senior manager fired him because he was focusing more on solving issues than new stuff. Also, support is a different org, they are born to suffer.
The manager wasn't going to get his own growth by not delivering much new stuff and just improved maintenance. So obviously he didn't focus on how we can reduce these recurring issues so that we have more bandwidth to focus on new issues. Because who cares about pressure on these developers, they are an unavoidable nuisance, you see (AI is solving that very long standing grievance).
Laser sharp focus on survival + growth + current bonus cycle will do that.
My day job has a Claude account, but for personal projects, I have been playing with different models and environments on my home server. My current setup is Qwen 3.8 Flash Next, Strata, and OpenCode/OpenChamber.
I already had a bunch of my projects on the server with with code-server (VS code in a browser) set up to access it, so switching between code-server and OpenChamber is just switching tabs.
However, I've mostly been managing it from my phone - the OpenChamber app is awesome. I still switch back to my laptop occasionally - it's a better interface for reading and writing code, and also the desktop OpenChamber app has a built-in browser that it can control, which comes in handy. I can bring up documentation in one tab, log into a service in another, and then tell the agent to do something. For example, this was how I got it to connect my Nest thermostat to my Home Assistant instance after I had tried and failed several times on my own.)
Oh, and separate from all that, I have Facebook muse set to automatically lower prices on a couple things I have on FB marketplace.
To be honest I would love for someone to work on the structuring of pg_dump for example, which is entirely driven by regexes and binary structures. It’s awful and absolutely not programmable - a real shame.
I look for touchscreens when looking for a cheap windows laptop for someone because they tend to be better quality screens (IPS, decent brightness, etc.) instead of some awful TN panel that's barely visible in a well-lit room.
I don't really expect anyone to use it as a touchscreen, but if they do, at least that will work too.
That’s a good requirement I didn’t think of that. A bad TN panel will make me sell or toss a laptop regardless of spec. Meanwhile I’ll put up with slower speeds if the screen is nice
it is also more capable than an esp32. Im dinking around with both. esp32 is very restrictive in its compute capacity. It isnt multifunctional at all either.
A pi zero is to play with, an esp32 is so tiny, that it is more of a build for a single thing, and then set it and forget it doing that single thing.
You cant really stack more and more cool stuff onto it and keep building on it.
That’s why esp-idf has components. I have a bunch of components that are basically “compile if this SDK config is set, otherwise pretend you’re an empty file” using macros.
Then I just pull in all my components. The ones I use will get compiled, the ones I don’t won’t.
Mostly works fine. Eventually you will run out of NVRAM to save binaries on, but another esp-32 is like $3.
OpenChamber ftw! I'm surprised it's not more popular - so much nicer to use than the TUI.
I'm always confused when people at work show me their opencode or Claude code setup of 6 terminal windows open simultaneously with the same illegible walls of text. No idea how people still prefer that over a nice GUI.
Once you really know your keyboard, it's like an extension of your hands. You can fly through those six terminals, and moving your hand to grab a mouse means stopping whatever you were doing. That wall of text is all familiar to me - I see an UI full of empty space and wonder what I could have used it for.
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.
You're not wrong, and I predominately use a TUI at work where I'm actually at the computer for ~8 hours a day.
But I use OpenCode / OpenChamber for personal stuff where I might only get 20 minutes at my computer before I have to go do something else. So the web interface and especially the mobile app get more use from me there. It's kind of wild to be working on a project while walking my dog or washing dishes or something along those lines.
I also used the desktop OpenChamber app once recently because it has a built-in web browser that the agent can fully control (unlike, for example, Gemini in Chrome).
Reading long walls of unrendered markdown is where the TUI is not fun and the GUI can shine. Especially when illustrations come to play.
Also editing your own prompts with a normal text input is far better IMO (instead of whatever magical box Anthropic or OpenCode has shoehorned into the terminal).
I really like Pi, especially for when you're running a local model and your context is particularly limited. But even when running a big model, I think building up your environment to be exactly what you want can be really powerful.
When I was first getting started and didn't realize that ollama defaults to incredibly tiny amounts of context, Pi was the only harness that actually worked because the rest of them used up all of the context and then some with the system prompt. However, these days I've figure out llama.cpp and proper context sizes.
OpenChamber has been the real game-changer that caused me to switch back to OpenCode, though. I love being able to check in on it from my phone, a browser, etc. instead of having to be at my computer to get anything done.
reply