arend321

Vertically integrated solo business on a Patroni controlled PostgreSQL cluster spread out over multiple dedicated servers with multiple providers.

Shocks Opencomm 2 headset or my Sony xm6 earbuds connected to a custom Android app. Android local Supertonic model for text to voice, private whisper on the server for voice to text. Local Nvidia Glider LLM for PII filtering of CRM related data. The Android app controls codex app server instances (mostly working with latest GPT model on high), switches between projects and threads based on voice commands, a ton of little tweaks to optimize my workflow. Every service except the public facing website runs behind a Wireguard VPN.

But it's a purpose built, tailored to my needs CRM, mostly automated. Like I ask, "which outstanding issues need my attention". I tell it what to do next, when to notify again and I'm done. All tedious form entry work is taken care of in the background.

The choice is do you want to walk or sit behind a desk when doing a task that needs human attention. It doesn't have to replace a nice "offline" outdoor activity.

The type of work indeed matters a lot, if you need any visual confirmation or have to look things up yourself it's probably not worth it. As a solo entrepreneur I manage my entire business workflow. Everything is accessible from an API, from accounting to my CRM to S3 storage or my PostgreSQL cluster. Tasks can be handed off between different agents to keep things separated.

Not sure when you last tried, but I feel I would not be able to do what I do today with last years models.

For sure, and a good part can already be automated. But certain things still require human intervention and always will. Keep in mind these work related walks do not replace other outdoor activities.

I may not work less, but certainly different and better. Just this morning I went for a long walk on the beach, barefoot in the water. Using nothing but voice interaction, I handled a couple of outstanding CRM tasks, sorted out some accounting issues and upgraded my search infrastructure (SearXNG) and most of all enjoyed my walk outside. I would not be able to do all this without AI and would be stuck behind my desk, daydreaming about going for that walk instead.

I think we should move to pull requests that describe succinctly what feature or bug needs to be pulled. Not the actual code. A PR for a bug needs an issue link with a test demonstrating the bug in an easy to verify way, eg an online playground/runner.

Ideally the project has a well written, living product and system implementation document that can be used to verify bug reports and feature requests against. Before even looking at the actual code implementation.

Glad I got a toll badge covering Italy, Spain and Portugal so the amount gets auto deducted every month, instead having to pay each individual toll segment. Anyway, the A25 heading from Salamanca Spain into Portugal is now toll free, same as some of the roads around Barcelona/Catalonia. So it's not all bad.

I was afraid of this but switched from Samsung to an Oppo Find X9 Ultra anyway as the new Samsung S26 Ultra feels stuck in the past. I was pleasantly surprised with ColorOS. The only thing Samsung has going for it is OneUI. OneUI is better, but not by a lot.

Android Wireless debugging is already a major pita to work with. Requires a wifi connection to even work, so I need to carry a mobile wifi router with me, instead of having it bound to my secure WireGuard connection. Next it assigns a random port number every time the wifi connection is interrupted, or when it considers now is a good time to reset the port number. It should be possible to set a stable port and and have it available, perhaps behind a few awkward UI/adb toggles.

I've been building out the Android app that works as the wrapper between codex and me this way. ADB debugging access over WireGuard. I ask to add a local wake phrase detection for the phrase "Hey codex" to start dictation. Codex tells me it thinks Vosk or OpenWakeWord might be a good fit, I voice select Vosk. Codex starts working. Codex deploys (updates) the app on my phone and restarts it and I hear the task complete response. I say "Hey Codex" to test and ask for some tuning/improvements, or move onto the next task. All while keeping my phone in my pocket.

But there are countless projects I work on this way. Eg, I got an email from person X, it says it encountered a bug when doing x and y. Codex reads the email (using nvidia/gliner-PII to hide PII data) and investigates the reason for the bug and proposes a solution. I ask it to implement the fix on my dev server and increase test coverage. I enjoy my walk and after say 7 minutes get a an overview of the fix and can decide to deploy to production.

It's not a replacement for being outdoors, connecting with nature. It replaces indoor desk bound office work.

Think long winding, quiet, dedicated cycling roads in forested areas and natural parks. Not busy roads shared with cars and lorries.

I have my phone in my pocket, no screen interaction is required. I use a headset (Shokz OpenComm2) with wind muff (when cycling). I made an Android app that listens for codex turn-complete or intermediate updates and plays them back to me. My answer is transcribed and pasted back to the relevant codex (tmux) session on the server (which I can select by voice) a tiny layer helps with things like /new, /plan, answer selection, etc.

I do a ton of coding (codex) with a tts/stt wrapper. During walks, cycling, in the car. Not every task is suited to this style of interaction, but many are. Long form codex replies are condensed, code blocks are suppressed all in the name of making it work for tts feedback. So it works best on well defined projects with guardrails, where you know the agent can perform well.