Ask HN: Reading material on how to be a better software engineer?

388 点作者 OneOffAsk超过 2 年前

I’ve gotten to be quite good at the actual coding part after a decade or so of programming. I’m not looking for better code practices, although I’ll obviously still learn and grow there.What I’m seeking is reading material regarding how to manage project scope, be better team member, converting asks to deliverables, managing expectations from management, enabling team members by opening communication channels across teams, time management, etc.Any suggested reading material? Preferably books, but excellent blog posts are welcome.

52 条评论

markshead超过 2 年前

A few books that I've found useful:The Goal - Eli Goldratt - It is a novel about optimizing a factory, but it is immensely valuable in thinking through what are the actual constraints on your team's ability to deliver software and how do you fix it without making other things worse. The Phoenix Project is kind of a modern retelling, but I'd start with The Goal.The Principles of Product Development Flow - Reinersten - Great for thinking deeply about how you deliver value through your system and the tradeoffs you are making in what you choose to focus on next. Once again it isn't specific to software, but very relevant.The 5 Dysfunctions of Teams - Lencioni - Common team problems and what to do instead.Influence: Science and Practice - Cialdini - How to get people into agreement so you can move forward--a skill that can be used for both good and evil.The Little Schemer - Friedman and Felleisen - It is kind of hard to describe why this would be useful, but I felt it made me think more deeply about what it means to program a computer in ways that indirectly supported the topics you mentioned. Or maybe I just happened to work through it at a point in my life when I was growing in those other areas too.

评论 #33861120 未加载

评论 #33891489 未加载

bitsofawesome超过 2 年前

The two most useful books I have read: Code Complete by Steve McConnell - Really covers how to be good at the craft of writing programs and constructing software. <a href="https://www.amazon.com/Complete-Microsoft-Programming-Steve-McConnell/dp/1556154844" rel="nofollow">https://www.amazon.com/Complete-Microsoft-Programming-Steve-...</a>The Effective Engineer by Edmond Lau - Covers how to focus on what you work on based on the leverage it provides you. <a href="http://www.effectiveengineer.com/" rel="nofollow">http://www.effectiveengineer.com/</a>

评论 #33856014 未加载

TruffleLabs超过 2 年前

The Mythical Man-Month: Essays on Software Engineering, Frederick P. Brooks * still relevant re: people are the key to getting things done; understand how people work together.<a href="https://www.abebooks.com/products/isbn/9780201006506" rel="nofollow">https://www.abebooks.com/products/isbn/9780201006506</a>

评论 #33860122 未加载

评论 #33856354 未加载

评论 #33925435 未加载

rubicon33超过 2 年前

Recommend this book, but honestly you don't need to read it:Deep Work: Cal NewportWhat you need to know from this book is that to write good software (both quality and quantity) you need to go deep. You need to fully absorb and understand the problem in your mind, BEFORE you begin writing code. And then, you need quiet undistracted time to map the thoughts in your mind, to code on paper.This process of turning a mental model in your mind, into a well designed code model, takes more focus than you think (if you want to do it well). Give yourself a quiet room with no visual distractions. Just you, and your code. Set aside a few hours.Most importantly of all - Remove the possibility in your mind, that a distraction could happen. I cannot emphasize this enough. Your mind will not go deep if, even on a subconscious level, you think a distraction could come. A text message, a spouse walking in, a co-worker asking a question, etc. These all need to be (as reasonably as possible) NOT possible so that your mind can go quiet, and you can take on the work.

评论 #33857225 未加载

pjmorris超过 2 年前

'Becoming A Technical Leader', Gerald Weinberg. Jerry, working for IBM, designed the telemetry system NASA used to track early manned space flights and then spent a career helping organizations, teams, and people achieve their goals, both technical and personal. He wrote many books on the topics you mention, all of them worthwhile. I picked this one as a place to start.'Making Things Happen', Scott Berkun. Berkun was a successful developer and product manager at Microsoft and the book captures his reflections and research on project management.

hardwaregeek超过 2 年前

