jbrechtel/willfullyobtuse.com
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Small touchups

Browse Source
This commit is contained in:
James Brechtel
2024-10-04 22:25:37 -04:00
parent 43d3891bee
commit 3f42924242
2 changed files with 60 additions and 216 deletions
Download Patch File Download Diff File Expand all files Collapse all files

274
one.org
View File

@@ -8,103 +8,11 @@ Hello,
Here's what I've been thinking about
* The problem with large companies
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/large-companies/
:END:
Organizing people is a difficult problem which only gets more difficult as youmore people need to be organized.
The larger a company is the more of its internal structures, rules, policies, history, etc are devoted _just_ to organizing people.
For me, realizing this was like the first time you hear a flourescent light buzzing in an otherwise quiet room.
Reasonable people can differ on this point, but for my own sake I'd much rather avoid all the people-organizing baggage that comes with large companies.
I don't have a hard-and-fast rule about the size of a place I want to work but the larger a place is then generally the more reason I need to want to be there.
Of course, this is all kind of theoretical at this point, as [[https://flipstone.com][Flipstone]] is my forever home.
#+BEGIN_SRC haskell
doThings :: String -> T.Text -> NEL.NonEmpty Char -> BS.ByteString -> IO ()
doThings = error "WTF is this"
#+END_SRC
* Simple CSS frameworks - 2024-09-30
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/simple-css-frameworks/
:END:
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
* Let people fail - 2024-09-25
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/let-people-fail/
:END:
** How (and why) to let people fail
Warning: This, like most things, will involve a fair bit of projection.
Effective and enjoyable collaboration with other people requires mutual trust.
I believe that for someone to feel trusted by another person then they need the space to fail.
I _think_ this is obvious when considering what not having the space to fail looks like.
Not having the space to fail means your collaborator is doing one of two things:
1. Directing every action you take a.k.a. micromanaging
2. Coming behind you and redoing all of your work
Both of these are attempts by the other person to minimize risk (or simply cases where they're failing to manage their own anxieties).
These actions are counter productive to fostering trust and should be avoided unless failure is too costly.
I'm _not_ saying all collaboration _requires_ building trust. There are times when you simply can't afford failure or mistakes.
What I am saying is that people frequently misjudge the value in deliberately giving others the space to fail for the sake of fostering trust.
Building trust is important and we should do it deliberately.
* TODO Just what is it you do here?
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/job-description/
:END:
I've never liked working at [[#/blog/large-companies/][large companies]]. Mostly because I think
they complicate things, but some things are more complicated at small
companies.
* TODO Managing Expectations
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/managing-expectations/
:END:
I'll figure this out one day. Until then I'll just keep saying yes and burning myself out making everyone happy.
* HTTPS @ Homelab
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/large-companies/
:CUSTOM_ID: /large-companies/
:END:
** HTTPS @ Home
I run a lot of services at home.
This includes, but isn't limited to
@@ -152,10 +60,8 @@ Then tell Caddy to reload the config and I'm done.
* Multi-room audio setup
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/multi-room-audio/
:CUSTOM_ID: /multi-room-audio/
:END:
** My multiroom audio setup
I've put my home audio solution together out of the following
components.
@@ -199,10 +105,9 @@ speakers over AirPlay.
* vi-editing everywhere
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/vi-everywhere/
:CUSTOM_ID: /vi-everywhere/
:END:
** vi modal editing in most places
For my sake, I prefer to have Vim bindings in as many places as
possible.
@@ -235,7 +140,7 @@ $endif
* AWS Cloudwatch Metric Filters
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/large-companies/
:CUSTOM_ID: /large-companies/
:END:
** Structed and passively collected metrics via AWS CloudWatch
@@ -288,153 +193,92 @@ of your application code to take advantage of. Cloudwatch Metrics is one
of those services and you can get a lot of value out of it with not much
effort.
* The default page
* Simple CSS frameworks - 2024-09-30
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /blog/default/
:CUSTOM_ID: /simple-css-frameworks/
:END:
This page is rendered with the default render function ~one-default~
specified in ~ONE~ org property.
I really like simple drop-in CSS resets like the one I use for this site.
** Do you want a table of content?
At the time of writing, I'm using [[https://picocss.com/][Pico]] but I also considered [[https://yegor256.github.io/tacit/][tacit]]
As you can see, ~one-default~ doesn't add a table of content (TOC). If
you want a default render function that adds the TOC to the page you can
use the render function ~one-default-with-toc~ presented in [[#/blog/one-default-with-toc/][The default
page with a TOC]].
The idea is that they provide nice default styling of HTML elements out of the box without the need to reference any specific classes.
** Headline foo
*** Headline bar
The idea works well for sites that are much more content than layout - like this one.
Some content.
Using tacit is a matter of incluing this link tag in the page's HEAD element:
*** Headline baz
#+BEGIN_SRC bash :results verbatim
tree
#+BEGIN_SRC html
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@picocss/pico@2/css/pico.min.css">
#+END_SRC
#+RESULTS:
#+begin_example
.
├── assets
│ └── one.css
├── one.org
└── public
├── blog
│ ├── default
│ │ └── index.html
│ ├── default-home-list-pages
│ │ └── index.html
│ ├── one-default-doc
│ │ └── index.html
│ ├── one-default-with-sidebar
│ │ └── index.html
│ └── one-default-with-toc
│ └── index.html
├── index.html
└── one.css
8 directories, 9 files
#+end_example
* The default page with a sidebar
* Let people fail - 2024-09-25
:PROPERTIES:
:ONE: wfot-default-with-sidebar
:CUSTOM_ID: /blog/one-default-with-sidebar/
:ONE: wfot-default
:CUSTOM_ID: /let-people-fail/
:END:
This page is rendered with the render function ~one-default-with-sidebar~
specified in the org property ~ONE~.
Warning: This, like most things, will involve a fair bit of projection.
** Do you want a sidebar and a TOC?
Effective and enjoyable collaboration with other people requires mutual trust.
Perhaps you want a sidebar listing all the pages on your website and a
table of content, as many modern documentation sites do. If so, you
can use the default render function ~one-default-doc~ presented in [[#/blog/one-default-doc/][The
default page with TOC and sidebar]].
I believe that for someone to feel trusted by another person then they need the space to fail.
** Headline foo
*** Headline bar
I _think_ this is obvious when considering what not having the space to fail looks like.
Some content.
Not having the space to fail means your collaborator is doing one of two things:
*** Headline baz
1. Directing every action you take a.k.a. micromanaging
2. Coming behind you and redoing all of your work
#+BEGIN_SRC bash :results verbatim
tree
#+END_SRC
Both of these are attempts by the other person to minimize risk (or simply cases where they're failing to manage their own anxieties).
#+RESULTS:
#+begin_example
.
├── assets
│ └── one.css
├── one.org
└── public
├── blog
│ ├── default
│ │ └── index.html
│ ├── default-home-list-pages
│ │ └── index.html
│ ├── one-default-doc
│ │ └── index.html
│ ├── one-default-with-sidebar
│ │ └── index.html
│ └── one-default-with-toc
│ └── index.html
├── index.html
└── one.css
These actions are counter productive to fostering trust and should be avoided unless failure is too costly.
8 directories, 9 files
#+end_example
I'm _not_ saying all collaboration _requires_ building trust. There are times when you simply can't afford failure or mistakes.
* The default page with TOC and sidebar
What I am saying is that people frequently misjudge the value in deliberately giving others the space to fail for the sake of fostering trust.
Building trust is important and we should do it deliberately.
* The problem with large companies
:PROPERTIES:
:ONE: wfot-default-doc
:CUSTOM_ID: /blog/one-default-doc/
:ONE: wfot-default
:CUSTOM_ID: /large-companies/
:END:
This page is rendered with the function ~one-default-doc~ specified
in the org property ~ONE~.
Organizing people is a difficult problem which only gets more difficult as youmore people need to be organized.
** Do you want to know more about one.el?
The larger a company is the more of its internal structures, rules, policies, history, etc are devoted _just_ to organizing people.
Check the documentation at https://one.tonyaldon.com.
For me, realizing this was like the first time you hear a flourescent light buzzing in an otherwise quiet room.
** Headline foo
*** Headline bar
Reasonable people can differ on this point, but for my own sake I'd much rather avoid all the people-organizing baggage that comes with large companies.
Some content.
I don't have a hard-and-fast rule about the size of a place I want to work but the larger a place is then generally the more reason I need to want to be there.
*** Headline baz
Of course, this is all kind of theoretical at this point, as [[https://flipstone.com][Flipstone]] is my forever home.
#+BEGIN_SRC haskell
doThings :: String -> T.Text -> NEL.NonEmpty Char -> BS.ByteString -> IO ()
doThings = error "WTF is this"
#+BEGIN_SRC bash :results verbatim
tree
#+END_SRC
#+RESULTS:
#+begin_example
.
├── assets
│ └── one.css
├── one.org
└── public
├── blog
│ ├── default
│ │ └── index.html
│ ├── default-home-list-pages
│ │ └── index.html
│ ├── one-default-doc
│ │ └── index.html
│ ├── one-default-with-sidebar
│ │ └── index.html
│ └── one-default-with-toc
│ └── index.html
├── index.html
└── one.css
* TODO Just what is it you do here?
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /job-description/
:END:
8 directories, 9 files
#+end_example
I've never liked working at [[#/large-companies/][large companies]]. Mostly because I think
they complicate things, but some things are more complicated at small
companies.
* TODO Managing Expectations
:PROPERTIES:
:ONE: wfot-default
:CUSTOM_ID: /managing-expectations/
:END:
I'll figure this out one day. Until then I'll just keep saying yes and burning myself out making everyone happy.

2
onerc.el
View File

@@ -1,4 +1,4 @@
(setq wfot-css "https://cdn.jsdelivr.net/npm/holiday.css@0.11.2")
(setq wfot-css "https://cdn.jsdelivr.net/gh/kimeiga/bahunya/dist/bahunya.min.css")
(defun wfot-default (page-tree pages _global)
"willfullyobtuse default render function