CareyB
1. cross-device/platform support. Once I was entirely Apple, I settled on Drafts (post processing when necessary), and Apple Notes. If you have multiple OS’s involved, the decision is harder (Evernote). The logic is that I wanted some contextually sensitive templates for field notes, and Drafts does that with its version of ‘macros’. Having the MacOS version makes writing reports from my notes is dead easy.
If you’re less concerned with re-typing, and/or transcribing, do what you want.
I’ve been in similar situations, but never without an immediately obvious solution.
That system WILL FAIL. Even as we speak the time-to-failure is shrinking.
Even if one of the solutions described below actually works, you won’t get 100% recovery.
I recall a story years ago - from MIT, if memory serves - where they rebooted a system because they had many generations of Sybase backups. When they tried, it didn’t work. Nobody had actually tested recovering from a backup.
Grit your teeth; cover your ass; and get on with it. The clock IS ticking.
Lots and lots of ‘finger errors’, as they call them in Formula 1.
Almost all Web sites are similar these days, and there’s a value to designing the UI/UX in a way users expect. I suggest that, for startups, and small businesses, there’s virtually no need for anything other than a basic Web presence. With the rise of social media, the appropriate account(s) will solve that problem for most.
I worked through the wild west of this industry, and it was semi-fun, but I think we’ve moved on, things have settled down, or are settling down, and there’s a minimum sufficient requirement for a Web presence that’s pretty freakin’ minimal.
1. We read much faster than we speak, so watching a video is massively less time-effective. If the junior is doing this on company time, they’re costing money.
2. There was an article somewhere about a dev exhibiting these ‘symptoms’. Turns out they were barely competent. Their entire method was to copy code they found on the Internet, and paste it in. They were entirely incapable of writing code from scratch. The article went on to elaborate that, after extensive (expensive) coaching from the senior dev who authored the article, the person turned out to be a pretty good developer. They just started their career trying to advance by gaming the system.
Someone once gave me the advice to never offer a discount. You can do things for free, but never discount anything. If you do, you’ll end up discounting everything.