[Go Make Things] The two types of harmful complexity in a web project

By rahmat hidayat

Wednesday, January 3, 2024

​

❄️ Holiday Sale! Now through the New Year, save 40% on Lean Web Club membership, private coaching, and all of my courses and workshops.

When consulting with clients, I often run into two types of complexity…

1. Using over-engineered tooling (like React) for simple, mostly static websites.
2. Using too little tooling for large, interactive, data-driven UI.

In both cases, the result is a site that's slower, more error prone, and harder to maintain.

Not all complexity is bad. Sometimes, it's unavoidable. But these two particular types of complexity are generally harmful to the long-term health of a project.

Over the next few days, I'm going to dig into this topic a bit more, with specific examples, and different approaches for addressing and simplifying overly complex projects.

And if you have a project that needs help, I have one consulting spot left. I'd love to work with you!

Cheers,
Chris

​

Want to share this with others or read it later? View it in a browser.​

​

Did someone forward this to you? Get Daily Developer Tips.

Don't want to get these emails? Totally cool. Update your subscriber preferences.

You can also unsubscribe from all emails from me, including updates to products you've purchased.

113 Cherry St #92768, Seattle, WA 98104-2205

Share :

Facebook Twitter Google+