Console applications - whether part of a larger (Symfony-)application or standalone-tool - usually are the bash-script of PHP developers. Thereby one often leaves the path of clean code and hacks a very pragmatic solution. Despite the fact that a lot of these fast solutions remain in project and need to be maintained for longer.
Drupal + Technology
The Drupal + Tech track is about technology-focused topics not related to a specific industry and concerning exciting new developments in Drupal core and contrib. This includes Drupal-specific topics, such as core conversations and Drupal backend and frontend development; but, even more importantly, it will showcase examples of integrating Drupal with cutting-edge technologies. We expect talks from people interested in (integrating Drupal with) Blockchain, cryptographics, IoT, and other up-to-the-minute technologies.
Note: we expect to get a huge amount of submissions to this track. We think it will be much easier for your session to get accepted if you propose it to a specific industry track (Education, Healthcare, Government, etc).
- Core & contribution developers
- Backend & frontend Developers
- Drupal for ambitious digital experiences
- API-first initiative
- Hyperledger Commerce
- Drupal & Blockchain
- Using Nightwatch.js for core and contrib JS testing
- Out of the Box/media/workflows
Drupal core maintainer for the Out of the Box Initiative.
Together we'll go beyond learning how tools like PhpStorm can level up your developer-y super powers and demonstrate how your developer life can change if you maximize your use of these tools.
Elm is a language that compiles to JS, and has no run time exceptions. It's like Vue, React or Angular2, only completely different.
Composer is recommended to manage the code base for PHP projects, including Drupal. Learn the basics to get you started on the right track.
Come get an all access preview of how your next generation Drupal sites are going to work with Layout Builder.
Encryption in Drupal: How, What and Why data should be encrypted. And amongst all questions: is it really secure?
Whether you are a site-builder, an advanced developer or a new user... come and find out yourself!
Those teams working in an agile fashion will usually bring the tester in as early as possible in the development cycle — often during the planning stages — to find potential problems before they create work to fix. But checking for potential technical problems is only a small part of what the QA team can do in this stage.
So, you do code reviews, and that's great. But there's always more that you can check during the review. More places you can check for any potential bugs or problems before deployment, before you find yourself with technical debt. Or worse: unforeseen downtime.
Documentation: What it is, the types of documentation, how to do them well, and why "if it's self documenting it doesn't need comments" is a stupid statement.