Skip to main content

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.

Coding

  • Writing solid code
  • Code complete
  • Programming Pearls, more programming pearls(recommended)
  • [NEW] Introduction to Algorithms


Programming

  • Refactoring (M. Fowler)
  • Pragmatic Programmer
  • Clean code
  • [NEW] Software Engineering: A Practitioner's Approach
  • [NEW] The Mythical Man-Month
  • [NEW] The Art of Computer Programming


Design

  • Applying UML and Patterns (GRASP patterns)
  • C++ coding standards (Sutter, Alexandrescu)
  • The C++ programming language (Stroustrup, Part IV)
  • Object-oriented programming (Peter Coad)
  • Patterns of Enterprise Application Architecture (Fowler)
  • DDD (Erik Evans)
  • [NEW] Design Patterns: Elements of Reusable Object-Oriented Software (GOF)
  • [NEW] Building Microservices: Designing Fine-Grained Systems (Sam Newman)
  • [NEW] RESTful Web Services
  • [NEW] Implementing Domain-Driven Design (Vaughn Vernon)
  • [NEW] Structure and Interpretation of Computer Programs
  • [NEW] Building Micro Services Designing Fine-Grained Systems (Newman)


Project (lifecycle, management, non-technical issues)

  • Design patterns (GOF)
  • Writing use cases
  • Rapid development
  • Software project survival guide (recommended)
  • Software estimation - demystifying the black art (recommended)
  • Debugging the development process (recommended) 
  • Agile Software Development, Principles, Patterns, and Practices (R.Martin)
  • Working Effectively with Legacy Code (Michael Feathers)


Professional

  • Clean coder
  • Mythical man month
  • Peopleware
  • Slack
  • [NEW] Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
  • [NEW] Microsoft Application Architecture Guide
  • [NEW] CODE: The Hidden Language of Computer Hardware and Software
Don't try to cover all these books in a few months, you also need practice, additional to theory. Besides this, some of the books need to be re-read after a while. 

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Azure Service Bus - How to extend the lock of a message | RenewLock

In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...