<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>
<div>Hello MIT WebPub,</div>
<div><br>
</div>
<div>We hope you had an excellent holiday break and wish you a very Happy New Year! We will not meet next week, but on Friday, February 19th from 3:30p to 5p (*note we are meeting on Friday not on Wednesday), we will have three 30 minute talks by <a href="http://thephp.cc/welcome">thePHP.cc</a>:</div>
<div>
<p><strong>PHP 7, PHPUnit 5, and Beyond</strong> (Sebastian Bergmann)<br>
Every eight weeks a new version of PHPUnit that adds new functionality<br>
is released. These releases do not break backwards compatibility, making<br>
it easy for developers to update. The October 2015 release, PHPUnit 5.0,<br>
however, needs to break backwards compatibility to prepare PHPUnit for<br>
PHP 7. We will discuss how PHPUnit had to be adapted for PHP 7, how<br>
PHPUnit benefits from PHP 7, what additional changes PHPUnit 5 brings<br>
with it, and we’ll close with a look ahead to PHPUnit 6.<br>
<strong>Bio</strong>: <a href="http://thephp.cc/consultant/sebastian-bergmann">Sebastian Bergmann</a> has instrumentally contributed to tranforming PHP into a reliable platform for large-scale, critical projects. Enterprises and PHP developers around the world
benefit from the tools that he has developed and the experience he shares.</p>
<p><strong>The Five Rules of PHP Craftsmanship</strong> (Stefan Priebsch)<br>
PHP gives developers a great deal of freedom to achieve their goals. In<br>
larger-scale projects, PHP also provides you with a lot of rope to hang<br>
yourself with, and short cycles of rapid development can quickly turn<br>
into years of maintenance nightmare. We will discuss five rules that<br>
every PHP developer and aspiring craftsman should know and stick to.<br>
<strong>Bio</strong>: <a href="http://thephp.cc/consultant/stefan-priebsch">Stefan Priebsch</a> (@spriebsch) is a co-founder of The PHP Consulting Company (<a href="http://thephp.cc">http://thephp.cc</a>). As a consultant and coach, he helps teams to develop
software successfully. He is a university lecturer for web programming and author of several textbooks. Being father of four-year-old twins, he also is an established scalability expert.</p>
<p><strong>How to manage your project’s toolchain in 2016</strong> (Arne Blankerts)<br>
Today, dependency management in PHP projects is done via composer.<br>
While this makes perfect sense for libraries, managing the toolchain<br>
via composer will lead to the installation of all the dependencies of<br>
these tools. Not only is this slow, but it will also mix them with your<br>
project’s runtime libraries. And even though most tools are available<br>
as a fully self-contained and executable phar archive, installing and<br>
updating them manually is everything but fun. Time to change that.<br>
<strong>Bio</strong>: <a href="http://thephp.cc/consultant/arne-blankerts">Arne Blankerts</a> solves IT problems long before many companies realize that they even exist. He focuses on IT security, performance and reliability, which he attends to with almost
magical intuition creating solutions that clearly bear his hallmark. Companies around the world rely on his concepts and LINUX-based system architectures.</p>
<p><strong>NOTE</strong>: Attendees without a Harvard ID card need to <a href="mailto:dtremont@oeb.harvard.edu">RSVP</a> for building access.</p>
<p><strong>When</strong>: February 19th @ 3:30-5:00pm (*note, this is a Friday)<br>
<strong>Title</strong>: PHPUnit, PHP Craftsmanship, and managing the toolchain<br>
<strong>Who</strong>: Arne Blankerts, Sebastian Bergmann, and Stefan Priebsch of thePHP.cc<br>
<strong>Where</strong>: CGIS Building, 1737 Cambridge St. Room K354 (**note the change in venue)</p>
</div>
<div>Thanks!</div>
<div>Donna and Raman</div>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
</body>
</html>