Developer journal

Developer journal is a section of my knowledge graph where I try to capture learnings during my day-to-day work.

Sections

• Pros & Cons of X

  • TODO [[GraphQL vs gRPC]]

• Screw-up story

• Everything you need to know about X

  • Bash shell
  • Git
  • Go

• Join me as I poke around X and understand how it works

  • [[Linux boot process]]
  • Fish shell has different PATH than neovim
  • [[Podman networking with tailscale tunnel]]
  • [[ANSI escape sequences]]
  • New lines and terminals: CR vs. LF

• Workflows & best practices checklists

• Annotated code walkthroughs

• Tips & Tricks

  • Image resizing
  • Automation
  • Find out what runs on a port on osx: sudo lsof -i -P | grep LISTEN | grep :8080

Candidates for “Join me as I poke around X and understand how it works”

• SVG
  • For example, this SVG

    • <svg xmlns="http://www.w3.org/2000/svg" x="0px" y="0px"
      width="32" height="32"
      viewBox="0 0 32 32"
      style=" fill:#undefined;"><path d="M 5 5 L 5 9 C 14.93 9 23 17.07 23 27 L 27 27 C 27 14.85 17.15 5 5 5 z M 5 12 L 5 16 C 11.07 16 16 20.93 16 27 L 20 27 C 20 18.72 13.28 12 5 12 z M 8 21 A 3 3 0 0 0 8 27 A 3 3 0 0 0 8 21 z"></path></svg>
      

    • has got a viewbox and width and height, how can I resize/alter the view window of the svg to make it fit the website
    • also, how can I make images scale up and down while keeping aspect ratio

Credit

• Code diary is a concept that I’ve seen mentioned multiple times on HN and also in the [[David Thomas, Andrew Hunt - The Pragmatic Programmer]]
• I’ve seen a YouTube video from Semicolon&Sons
  • {{video https://www.youtube.com/watch?v=tarmCEHfGa0}}
  • In this video Jack Kinsella describes how he moved the more complex learnings from his software engineering from #spaced-repetition to code diary.
  • His diary so far contains the following categories:
    • Pros & Cons of X - here he describes tradeoffs connected with a technology/design pattern
    • Screw-up story - learnings from mistakes
    • Everything you need to know about X - Overview of API/Technology e.g. Docker basics
    • Join me as I poke around X and understand how it works - noticing a phenomena and then going one level deeper and understanding why does it happen, e.g. Why colors disappear when we pipe output to another command?
    • Workflows & best practices checklist that I prepared for myself
    • Annotated code walkthroughs - e.g. finding a nice Makefile and finding out what id does and leaving a lots of comments