StatusCake

Ditch The Shackles – The WYSIWYG Editor!

DNS

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.

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

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

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.