Heuristic Outcomes by Ade Oshineye

Software craftsmanship, photography and heuristics.

Saturday 14 May 2011

Quadriga

at 20:48
Email ThisBlogThis!Share to TwitterShare to Facebook
Labels: google
Newer Post Older Post Home

Search This Blog

About Me

Unknown
View my complete profile

Blog Archive

  • ►  2017 ( 3 )
    • ►  December ( 1 )
    • ►  June ( 1 )
    • ►  May ( 1 )
  • ►  2016 ( 5 )
    • ►  October ( 1 )
    • ►  August ( 1 )
    • ►  July ( 1 )
    • ►  June ( 2 )
  • ►  2015 ( 4 )
    • ►  September ( 1 )
    • ►  June ( 1 )
    • ►  January ( 2 )
  • ►  2014 ( 1 )
    • ►  December ( 1 )
  • ►  2013 ( 14 )
    • ►  December ( 2 )
    • ►  November ( 1 )
    • ►  October ( 1 )
    • ►  September ( 3 )
    • ►  June ( 1 )
    • ►  April ( 1 )
    • ►  March ( 4 )
    • ►  February ( 1 )
  • ►  2012 ( 2 )
    • ►  December ( 1 )
    • ►  March ( 1 )
  • ▼  2011 ( 8 )
    • ►  July ( 1 )
    • ▼  May ( 2 )
      • Quadriga
      • What is Developer Experience?
    • ►  March ( 1 )
    • ►  January ( 4 )
  • ►  2010 ( 36 )
    • ►  December ( 1 )
    • ►  August ( 1 )
    • ►  July ( 1 )
    • ►  June ( 2 )
    • ►  May ( 12 )
    • ►  April ( 2 )
    • ►  March ( 6 )
    • ►  February ( 5 )
    • ►  January ( 6 )
  • ►  2009 ( 7 )
    • ►  December ( 6 )
    • ►  October ( 1 )

Popular Posts

  • Awkward questions for those boarding the microservices bandwagon
    Why isn't this a library ? What heuristics do you use to decide when to build (or extract) a service versus building (or extracting) a...
  • Software Craftsmanship: More than just a manifesto
    TL;DR Ill-informed proponents of Software Craftsmanship tend to make the following mistakes: they don't read anything except the man...
  • 47: First past the post
  • What is Developer Experience?
    Developer Experience ( #devexp ) is an aspirational movement that seeks to apply the techniques of User Experience (UX) professionals to t...
  • Apprenticeship Patterns is now Creative Commons licensed
    Just over 5 years ago Dave and I started Apprenticeship Patterns on a wiki. We used that wiki to organize the stories we found as we went ...
  • Omnivorous inclusiveness and the closing of the browser parenthesis
    In the past I've thought of the web as a convoy of browsers . That turns out to be wrong. Nowadays (thanks to a long lunch with Paul ...
  • 44: Time to (let) go
  • Why doesn't this blog allow comments?
    Should your blog have comments? That's one of the perennial questions that every blogger faces. Are comments a way to bring in vital f...
  • On translation
    People are often surprised when they discover that Dave Hoover and I have only met twice. Yet, somehow, over the course of 4 and a half yea...
  • The irony and the tragedy of OAuth scopes
    I was taking a look at my PeerIndex profile when I got the above screen. I was surprised since the button I clicked said "sign in ...

Labels

52.0 aesthetics android APIs apple apprenticeship patterns artificial intelligence atom blogging books buzz comments communities computational aesthetics conferences context curation developer experience devexp devrel gated communities generative communities google google+ googleio history identity io16 io2016 machine learning microservices mobile multi-context multi-device multi-screen nostalgia open openid openwebfoo osjam personal area networks photos pimlico pirate testing portable content units post-pc presentations product design progressive web apps python refactoring reftest retrospective slice sluice social-login social-web software craftsmanship speakerconf syndication tdd testing thoughtworks value web writing xtc
Powered by Blogger.