For many years, pretty much my whole professional career, I’ve worked at many organisations and companies. And in all of them, I tried to take a fun, side job, challenge, of promoting Drupal, be it inside or outside of said organisations. Because it was a fun thing to do, because I believe in Open Source, and because it was the right thing to do.
Drupalcon Pittsburgh is just around the corner, and if you are still thinking “what’s in it for me”, maybe this is not the event for you. I’ll make it easier for you, here you’ll find some reasons why you “should not attend Drupalcon Pittsburgh”.
Visual Regression testing: a different approach with GlitcherBot
Last night I got invited at Drupal Yorkshire to talk about my article regarding improving developer experience. You can see the original article here: Speed up your local development.
There is an on going issue for Layout Builder which aims to expose the overridden layout of a given node. However to expose the default layout if a node is not overriding the default layout is a bit trickier.
Truth is, the low code phenomenon is here to stay. But that’s just half a truth. The other truth is, low code is nothing new, neither has not the potential to change the software industry. It has ALREADY shaped the software industry from its very beginnings.
Who am I going to lie, I am a big fan, you know that already DDEV ;-).
We all know that setting up a Drupal site (or Wordpress, laravel, typo, magento, ...) is just a breeze with DDEV. However sometimes you need something even quicker, like just a database and PHP.
(and don't break the bank while doing it)
After the frustration of watching how 16GB in an expensive MacBook Pro was not enough to power the tools I use for my local development I decided to buy a cheap old Workstation in Ebay (around 100£) and I set it up to be synced with my Mac as a local development tool.
Learn how I did it and how you can benefit of that as well for a happier, more productive developer life.
I've been looking for some good book and reading recommendations for someone trying to break into a devrel or developer relations role
So far this is what I've read or nearly finished reading and I've enjoyed:
First two obvious (at least because of the title itself, direct to the point, but the contents are really good):
What is a Developer advocate anyway?