I’m currently reading Peopleware which is simultaneously very insightful and very obvious. It’s also a bit of a marker in time of how software development worked. I’d say a lot has improved with remote work, at least for some companies.I found The Mom Test pretty helpful for honing a product mindset. I’ve fallen into the trap of writing code simply because I find it less daunting than talking to users. The Mom Test is a good reminder on priorities.

评论 #33858314 未加载

评论 #33857223 未加载

rahimnathwani超过 2 年前

Staff Engineer: Leadership beyond the management track by Will Larson (<a href="https://staffeng.com/book" rel="nofollow">https://staffeng.com/book</a>)Peopleware

评论 #33855843 未加载

pkoird超过 2 年前

So I asked this same question to ChatGPT, here's its response. This thing really does have the potential to be a good recommendation tool for books/resources."Here are a few books that may be helpful for improving your skills as a software engineer:"The Pragmatic Programmer" by Andrew Hunt and David Thomas: This book offers practical advice on a wide range of topics, including how to write clean and maintainable code, how to work effectively with others, and how to manage your time and priorities."Clean Code" by Robert C. Martin: This book focuses on the importance of writing code that is easy to read and understand, and provides specific guidance on how to write clean and maintainable code."Peopleware" by Tom DeMarco and Timothy Lister: This book discusses the human side of software development, including how to create effective teams and work environments, and how to avoid common pitfalls such as overwork and burnout."Agile Software Development" by Alistair Cockburn: This book provides an introduction to agile software development methodologies, which are designed to help teams deliver high-quality software quickly and efficiently.In addition to these books, there are many excellent blog posts and online resources on these topics. Some websites that may be helpful include the Pragmatic Programmer blog, the Agile Alliance website, and the ACM SIGSOFT Software Engineering Notes journal.Another helpful resource may be attending conferences and workshops on software engineering and related topics. These can provide opportunities to learn from experts in the field, network with other professionals, and stay up to date on the latest trends and best practices. Many conferences and workshops also offer certification programs, which can be a valuable way to demonstrate your knowledge and expertise to potential employers. Some well-known conferences in the software engineering field include the ACM SIGSOFT International Symposium on the Foundations of Software Engineering (FSE), the ACM SIGCHI Conference on Human-Computer Interaction (CHI), and the International Conference on Software Engineering (ICSE). "

评论 #33861218 未加载

评论 #33857642 未加载

评论 #33858747 未加载

评论 #33898686 未加载

loloquwowndueo超过 2 年前

I got a ton of value out of “Peopleware: Productive Projects and Teams”. Even if you’re not a manager that can directly follow the advice, as an engineer it will provide great clues on how to ensure environment and team dynamics can greatly influence efficiency and chances of success.Of course my all time favorite is The Mythical Man-Month. But that’s already mentioned elsewhere in this thread.I haven’t read “Drive: The Surprising Truth About What Motivates Us” but some of the concepts it talks about are also of interest (on how to ensure workers are motivated and I’m not talking about “the beatings will continue until morale improves” :) )

summertime42超过 2 年前

I have all of these on my shelf. Fantastic reads.* Extreme Programming Explained by Kent Beck* Clean Code and The Clean Coder by Robert C. Martin* Soft Skills by John Sonmez (1st edition)* Pragmatic Programmer by Andrew Hunt and David Thomas* Working Effectively with Legacy Code by Michael Feathers* The Mythical Man-Month by Frederick Brooks(Selfish plug) Additionally, I wrote my own book concerning the entire industry, from just starting out to becoming a self employed consultant when you get sick of fulltime work - all soft skills from my decade or so of the industry, as well - <a href="https://www.amazon.com/dp/B0B43V1JJW" rel="nofollow">https://www.amazon.com/dp/B0B43V1JJW</a>

评论 #33856977 未加载

评论 #33857898 未加载

cauthon超过 2 年前

A Philosophy of Software Design by John Ousterhout is good reading

评论 #33858068 未加载

ArcMex超过 2 年前

