Have a look at the following code. How does it make you feel?

<Field
type={intDur}
res={res}
onUpdate={calcDur}
/>

This component could contain the best code ever written. The gods of code could have passed it down, chiseled into a stone tablet, it would still suck.

res could be short for response, result, resource, resume, reset, reserved, restore, resolve..

Naming things is hard, but there’s a way to make it infinitely better:

Don’t name things for yourself or the computer! Name things for your colleagues!

It’s a 1-step program:

Naming functions:

Name functions by what they do. It doesn’t matter if the names…


Or: Help! I am drowning in knowledge

A few years ago you had people that knew everything there was to know about the web and the technologies that power it. Everything!

Now though, the amount of new knowledge in the form of frameworks, tools, practices, languages and skills are growing out of control. There’s no way a person can know everything there is to know about the web.

People don’t like this, which is understandable.

It’s intimidating for people that have been doing it since the beginning, and must be worse still for anyone just getting started with development.

So, what should you learn?

The best advice I can think of…


Ready for a change of scenery?

As a long time Sublime Text 2 user I could never get to grips with other editors. Years of practice meant the key commands were almost hard wired into my brain, and although I tried and liked several alternatives I just couldn’t give up on the multi-editing, super fast searching and simplicity.

Then from out of nowhere came VS Code, an open source code editor by Microsoft(!?). After seeing a lot of good reviews on my twitter timeline I gave it a go, with no expectations.

After playing around with it I was left confused and aroused, it was.. good!


Escaping the dynamic content pitfalls

Building great and unique websites/web apps where the content is managed by the Client comes with many challenges. With the now de-facto responsive website allowing for user-entered content is even harder.

For some projects, the benefits a CMS can bring outweighs these extra complexities, but I’ve seen cases where they’ve brought nothing but pain.

I often refer to the below chart. I made this as a joke, but I think it illustrates the case. You cannot have a site that is 1: fully content managed, 2: good looking and 3: quick to build (cheap). …


Part 1/2: What is it? Where did it come from and how to stop it from happening.

There is an ancient evil haunting all workplaces. It’s known as legacy code.

It’s the stuff of nightmares. The kind of thing that sucks the life out of any developer and kills careers. A frankenstein’s monster of spaghetti code, bad practices and zero documentation, forged in the fires of Mount Doom and FTP’ed into the domain of mankind.

Behold! The main.css file; Thousands upon thousands of lines, selectors a deadly mix of id’s, class names and some base selectors thrown in for good…


A crazy attempt at predicting the unpredictable

The other night i couldn’t sleep and did what i usually do, think of something really complex that just knocks me out.

This time though, i didn’t think about the usual stuff like “where is the universe?” or “are we all in a simulation?”, but instead “where is the web going?”

I like thought experiments, so let’s do one now. What will the job of a web developer look like in 10–20 years?

Now

Today, we hand-code websites and applications. There’s several services that can do part of that job for you — even…


Creating a smooth scrolling experience

60fps cat in snow action

Over the last few months I've worked on a few different interactive case studies. I guess what you’d call Parallax sites. The kind of page where things move around as you scroll. As it turns out these are quite hard to get jank free (Smooth, without lag or stuttering) as even a tiny hiccup is very noticeable when the page is scrolling.

It’s forced me to put a lot of time and effort into performance and optimising animations. …


What I have learned: Abridged version

Part 1 of x

I've been learning Angular for a while now. Although there’s still some parts of Angular development i have yet to fully master, I wanted to compile my current knowledge in a quick-read format.

I’m writing this post mainly to learn — as I find documenting a great way to memorize — but I hope it can be of help to others aboard the ng-express.

To summarize: The following does not go into details. It is not a beginner’s guide, nor is it a tutorial. …

Bård Hovde

Front-End Developer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store