The development of OKRs is generally attributed to Andy Grove, the “Father of OKRs”, who introduced the approach to Intel during his tenure there and documented this in his 1983 book High Output Management. Grove’s simple but effective concept is explained by John Doerr: “The key result has to be measurable. But at the end you can look, and without any arguments: Did I do that or did I not do it? Yes? No? Simple. No judgments in it”.
LFG! Run to storage, cleaned the house, checked email, chatted with a few people, and cleaned up some data on one of my harddrives.
Just for the record, the reason `withassets` is one word (I understand it’s not very English) is because (1) “with” is one syllable, and (2) it’s a single token.
On counting syllables: I prefer names that are short, while still being descriptive. Previously, I named something “more notes” when some reviewers favored “additional notes”. Generally, I think 2-3 syllables is a good length for a name. Good examples: facebook, instagram, google, sprokets. Bad examples: wikipedia, asset pipeline.
On lack of underscores: an underscore is safer than a dash (which is a mathematical operation), but it’s still a special character that separates tokens. I saw a client database where table names were just a-z letters, no capitalization, no other chars. While other readers ridiculed that choice, I found it interesting. `withassets` is a sub-environment so to say, and it’s one thing. It’s not separable into “with” and “assets”. If there is ever a need to have `development_withcache`, `development_withssl`, splitting environment name by underscore clearly gives you the major and minor parts. Introducing an underscore in the middle of a token may require more complex parsing.
- cleaned up google storage
- cleaned up facebook. from 1000 friends to 10.
- Cleaned up some content – this shelter-at-home situation allows me to do some major cleaning
- cleaned the house, too.
- docker, css themes
- finished reading “consider phlebas”
- some ionic,
- some content
- being social
- Studying react
- Handed BJJC off and hopefully no more time commitment from me on this one.
- made personal archive more robust, removed some PPI that shouldn’t’ve been there
- Assigned a task to graphic design guy
- reviewing backend work today.
- handed a piece of work to frontend – getting closer to having a functional app!
- Client communication
- Iterating on mockups
- preparing mock data
- reviewed the way to setup ionic, and
- reviewed the way to setup microsites3
- communicated requirements to two new coders: front and back
- iterated on “watcher” functionality
- communicated with a client
- pushed a fix to WasyaCo that re-allows actually sending me messages from the form
- Did frontend work today
- More exciting graphics are coming!
- Did some projections for profit and loss on the TGM project
- Solicited some feedback on the business plan, awaiting feedback
- Wrote some more technical requirements.
- Deployed the next development version – nothing is ready to show, but the team still needs to look at the current version in detail.
- Did homework for UoPeople
- Wrote a bunch of specification for… surprise project!
- Practiced technical problem solving
- Wrote a bunch of code, reviewable on github, for a… project. I need to come up with a name. How is Warbler for a name?
They were made illegal fairly quickly. A few Reddit subreddits were shut down over digital privacy violations as soon as they were created. Anyway, how does one get onto the deep fake train?
Turns out this is the software suite that’s used “95% for the time” for deep fake creation: https://github.com/iperov/DeepFaceLab
And here is a tutorial: https://mrdeepfakes.com/forums/thread-guide-deepfacelab-2-0-explained-and-tutorials-recommended
Of course, this is a reminder to myself as much as anything else, to go back to this and read up and do a trial run, when I have the time.