I’m always looking to improve my set of skills, so thank you for the thread and thank you for the responses- I have managed to pick up some recommendations.My personal recommendation would be Deep Work by Cal Newport as it is my most recent read, having completed it just the day before yesterday.I applied what I learned and discovered that I was able to meet deadlines much easier than before. I’m also in the process of applying deep focus techniques to my work weeks to ensure I have a tangible build or product every Friday. Could be a document, a repo, a feature, etc. So far so good. This past week I delivered a Design Spec document in record time.Thanks again and take care.

mikehollinger超过 2 年前

“The Effective Manager” by the people behind Manager Tools (a great podcast) is a really, really good view of this.Re: Communication, this book starts there and builds upon that foundation. It’s targeted at line managers, but anyone in a leadership position can and will benefit. For example, I don’t do one-on-one’s with my team. I do “Project Management 1:1’s” or “Weekly project status updates.” I don’t always give feedback the way they prescribe (because the team doesn’t formally report to me). I do, however, go out of my way to say “Just to let you know, when you do X, Y happens.” And from the book, learned that there’s a 10:1 ratio of positive to negative feedback to strive for.Side note: Manager Tools has a great podcast series that is arranged into a “map of the universe” [1] which shows a huge list of topics, and how to discuss everything from good or bad performance, dealing with various types of conflict, to even how to structure emails or how to address a personal scent issue (which I’ve actually used).[1] <a href="https://www.manager-tools.com/map-of-the-universe" rel="nofollow">https://www.manager-tools.com/map-of-the-universe</a>

评论 #33855805 未加载

jpgvm超过 2 年前

People have recommended some excellent books.I will advise something different, find a mentor.The most important parts of actually -engineering- software, not bashing out code come from intuition and taste and these are best taught through a mentor.If you can't find a mentor at your current company then consider getting involved in OSS, particularly in well engineered projects like Linux, PostgreSQL, Apache projects, etc. If you have the capacity for this it's one of the strongest ways to increase your capability and strengthen/widen your network which will help further your career in other ways.Once you have found a mentor focus on being a good student. Learn how to ask the questions that will prompt insightful answers, the "why" rather than the "how". Especially try to learn what -not- to do. Experience doesn't always need to come first hand... getting burnt isn't necessary to understand not to touch hot stuff.Not the answer you asked for but I think perhaps even more important than what you can learn from a book.

ldjkfkdsjnv超过 2 年前

My personal opinion is reading about coding does nothing. Its like reading about math without doing the exercises. You need to work on good codebases, and have your code reviewed by people who are good.

评论 #33856562 未加载

评论 #33856602 未加载

评论 #33860302 未加载

评论 #33856894 未加载

评论 #33856540 未加载

评论 #33860271 未加载

评论 #33860975 未加载

评论 #33885960 未加载

allenleein超过 2 年前

SICP (Structure and Interpretation of Computer Programs)<a href="https://web.mit.edu/6.001/6.037/sicp.pdf" rel="nofollow">https://web.mit.edu/6.001/6.037/sicp.pdf</a>

pieterr超过 2 年前

Camille Fournier - The Manager's Path<a href="https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897/" rel="nofollow">https://www.amazon.com/Managers-Path-Leaders-Navigating-Grow...</a><a href="https://www.elidedbranches.com/" rel="nofollow">https://www.elidedbranches.com/</a>

评论 #33859829 未加载

leetrout超过 2 年前

A Philosophy of Software Design<a href="https://web.stanford.edu/~ouster/cgi-bin/book.php" rel="nofollow">https://web.stanford.edu/~ouster/cgi-bin/book.php</a>Righting Software<a href="https://rightingsoftware.org/" rel="nofollow">https://rightingsoftware.org/</a>

squeegee_scream超过 2 年前

Will Larson’s An Elegant Puzzle <a href="https://lethain.com/elegant-puzzle/" rel="nofollow">https://lethain.com/elegant-puzzle/</a>. It is mostly or entirely taken from his blog so you can just read the blog for free but I find the book valuable

dxs超过 2 年前

