Shukry Zablah

Summary of _Extreme Ownership_, Part I

In this post I summarize a few leadership insights extracted from Part I of Extreme Ownership: How U.S. Navy SEALs Lead and Win by Jocko Wilink and Leif Babin.

Extreme Ownership. Leaders must own everything in their world. There is no one else to blame.


The following insights are quotes from the book.

  1. On any team ... all responsibility for success and failure rests with the leader. The leader must own everything in his ... world. ... When subordinates aren't doing what they should ... the leader must train and mentor the underperformer. If underperformers cannot improve, the leader must terminate them.
  2. There are no bad units, only bad officers.
  3. When setting expectations, no matter what has been said or written, if substandard performance is accepted and no one is held accountable ... that poor performance becomes the new standard.
  4. ... a leader must be a true believer in the mission. The leader must explain not just what to do, but why. It is the responsibility of the subordinate leader to ... ask if they do not understand. Only when leaders at all levels understand and believe ... can they pass that understanding to their teams.
  5. ... if you approached it as "he did something wrong" and "he needs to fix something" and "he is at fault", it becomes a clash of egos. ... if you put your own ego in check, meaning you take the blame, that wll allow him to ... see the problem without his vision clouded by ego.


In this post I comment on how I added Google Analytics tracking to this website. In my earlier posts I mentioned how I'm using Common Lisp tooling, specifically, the Coleslaw blogware. Coleslaw actually already had a Google Analytics plugin, but unfortunately it used legacy code (the javascript not the lisp) and I did not see any reason to include this in my personal site. This is why I added what I wanted to Coleslaw.


Last post I shared how I was able to set up a Coleslaw-generated static site, deployed on Gitlab Pages. You can check out the progress of this website in my repository.

I had ran into problems using the pygments plugin for syntax highlighting in code blocks. In this short post I will walk through the few steps needed to resolve this.

;; Syntax highlighting works fine!
(define (eval exp env)
  (cond ((self-evaluating? exp) exp)
        ((variable? exp) (lookup-variable-value exp env))
        ((quoted? exp) (text-of-quotation exp))
        ((assignment? exp) (eval-assignment exp env))
        ((definition? exp) (eval-definition exp env))
        ((if? exp) (eval-if exp env))
        ((lambda? exp)
         (make-procedure (lambda-parameters exp)
                         (lambda-body exp)
        ((begin? exp) 
         (eval-sequence (begin-actions exp) env))
        ((cond? exp) (eval (cond->if exp) env))
        ((application? exp)
         (apply (eval (operator exp) env)
                (list-of-values (operands exp) env)))
         (error "Unknown expression type - EVAL" exp))))


I used to use the Hugo static site generator for my personal site. I wanted to try to use Coleslaw instead. I am currently using Common Lisp for fun, so it makes sense to use Common Lisp tooling if possible. In this post I walk through how I set up my computer, my personal site, automatic deployment with Gitlab CI, and a custom theme.