The Forever War
Joe Haldeman, George Wilson, et al.
4.4 on Amazon
7 HN comments
The Soul of A New Machine
Tracy Kidder
4.6 on Amazon
7 HN comments
Code: The Hidden Language of Computer Hardware and Software
Charles Petzold
4.6 on Amazon
7 HN comments
The Structure of Scientific Revolutions: 50th Anniversary Edition
Thomas S. Kuhn
4.5 on Amazon
7 HN comments
Digital Minimalism: Choosing a Focused Life in a Noisy World
Cal Newport
4.6 on Amazon
7 HN comments
Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones
James Clear and Penguin Audio
4.8 on Amazon
7 HN comments
Operating Systems: Three Easy Pieces
Remzi H Arpaci-Dusseau and Andrea C Arpaci-Dusseau
4.7 on Amazon
7 HN comments
Design Patterns: Elements of Reusable Object-Oriented Software
Erich Gamma , Richard Helm , et al.
4.7 on Amazon
7 HN comments
The Origin of Species: 150th Anniversary Edition
Charles Darwin and Julian Huxley
4.6 on Amazon
7 HN comments
The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change
Camille Fournier
4.6 on Amazon
6 HN comments
Open: An Autobiography
Andre Agassi, Erik Davies, et al.
4.7 on Amazon
6 HN comments
Getting to Yes: Negotiating Agreement Without Giving In
Roger Fisher , William L. Ury, et al.
4.6 on Amazon
6 HN comments
Lonesome Dove: A Novel
Larry McMurtry
4.8 on Amazon
6 HN comments
How to Avoid a Climate Disaster: The Solutions We Have and the Breakthroughs We Need
Bill Gates
4.5 on Amazon
6 HN comments
Working in Public: The Making and Maintenance of Open Source Software
Nadia Eghbal
4.6 on Amazon
6 HN comments
bwh2onMay 8, 2021
bwh2onApr 30, 2021
bwh2onApr 21, 2021
* Masters of Doom
* Where Wizards Stay Up Late
* Working in Public
bwh2onJune 9, 2021
dgb23onJuly 19, 2021
- Coders at Work (Seibel)
- Working in Public (Eghbal)
The first one is very entertaining. Read it a couple years ago and found it gives some valuable perspective. The second one is on my reading list, it was recommended around these boards.
Related to software design, there are many. The two that are on my recent list are:
- Software Design for Flexibility (Sussman, Hanson)
- A Philosophy of Software Design (Ousterhout)
I can't comment personally on their content yet, still have to work through those two, but I have zero doubts to learn something valuable. Certainly consider them.
IvyMikeonApr 15, 2021
If you pay $X for someone to "resolve" the issue, when they submit a patch that doesn't work, or doesn't follow the style guide, or doesn't fit the software architecture, or is otherwise unsatisfactory, how much time are you going to spend fixing/massaging/arguing? Will it be worth it to answer the jilted contributor who keeps sending "I want my $50!!!!" emails?
Nadia also has a quick 10-minute presentation on some ways you can use money to help open source, but without actually paying for bug fixes. [2]
[0] https://smile.amazon.com/dp/0578675862
[1] https://blog.domenic.me/hacktoberfest/
[2] https://www.youtube.com/watch?v=bjAinwgvQqc