You can take a look at the following. Doesn't look like anyone else has mentioned this yet.As with everything else, check it out, adopt what looks good, adapt it to your needs.> Watts Humphrey: <a href="https://en.wikipedia.org/wiki/Watts_Humphrey" rel="nofollow">https://en.wikipedia.org/wiki/Watts_Humphrey</a>> Personal software process: <a href="https://en.wikipedia.org/wiki/Personal_software_process" rel="nofollow">https://en.wikipedia.org/wiki/Personal_software_process</a>> Team software process: <a href="https://en.wikipedia.org/wiki/Team_software_process" rel="nofollow">https://en.wikipedia.org/wiki/Team_software_process</a>> More at Libgen: <a href="http://libgen.rs/search.php?req=watts+humphrey&lg_topic=libgen&open=0&view=simple&res=25&phrase=1&column=def" rel="nofollow">http://libgen.rs/search.php?req=watts+humphrey&lg_topic=libg...</a>> More at PDF Drive: <a href="https://www.pdfdrive.com/search?q=watts+humphrey&pagecount=&pubyear=&searchin=&em=1" rel="nofollow">https://www.pdfdrive.com/search?q=watts+humphrey&pagecount=&...</a>

antipaul超过 2 年前

The Missing Readme” book seems right up your alley<a href="https://nostarch.com/missing-readme" rel="nofollow">https://nostarch.com/missing-readme</a>“The Missing README fills in that gap—a distillation of workplace lessons, best practices, and engineering fundamentals that the authors have taught rookie developers at top companies for more than a decade”Get it just for the “Design Doc” template!

评论 #33857288 未加载

bwb超过 2 年前

Michael Levine shared the best books about leading great software teams, this might be right up your alley: <a href="https://shepherd.com/best-books/if-you-want-to-lead-great-software-delivery-teams" rel="nofollow">https://shepherd.com/best-books/if-you-want-to-lead-great-so...</a>And, John Sonmez wrote about great books for software developers on the soft skill size - <a href="https://shepherd.com/best-books/fun-for-software-developers" rel="nofollow">https://shepherd.com/best-books/fun-for-software-developers</a>

bilsbie超过 2 年前

Anyone know if the old Joel on software essays are still around? Are they still relevant?

评论 #33858350 未加载

ayewo超过 2 年前

Mythical Man Month by Fred Brooks is pretty good. There is also the Design of Everyday Things (TDoET) by Don Norman.Structured Design from 1975 by Larry L. Constantine and Ed Yourdon is another excellent book that I am currently reading now.

Multicomp超过 2 年前

> converting asks to deliverables, managing expectations from management, enabling team members by opening communication channels across teams, time managementThese all sound like David Allen's Getting Things Done, the art of stress free productivity.> converting asks to deliverablesGTD teaches you to ask what the correct outcome is and what the next action item to get there is (and what those questions even mean) so your projects are always moving forward> managing expectations from managementGTD talks about setting up project lists so you are current and keeping you current when you meet with management>enabling team members by opening communication channels across teamsGTD teaches you how to brainstorm with the group and how to ensure everyone in a meeting knows what the next step to move the project forward is>time managementGTD teaches you someodels to help you best know what your time landscape is and give you reminders of what tasks need to be when and where if known otherwise it has a model of helping set priorities based on contexts available to you

jshen超过 2 年前

Become a better story teller and persuader, and learn how to make better decisions and manage risk. A few books that helped me in no particular order …The Science of Storytelling - Will StorrInfluence - Robert CialdiniThinking Fast and Slow - Daniel KahnemanAntifragile - Nassim TalebHow Innovation Works - Natt RidleyThe One Thing You Need to Know - Marcus BuckinghamTeam of Teams - General Stanley McChrystal

ilaksh超过 2 年前

