this post was submitted on 09 Feb 2026
27 points (100.0% liked)

Programming

26088 readers
154 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
27
Using an engineering notebook (ntietz.com)
submitted 1 month ago by codeinabox@programming.dev to c/programming@programming.dev
12 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] labsin@sh.itjust.works 1 points 1 month ago

I have a more mixed approach.

Decisions or attempts, i try to document them as comments on the ticket. It feels a bit like a conversation with my future self ๐Ÿ˜„

Things that pop up in my head that I don't want to forget, but don't have time to write out, I put in a new tab on nodepad++

Archi things go as markdown in de source code

Investigations and reports in a wiki

All these have all the pros of an engineering handbook out of the box (date, issuer, ...)

I only use paper for the stuff I don't want a trail off and just want to throw away afterwards.