I seem to be learning again and again that software design begins with stories. A lot of smaller stories, as told by humans, in a human language, in no particular order. Such individual stories are actually chapters in a larger book, yet to be put in order. And the complete story has yet to be discovered.

No, it's not about technology, it's about how technology can support human interest, achieved by means of our interest in technology. Technology is a means to serve the interests of all parties. It's not about developers being tools themselves to support another party's interests with their knowledge of technology, enslaved to someone's wishes, needs, limits, or requirements. Developers should have their own interests at heart, by which they are able to support another party's interests. They should guard their own interests: that's how they learn and grow, and invest gained experience again so they can keep supporting other party's interests.

But it remains a human story above all, not a technology story. The human story reveals value, necessity, raison d'être, and the technological story exists only to support that. Technical stories originate from human stories. It's partially about keeping everyone happy and satisfied as can be. But it's complicated. It's so easy to get lost in technology, overtaken by virtual enemies or otherwise overwhelmed because of our limited human mental capacity. I didn't even mention lack of understanding of what software design actually entails or needs (on both sides), impossible deadlines, developer inexperience, how the story changes over time, or how destructive management can be. Yes, it's complicated at best. Partially because it requires the collaboration of parties that don't understand each other's needs very well nor how to align them. But we learn to communicate along the way. We do that to create better stories. We do that so we can learn to write our own stories, instead of having it written for us by someone else. Better stories make people happier.

There's a gap between the human world and the computer world. The human mind and the computer mind are separated by mismatch. They're not actually compatible. The only friendship they share seems superficial and exists only as long as it's beneficial. Then we break up and things quickly become hateful. Until it's all fixed again.

Designers and developers stand in between worlds, trying to bridge the gap. Communication requires complex translation cycles to and fro, and mistakes in translations are rather costly. Clients reveal their wishes, while developers wage war.

That is what we are, my friend: warriors, without a doubt. We are. Trust me, I've seen it.

DON'T BE AMBITIOUS. AGAIN: DON'T BE AMBITIOUS.

To the optimist, the glass is half-full. To the pessimist, the glass is half-empty. To the engineer, the glass is twice as big as it needs to be. To the economist, too much money has been spent on the glass.

Am I testing this code, or is this code testing me?

How do programmers become wealthy? I don't know... Inheritance.

Most programmers have to wait until they get arrays.

I had a problem, so I decided to use OOP. Now I have a ProblemFactory...

Therapist: Do you get enough rest?

Programmer: Of course. REST is a lifestyle.

Also see Programmer Humor and https://www.reddit.com/r/ProgrammerHumor/.

To understand recursion, you must first understand recursion.

// Customer advice: keep it simple.
public class CustomerSuppliedPredicate : IPredicate
{
    public bool ItRainedYesterday { get; init; }
    public bool MySocksAreStillWet { get; init; } 
    public bool MaryWillCallMeTomorrow { get; init; }
    public bool ThereIsATrafficJamOnRoute66 { get; init; } 
    public bool IWillBeFamousInOneYear { get; init; }
    public bool ConditionalNestingOverflows { get; init; }
    public bool CyclomaticComplexityIsViolated { get; init; }
    
    public bool IsSatisfied()
    {
        if (IWillBeFamousInOneYear)
        {
            if (!ItRainedYesterday || !MySocksAreStillWet)
            {
                if (MaryWillCallMeTomorrow)
                {
                    if (!ThereIsATrafficJamOnRoute66)
                    {
                        if (ConditionalNestingOverflows || CyclomaticComplexityIsViolated)
                        {
                            return true;
                        }
                    }
                }
            }
        }
        
        return false;
    }
}

try
{
    var result = new CustomerSuppliedPredicate().IsSatisfied();
    
    if (result)
    {
        System.Random.Shared.Next(1, 4) switch
        {
            1 => DoSomethingArbitrary_1(),
            2 => DoSomethingArbitrary_2(),
            3 => DoSomethingArbitrary_3()
        }
    }
}
catch (TooManyConditionsException ex)
{
    // Don't even try to fix this.
    // The real problem actually is not in the code, even though the code is bad...
}

// Programmer reimplementation:
// - Follow customer advice.
// - Apply KISS.
// - Use advanced programming techniques.
// - Deliver expected functionality.
public class ImprovedPredicate : IPredicate, IHighlyAccurateEstimate
{
    public bool IsSatisfied()
        => System.Random.Shared.Next(0, 2) == 1;
}

public interface IRule;

My biggest challenge right now is to bring order and routine to what otherwise becomes a guessing game of chance: I need a method (pun intended). ~ Phundamentals

The right structure of a software system is more important than its correct behavior. ~ Stefano Santilli

The Zero Principle of Software Design

The creative mind cannot be made subject to the principles of production systems nor be imprisoned in its methodology without impairing its creative potential, no matter how hard one craves control. Creativity or control, choose one. ~ Phundamentals

What's the value of being wise, when being right is the only thing that matters? ~ Phundamentals

Nothing is more dangerous than an idea when it is the only one you have. ~ Emil Chartier Alain

IO : Input/Output Information Overload

AIO : All In One Assault by Information Overload

HIO : Health Information Organization Hurt by Information Overload

BIO : Biography Brain-damaged by Information Overload

Many rules were created so we could keep up appearances and hide behind them, but we, truthseekers, cannot. ~ Phundamentals

AKA: Boolean logic

Rule systems were created by rulers to control the mind of those being ruled. They are meant to distract from the control that is being exercised through them. ~ Phundamentals

There are no secrets to success. It is the result of preparation, hard work, and learning from failure. ~ Colin Powell

Decisions are often based on intuition. Intuition requires experience. Experiences requires making a lot of mistakes.

Encapsulate what varies, and separate it from what stays the same. ~ The Many

False hopes must be crushed.

1. If it seems too difficult, then arrive there faster.
2. If it is too difficult, then accept the fact.

The Psychology of Coding: Overcoming Mental Blocks and Staying Motivated

Second Order Thinking

D.R.Y.M. Don't Repeat Your Mistakes...

DRY gone bad

If you want to go fast, go alone. If you want to go far, go together. ~ African proverb