coding for fun: why i still build useless things

func BuildUselessThing() Joy {
    return Experiment().
        WithoutPressure().
        IgnoringBestPractices().
        JustForFun()
}

“creativity is intelligence having fun.” - albert einstein

most side projects are useless.

that’s not a bug. it’s the whole point.

why it works:

• no deadlines killing creativity.
• no stakeholders second-guessing you.
• no perfectionism paralysis.
• just you, code, and pure experimentation.

this is how you actually grow.

when you code for yourself, all the noise disappears:

• no security audits.
• no architecture reviews.
• no framework debates.
• no “best practices” prison.

just you building whatever weird shit comes to mind.

  freedom -> experimentation -> learning -> [real skills]

useless projects build real skills.

you solve problems you’d never touch at work. explore tools you didn’t know existed. find solutions no one expected.

because you’re not trying to be “perfect”, you get better. faster. embrace simplicity over complexity: ship first, optimize never.

this isn’t just about code:

• want to master something? remove the pressure.
• want to innovate? give yourself permission to fail.
• want to grow? build useless things.

so yeah, i still code useless things.

every “pointless” line of code makes me better at the serious stuff.

stop waiting for the perfect project. build something weird. make it messy. your turn to build: the world’s unfinished anyway.

serious code pays bills. useless code pays dividends.