The cloud is the original code base and the on premise is a FORK! Can you believe it? It's not even the same code and the on premise solution is so far behind.
Lol... Don't want to go down that rabbit hole. So many tools have been written to help with submodules. Such a shame. I feel like the only success path for submodules in any project is for anyone working on the project is to understand them completely.
I first read Atlassian and could potentially get on board (they have made tons of QoL changes, which I love and actually like. Their API still isn't that great, though). And same with AWS. At first it's confusing for sure. A lot of their offerings are wrappers around OSS that is much more intuitive. But comparatively to Azure and GCF, they're all confusing at first.
But then I read git, Docker, and Linux. Now I'm concerned about your approach to any of these tools.
For example Linux. There is _a lot_ of documentation out there. Man pages and arch Linux wiki just to name two that have a massive knowledge base.
Git. I mean holy smokes, I'm going to assume you've never used any other VCS because everything else before it was hell on earth (in my opinion, people have things to say about this). I would focus on learning some git commands and I think you'll really like it. Going straight into a GUI you might be confused when you have to fix a problem via CLI when GUI messes it up.
Docker - yeah, I see your point. It's not as apparent when you're trying to pull different architecture images. Kind of a shame. Maybe Rust WASM/WASI will replace it one day (kind of joking here).
50ish hours give or take 10. I'd say a good 10-15 of those hours are researching and studying material on how to improve current projects and my own development. It's greatly beneficial for the company I work for and myself in my opinion.
A good example is gRPC. We all can use it no problem, but using it correctly and efficiently is outside the scope of some teams so I like to spend the time to understand it deeper and spread that knowledge within our groups.
Thanks for this write up. I have also been nervous about the companion part. I was annoyed when I first learned that and it was locked. I've been wanting a small phone that was android just for things like Spotify, taxi, Gmail, gps, and text/phone. just essentials virtually.
I was obsessed with this phone a couple years back, but was annoyed that it was only available as a companion and locked to Verizon. I'm a Google Pixel lover because of the simplicity, software, and size. But I have always wanted a phone that was super small and was for essentials.
nice :sunglasses: