"What are your top 12 #programming books?"

Me: 🤔

@davidbisset "Googling the Error Message" is a must-have classic
@davidbisset I'm definitely the one rewriting the frontend pretty often 😆
@davidbisset there should be one with a platypus and some title like "no-code business solutions"
@davidbisset That looks just like my work bookshelf.

@davidbisset

The TTL Cookbook.
Up the Organization.
Catch-22.
War and Peace.
Green Eggs and Ham.
Stranger in a Stranger Land.
The Timeless Way of Building.
A Tale of Two Cities (if you can't find War and Peace).
Atlas Shrugged (if you hate yourself).
The Number of the Beast ("Gay bounce!").
The Art of War.
The Bible (Old Testament only).

@davidbisset These are awesome! But I still want to know why "Coding on the Weekend" is so much smaller than the rest.

@davidbisset @cstross aw. No Regex owl?

- refactoring - Fowler
- antipatterns
- progit
- pragmatic programmer
- mastering regular expression (with the owl)
- clean code - Robert Martin
- learning Python- lutz
- dive into python
- countdown to zero day ( scary very scary )

@davidbisset Top Three are:
Googling the Error message
The Guy Who Wrote This Is Gone
Vague Understanding of computer Science
Story:
I had a close group of computer geeks in school. Unfortunately their families were far richer than mine so they moved away while I languished. One of them built explosives for fun.
We often talked about computer science in over-the-top analogies.
Example:
The old laptops the school handed out were "Hamster boxes" And we measured the TTL in H-cycles - or how long the poor beleaguered hamster inside each laptop to carry one data signal/packet etc. from one side of the laptop to the other.
@davidbisset I love well-matched the animals are to the titles 😁
@davidbisset
The #helpdesk and #support use several of these books.
@davidbisset @cm_jc This is dated. Now replaced entirely with ChatGPT. 😉
@davidbisset “Making design choices you’ll regret” featuring the 🦂 astride a 🐸 is one of@my favorites
@davidbisset
I think my top two are "Blaming the User" and Trying Stuff Until it Works."
@davidbisset I don't know what you're talking about, "Fixed it again, hopefully for good this time" is a perfectly good and endlessly useful commit message I don't have to stand for this kind of slander
@davidbisset I dig this books. I know Blaming the User is often referenced at the office by the whole team I work with.
@davidbisset > Forgetting how your own code works

This or how you get good at documenting your stuff :D

@davidbisset

First I was looking for a camel then I read the titles...

@davidbisset I relate way too much to nearly all of these.
@davidbisset I'll add two of my favorites...
@davidbisset I heavily recommend the kitten book (nr. 8 in your list) to my students.
@davidbisset @kyhwana it’s missing the perineal best seller “which symbol matches zero or one… ? Or +”

@davidbisset Book 13 - Getting Bad Code Advice from Stack Overflow.

Book 14 [Special Edition] - Using ChatGPT for Coding Help

@davidbisset Is forgetting how your own code works is a great one. ive read it multiple times.
@davidbisset it misses my favorite: sysadmin golden handbook called "Essential Hoping Things Works"

@davidbisset

Not programming-related exactly, but certainly adjacent:

@davidbisset

Changing stuff and seeing what happens.

It's been almost 40 years. Can I admit I brought down the MD water system (?) by wondering what happened if you tried to delete a location?? I mean, it wouldn't let you do that without a challenge, would it?

And it was one of those really fast and vast databases just before relational databases

I think we all had most of the afternoon off then.

@davidbisset Every Developer read all of them.