La vérité sur le chiffrage en Sociétés de Services en Logiciels Libres : “Nous aimons coder. Coder ne nous coûte pas car c’est notre plaisir. D’ailleurs, nous codons gratuitement une bonne partie de notre temps (dans le cadre de nos contributions open sources). Le reste de notre travail, en revanche, nous coûte.”
Stop Using Story Points : ”Like researchers of fast food, we now know that the Agile Happy Meal contains unnatural ingredients that decrease agility and cause process indigestion.”
What’s my IT strategy? : “Take a company’s IT strategy [...] Now remove XXX [...] What is left, is the IT strategy”
Java feature applicatbility : “I group Java features in three categories: day to day, occasionally and never (frameworks and libraries only). The rule is simple: if you find yourself using given feature more often then suggested, you are probably over-engineering”
The Most Important Question : “Everything involves trade-offs, where benefits must be weighed against their associated costs. Evaluating those trade-offs and choosing according to the needs of the customer is a key responsibility of an architect.”
Learnable programming : “A programming system has two parts. The environment is installed in on the computer, and the language is installed in the programmer’s head.”
Some things I’ve learnt about programming: ”When writing code it’s sometimes tempting to try stuff to see what works and get a program working without truly understanding what’s happening.”
Dear “API providers”: “I just want the data on your website in a machine readable format. XML, JSON, RDF, CSV, YAML, I don’t particularly give a fuck.”
OAuth 2.0 and the Road to Hell: “At the core of the problem is the strong and unbridgeable conflict between the web and the enterprise worlds”
Agile France : Le combat des chefs : avec Bougetépostix et Testotomatix… tout un programme.
Le changement, c’est (bientôt) maintenant: “nos organisations privées ou publiques, notamment tertiaires, sont orientées vers leur maintien, plus que vers le service à leurs usagers”
“When I give a talk, I do stuff that I’m interacting with on-the-fly. Because that is what the computer is for. People who don’t do that either don’t understand that or don’t respect it.”
The care and feeding of software engineers (or, why engineers are grumpy) : That’s really what drives software engineers more than anything else: the idea that people we don’t even know will be affected by our work.
Top 10 Things Every Software Engineer Should Know:
- 1) Fundamentals of Emotional Intelligence
- 2) Understand the Business of your Customer
- 3) Minimum One Programming Language for each Mainstream Development Paradigm
- 4) Know your Tools
- 5) Standard Data Structures, Algorithms and Big-O-Notation
- 6) Don’t Trust Code without Adequate Test
- 7) Basics of Project Management, Lean Management and Agile Concepts
- 8) Key Metrics of Software Development
- 9) The Root Cause of the Last Defect
- 10) Understand the Infrastructure
: if you’re going to dump on something in the way many people do about ORMs, you have to state the alternative. What do you do instead of an ORM?
: The database is just a detail that you don’t need to figure out right away.