
As part of my Let’s Invest in Ourselves For 2017 post I said I wanted to read Clean Code: A Handbook of Agile Software Craftsmanship by Robert Martin. I had a hard time writing a post about what I learned in that book because it’s mostly just a laundry list of things you should (or shouldn’t) do in order to create easier to read code. I’m rereading it with the other programmers at work (at my suggestion) and I realized that there were a lot of things that I’m still not doing that could improve the quality of my code.
To that end I’ve started a new process. Every Friday, I’m going to pick 5 items from the book and place them on my monitor. Before I make a commit, I’m going to review all my changes and make sure any new code fits those items. The idea is that instead of trying to focus on 100 items all at once I’ll focus on 5 and then
I’m also posting these to Twitter with the hashtag #ImplementingCleanCode.

Nic discussed why it’s important for all software but especially open source to be accessible for all users regardless of how they’re accessing your site.
Read More

Jessica talked about what annotations are and how to convert those into estimates. Her talk revolved around a waterfall approach but I could see how you could integrate it into an Agile process.
Read More
Terry gave an overview of Virtual Machines (VM), Serverless options, and Containers. He also did some demos to show them off.
Read More
Gabriela went over several of the new features in MySQL 5.7 and discussed the fact that 5.7 has a more strict set of settings to make sure you get the correct results.
Read More
Michael gave us an overview of the different Amazon Web Services (AWS) and walked through what you would need in order to get a PHP site up and running with a database, load balancing, fault tolerance, high availability, security, and performance. He slowly built up a crazy diagram of everything needed for this process.
Read More
Beau went over why Symfony Flex exists and what it’s good for. He also went over some basic steps and how to get started with a basic application.

Tessa went over why you need continuous integration & deployment and very basically how to do it. The basic take away is that when you have a larger team having automated tests and deployment can save a lot of work
Read More
Chris explained why we should be using scripting to automate tasks and then when into why to use BASH and some basic examples.
Read Moresubscribe via RSS