Blog posts

    What new programming languages should you add to your “repertoire”? What new tools should you consider including in your toolbox? Are there any special soft skills that you should develop or further “polish”? And what bachelor's degree should you have? In short: "How do you become an automation engineer?" That is the question... A very legitimate one, if you think that: Companies in all industries are implementing automation. From streamlining their software development processes to automating their business processes, they all have one major “need” in common: the need for...
    Faster project starts, faster development cycle, faster (and reliable) delivery, enhanced scalability and security, higher quality, better collaboration, happier clients... And the list of benefits that you can “reap” from implementing a Drupal 8 DevOps-based workflow is an endless one. And best of all: these benefits are no longer restricted to certain... scenarios. For, let's face it: The old constraints — that you should have an enterprise-sized team (or a dedicated DevOps team) worth the financial effort or a significant project budget — don't stand anymore.
    Rebuild or refactor? Should you refactor an existing project and keep improving it or just... rebuild the whole codebase from the ground up? That is the question. Now, let me take a "lucky guess" and assume that: you're facing the challenge of working with legacy code, the app in question has poorly written code, is unscalable and takes up a lot of memory, it's a buggy app, with lots of architecture and design issues, its current features and functionality are rudimentary and/or no longer relevant. So, what should you do now?
    How do you scale agile software development from a small team across... multiple teams? From a small-scale project to an enterprise-sized one? You implement one of those powerful enterprise agile frameworks gaining traction these days, right? “OK, but which one?” And how do you choose that specific one? What should you base your selection on? Which scaling approach best suits your: organizational structure, team size, business processes, project particularities and...
    Decided to dive into deep learning? Maybe you're thinking about developing your own face detection algorithm? Or one for... recommending certain products in your online store. Or maybe your own text classification model? The question that you might be struggling with right now must be: "Which is the best deep learning framework for my DL project, for the particular challenges that I'm facing?" What should you base your final choice on? On ease of use or maybe...
    Why not automating all those tasks that go into the Drupal deployment workflow by applying proven coding techniques to the way you set up and organize your infrastructure? Now, just think of the convenience of having a tool that would just turn APIs into declarative configuration files that your team could easily: share, edit, version, review. An IaC tool that would automate all those tasks included in your workflow. One that usually calls for "joggling” with multiple environment and synchronizing code or configuration changes between them: apply a specific modification on...
    What does it take to build an effective Drupal team? What are the main characteristics of high-performing, successful teams working on large-scale Drupal projects? How do you scale your small team to accommodate the needs and requirements of more complex, custom Drupal projects? Is it really just a matter of... numbers? Is it as simple as having more people with the same Drupal-specific roles (site builder, Drupal architect, back-end developer, themers etc.) in your team? Or is it more about thoughtful planning? About attracting the right talents...
    "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.