Archive - Engineering Harmony

Why it's time to be imperative

It’s imperative that teams are using AI

Jun 27

It's imper-AI-tive

We've established the clear benefits of declarative rather than imperative leadership.

Jun 26

Declaring victory

Declarative leadership FTW?

Jun 25

Imperative or declarative leadership

You may be familiar with the differences between imperative and declarative code.

Jun 24

It's the question that's valuable

With AI, the price of intelligence can be metered in cents.

Jun 23

Awareness is enough

We often think the hard work is in solving a problem.

Jun 20

Let's walk and talk

Last week, I faced a dreaded task: corporate board papers.

Jun 19

AI: the Anti-Internet

AI was born from the internet.

Jun 18

Part-time, full focus

The final stretch before a release is always intense.

Jun 17

Optionality vs. Tech debt

Recorded on Friday, here’s a brief walkthrough of optionality, tech debt and why the language we use is critical to how we understand our roles as…

Jun 16

Humans, AI and what we can learn from Substack

Nothing in this post is original.

Jun 13

Tech debt is an outdated concept

Tech debt is often overused as a blanket statement for all manner of engineering issues. What if we reframed our approach?

Jun 12

#nojs-banner { position: fixed; bottom: 0; left: 0; padding: 16px 16px 16px 32px; width: 100%; box-sizing: border-box; background: red; color: white; font-family: -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; font-size: 13px; line-height: 13px; } #nojs-banner a { color: inherit; text-decoration: underline; } This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts