Archive

• Bad modules, good modulesMay 30, 2024
• How to write testsApril 29, 2024
• Tests should give confidenceMarch 20, 2024
• The simplest dependency injectionFebruary 19, 2024
• Don’t automate everything. Go Elon instead.January 11, 2024
• Unit tests can (and should!) go through many classesNovember 23, 2023
• Making sense is overratedApril 18, 2023
• Consistency in Programming – 10 Symptoms [CliftonStrengths #5]March 6, 2023
• Ideation in Programming – 10 Symptoms [CliftonStrengths #4]February 27, 2023
• Developer in Programming – 10 Symptoms [CliftonStrengths #3]February 20, 2023
• Individualization in Programming – 10 Symptoms [CliftonStrengths #2]February 6, 2023
• Responsibility in Programming – 10 Symptoms [CliftonStrengths #1]January 27, 2023
• 6 lessons from the first project in UnityDecember 17, 2022
• 🎉 Puzzle Balls Release 🎉December 9, 2022
• Let’s make a project – part 3, first artifact 🎉September 29, 2022
• Let’s Make a Project – part 2, not deadAugust 17, 2022
• Let’s Make a Project – part 1, basicsJune 22, 2022
• Communication benchmark – number of questionsJune 9, 2022
• 7 reasons not to write testsApril 1, 2021
• Send that linkMarch 24, 2021
• Swimming 2020January 13, 2021
• 7 reasons why I’m skeptical about TypeScriptAugust 6, 2020
• Swimming 2019January 6, 2020
• “Automate everything” is a scamDecember 12, 2019
• The pyramid of software development principlesOctober 21, 2019
• YAGNI vs good designAugust 19, 2019
• 9 ideas on how to improve visibility in your projectJune 17, 2019
• How to communicate in IT: Extreme VisibilityApril 17, 2019
• 10 more communication quick wins for developersMarch 25, 2019
• Why are there no full stack mobile devs?February 25, 2019
• Manage complexity bottom-upFebruary 9, 2019
• Swimming – revisitedJanuary 3, 2019
• Kick-off – dev-related topics to coverDecember 28, 2018
• Styling <br> tag – 2 casesNovember 26, 2018
• 5 Things I Used To Get Wrong About TDDOctober 19, 2018
• Why I Like American FootballOctober 11, 2018
• YAGNI is KingSeptember 3, 2018
• My Habits as a ProgrammerAugust 6, 2018
• Don’t Test DataJuly 17, 2018
• Don’t Test ImplementationJune 29, 2018
• Two Faces of Just-in-Time LearningJune 8, 2018
• Responding to code review – Getting Remarks AppliedMay 16, 2018
• Boolean arguments in Ruby vs clean codeApril 26, 2018
• My Ruby progress in 13 monthsApril 11, 2018
• The missing piece of (almost) every code reviewMarch 31, 2018
• Why I don’t like working remotelyMarch 15, 2018
• Uncle Bartek’s attitude towards code comments (+ examples)March 5, 2018
• 10 communication quick wins for developersFebruary 5, 2018
• 8 reasons why I love swimmingJanuary 25, 2018