Good luck finding someone with all those qualifications, with at least three projects that meet all the criteria in their portfolio, and willing to work in NY for $100k. The caliber of candidate they seem to be looking for is easily worth over twice that.

That said, the market is full of desperate job-seekers who might take the bait.

The way this comment is written doesn’t sound anything like the OP or the GitHub issue. Different tone, different dialect/spelling… lot of linguistic red flags. Not that I’m judging either way, it’s just suspicious how vastly different they are.

Are the release notes AI generated? It reads like it.

In years past, I’ve used Elasticsearch and Kibana. The learning curve is steep and the system resource requirements warrant a dedicated machine, but once you get it dialed, it’s really effective as a centralized logging server.

Prometheus and Grafana are for time-series data (metrics), not logs. If you’re already getting that from netdata, don’t bother with these, as they’d be redundant with what you have.

syslog is about as idiomatic as it gets for log management in linux, but i don’t have enough experience using it effectively to give any pointers there. If you don’t really know what you want, yet, and just want to collect logs from all the things and see them in one place so you can begin to try and make sense of them and make refinements from there, then syslog seems like an excellent place to start.

I’ve installed Debian Linux on over 50 devices by now. A vanilla configuration with GNOME works pretty much out of the box for me on a high-end desktop with a modern NVIDIA graphics card.

I’d say the biggest part of the learning curve is figuring out which apps are good and suitable for what you’re trying to do. Just like with Windows and macOS and Android and iOS, there’s only a handful of viable options among an overwhelming sea of poor ones.

There are many wrong ways to install NVIDIA on any given Linux distro and architecture, and only one functional way. As others here are saying, that’s on NVIDIA, not you or Linux.

General advice: whenever possible, strongly prefer your distro’s standard package manager to install things over any other method. With Ubuntu, I believe that’s either apt or snap.

Also: if you find yourself poking around in some obscure system internals while troubleshooting an issue, you probably took a wrong turn somewhere.

RE autoscaling: effective distributed systems design isn’t really language-dependent. Java apps can scale just as well as ones written in Go. That said, I can see there being a case for Java apps not making it as easy to build that way. There’s definitely a lot of mainframe/monolith-oriented patterns in both the standard library and in enterprise Java culture.

As for the job market and career investment, I’d say this:

• Keep investing more deeply in what you’re good at. That’s your foundation and what sets you apart.
• Avoid chasing the “next big thing” based on speculation and trends alone.
• The next step in your career hinges more on your ability to think and design at higher levels than it does on lateral moves to another programming language.
• Explore languages and technology that you think are interesting, relevant, or can provide value or elevate what you’re already doing. The main benefit of doing this is to engage your brain differently and encourage change, improvement, and growth. This will indirectly improve your work and help your career.

I’ve written a lot of Java in my career and studied it in college, and I’ve written one app professionally and several hobby projects and utilities in Go. There’s a lot to like about it, regardless of its marketability on a resume.