Test Driven Development soll auch Spaß machen, dachte sich Jeff Welch und forderte vor ein paar Tagen auf Twitter: „Make your tests fabulous“. Da ich mich tags zuvor mit Unit Tests für JavaScript mittels Mocha und Jasmine beschäftigt hatte, musste ich einfach antworten:
"NyanCat-Reporter für PHPUnit" vollständig lesen@whatthejeff @s_bergmann @__edorian I demand a Mocha-like Nyancat reporter vimeo.com/44180900
— Matthias Gutjahr (@mattsches) February 14, 2013
At last week's Webmontag Frankfurt (?), Robert Reiz talked about continuous updating of dependencies with VersionEye. VersionEye, in its own words, is a
cross-platform search engine and crowdsourcing app for open source software libraries.
Essentially, the service tracks more than 170.000 libraries in languages like Java, Ruby, PHP, Python, and many more, and monitors any updates to those libs. Registered users can keep track of their projects and the libraries used in these projects. If any updates occur upstream, VersionEye sends out a mail. As a developer, you don't have to manually check on all the GitHub repositories anymore, VersionEye does that for you.
Source: versioneye.com via VersionEye on Pinterest
VersionEye also allows you to create beautiful graphs like this one here on the right. It also lists all the licenses of all the libraries used in your project, an let's you see which libraries you use most often.
Adding a PHP project to the service couldn't be simpler (if you use Composer, which you should!): Just upload your composer.json to VersionEye, and you're all set up. The same goes for project files like package.json (node.js), requirement.txt (Python Package Index), pom.xml (Maven) or Ruby Gemfiles. You can also connect VersionEye to your GitHub account, and it will notify you of outdated dependencies in your repositories.
Robert also said that there already is a VersionEye module for ZF2 and the ZendDeveloperTools that calls the VersionEye JSON API to track dependencies. However, I could not find a Symfony2 bundle with this functionality. So I wrote one.
"VersionEyeBundle for Symfony2" vollständig lesenEine gute Dokumentation ist wichtig für jedes Projekt, egal ob es sich dabei um ein von der Community entwickeltes Open Source-Tool handelt oder um eine für einen Kunden geschriebene Software. Eine API-Dokumentation erleichtert es Entwicklern, neu ins Projekt einzusteigen oder sich einen Überblick über alle relevanten Teile des Projekts zu verschaffen.
Ein weiterer Vorteil von API-Dokumentationen ist, dass sie sich schnell und automatisch generieren lassen. Dieser Schritt kann in den Build-Prozess integriert werden, so dass immer eine aktuelle, ggf. auch versionierte Dokumentation vorliegt. Sie sind sozusagen der leicht erfüllbare Mindeststandard für eine Dokumentation.
Denn, seien wir ehrlich, eine API-Dokumentation erklärt und veranschaulicht nicht (das machen Codebeispiele und handgeschriebene Dokumentationen), sondern ist eher eine Art Nachschlagewerk. Durch die immer besseren Funktionalitäten von IDEs verliert es sogar mittlerweile an Bedeutung. Ich persönlich schaue nur selten in einer API-Dokumentation nach, wenn ich das Projekt schon in meiner Entwicklungsumgebung vorliegen habe. Your mileage may vary 
Gestern durfte ich beim Stammtisch der Google Developer Group Rhein-Main einen Einführungs-Vortrag zu Ingress halten. Das Treffen fand im schönen neuen Frankfurter Coworking-Space Die Zentrale mitten in Bornheim statt.
Die Slides zu meinem Vortrag habe ich hier online gestellt. Vielen Dank an Jochen für die Einladung und an alle Teilnehmer fürs mitdiskutieren. Der Abend hat mir sehr viel Spaß gemacht!
I suppose this post has to be in English because the PHP Benelux Conference 2013 was an international conference with participants from 17 countries. It took place in Edegem near Antwerp last weekend. Friday and Saturday that is.
After four hours on the road, I arrived at the venue on Friday shortly after noon. The keynote by The Grumpy Programmer Chris Hartjes was scheduled for 13:20 so I had enough time to register and chat to some people. Most of them were from Belgium and the Netherlands, but I also met some German and Swiss guys there. The keynote was fun and addressed some important issues concerning software quality and security.
Next up was Igor Wieder's session on Silex Anatomy and Symfony Components, and it was a solid session although the focus was not on Silex so much, but on his microframework YOLO. Like Silex, it's based on the Symfony Components, but does some things differently.
I then skipped the next session slot and checked in at my hotel. Fortunately, I made it back in time for Kris Buytaert's session 7 tools for your DevOps stack. I really think DevOps is a great movement and would love to use more tools like those he talked about. But there's definitely a learning curve ...
Sadly, I missed the so-called "Social", the social event that evening, because I felt tired and slightly ill, so I preferred to go to bed early and collect my strength for ...
"My PHP Benelux 2013" vollständig lesen