The Daily Drupaler
This is an archive of the 811 email messages I have sent to my daily mailing list since the 12th of August, 2022. Enjoy!
- 19th May 2023: Semantic versioning
- 18th May 2023: Why is backward compatibility important?
- 17th May 2023: What is deprecated code?
- 16th May 2023: Mastering your tools improves productivity
- 15th May 2023: Is the Drupal release cycle too fast?
- 14th May 2023: Releasing small changes often is less risky
- 13th May 2023: When You Do Things Right, People Won't Be Sure You've Done Anything at All
- 12th May 2023: Always listen to the mob
- 11th May 2023: Why I like pair and mob programming
- 10th May 2023: Tailwind CSS makes change easier
- 9th May 2023: The single responsibility principle
- 8th May 2023: Only write enough code to get a failing test
- 7th May 2023: You don't need to think about what to do next
- 6th May 2023: Why it's important to see the test fail
- 5th May 2023: Getting to green
- 4th May 2023: Speaking at the Symfony UK meetup in London
- 3rd May 2023: Just because core is supported...
- 2nd May 2023: Does it depend on who you ask?
- 1st May 2023: Should Drupal 7 support be extended again?
- 30th April 2023: Will we see Drupal 7.100?
- 27th April 2023: Write the test backwards
- 26th April 2023: Structure a new test by writing comments first
- 25th April 2023: Shortening the feedback loop even more
- 24th April 2023: CI pipelines should start locally
- 23rd April 2023: Laravel Pipelines
- 22nd April 2023: Configuration files as a service
- 21st April 2023: Making my Drupal module template Drupal 10 compatible
- 20th April 2023: Micro-refactorings
- 19th April 2023: Camel-case or snake-case for Drupal code?
- 18th April 2023: Consistency is key
