5 Books Every New Software Engineer Should Read to Succeed

[@itsam00n]

thats a lot of great information , thanks a lot

[@diegosarkissian]

Really happy it was helpful. They are very good reads! And given they are older books, many local libraries usually have them available 💪

[@DebdootBasuRay]

Good video❤

[@diegosarkissian]

Thanks mate. Very happy you enjoyed it!

[@danielg.1008]

See the full video, summary Main topics: Software engineering principles, productivity, general soft skills, no the Books: pragmatic programmer by David Thomas, Clean Code by Bob Martin, Modern software engineering by David Farley, 100 page Machine Learning by Andre Burkov, deep work rules for focused success by Cal Newport, getting to Yes by Roger fisher, Never split the difference by Chris Voss.

[@Cempa666]

That quote about paying for mistakes is not from “Clean Code” it’s from “The Clean Coder”, both are Uncle Bob books so the confusion is understandable.

[@diegosarkissian]

Certainly my mistake, I must have mixed the quotes from both of the lists I have. Thankfully a very interesting and impactful quote nonetheless. Thanks for the correction 🙏

[@ruixue6955]

Interesting thing about the Clean Codes book is that My current team thinks IT as a legend that would never come true. My lead told Code should Be Simple, so when I implemented My tasks with many small classes, i got criticized by every one😂 and i seem to Be The only one who wrote enough unit tests

[@diegosarkissian]

Nooo way 😂. Thanks for sharing that anecdote. Any other resources you've found that have helped you as a software engineer??? Would love to know. Cheers 🚀

[@ruixue6955]

@@diegosarkissian I didn't mean that the Clean Code book does not make sense, but just wondered whether any of my team members have read it at all, and thus they doubted about the clean code approaches. I think it is also related to their experiences and their own knowledge. Personally I definitely vote for the clean code methodology. My current project's code base contains classes with thousands of lines of code, and our team just keeps adding more code to those existing classes, and some of them even did the copy-paste approach when working on new tasks, when I reviewed their code with negative comment on this, they told there is already existing style, why not copy them. On the opposite, they don't like my implementation with my own style with small classes, since they feel that it is too complex. This is indeed a bit of worrisome from my side

[@kreed1415]

I really have to push back on telling people to read Clean Code. The examples and overall methodology in that book is so incredibly outdated and are frankly just wrong. Hardcore addiction to abstraction and class-based nonsense is a 2010's era mindset that created nothing but slow legacy code.

[@diegosarkissian]

There are certainly some outdated concepts but I really learned some valuable lessons as a beginner. Any other book in the same genre you would recommend over Clean Code??? I would love to know and check it out.