I was consulting like this too, but my wife also had a full time corporate job. It all kind of ended with her team having layoffs around the same time that most of my clients figured out that they could use AI to do most of my work at a tiny fraction of my rate. I had built up a lot of experience working with oil and gas software, and I thought that was pretty solid, but it's hard to compete with $20 a month. Anyway, after all that, I found a stable job with good health insurance.
It would be pretty nice to write those simple things in one language if you have a ruby server, react front end, and postgres database. You could target different parts of the stack but think/implement in one language. Seems nice to me.
I got a stable job! I was unemployed for a few months, we paid a small fortune for health insurance, and I got ulcers from the stress, but things worked out! I enjoy my team, and I'm hopeful about 2026.
Microsoft Access form that connects via IIS to an Excel spreadsheet acting as a database. Also the server it's running on is sitting on a wooden table.
The thing about language is that words have a weird distribution. The most common 100 words show up in every single sentence, but then tons of "common" words show up statistically almost never. Like, "octopus" is a common word that is only going to be useful if you're talking to a marine biologist, or a three year old that's obsessed with octopuses, otherwise you're hardly ever going to use that word. There's a lot of words like that. "Spine" of a book? It's probably not "spine" in your target language.
reply