Blog posts

    "I hate Scrum (meetings)!" "Scrum doesn't work." "The Daily Scrum Meetings Are Talking Too Long". I bet you're all too familiar with these complaints about Scrum and overall about the Agile approach to software development. But a scrum meeting shouldn't take more than 15 minutes. And yet they do... Therefore, these meetings have slowly turned: into one of the most dreaded times of the day for your development team, into some true productivity suckers...
    And this is your chance to shine in the open-source world! For, even though everybody agrees that poorly-written documentation is still a “popular” issue on Github, very few maintainers put the effort needed to write user-friendly, well-documented docs for their open source projects. In this respect, here's a guide for you on how to write great open source documentation: But does that even exist? A great open source documentation, I mean...
    Is it a coder or a software developer that you need to add to your team? How can you tell? What is the difference between a developer and a coder (if there is one at all)? What distinguishing characteristics can you use for telling the difference between a coder and a software developer? Distinguishing “marks”  that would also point out to you the role that you need to hire for... Let me give you some clues here: A coder is someone who... writes code, right? Some who masters the “art of writing code”, we might say, and thus counterbalance the pejorative meaning that this term has unjustly acquired.
    It's no groundbreaking news for anyone anymore: Drupal 8's database agnostic and it comes with a drastically improved core entity API. This allows it to interact with remote data stored in pretty much any type of external database. In this respect, there's a whole array of contributed modules that you can use for retrieving and integrating external content into your Drupal website. Now the new challenge that arises is: what if you wanted to display that external data as... Drupal entities? And this is precisely where the Drupal 8 External Entities module steps in!
    What is the discovery phase of a project? What happens during this process? And is it really essential for your software product's development process? In other words: what if you just skipped it? What then? Do you really need to collect, “weigh” and evaluate all that information way in advance? Way before actually launching your product? Couldn't you just go... agile and adjust to changes of scope and requirements along the way? Now, let's shed some light on this still too vague, too often misinterpreted expression: The "discovery phase" in a software product's development cycle.
    It better be "overloaded" with irresistible benefits for you to invest X hours of your (too) valuable time in learning yet a new programming language, right? It better have: clean code, a crystal-clear syntax, an unexpectedly simple design pattern... But these are all terms already describing the Elm architecture itself! The famous Elm architecture! One of the most compelling reasons why so many developers have found themselves  "enamored" with this functional programming language. So, instead of being hesitant to learn Elm for... no specific reason...
    A painless, budget-friendly and fast Drupal 7 to Drupal 8 migration process... “Is this a joke or what?” you might ask yourself. Not at all: you can always migrate to Drupal 8 using Docker to accelerate the whole process. Just think about it: you'd have a whole ecosystem of  Docker images ready to be moved over to your new Drupal 8 site. Docker images for Drupal which would automatically: minimize all the issues that occur (and they always do) during migration, streamline the content transfer, cut down on the usual costs involved in a Drupal migration process...
    If only working with PDFs in Drupal 8 was as easy as handling images in media libraries... Now, who's with me for a "PDFs in Drupal core" initiative? No need to "despair", though: if you need to generate and handle PDF files on your Drupal 8 website, you still have a handful of tools (meaning useful PDF Drupal modules), Composer and PDF generating libraries at hand. Inspired by an older Drupalcon session on "PDFs in Drupal" and Mediacurrent's synthesizing blog post on this topic, I've decided to put together some sort of compilation of the best available tools.
    You don't need to be a giant in the IT industry to be “toying” with the idea of automating your business processes. In the name of boosted productivity, efficiency and saving resources, that you could invest in... innovation instead. The IT leaders of the future work ON and not IN their businesses. They channel their resources on the big-picture tasks, not get tangled up in routine operations.To help you get to a grip with automation, I've selected 7 best automation ideas for an IT company “divulged” by some of the world's leading entrepreneurs. “Ideas” of building a custom...
    In other words: while working on a project, keep in mind the actual Drupal admin user, as well! Don't focus exclusively on building the end user's experience! Creating a great Drupal admin user experience for your client's IT staff is equally crucial, you know. For you can't just hand over the Drupal project to your client along with a long list of instructions for his/her site administrators to work it out... somehow, thinking that: “These are trained folks, they'd just... learn it”. Instead, do invest the same resources to meticulously plan and to build the user experience of...