Last Friday I attended the DomCode conference in Utrecht. This is a very friendly, inclusive, welcoming conference. Organisers Aisha Sie, Lucas van Lierop, Ross Tuck and their extensive team of volunteers did a wonderful job at fixing all the big - and small - stuff. They succeeded in attracting ~275 people to come to the capital of our province, Utrecht, where coincidentally one of the Ibuildings offices is located too. In fact, Lucas van Lierop is one our employees, and Ross Tuck has been one in the past. So it only made sense for me and several others of the Utrecht team to attend the conference, and even help out during the day.
Bamboo and BitBucket are both Atlassian products. They work together nicely and you don't have a lot of configuration to do, so they’re perfect for a lot of developers. For developers using the Gitflow workflow, things can be better though. One of the most controversial features is pull request building, which Bamboo doesn’t offer out of the box. CI tools like Travis offer integration for gitflow right away, including pull request building. But what if you want to stick with the Atlassian suite for all your tasks? How can we build pull requests and show their status in BitBucket?
In previous articles we answered some important questions already: why would you write tests in the first place? And, will it make you faster or slower?
Now we need to answer one other important question that should guide you in your daily quest to improve the quality of the code you deliver: when should you write a test?
In a previous article we answered the question "why you would write tests", or specifications for your software project. In this article we'll discuss costs and benefits of writing tests.
The world of "software testing" is quite a confusing one and it takes several years to understand what's going on and how to do things "right". In no particular order:
Developers use different words for different types of tests, but also for different types of test doubles.
Developers are looking to achieve widely varying goals by writing tests.
Developers have divergent views on the cost of writing and maintaining a test suite.
Developers don't agree on when to test software (before, during, after writing the code).
Last week I took part in the first ever Symfony Catalunya conference. The conference was a major event in Barcelona, attracting 400+ Symfony developers. It seems that most of the attendees were from Spain or Catalunya. I was surprised to see that some Dutch people were present too!
At Ibuildings we had been anticipating DPC 2016 for quite some time. Our internal DPC crew rebooted in January, starting with an update of the website and a mailing to announce that the Call for Papers was open again. We received about 350 proposals, which we narrowed down to 55 talks and 11 tutorials. It seems we made a good selection of talks, since many people complained that it was hard to pick the right talk to watch, given there are 5 parallel talks at any time...
Last week I've been attending, and speaking at, the NCrafts conference in Paris. It was a great conference, which had many talks to offer on wide-ranging topics that should make any software craftsman/craftswomen quite happy. Below you will find some remarks, summaries, notes, etc. related to the talks I visited on the first day of the conference.
As you may know, this year's Dutch PHP Conference will again take place in Amsterdam in a well-known convention centre called "RAI". At the end of the Tutorial Day we will head back to the centre of town for the second edition of the Code Night...
A while ago, somebody asked me for some reading material on JavaScript best practices. This was the moment I realized that Douglas Crockford's JavaScript: The Good Parts is actually outdated.
Last time I blogged about DPC, we were still waiting for some speakers to confirm their presence. Now I can tell you that the schedule is complete (with some of the more recent additions: Sara Goleman with talks on HHVM extensions and types, and Christopher Pitt on functional programming and automation). Don't forget to buy your tickets - Early Bird prices are available until April 22nd!
Now it's time to shine a bit more light on the tutorial day, right before the main conference days (on June 23rd). We have made quite a broad selection of topics:
Do you want your websites users to log in? For certain types you would, but often there is no need. The Ibuildings website does not allow you to register an account and log in. Why would it?
However by default Drupal 8 (and earlier) considers logging in on /user part of the frontend theme. This means that either you have to theme it or accept a horribly broken login page.
Or you could convince Drupal to apply the admin theme to user pages.
A couple of weeks ago we announced the schedule for the Dutch PHP Conference. I already mentioned that we have a great selection of experienced speakers as well as many speakers who are less familiar with the conference stage but are eager (and ready) to take it. At the main conference days we have 5 tracks packed with interesting talks. At the beginning of the first day and at the end of the second day we'll have a keynote. Let me briefly introduce the keynote speakers to you now!
It's been a great honor to receive a total of 350 talk and tutorial proposals for the 10th edition of our annual Dutch PHP Conference. Proposals covered a wide range of topics. Many talk proposals had been submitted by experienced speakers, some by absolute beginners. A number of speakers seems to have proven their skills at local meetups and are now ready to take the stage on a conference like DPC, where there might be a 100 or up to 220 people listening to you.
This is the first blog post in what will hopefully become a new series where we look at old Drupal 7 & 8 security advisories (at least 3 months ago so they should be patched everywhere) and try to learn from the mistakes of others.
As a first post I'd like to pick an older vulnerability, one I've used in presentations to demonstrate how hard it can be to properly apply HTML encoding for Drupal.
If you want to know what JavaScript really is, you have to look beyond just the language. In contrast to PHP, there are several platforms that it runs on. And then there’s the ecosystem, which is nothing like the one PHP has.
