things i learnt

• Things I Learnt The Hard Way - Don't Defend Bad Code
• Things I Learnt The Hard Way - Global Changes Must Be Discussed With The Whole Team First
• Things I Learnt The Hard Way - Be Transparent With The User
• Things I Learnt The Hard Way - One Version To Add, One Version To Remove
• Things I Learnt The Hard Way - Git-Flow Is The Way To Go
• Things I Learnt The Hard Way - Own Your Shit
• Things I Learnt The Hard Way - Gerrit Is A Mistake
• Things I Learnt The Hard Way - Nothing More Permanent Than A Temporary Solution
• Things I Learnt The Hard Way - You Always Have The Time
• Things I Learnt The Hard Way - Blogging About Your Stupid Solution Is Still Better Than Being Quiet
• Things I Learnt The Hard Way - ... Unless That Code Style Is The Google Code Style
• Things I Learnt The Hard Way - Don't Confuse Hero Project With Hero Syndrome
• Things I Learnt The Hard Way - Create Libraries
• Things I Learnt The Hard Way - Blogging About Your Stupid Solution Is Still Better Than Being Quiet
• Things I Learnt The Hard Way - Toxic/Aggressive People Are Not Fixable
• Things I Learnt The Hard Way - I.T. World Is Really Small
• Things I Learnt The Hard Way - Keep A List of Things I Don't Know
• Things I Learnt The Hard Way - Toxic/Aggressive People Are Not Fixable
• Things I Learnt The Hard Way - Beware of Microaggressions
• Things I Learnt The Hard Way - Beware of Toxic People
• Things I Learnt The Hard Way - You'll Learn About Yourself The Hard Way
• Things I Learnt The Hard Way - People Get Upset About Code And Architecture Quality 'Cause They Care
• Things I Learnt The Hard Way - Pay Attention On How People React To You
• Things I Learnt The Hard Way - Code of Conduct Protect YOU, Not THEM
• Things I Learnt The Hard Way - Don't Tell It's Done When It's Not
• Things I Learnt The Hard Way - Take Responsibility For The Use Of Your Code
• Things I Learnt The Hard Way - If It Doesn't Run On Your Computer, You Have A Problem
• Things I Learnt The Hard Way - Learn To Say No
• Things I Learnt The Hard Way - When It's Time to Stop, It's Time To Stop
• Things I Learnt The Hard Way - Companies Look For Specialists But Keep Generalists Longer
• Things I Learnt The Hard Way - Keep A List of Stupid Bugs That Took More Than 1 Hour To Solve
• Things I Learnt The Hard Way - Units Makes Things Clear
• Things I Learnt The Hard Way - Think About The Users
• Things I Learnt The Hard Way - Code Formatting Tools Are Ok, But No Silver Bullet
• Things I Learnt The Hard Way - Code Reviews Are Not For Style
• Things I Learnt The Hard Way - Code Style: Follow It
• Things I Learnt The Hard Way - ... Unless That Code Style Is The Google Code Style
• Things I Learnt The Hard Way - Even for Application Composition, Start Stupid
• Things I Learnt The Hard Way - Not Just Function Composition, But Application Composition
• Things I Learnt The Hard Way - Command Line Options Are Weird, But Helpful
• Things I Learnt The Hard Way - The Config File Is Friend
• Things I Learnt The Hard Way - Create Libraries
• Things I Learnt The Hard Way - Logs Are For Events, Not User Interface
• Things I Learnt The Hard Way - Optimization Is For Compilers
• Things I Learnt The Hard Way - Organize Your Code by Data/Type, Not Functionality
• Things I Learnt The Hard Way - One Commit Per Change
• Things I Learnt The Hard Way - Always Use A Version Control System
• Things I Learnt The Hard Way - Debuggers Are Overrated
• Things I Learnt The Hard Way - Shortcuts Are nice, But Only In The Short Run
• Things I Learnt The Hard Way - Logs Are For Events, Not User Interface
• Things I Learnt The Hard Way - Resist The Temptation Of Easy
• Things I Learnt The Hard Way - Start Stupid
• Things I Learnt The Hard Way - Always Use Timezones With Your Dates
• Things I Learnt The Hard Way - Always Use UTF-8 For Your Strings
• Things I Learnt The Hard Way - Cognitive Cost Is The Readability Killer
• Things I Learnt The Hard Way - Thinking Data Flow Beats Patterns
• Things I Learnt The Hard Way - Learn The Basics of Functional Programming
• Things I Learnt The Hard Way - The Magical Number Seven, Plus Or Minus Two
• Things I Learnt The Hard Way - Understand And Stay Away From Cargo Cult
• Things I Learnt The Hard Way - Don't Mess With Things Outside Your Project
• Things I Learnt The Hard Way - Design Patters Are Used to Name Solution, Not Find Them
• Things I Learnt The Hard Way - "Right Tool For The Job" Is Just To Push An Agenda
• Things I Learnt The Hard Way - The Right Tool Is More Obvious Than You Think
• Things I Learnt The Hard Way - If Your Data Has a Schema, Use a Structure
• Things I Learnt The Hard Way - It's Better To Let The Application Crash Than Do Nothing
• Things I Learnt The Hard Way - Types Say What You Data Is
• Things I Learnt The Hard Way - If You Know How To Handle It, Handle It
• Things I Learnt The Hard Way - A Language Is Much More Than A Language
• Things I Learnt The Hard Way - Don't Use Booleans As Parameters
• Things I Learnt The Hard Way - If A Function Description Includes An "And", It's Wrong
• Things I Learnt The Hard Way - Beware of Interface Changes
• Things I Learnt The Hard Way - Good Languages Come With Integrated Documentation
• Things I Learnt The Hard Way - The Function Documentation Is Its Contract
• Things I Learnt The Hard Way - Documentation Is a Love Letter To Your Future Self
• Things I Learnt The Hard Way - Future Thinking is Future Trashing
• Things I Learnt The Hard Way - Testing Every Function Creates Dead Code
• Things I Learnt The Hard Way - Good Languages Come With Tests
• Things I Learnt The Hard Way - Disclaimer
• Things I Learnt The Hard Way - Gherkin Is Your Friend to Understand Expectations
• Things I Learnt The Hard Way - Unit Tests Are Good, Integration Tests Are Gooder
• Things I Learnt The Hard Way - Tests Make Better APIs
• Things I Learnt The Hard Way - Make Tests That You Know How To Run on the Command line
• Things I Learnt The Hard Way - Be Ready To Throw Your Code Away
• Things I Learnt The Hard Way - Intro
• Things I Learnt The Hard Way - Spec First, Then Code
• Things I Learnt The Hard Way - Write Steps as Comments