The Daily Drupaler
This is an archive of the 809 email messages I have sent to my daily mailing list since the 12th of August, 2022. Enjoy!
- 10th March 2025: Contrib-first doesn't mean building for every use case
- 9th March 2025: Submit your session proposal for DrupalCon Europe
- 8th March 2025: CSS variables everywhere
- 7th March 2025: Rebase and reorder
- 5th March 2025: Feature branching slows delivery
- 3rd March 2025: How much would it cost to build Drupal?
- 1st March 2025: Solve one problem at a time
- 28th February 2025: Do we still need CSS preprocessors?
- 27th February 2025: Smaller modules are more reusable
- 26th February 2025: Don't create test.php files
- 25th February 2025: What would a suckless version of Drupal look like?
- 24th February 2025: To patch or not to patch
- 23rd February 2025: Tests aren't a line item
- 22nd February 2025: Speaking at PHP Thames Valley
- 21st February 2025: More code, more problems
- 20th February 2025: Don't branch, use feature toggles
- 19th February 2025: Roll back or fix forward?
- 18th February 2025: Feature branches cause merge conflicts
- 17th February 2025: What are CI and CD?
- 16th February 2025: Don't pre-optimise
- 15th February 2025: Rebuilding Bootstrap with Tailwind CSS (and Sculpin)
- 14th February 2025: Drupalisms and de-jargoning Drupal
- 13th February 2025: Using readonly in PHP
- 12th February 2025: Small and fast
- 11th February 2025: Tidy then push
- 10th February 2025: Refactoring and Test-Driven Development
- 9th February 2025: Simpler code doesn't mean less code
- 8th February 2025: Writing more tests than production code
- 7th February 2025: Having less code than you started with
- 6th February 2025: How I work around legacy code
