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
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026