How the internet used to be

Posted by Pete Morley

How the internet used to be

Back in the old times, The Internet was pumped directly in to your house through a pipe. It was the same pipe that was used for the analogue telephone and so it came with various caveats that we just accepted as modern, futuristic life.

In the olden times you would be surfing The Internet Super Highway, or ‘the web’ and then suddenly your Mum’s on the phone and you’re cut off.

There was a romantic, Wild West side to this. One moment you could be reading about some obscure Australian soap, catching up on the latest Evangelion gifs, or half way through printing a 1400 page pure text walkthrough of Final Fantasy 7. You could be planning Friday night on MSN while downloading -I promise this is System Of A Down doing Legend Of Zelda this time.mp3- and then boom. Screech, Chuurn, your Aunt’s talking through the internal speaker.

The early internet was exciting, frustrating at times; but there was one thing that made it great.

There was a level of kudos in just doing, sharing knowledge and making new things. People who were online at the time were semi-confined to niche groups or interests and people in those groups tended to share fandom, development, design and general ‘internet’ knowledge. Often you’d find yourself breaking out of your little web-groups, falling down rabbit holes of interesting snapshots of people’s lives, fandoms and stories. As you found new websites and groups you discovered new ways of presenting, coding and designing things. And with that came more little snippets of knowledge that people shared, for the kudos.

The thread that kept these little pockets of the internet thriving was the idea that knowledge was something to be celebrated and shared and that you could just create something for the sake of it.

One of my first websites was an Evangelion fan site. So as a little tribute to that, I set up https://centraldogma.co.uk. Part of me looks at the web nowadays and I’m sad how commercial it’s become, like a lot of early web-tinkerers I make websites for a living now. But I think it’s important to keep the experimental and whimsical aspect of the Internet alive, have a bit of fun with it, and to foster that free flow of knowledge and ideas when you can.

Let’s be controversial. Some advice for digital graphic designers

The worst piece of self-affirming advice I see and it’s been thrown around for the last 15 or so years. This really wasn’t the mindset, and it’s stunted a generation of web designers. 

Graphic designers don’t need to know how to code. 

It’s an idea that gets repeated, usually as reassurance. On the surface, it sounds liberating; especially if you’re a designer who has no interest in becoming a developer.

But it’s also one of the most limiting pieces of advice in modern web design.

If you design for the web and you don’t understand how the web is built, you’re designing in the dark. I’ll go as far as to suggest that you aren’t designing anything at all; you’re just making pictures.

Should I, as a graphic designer understand how to code?

Yes. Yes, you fucking should. 

I’m not saying that you need to know how to build an accessible, lean WordPress theme from scratch, or that you should know how to plug a front end in to a custom CMS. You don’t need to know how to develop web apps in Laravel, React, or interpret complex database systems. In fact, I’d suggest you don’t even look at those things unless you find dev enjoyable (which I do, because it’s actually quite fun).

You don’t need to know APIs, SEO, GEO or any three word acronyms other than CSS. 

But the absolute fact — and this is true of every single creative endeavour — is that the more you do know about the entire process, the better you will be as a designer.

This isn’t art. The end product, and it is a product, has to answer to the clients question: It needs to convert, raise awareness, increase sales, convince investors. Impact should be measurable. It also has to be accessible, scalable, on brand, on budget and, possible to build

The more you know about the post design process, the further you can push your creative work. 

What’s interesting is that all these disciplines start with HTML and CSS then quickly bleed in to each other. If you can build up the websites you design as static HTML and CSS front ends, you’ll quickly start to streamline your work. You’ll begin breaking sections in to reusable components because it’s efficient. You’ll build out a CSS framework with a solid starting point and foundation to save time. Your code will get leaner. You’ll quickly refine a library of modules and parts that complement your design style as you revisit your design process to see how far you can push them. 

So break out notepad and start building some of your frontends. You’ll become a better designer because of it, developers will want to work with you and we will all live in harmony. 

Bring back webrings! Friends, projects, likes and links.

© 2006 onwards petemorley.co.uk/petemorley.me