My suggestion is that besides reading books, you could try to build a startup. It could just be consulting on your own (or with ChatGPT or Fiverr/freelancing sites as your team). Then you will gain direct experience in a lot of those things.Also here are a few ideas for managing scope, deliverables, expectations, time management. Structure things financially so that they are tied to relatively short iterations that require direct interaction with working software and between the engineers and the users and management at regular intervals. The communication with users AND management, payment, and deployment of working software at regular intervals should be strictly enforced. The project should not continue into the next iteration until all of those requirements are met for the current one.

评论 #33857097 未加载

评论 #33858369 未加载

la_fayette超过 2 年前

Elicitating the real needs of customers is the most challenging part for me within a software development process. The concept of Domain Driven Design (book by Eric Evan) helped me a lot to decode the language of the customer and transform it into an object model.

chiefalchemist超过 2 年前

"You're Not Listening" by Kate Murphy.It's not at all software related but it will make you a better teammate, partner (i.e., client relationship), manager and/or leader.Technology is the easy part. People, that's the difference between average and above.

评论 #33857300 未加载

mystickphoenix超过 2 年前

A few things come to mind along with what's already been mentioned:Assorted Non-Book Readings:- <a href="https://randsinrepose.com/dont-skip-this/" rel="nofollow">https://randsinrepose.com/dont-skip-this/</a>- <a href="http://www.stilldrinking.org/programming-sucks" rel="nofollow">http://www.stilldrinking.org/programming-sucks</a>- <a href="https://sysadvent.blogspot.com/2019/12/day-21-being-kind-to-3am-you.html" rel="nofollow">https://sysadvent.blogspot.com/2019/12/day-21-being-kind-to-...</a>- <a href="https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/" rel="nofollow">https://donellameadows.org/archives/leverage-points-places-t...</a>- <a href="https://grugbrain.dev/" rel="nofollow">https://grugbrain.dev/</a>- <a href="https://changelog.com/posts/rich-hickeys-greatest-hits" rel="nofollow">https://changelog.com/posts/rich-hickeys-greatest-hits</a>- <a href="https://github.com/papers-we-love/papers-we-love/blob/master/design/out-of-the-tar-pit.pdf" rel="nofollow">https://github.com/papers-we-love/papers-we-love/blob/master...</a>- <a href="http://www.cs.unc.edu/techreports/86-020.pdf" rel="nofollow">http://www.cs.unc.edu/techreports/86-020.pdf</a>Books:- The Phoenix Project: Gene Kim, Kevin Behr, George Spafford- Deep Work: Cal Newport- The Art of Leadership: Michael Lopp (Rands)- Extreme Ownership: Jocko Willink and Leif Babin (once you get through the ho-rah stuff it's a fantastic read)- Time Management for System Administrators: O'Reilly (fantastic for interrupt driven work)- Elements of Clojure: Zachary Tellman (not just for Clojure devs)

评论 #33856117 未加载

jm1271超过 2 年前

Software Estimation: Demystifying the dark art is an under-appreciated book in this area.

评论 #33858408 未加载

评论 #33856060 未加载

vl超过 2 年前

Peopleware and Mythical Man-Month are fundamental to understanding larger software projects and teams.They often state obvious things, but I didn’t guess them myself.Mythical Man-Month also provides important historical perspective.

foobazgt超过 2 年前

OP, I've been thinking about starting a column on those kinds of lines - generalized engineering advice. I have 20+ years of experience in the industry and have held both principal engineer and engineering director positions at S&P 500s. Does that hold your interest?For everyone else, I think I've created an interesting backlog of topics, but I'd love any advice about additional topics that would interest folks, how to kickstart an initial audience, what platform to use, how to moderate without losing my mind, and anything else that'd be useful to know doing this kind of thing.

评论 #33858259 未加载

评论 #33862039 未加载

评论 #33857157 未加载

merolish超过 2 年前

This list was posted a few months ago: <a href="https://news.ycombinator.com/item?id=32305997" rel="nofollow">https://news.ycombinator.com/item?id=32305997</a>

vasco超过 2 年前

I know you asked for books or blog posts, but I believe the best way is to read lots of code from the tools you use. Look into how your favorite libraries do things, for a start.

评论 #33858399 未加载

Solvitieg超过 2 年前

