It was only a matter of time before I fell in love with Domain-Driven Design.

Not only did it clarify how to organize my code and untangle the spaghetti…

The truth is: I’m a word nerd.

I’ve always loved books.

I’ve always loved writing.

I’ve always found magic in accents, languages, blogging, poetry, songwriting, copywriting..

Anything and everything within the realm of words, I’m in.

While I’d love to “TED talk” your inbox full of word-related self development content like affirmations, NLP, subconscious programming & so on…

If you’re getting this email, it’s because you’re a software developer.

<aside> <img src="/icons/circle-alternate_green.svg" alt="/icons/circle-alternate_green.svg" width="40px" /> In this letter, I’d like to take you on a little journey and:

• discuss why language matters so much as a developer
• explain how I’ve noticed code-first developers think & talk about code
• discuss how refining my language and definitions has helped me improve my ability to develop The Software Essentialist
• share an update on the course & book progress
• let you know about an upcoming sale! </aside>

Why language matters as a developer

Say I told you to go look for stones and bring ‘em back.

Why? Ah, because we’re going to cast ‘em in the water and make pretty ripples.

Nice way to spend a Sunday afternoon, no?

Cool, so unconsciously, what’d you’d do is formulate a definition for rounded, cast-able stones in your mind.

There’s something called the Reticular Activating System — basically the part of your brain that helps you notice stuff that’s relevant.

Based on this instruction, you’d constrain your perception to small, tiny, throwable stones, probably.

—

Now if I said that we were going to get some stones again, but this time, it was to forge some weapons.