:PROPERTIES:
#+SETUPFILE: setup.org
#+keywords: advice relationships people
#+export_file_name: let-people-fail
#+subtitle: 
:END:

* How (and why) to let people fail
Warning: This, like most things, will involve a fair bit of projection.

I have some thoughts about collaboration.

While a lot of this is obvious and well accepted, I think there are some fine points worth elaborating on.

The obvious part is that people work better together when they believe they are trusted. Trust breeds initiative and independence. Distrust breeds resentment and inaction.

Consider the flip side of trust, for a moment.

A common way that people show _distrust_ when collaborating is either micromanaging or just coming in behind someone and redoing their work.

If that demonstrates distrust then 

It's not enough that you simply _do_ trust someone else to get the benefits, you need to show it. I think this is the part that many people skip or ignore.

This is, of course, true in general. 

** Very simple CSS frameworks
:PROPERTIES:
#+keywords: CSS
#+export_file_name: css-frameworks
#+subtitle: 
:END:

*** Minimal CSS / fancy resets
I really like simple drop-in CSS resets like the one I use for this site.

At the time of writing, I'm using [[https://picocss.com/][Pico]] but I also considered [[https://yegor256.github.io/tacit/][tacit]] 

The idea is that they provide nice default styling of HTML elements out of the box without the need to reference any specific classes.

The idea works well for sites that are much more content than layout - like this one.

Using tacit is a matter of incluing this link tag in the page's HEAD element:

#+BEGIN_SRC html
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@picocss/pico@2/css/pico.min.css">
#+END_SRC

#+BEGIN_SRC haskell
  doThings :: String -> IO ()
  doThings name = do
    putStrLn name
#+END_SRC