public marks

PUBLIC MARKS with tag "best practices"

This year

2016

Why we use progressive enhancement to build GOV.UK | Technology at GDS

by Spone (via)
There seems to be a common belief among front-end developers that progressive enhancement is either old fashioned or has simply been replaced by single page applications. This is a problem of perception. We’d like to explain why we use progressive enhancement to build GOV.UK.

The Basics of Web Application Security

by Spone
Modern web development has many challenges, and of those security is both very important and often under-emphasized. While such techniques as threat analysis are increasingly recognized as essential to any serious development, there are also some basic practices which every developer can and should be doing as a matter of course.

A technical guide to SEO

by Spone
If you're the owner or maintainer of a website, you know SEO matters. A lot. This guide is meant to be an accurate list of all technical aspects of search engine optimisation. There's a lot more to being "SEO friendly" than just the technical part. Content is, as always, still king. It doesn't matter how technically OK your site is, if the content isn't up to snuff, it won't do you much good. But the technical parts do matter, after all.

2015

GitFlow considered harmful

by Spone (via)
GitFlow is probably the most popular Git branching model in use today. It seems to be everywhere. It certainly is everywhere for me personally - practically every project at my current job uses it, and often it's the clients themselves who have chosen it. I remember reading the original GitFlow article back when it first came out. I was deeply unimpressed - I thought it was a weird, over-engineered solution to a non-existent problem. I couldn't see a single benefit of using such a heavy approach. I quickly dismissed the article and continued to use Git the way I always did (I'll describe that way later in the article). Now, after having some hands-on experience with GitFlow, and based on my observations of others using (or, should I say more precisely, trying to use) it, that initial, intuitive dislike has grown into a well-founded, experienced distaste. In this article I want to explain precisely the reasons for that distaste, and present an alternative way of branching which is superior, at least in my opinion, to GitFlow in every way.

GitLab Flow | GitLab

by Spone & 1 other
Version management with git makes branching and merging much easier than older versioning systems such as SVN. This allows a wide variety of branching strategies and workflows. Almost all of these are an improvement over the methods used before git. But many organizations end up with a workflow that is not clearly defined, overly complex or not integrated with issue tracking systems. Therefore we propose the GitLab flow as clearly defined set of best practices. It combines feature driven development and feature branches with issue tracking.

Filmsourcing

by gregg
Sharing Filmmaking Resources

2014

The offline cookbook - JakeArchibald.com

by Spone
When AppCache arrived on the scene it gave us a couple of patterns to make content work offline. If those were the patterns you needed, congratulations, you won the AppCache lottery (the jackpot remains unclaimed), but the rest of us were left huddled in a corner rocking back & forth.

7 Principles of Rich Web Applications |

by Spone
This is a writeup based on a presentation I gave at BrazilJS in August 2014. It builds on some of the ideas I’ve been blogging about recently related mostly to UX and performance.

How To Scroll

by Spone
Scroll-based interaction is incredibly popular for interactive storytelling. There are many compelling reasons for this, yet scrolling is surprisingly nuanced and easy to break. So here are five rules for employing scrolling effectively.

Enduring CSS: writing style sheets for rapidly changing, long-lived projects - Author and responsive web developer Ben Frain

by Spone
When architecting CSS for a large scale project it’s a common aim to abstract visual patterns for re-use, DRY out code and normalise our designs as much as possible. However, for rapidly changing projects, I’m no longer convinced those principles should necessarily be followed to the nth degree, nor that they offer the biggest wins. This post describes what I consider the most advantageous practices and approaches when authoring CSS for a rapidly changing, large scale web project.

Want to Be a Better Project Manager? Learn How to Cook. — Medium

by gregg
The commonalities between time, resource management and culinary skill; resolve under pressure, managing critical paths, measuring properly, and finding the right recipe.

PUBLIC TAGS related to tag "best practices"

ajax +   alire +   amazon +   analyse +   api +   apple +   architecture +   astuces +   aws +   bestpractice +   bonnes pratiques +   case study +   cheat sheet +   checklist +   code +   conseils +   css +   design +   dev +   development +   django +   développement +   email +   facebook +   guide +   guidelines +   html +   ipad +   iphone +   javascript +   management +   mobile +   performance +   php +   prog. +   rails +   rest +   security +   seo +   software +   sql +   standards +   tutorial +   tutorials +   ui +   ux +   web +   webdesign +   webdev +   xhtml +  

Active users

Spone
last mark : 09/01/2017 21:38

mfaure
last mark : 05/01/2016 16:46

gregg
last mark : 06/02/2015 21:38

ghis
last mark : 19/10/2014 23:39

Hieroglyphe
last mark : 10/09/2014 14:07