Version control Development enviroments

20 Aug 2014

Version control & Development enviroments

Being a developer

“Inhale… and exhale. Relax and keep working.” Not really how it is to be a webdeveloper all the time. This post is about how to get more breathing room and make sure that your misstakes will not matter.

The first step to give yourself breathing room

Version control; relax and let yourself experiment with diffrent files by branching out to a separate branch. Git checkout -b branchname

Expanding on VC

Services and branches

Have a service listen to your repo and set it up to listen for changes on branches for changes and commits, and upon commits deploy to the server, being it production or live.


A topic I’m not super enlightened in, are tags. Haven’t used tags in git at all. Wonder what it is meant to do. Listened to a podcast while writing this actually (web ahead) and in the episode i listened to they mention it, didn’t stick in my head though.

Take a listen yourself: WebAhead episode 79

Local is fast

Everybody should have their own development/production enviroment. VM or server at haven’t figured out yet, but something along those lines would be optimal for a safe and relaxed enviroment.

Workflow: Style guide driven development

Also a diffrent topic I recently read an article about, was working on the front-end straight into and from styleguides. What I think this would mean in practice, would be that from a concept/mockup you extract elements and develop them separately and put them and present them in a standalone enviroment to be expanded and prototyped upon and with. The elements would then be refined in the markup of the styleguide and eventually updated and iterated upon.

Get strapped!

Why I want to embrace this topic and kind of way of doing things, is because I want sites and apps; projects(!), to be built using kind of a framework. Every websites stylesheet should more or less be a bootstrap kind of framework, where all you have to do is add the diffrent classes to get the kind of component/element and behavior that you want.

The article meant that the work flow would mean working on the backend of things could be built simultaneously. However I think this approach would require a longer startup time to initiate. The benefits however would be the prototyping experience with the elements, and the OOP style of things.

Article on styleguide driven development from the Envato blog

codepen pen arrow-right arrow-down arrow-left twitter github