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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP