Basic Things

After working on the initial stages of several largish projects, I accumulated a list of things that share the following three properties:

• they are irrelevant while the project is small,
• they are a productivity multiplier when the project is large,
• they are much harder to introduce down the line.

On over-engineering; finding the right balance

A big debate among developers is whether to write code for today’s problem or to build a general-purpose solution for future needs. Both approaches have their pros and cons. Specific-purpose code can quickly become messy. But overly general code can add unnecessary complexity. This post, obviously opinionated, argues for a middle ground. That’s the sweet spot, as always.

As a software developer, I've always tried to write flawless code. Great code is not just functional – it should also be elegant, efficient, and robust.

Transmission Control Protocol (TCP) provides a reliable, connection-oriented, byte-stream, transport layer service. And its implementation is quite interesting.

Measuring Software Complexity: What Metrics to Use? 

• Add unnecessary complexity.
• Increase development and maintenance costs.
• Reduce your iteration speed.
• Avoid you from getting market-fit. 

The Rise Of User-Hostile Software |  

Guidelines to improve your software design skills with .NET (Part I)