I noticed nobody had mentioned any Youtubers. Surprisingly there are a few Youtubers who bring a ton of industry experience to their videos.I found these channels to be helpful:- Rahul Pandey (e.g <a href="https://www.youtube.com/watch?v=ADWkkJtZna4" rel="nofollow">https://www.youtube.com/watch?v=ADWkkJtZna4</a>)- A life engineered (e.g <a href="https://www.youtube.com/watch?v=4i5iFlP01mQ" rel="nofollow">https://www.youtube.com/watch?v=4i5iFlP01mQ</a>)

评论 #33859574 未加载

medler超过 2 年前

The Unwritten Laws of Engineering by WJ King is a great book on the people-skills side of engineering and management. At ~60 pages it’s also mercifully short and to the point.

soheil超过 2 年前

There are many books, articles, and other resources that can help you to become a better software engineer. Some popular choices include "Clean Code" by Robert C. Martin, "The Pragmatic Programmer" by Andrew Hunt and David Thomas, and "Code Complete" by Steve McConnell. These books provide practical advice and guidance on a range of topics, including design, testing, debugging, and refactoring.

评论 #33861877 未加载

ljf超过 2 年前

I loved 'Joel on Software' - I got a heap from it (I was a PO but attempted to be as technically aware as possible).Taught me so much about all the things you mentioned

turtledragonfly超过 2 年前

This is more on the "managing lots of code" rather than the people side of things, but: John Lakos has a book called "Large-scale C++, volume I: Process and Architecture."Even if you don't read the book, I think this talk he gave on it is a good watch: <a href="https://www.youtube.com/watch?v=4NvRnkz6jVM" rel="nofollow">https://www.youtube.com/watch?v=4NvRnkz6jVM</a>

Noe2097超过 2 年前

Try "Extreme Ownership".It will give you concrete examples on how to broaden your scope out of just your individual contribution, by learning to care for all the rest, and pushing you to realize that to a large extent, the things you see as broken you can actually fix.Even when they are not inside the codebase you are in charge of. Even if they aren't even on engineering side.

jdougan超过 2 年前

"Death March", by Ed Yourdon. Most of the reccommended books In this thread are about trying to keep a project in a good place. This book is about what to do when it has already gone wrong. You can make a not terrible argument that much of the industry has gone to an all-death-march-all-the-time model. This book can help.

zb超过 2 年前

I’m currently reading The Staff Engineer's Path by Tanya Reilly and it’s really good (so far). It’s a great thing to read at the point it sounds like you have reached, where programming a little better is no longer going to move the needle, even if you aren’t in a position to apply everything in it yet.

rglover超过 2 年前

Systemantics is a fun read: <a href="https://www.amazon.com/SYSTEMANTICS-SYSTEMS-BIBLE-John-Gall-ebook/dp/B00AK1BIDM" rel="nofollow">https://www.amazon.com/SYSTEMANTICS-SYSTEMS-BIBLE-John-Gall-...</a>

pkdpic超过 2 年前

> Weaving the Web by Tim BL> Of Ants and Dinosaurs by Liu Cixin> The Unix O'Reilly GuideAll quick entertaining reads. All written by software engineers. All utterly useless for managing state in your React apps.

brnstz超过 2 年前

Worse is Better: <a href="https://www.dreamsongs.com/RiseOfWorseIsBetter.html" rel="nofollow">https://www.dreamsongs.com/RiseOfWorseIsBetter.html</a>

smcleod超过 2 年前

An absolute must from a "how to think" and cultural perspective is The Phoenix Project, many years on I still think back to this frequently.

mooreds超过 2 年前

Hiya,I'd consider these books/articles/podcasts:* Secrets of Consulting by Gerald Weinberg: <a href="http://geraldmweinberg.com/Site/Consulting_Secrets.html" rel="nofollow">http://geraldmweinberg.com/Site/Consulting_Secrets.html</a> Every problem is a people problem.* Refactoring by Martin Fowler et. al: <a href="https://martinfowler.com/books/refactoring.html" rel="nofollow">https://martinfowler.com/books/refactoring.html</a> talks about how and why to refactor, as well as providing a nomenclature for the process.* Code Complete by Steve McConnell. <a href="https://stevemcconnell.com/books/" rel="nofollow">https://stevemcconnell.com/books/</a> A bit dated (the last version I could find was from 2004) but a great overview of the entire software process, from requirements to maintenance.* The Mythical Man-Month by Fred Brookes: <a href="https://www.oreilly.com/library/view/mythical-man-month-the/0201835959/" rel="nofollow">https://www.oreilly.com/library/view/mythical-man-month-the/...</a> best practices about software development, written about a project from the 1960 and 1970s.* The Joel On Software Strategy Letters: <a href="https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-ben-and-jerrys-vs-amazon/" rel="nofollow">https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-...</a> is the first one. All of them (I think there are five) are great.* Letters to a New Developer: <a href="https://letterstoanewdeveloper.com/the-book/" rel="nofollow">https://letterstoanewdeveloper.com/the-book/</a> Please note I wrote this, but I still think it does a good job of discussing the "soft skills" in an easily digestible format.* Pragmatic Programmer by Dave Thomas and Andy Hunt: <a href="https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/" rel="nofollow">https://pragprog.com/titles/tpp20/the-pragmatic-programmer-2...</a> Haven't read the revised 20th anniversary edition, but the first one opened my eyes to the craft of software.* High Output Management by Andy Grove: <a href="https://bookshop.org/p/books/high-output-management-andrew-s-grove/6730629" rel="nofollow">https://bookshop.org/p/books/high-output-management-andrew-s...</a> a great way to think about throughput* The Phoenix Project by Gene Kim et. al: <a href="https://itrevolution.com/product/the-phoenix-project/" rel="nofollow">https://itrevolution.com/product/the-phoenix-project/</a> Fun novel(!) about applying lean management principles to software engineering.* Radical Candor (haven't read, but it's been recommended): <a href="https://www.radicalcandor.com/" rel="nofollow">https://www.radicalcandor.com/</a> About communication.* Good to Great by Jim Collins: <a href="https://en.wikipedia.org/wiki/Good_to_Great" rel="nofollow">https://en.wikipedia.org/wiki/Good_to_Great</a> Focuses on what great companies bring to the table. Helps me evaluate where to work.* Mastery Autonomy and Purpose: A great video about what people really want in work: <a href="https://www.youtube.com/watch?v=MzXXC4MZZnY" rel="nofollow">https://www.youtube.com/watch?v=MzXXC4MZZnY</a>* <a href="https://www.manager-tools.com/podcasts" rel="nofollow">https://www.manager-tools.com/podcasts</a> a podcast about managing people. You didn't say you wanted to be a people manager, but knowing what managers think about will make you more effective in any org.* Managing Humans by Michael Lopp: <a href="https://managinghumans.com/" rel="nofollow">https://managinghumans.com/</a> The whole Rands site is work reading, but I enjoyed this book about how to manage teams and build software. See above.* Don't Make Me Think by Steve Krug: <a href="https://sensible.com/dont-make-me-think/" rel="nofollow">https://sensible.com/dont-make-me-think/</a> Easy ways to think about usability, focusing on webapps. Short and easy.* Badass: Making Users Awesome, by Kathy Sierra: <a href="http://seriouspony.com/badass-users-the-book" rel="nofollow">http://seriouspony.com/badass-users-the-book</a> Will help you put yourself in the shoes of your users and think about how to build software they will love. Short and easy.Hope this helps.

jll29超过 2 年前

> Ask HN: Reading material on how to be a better software engineer?That's a bit like "Ask HN: Reading material on how to be a better pianist?"You will need to write and maintain a lot of code, and make a lot of mistakes, then you will get gradually better.

supr_strudl超过 2 年前

The Pragmatic Programmer (Hunt)Refactoring (Folwer)

dunk010超过 2 年前

The Design of Design.

boredemployee超过 2 年前

forget it... AI gonna replace all of us