Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Sometimes the easiest solution isn’t the best solution – and unfortunately a lot of Developers start their career on the wrong path thinking otherwise.
When I first was learning how to make websites I loaded up the latest version of Adobe Dreamweaver (then Macromedia) and started designing away – adding tables (This was awhile ago!), some animated gifs and yes, on occasions – even some midi files. The sites that were made were predictably a splurge of awfulness that were by all counts an serious offence to the eyes – but they were my own sites and even now I have a special place in my heart for those sites as they got me into an industry I love.
I was making these ‘Dreamweaver’ sites with a few years and what did I learn? Absolutely zilch. Nadda. Not a darn thing! Sure the end result looked impressive for someone who couldn’t code (or clearly could design!) but all I was doing was using menus, dragging and dropping pictures and in general having the code written for me by the underlying editor. It was all too easy to produce these sites and think I had no need to learn how to code, the end justifies the means if you will.
This was the single largest mistake of my development life and yet one I suspect quite a few young programmers made and even to this day still make. If I could go back to 14 year old me and make myself open up Notepad and just attempt to code everything from scratch I would – and it would not of taken me years longer than it needed to learn the wonders of CSS, HTML and Javascript.
So why is it that even now colleges and schools all over are still teaching kids to use Dreamweaver before actually teaching them to code. Dreamweaver and other WYSIWYG editors are great tools and heck I even use them to do this day for prototyping – but they are tools that are meant to assist your coding, not replace it.
So what’s my point? Un-install your WYSIWYG editors until you can build the exact same site without needing them. Creating your sites from scratch will take longer, you’ll likely even have more trouble – but in the long run… in the long run you’ll thank yourself. Editing your own code is a darn sight easier than editing some of the garbage that editors generate for you, and beyond that you can be more creative when you remove the shackles.
James Barnes
Share this
More from StatusCake
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026