94 is the oldest relative I’m aware of. It was my great grandfather. Staying active his whole life, a simple diet, and a generally positive outlook seems to have been the key.
Most of my family say I’m a lot like him!
94 is the oldest relative I’m aware of. It was my great grandfather. Staying active his whole life, a simple diet, and a generally positive outlook seems to have been the key.
Most of my family say I’m a lot like him!
I love doing that…
Edit - To be clear, since my reply got some upvotes, I meant that I enjoy being the senior developer diving into the legacy code. I actually really like it!
Man, I hate it when that happens.
Great, now reverse it!
Right, it’s Sisko’s “It’s easy to be an angel in paradise…” from season 1. That’s the main theme of the whole show - how do the Federation’s ideals hold up in significantly less than ideal conditions? What does it mean to be “the good guys” when all of the choices in front of you are varying degrees of bad?
People always mention the later seasons, understandably so, but it carries through the entire series. In some ways, it’s even more prominent in the early seasons when DS9 is portrayed as being pretty remote, Federation back up is far away, the main cast is own their own, and the Cardassian fleet is always nearby.
It’s where I get my food. And most of my stuff.
Overweight or not, I’ve always preferred mustache-d Scotty
Ah yes, the “Max Power” way…
Hmmm, interesting. I like brew, for sure. And devcontainers worked ok for me when I was working on something by myself.
But as soon as I started working on a side project with a friend, who uses Ubuntu and was not trying to develop inside a container, things got more complicated and I decided to just use brew instead. I’m sure I could have figured it out, but we are both working full time and have families and are just doing this for fun. I didn’t want to hold us up!
Our little project’s back end runs in a docker compose with a Postgres instance. It’s no problem to run it like that for testing.
Maybe a re-read of the documentation for devcontainers would help…
Personally, I have found the developer experience on Bluefin-dx (the only one I’ve tried…) to be…. mixed.
VSCode + Devcontainers, which are the recommended path, are pretty fiddly. I have spent as much time trying to get them to behave themselves as I have actually writing code.
Personally, I’ve resorted to using Homebrew to install dev tools. The CLI tools it installs are sandboxed to the user’s home directory and they have everything.
It’s not containers - I deploy stuff in containers all the time. But, at least right now, the tooling to actually develop inside containers is kind of awkward. Or at least that’s been my experience so far.
I think the ublue project is fantastic and I really like what they are doing. But most of the world of developer tooling just isn’t there yet. Everything you can think of has instructions on how to get it going in Ubuntu in a traditional installation. We just aren’t there yet with things like Devcontainers.
I won’t tell you to “just change jobs”. I know it’s not that simple.
But I will say that I have a job in a line of work I genuinely enjoy, so I look forward to Mondays.
I might be in the minority, but I get more excited about the idea of maintaining/working on some creaky old legacy code base than I do about the idea of starting a new project from scratch.