If it was actually only a single curse word and not maliciously directed at any individual, apologize and start recording the meetings, you probably have your phone out anyway, download the Hi Q app, just let it run. That person probably has something to hide about their work habits. You don't have to trot out the recordings at the first sign of back stabbing, let them pile up and if they make a serious play to get you canned you can start to share them at an advantageous moment. I learned this the hard way. I started keeping my phone in my breast pocket if there was not a table to set it on, people who make those sort of HR reports always have something to hide or protect usually their own incompetence. You may never need them but it literally can't hurt.
I agree with 6 months not being enough for an mvp, i'm 1 year in and am 85% to mvp, i do have validation from a consulting firm i used to work for where we successfully sold many enterprise clients before our owner sold and retired. Unless your mvp is dumb simple, plan on 2 years to develop a SaaS product that does not require massive manual intervention behind the scenes.
Break the work up into smaller chunks, writw them down on a physical piece of paper. Also try running the program Focalfilter, block the sites which most commonly distract you.
The reality is that both need to happen regularly. Issues that are too sensitive for the entire group are talked about during the regularly scheduled 1 on 1 or an ad hoc 1 on 1 if the issue is urgent.
In that case you probably want to just go with the plumber your inlaw recommended. Would kind of be awkward to explain that you wasted their recommended plumbers time only to save a few bucks with some rando from the white pages.
As the CTO of a DaaS startup in stealth mode working on our MVP, expect to take a year or more. We also offer SaaS that centralizes workflow around using the data, enterprise customers expect a level of polish and reliability that is not expected from the next facebook/airbnb clone, desk procedures, train the trainer programs and other ISO processes can't be revamped every single release. Keep fighting the good fight.
You never had a go program fail to compile, only to fix the problem then try to compile again? Replace 'run' with 'compile' and you could still type a bunch of go code and have to make changes before you deploy or no?