jjmiv
otherwise I'm slowly working on a Spoon that figures out if there is an active meeting in Zoom, Teams, Huddle, Google Meet and will allow for muting, video enable/disable and screen sharing etc
1 - Buy a mechanical keyboard that's already put together - Razer, Logitech and Corsair and even makers such as Novelkeys have models that are ready out of the box!!
2 - Buy a kit - basically via group buy in most cases but you end up putting most or a few of the parts together yourself. Often these kits come with everything but sometimes you end up having to get the keycaps and/or switches yourself.
3 - Buy all the separate parts and choose your own adventure - this is another way!! Pick everything you want - case, pcb, switches, stabilizers, plates(or no plate if you want), switches and keycaps!
4 - Mod an existing keyboard - take a keyboard that you bought off the shelf and solder on your own switches or just change the keycaps. I have a great Cooler Master board that I moved the pcb into a custom housing. This option is not as common i feel but its out there!
While this can be a lucrative hobby do not feel like you cannot choose option 1 to get yourself involved. Its ok if you are not building everything from scratch or printing the the PCB yourself. Enjoy it, you are all allowed to be here!
you need to put a buyout in writing with an end date (yes, with lawyers help). that way if they actually come out of their shack to cash in when you reach better growth you can point to this legal document.
i would consider to put everything in writing- your work and effort, start to omit their info from the website and products, but i would not remove their name + cofounder from things until you've issued that document with an end date and timeline of how you will terminate them from your business.
I use it with github. wanted to use github pages but was tired with having to use submodules in order for it to recognize the docs folder.
i've been reading through this book and it does a decent job of covering the principles for CICD, builds, tests releases: https://www.amazon.com/Continuous-Delivery-Deployment-Automa...
you'll run across various "thought leaders" in devops and its important to remember that a) each employer treats devops and cicd differently and you'll want to learn their practices as you bring about your own ideas to the culture and b) form your own opinions, just b/c thought leaders and books are out there its important to learn what you like to do and improve how you like to do it.
- this mess will appear to your future employers as to why you want to leave.
- although i'm sure your fellow devs will not be happy, they should understand your reasons and respect your choice.