Happy new year everyone, and welcome to the first Weekly (truly?! will this be the year?) Head Voices of 2018!
I ended 2017 with a longish (by my standards) run in the morning, followed by a laid-back mini-party and finally by struggling really hard to stay awake until midnight.
In contrast, returning to the office on January 2 was a pretty good way to ease gradually into work in 2018. Many colleagues were still on vacation, so the week felt a bit like work with training wheels.
Pro-tip #1 for the new year: In the last few weeks of 2017 I started (again…) explicitly making quiet time at the start of the day to think about what I want to take care of. These take the form of a small number of Org mode “- [ ] Do this thing” checklist items that are usually related to but separate from my main tasks. I find it amazing to which extent these few minutes are able to shape my day. (In my org mode monthly journal, I also usually start by listing out manually the tasks I want to complete during that month, as well as the ideas / thoughts / principles I want to keep in my sights.)
Pro-tip #2 for the new year: After years of resisting these types of software tools due to my belief that I should simply apply more grit and will power to squeeze out more focus hours, I finally broke down and purchased the macOS app called Focus. You click its pretty icon, and then your computer goes into focus mode: The Mail application and a bunch of other non-focus-related apps all get killed, and a bunch of websites (reddit, youtube, work chat, etc) are blocked for a user-configurable block of time. I rationalised this purchase with the following reasoning: It usually takes a single moment of weakness for a distraction to terminate a valuable block of focus. It takes a single moment of strength for this tool to start a valuable block of focus.
Although I’m having fun, I really don’t think I’m supposed to use bullets like this.
Thank you very much for spending time here with me. I wish you a week of value and focus, followed by a visit to the next WHV!
P.S. This post was finished during a 30 minute FocusApp block. Background music: Balance 014 by Joris Voorn, one of my favourite music creations ever.
In the period from Monday June 12 to Sunday June 25 we were mostly trying to get through the winter, fighting off a virus or three (the kind that invades biological organisms you nerd) and generally nerding out.
One more of my org2blog pull requests was merged in: You can now configure the thumbnail sizes your blog will automatically show of your uploaded images. Getting my own itch scratches merged merged into open source projects never fails to makes me happy, even although in this case there can’t be more than 5 other people who will ever use this particular functionality.
ASP.NET Core SURPRISE!
For a work project I was encouraged to explore Microsoft’s brand new ASP.NET Core. While on the one hand I remain wary of Microsoft (IE6 anyone?), I am an absolute sucker for new technology on the other.
You may colour me impressed.
If I had to describe it in one sentence, I would have to describe ASP.NET Core as Django done in C#. You can develop and deploy this on Windows, Mac or Linux. You model and query your data using Entity Framework Core and LINQ for example, or Dapper if you prefer performance and don’t mind the SQL (I don’t), or both. You write controller classes and view templates using the Razor templating language.
C# 7.0 looks like it could be a high development velocity language. It has modern features such as lambdas with what looks like real closures (unlike C++ variable capturing), as well as the null coalescing operator (??) and the null conditional operator (?.), the latter of which looks superbly useful. Between Visual Studio on Windows and the Mac, or the new Intellij Rider IDE (all platforms) or Visual Studio Code (all platforms), the tooling is top notch.
Time will have to tell how it compares to Python with respect to development velocity, a competition that Python traditionally fares extremely well at.
Where ASP.NET Core wins hands down is in the memory usage department: By default you deploy using the Kestrel web server, which runs your C# code using multiple libuv (yeah, of lightning fast node.js event loop fame) event loops, all in threads.
With Django I usually deploy as many processes as I can behind uwsgi, itself behind nginx. The problem is that with Python’s garbage collector, these processes end up sharing very little memory, and so one has to take into account memory limits as well as CPU count on servers when considering concurrency.
The long and the short of this is that one will probably be able to process many more requests in parallel with ASP.NET Core than with Django. With uwsgi and Django I have experimented with gevent in uwsgi and monkey patching, but this does not work as well as it does in ASP.NET Core, which has been designed with this concurrency model in mind from the get go. My first memory usage and performance experiments have shown compelling results.
Hopefully more later!
A cadence of accountability
Lately my Deep Work habits have taken a bit of a hit. At first I could not understand how to address this, until I remembered mention of a cadence of accountability in The Book.
Taking a quick look at that post, I understood what I had forgotten to integrate with my habits. Besides just doing the deep work, it’s important to “keep a compelling scoreboard” and to “create a cadence of accountability”.
Although I was tracking my deep work time using the orgmode clocking commands (when I start “deep working” on anything, I make an orgmode heading for it in my journal and clock in; when I’m done I clock out; orgmode remembers all durations) I was not regularly reviewing my performance.
With orgmode’s org-clock-report command (C-c C-x C-r), I can easily create or update a little table, embedded in my monthly journal orgfile, with all of my deep work clocked time tallied by day. This “compelling scoreboard” gives me instant insight into my weekly and monthly performance, and gives me either a mental kick in the behind or pat on the shoulder, depending on how many deep work hours I’ve been able to squeeze in that day and the days before it.
The moment I started doing this at regular intervals, “creating a cadence of accountability” in other words, I was able to swat distractions out of the way and get my zone back.
This is an interesting similarity with GTD (which I don’t do so much anymore because focus is far more important to me than taking care of sometimes arbitrary and fragmentary tasks) in that GTD has the regular review as a core principle.
Us humans being so dependent on habits to make real progress in life leads me to the conclusion that this is a clever trick to acquire behaviour that is not habitual: Work on an auxiliary behaviour that is habitual, e.g. the regular review, that encourages / reinforces behaviour that is perhaps not habitual, e.g. taking care of randomly scheduled heterogeneous tasks (GTD) or fitting in randomly scheduled focus periods (Deep Work of the journalistic variant).
As an aside, cadence in this context is just a really elegant synonym for habit. I suggest we use it more, especially at cocktail parties.