Skip to main content

Books for software developers professionals

As a software developer you expected to write some code. The difference between a good and mediocre developer is a combination of knowledge and skills. I compiled a list of books that are necessary to all the developers.


At the very early stage of the career, the developer should learn the basics: how to structure his code, how to write small functions, what is desirable and what is not. I can suggest two books for people starting in software development: "Code Complete: A Practical Handbook of Software Construction" from Steve McConnell and "Clean code" by Robert C. Martin. The first one presents the basic rules on how to write good code, and the second one explores in greater depth the best practices for writing good code.



A also strongly suggest to learn about the design patterns that exists in the
software development. There are two well known books, the Design patterns : elements of reusable object-oriented software by the gang of four (Erich Gamma,‎ Richard Helm,‎ Ralph Johnson,‎ and John Vlissides) and the Head First Design Patterns by Eric Freeman,‎ Elisabeth Freeman,‎ and Kathy Sierra.






After you learn the basics of designing software, you have to move to the architecture side. There are two books that I liked most: the Clean Architecture: A Craftsman's Guide to Software Structure and Design from Robert C. Martin and Working Effectively with Legacy Code by Michael Feathers. Both are necessary if you are involved in big projects that require both new development and maintenance of the old code. As you are getting older you will also suggest having a look at The Mythical Man-Month: Essays on Software Engineering by  Frederick P. Brooks Jr. Old book, but provides a good view of the management of large projects.



Finally, we must not forget to train ourselves continuously. What are the best books about this practice out there? I will suggest two of them: The Clean Coder: A Code of Conduct for Professional Programmers  from  Robert C. Martin and The Pragmatic Programmer by Andrew Hunt and David Thomas. As a developer you never stop training and improving yourself. These two books can provide the directions required for a successful career, at least as a developer.



If you think these books are expensive, you can try buying them used or watch for discounts in big bookstores like Amazon using a third party site (like keepa.com).



An alternative solution is to sign up for O'Reily from learning.oreilly.com/signup/ although I found them expensive. I was using O'Reily when it was bundled with an ACM subscription for around 100 Euro, however after they stopped this offer, I will probably cancel the ACM subscription itself although they are still offering some books through skillport.
Labels:

Popular posts from this blog

Static linking with gcc and g++

In this tutorial, we will explain what the static linking is, how this affect the size of final binary, and why statically linking with g++ sometimes is pain. By definition, a statically compiled binary is a group of programmer ‘s routines, external functions, and variables which are packed into the final binary executable. The compiler or the linker produces the final object and embeds all the functions and variables and the linking phase.  There are two reasons of using dynamic linking and shared libraries: 1) Avoid creating a huge binary, if all the programs use a standard set of libraries why not having the operating system providing to them 2) Compatibility on operating system and machine dependant characteristics: sometimes the libraries must be implemented based on the architecture or the operating system and using dynamic linking is an easy way to avoid this catch. On the other hand, static linking is the ideal way of distributing one software product, pay...
Read more

Processing Milky Way in RawTherapee

This text is an analysis of a video I did some months ago how to process photos of our Milky Way in RawTherapee. You can find the picture here . The photo was taken by wiegemalt. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Editing: Step 1: Fixing lighting The first thing someone notices when opening the picture is the extreme noise due to high ISO used (1600 - check the picture on the right). The first thought is to de-noise the picture, however, if you do that you are going to loose the details of the night sky. The main reason for the high noise is the additional exposure Rawtherapee adds when the 'Auto' button is pressed. In particular, the RT adds +2.4 EV to equalize the picture. This is Wrong! What we want is to keep the noise down and at the same time bring the stars up. That's why we are going to play with the Tone Curve of the RT. To adjust the light properly we increase the cont...
Read more

Auto - Vectorization with little help from GCC!

This tutorial helps the programmers to benefit the progress of the auto-vectorization algorithms that are implemented in modern compilers, such as gcc. Before you start playing with the vectorization of your code i assume that you don't have any bottleneck in you code (like dynamic memory allocation etc) in the critical path. In this tutorial we will use the gcc 4.4.1, but the same steps can be applied to newer or older versions.  First of all there are two issues with auto vectorization:  1) gcc must know the architecture (eg what SIMD instructions are available)  2) The data structures must by properly aligned in memory The first step is to find the architecture of your processor and point it to gcc using the flags -mtune=... / -march=... you specify the architecture.  For example, my laptop is core2Duo so i put -march=core2. You can find more more information  here .  The next problem we must solve is knowledge of memory alignment. ...
Read more