The Daily Drupaler
This is an archive of the 810 email messages I have sent to my daily mailing list since the 12th of August, 2022. Enjoy!
- 13th February 2024: It takes the drama out of open-source
- 12th February 2024: Symfony conventions making their way to Drupal
- 11th February 2024: Twig, Symfony and SymfonyCasts with Ryan Weaver
- 10th February 2024: Do you really need it?
- 9th February 2024: Defining boundaries between custom Drupal modules
- 8th February 2024: Experimenting with Architectural Testing
- 7th February 2024: Running tests in parallel with Paratest
- 6th February 2024: Tim Lehnen and the Drupal Association
- 5th February 2024: .gitignore or .gitallow
- 4th February 2024: Speaking about Sculpin at PHPSW
- 3rd February 2024: Reducing complexity makes contribution easier
- 2nd February 2024: Automated tests prevent you from adding regressions
- 1st February 2024: Start with a failing test
- 31st January 2024: Automated tests mean you can make changes quicker
- 30th January 2024: TDD doesn't mean you know everything upfront
- 29th January 2024: Violinist and automation with Eirik Morland
- 28th January 2024: Ignoring things globally
- 27th January 2024: gitignore - inclusive or exclusive?
- 26th January 2024: Write once, manage forever
- 25th January 2024: Speaking at PHP Oxford
- 24th January 2024: Defining Ubiquitous language
- 23rd January 2024: Why use automation tools for dependency updates
- 22nd January 2024: Tailwind CSS workshop recording
- 21st January 2024: Where is the value in your application?
- 20th January 2024: PHPUnit or Pest?
- 19th January 2024: Tests can assert multiple things
- 18th January 2024: Is zero unlimited?
- 17th January 2024: Please don't use short variable names
- 16th January 2024: Daily or quarterly?
- 15th January 2024: Don't be perfect, be useful
