If we do this, what are we not doing?

Context: perfecting the art of managing up, and in particular, reporting to the board of directors.

Another great podcast episode from The Knowledge Project/Farnam Street in which they touch on various topics, but one caught my attention. At a certain point they talk about a period of underperformance and this sentence caught my attention:

I understand what you are doing and why you’re doing it, and I understand what you are not doing and why you are not doing it. See you next month.

And I was thinking at the current AI hype, but then again I think it applies to any hype in technology, as we seem to experience this on a pretty regular basis (AI, crypto, microservices, big data, cloud, nosql, SOA, etc).

So I think in the future I'll borrow this practice and, in addition to covering what we do, I'll also cover what we are not doing and why.

On the theme of AI a couple of data points that I think are relevant:

looking at impact of AI on financial results. I mean, at the end, once you've removed all the fluff, what everybody cares about is the bottom line. For Google, it seems it is: AI positively improves Ad effectiveness (remember: Google is an Ad company which happens to be running a bunch of services on top). For AMD it's also a positive, however I would argue that's a weaker indicator of AI viability.

Apple is (typically for Apple) absent in the AI space: are they building something in secrecy or are they waiting until the killer app comes up? I think once Apple jumps in we'll know if AI is really as disruptive as everybody claims it to be.

Popular posts

A not so short guide to ZFS on Linux

Image
Updated Oct 16 2013: shadow copies, memory settings and links for further learning. Updated Nov 15 2013: shadow copies example, samba tuning. Unless you've been living under a rock you should have by now heard many stories about how awesome ZFS is and the many ways it can help with saving your bacon . The downside is that ZFS is not available (natively) for Linux because the CDDL license under which it is released is incompatible with the GPL. Assuming you are not interested in converting to one of the many Illumos distributions or FreeBSD this guide might serve you as a starting point if you are attracted  by ZFS features but are reluctant to try it out on production systems. Basically in this post I note down both the tought process and the actual commands for implementing a fileserver for a small office. The fileserver will run as a virtual machine in a large ESXi host and use ZFS as the filesystem for shared data.
Read more

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Image
Who said that grepping Apache logs has to be boring? Sample of dashboard that can be created with ELK. Pretty impressive, huh? The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions. ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).
Read more

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in
Read more