I've had a couple of LLCs in the US (now and in the past) and they've been pretty hands-off as far as paperwork/tax stuff go. More or less, just keep good books and file/pay quarterly taxes and that's about it. I'm curious about what you've run into?
The same way you become good at anything at any point in your life: decide you want to and then put in the deliberate/consistent practice to make it happen. Set aside 15-20 minutes per day, work through Khan Academy, Math Academy, or a precalculus textbook, and then (the hard part) keep doing that.
Rails or Laravel, take your pick. Personally, I've been using Laravel + Filament. It's so fast to get up and running with & it doesn't hamstring you when you want to do anything more complex.
> What I'm talking about is people below average when it comes to understanding concepts, or conceptualizing altogether. Their intuition is always twisted and wrong. Completely lack critical feedback. Work needs to be decomposed for them in extremely precise steps if you want anything to happen.
Consider that the statement "their intuition is always twisted and wrong" is itself probably wrong. Their intuition is based on their professional and personal experiences. Two different people with different experience are not going to have the same intuition and that's okay. It's not productive to turn that into a personal judgement ("this person arrived at a different conclusion than I did - let's figure out why" is very different from "this person is an unteachable idiot")
Personally, I'd consider this an opportunity to help develop somebody's talent. I happen to find mentoring to be a very fulfilling part of the job though, so I lean into it a bit more than is strictly necessary. I'd probably start approaching this as a teaching problem, rather than a collaboration problem. If _telling_ this person something doesn't work, _show_ them. If that doesn't work, get some hands-on time by pairing with them on some tasks (in whatever configuration works -- try letting them navigate or drive, and you fill the other role).
If all of those things fail, go to your manager with something along these lines:
"I've been working with so-and-so on some things that they got stuck on. It has impacted the time that I have available for the work that is assigned to me. I'm happy to continue doing that if you're okay with the time investment (roughly x hours over the past month)."
If it's really impacting your work, they'll probably ask why it's taking so much time, so follow up with something like:
"In pairing with them, I've identified some knowledge gaps around x, y, and z -- the time spent is not just on the task at hand, but also in mentoring/teaching to get them up to speed in those areas. If it's too much time, we could consider investing in some training on those topics to get them up to speed independently. Once that foundation is laid, I think our pairing sessions could go much faster (or potentially be eliminated altogether). Alternatively, we could try pairing them with somebody else on the team -- it's possible that I'm not explaining things in a way that works for them."
Give them a lot of grace and focus on leveling up the team as a whole, rather than remedying your personal situation. You'll likely get more engagement from your manager that way, since your manager ostensibly _also_ wants to level up the team as a whole.
The workflow that you show in your repository is really not that different from Chezmoi. If you configure a post-add hook in Chezmoi (https://www.chezmoi.io/reference/configuration-file/hooks/), you can do `chezmoi add ~/.config/whatever/whatever.conf` and have the file auto-added to the Chezomi git repo + push it to some remote if you'd like.
I was also not thrilled about the idea of shipping an encrypted blob of important secrets around. I want my dotfiles to be public, so it's much nicer when the tool I use for managing my dotfiles natively integrates with 1password. Much of the templating functionality that I use from chezmoi is specifically for pulling stuff out of 1password.
Finally, the yadm "alternate files" functionality is nice, but I didn't really care about alternates for different OSes or hostnames or whatever. I wanted some configuration for my work machine(s) and some configuration for my personal machine(s) - that's it. That's the only distinction I care about. Chezmoi made it easy to prompt for the type of machine + change the things that get configured accordingly when bootstrapping a new machine (https://github.com/cweagans/dotfiles/blob/main/.chezmoi.toml...).
Did chezmoi make it easy to edit and then add fileswith changes?i hated always having to chezmoi this and that rather than doing what i want then runn*ng yadm -u to pick up all the changes in my tracked files
Pretty sure there are a couple of aliases that you could create to get you the workflow you want. I just edit my files on disk, chezmoi add file, then periodically fit commit and push them. You could create a post add hook to automatically git add/commit/push + I’m reasonably sure there’s a chezmoi command to list all tracked files, so you could iterate through all of them and do whatever you want with them.
If you have a 7 day expiration, some sysadmin is going to set up the renewal check on a weekly cron job. When the cert renewal fails, they don't have any time to act. 6 day expiration = you run the check daily. If something fails to renew, you might have a little more notice.
At risk of sounding like the dropbox/rsync guy, is this materially different from what you can accomplish with Prometheus, the Blackbox exporter, (optionally) the node exporter, and Grafana?
reply