Back in 2000, we built our first commercial website and tested it on a 56k modem, feeling proud when a page loaded in less than a minute. Google was just two years old. There was no responsive design, smartphones were science fiction, and if you mentioned AI to a web developer, they would likely think you meant the imminent Spielberg movie.
A lot has changed since then.
In the past twenty-five years, we’ve seen technologies arrive with lots of excitement and then quietly disappear. We watched Flash become popular and then fade away. We experienced the browser wars, adapted to mobile, and learned to work in an industry that seems to reinvent itself every year or so.
What surprises us most isn’t how much has changed, but how much has stayed the same.
The things that made websites work well around the year 2000 are basically the same things that make them work today.
The tools have improved, but the main principles remain resolutely unchanged.
Understand the problem before proposing the solution
In 2000, clients would ask for a website much like someone might ask for a car. They knew they needed one, but often weren’t sure what it should do, who it was for, or how it should work.
Our job, then and now, was to slow things down and ask the tough questions. What are you trying to achieve? Who needs to find you? What should happen when they do? How will you know if it worked?
These conversations aren’t glamorous, but they’re where good projects start. Even after a quarter of a century, we still ask these questions because the answers shape everything that comes next. Structure, content, features, tone, and long-term success all depend on getting this right.
If you skip this step, you’ll likely end up with something that at best good but doesn’t really work. Technology has given us many new ways to build websites, but it hasn’t given us a way to avoid thinking things through.
Clear communication beats technical cleverness
We’ve always believed that if we can’t explain what we’re doing in plain English, we probably don’t understand it ourselves. Technical terms have their place, but they’re often used to hide confusion instead of making things clear.
This is more important than ever. Clients now hear terms like headless CMS, serverless architecture, and AI-powered personalisation, which can sound expensive and a bit intimidating. But what they really want to know is simple. What does this do? Why does it matter? How will it help the business?
Even the best technical solution isn’t very useful if the client doesn’t understand what they’re getting or why it matters. Complexity isn’t valuable on its own. We’ve been translating from developer-speak to plain language since before ‘the cloud’ meant anything other than weather, and it’s still a valuable skill.
Reliability is not exciting, but it is everything
No one has ever called us in a panic because their website was working perfectly. The urgent calls always come when something breaks, usually at the worst possible time.
Most clients don’t want magic from their web partner. They want reliability. Answering emails, meeting deadlines, being honest about bad ideas, and being there if things go wrong.
These qualities aren’t glamorous and rarely appear on agency websites, but they’re surprisingly rare. Over the years, we’ve worked with many clients whose previous developers just stopped responding. No explanation, no handover, just confusion and an unfinished website.
Being quietly dependable has worked well for us. Simply doing what you promised, when you promised, is still very effective.
The user always comes first
Long before user experience became a field with its own conferences and job titles, we asked a simple question. Will this make sense to the person using it?
It’s surprising how often this is overlooked. Websites are often designed to impress other designers, please internal teams, or use the latest technology. The real user, who is usually busy and a bit impatient, is left to figure things out alone.
They rarely bother.
Good web development has always been about empathy. You’re not building for yourself or your portfolio. You’re building for someone who wants to finish a task quickly and move on. If they don’t have to think about how your website works, you’ve probably done it right.
Craftsmanship still shows
There’s a quiet satisfaction in doing work well. Clean, readable code that others can understand. Smart decisions made early to avoid problems later. Attention to details most people won’t notice, but would miss if they weren’t there.
This isn’t about perfectionism or extra flourishes. It’s about professional standards. The same instinct that makes a good carpenter finish the back of a cupboard or level something no one will ever measure.
Artificial intelligence can now write code, and sometimes it does a lot of it quite well. But it can’t care if the work is good, maintainable, or right for the job. That’s still up to people, and it still matters.
Looking ahead by remembering where we have been
The web industry often forgets its own history. Every new technology shows up as if nothing like it has ever existed, and we end up relearning the same lessons at a high cost.
We prefer to bring our experience forward. Not as nostalgia or resistance to change, but as perspective. Seeing trends come and go gives you healthy skepticism. You learn to spot real progress and avoid getting distracted by flashy things that only make things harder.
2026 will bring new tools, new challenges, and lots of new terms to learn. That’s part of what keeps this industry interesting. We’ll handle it the same way we always have, by understanding the problem, communicating clearly, being reliable, focusing on the user, and taking pride in good work.
Some things don’t need to be disrupted.