Blog posts

    With Nightwatch in Drupal 8 for some time now, have you managed to integrate it into your CI workflow? Are you leveraging it to its full potential? Now just yet? Even though you're so relieved (like I am) that the days when PHPunit was the only option for browser testing in Drupal are over... Well then, time to get familiar with this JS tool for writing browser tests now included in Drupal core. In this respect, here's an overview of: the most attractive benefits for using a JavaScript tool to test the JavaScript functionality of your Drupal website
    Is it time yet? Time to move from a project-based to a product-based model? From an operations-based approach, focused on project delivery, to one focused on... product delivery instead? Why would you? What would be the main benefits? Why not just stick to a project-based structure? What are its limitations? And, most of all: what are the challenges to expect when taking the leap to this new organizational setup? Here are some possible answers to most of your questions. But first: what's a product based company? Salesforce, Adobe, Microsoft...
    “Drupal 9 is Drupal 8 “stripped off” all deprecated functionality, with all its dependencies upgraded.” “It's actually no bigger deal than a new Drupal 8 minor release.” “Or: Drupal 9 is just a... small update to Drupal 8.” You must have already read all these reassuring posts on the release of Drupal 9, so you can't help wondering: can we even talk about a Drupal 9 vs Drupal 8 comparison? Are there any new features in Drupal 9? Any new major differences at all, between these 2 major releases? If not, why bother releasing a major version at all?
    Too bad that you're not writing code by yourself and for your own pleasure, right? Instead, you're part of a team (in most cases) and you develop software products for clients... So, growing and constantly nourishing your communication skills as a software developer becomes critical. And I've just managed to “bust two myths” in one shot: that being a good communicator is some sort of innate talent; it's NOT, it's a perfectly "trainable" skill that you can "seed" and "water" on a daily basis, that brilliant programmers are self-sufficient; in fact, you can perfectly “sabotage” your whole work
    Considering that static site generators have been a thing for... almost forever. Is JAMStack just a “newish” label stuck to an age-old web development concept/set of tools? Or is it (much) more than that? What is JAMstack, more precisely? And why would you even consider it for your next project? What's the “revolutionary” concept behind the JAMstack architecture? What sets it apart from other architectures? Apart from any other JavaScript SPA & RESP API kind of setups... What are the clear benefits for using this newly born “star” on the static site generator scene?
    How do you deal with on-demand tasks when working on a website/mobile app development project? And what about last-minute changes coming from your clients? How should you manage feature requests so that you maintain the balance between keeping your clients happy and avoiding scope creep? How should your feature request workflow look like: what collaboration tool or project management app to use for keeping a close track of all these requests? what agile strategies for handling bugs and feature requests should you implement from the get-go?
    In other words: do these 2 command-line tools (still) compliment each other? Can you run them together? And, if not, which one of them should you favor in a Drupal Console vs Drush "debate”When would you choose one over the other? And what would you base your choice on? What are their most powerful commands? Those that would eventually help you choose the best CLI for you? On one hand, you have good old Drush, with its familiar commands speeding up the most common Drupal development tasks. And on the other hand, you have Drupal Console...
    For the old question “(Why) Should I digitally reinvent my business?" has been replaced by: “How can I step up my digital transformation game?” Given the well-known “brakes” — skills shortages and the inconveniences of the traditional hand-coding development tools — you legitimately ask yourself: "How can I streamline my core operations to deliver stellar customer experience... at a low cost?” By exploiting the capabilities of a low-code development platform, that's how! Therefore, here are 3 major impacts that low code development has on your business' digital reinvention...
    2 of the best Node.js web frameworks, each one with its own philosophy, load of clear benefits and set of drawbacks. So, how would the results of a Koa vs Express comparison look like? How are they different when it comes to the middleware implementation approach? What are the obvious benefits of using Koa over Express? And what project requirements would make Express a better candidate? Let's dig into the 2 piles of framework-specific features, advantages, limitations, and use cases and dig out the arguments to base your final choice on:
    Everyone is talking about automation these days. We automate application deployment, code testing, Analytics reports, bulk image optimization, server builds... Up to the point where we run the risk of... over-automating our business processes. The critical point where our small business automation strategies become first ineffective, then even dangerous. When, instead of “reaping” those results that we've set up our workflow automation in the first place: to free our staff from “mundane” tasks so they can focus on higher-value processes, to cut down costs, to reduce the risk of human error