9 posts tagged with "code"

Code review is the process of having others review code that is written and accepting feedback and adapting the code to the feedback given. These days code review is seemingly at every IT department and widely ruled agreed upon as a best practice. It is often one of the largest sources of conflicts within a development team since giving and receiving criticism about work is often hard to do while remaining detached from the work itself. After several years of code review in several teams, I've noticed somethings that work and something that don't, as well as, things that are often touted about code review which I don't think are quite true by default. Here I'll try and share what I currently think about code review.

Estimations are one of the most important parts of project planning and one of the most common tasks that developers do no matter which language they code in, what team they are on, or which company they work for. Estimating is hard, so hard we pretty much get it wrong a lot of the time.

PHP Conferences are a lot of fun to attend, they're a great way to get to meet people who work in the industry and chat about all sorts of things. I've noticed a lack of a single place to find PHP Conferences so I decided to create this list.

Some of these have already happened but I figure it would be good to know what has happened to be able to start thinking about next year and following their accounts or signing up for their newsletters.

Building an admin system is a requirement for most plans. But since it's not customer-facing it's not of much importance and the actions are often less complex than the customer-facing system. Often the best way to build your admin system is to use a bundle/package that provides the skeleton framework. Here we'll go over the options.

Learning to program is hard, really hard. Advanced programmers forget how hard it was for them to learn, and beginners aren't often aware that the language they choose to program in has an effect on their learning. In this article, I'll make the case that PHP is the best language to use when learning to program.

For the most part, sanity checks are put into the code to ensure there are no bugs. For this reason, guaranteeing sanity checks are done correctly becomes necessary. If you do not check to see if the data is valid, and it is invalid, then you’re going to allow invalid data to proceed. Here, I’m going to discuss how I think we should do sanity checking in PHP.

Single Responsibility Principle (SRP) is probably one of the most well-known principles from SOLID. At its core is a desire to prevent classes from becoming overwhelming and bloated. While enabling the ability to change how a single thing works by only changing a single class. So the benefits of the Single Responsibility Principle are that you have an easier codebase to maintain since classes are less complex and when you wish to change something you only have to change a single class. In this blog, I will go through some ways to try and help avoid breaching the Single Responsibility Principle while doing code review.

Logging is a very important part of operating an application if you're unaware of what happened in your system you're unable to quickly and efficiently identify the issue. However, logging can open up some potential pitfalls. One of them being including secrets and other sensitive information within the logs accidentally. Twitter and Github both accidentally logged people's passwords in plain text. To help protect our users we've made it so that we automatically filter passwords out of the logs created via monolog. And we're going to share how we did it so you can also ensure your logs are also secret free.

The aim of this article is to explain to non-technical individuals that PHP isn't as bad as many make it out to be. Try to answer some of the more common assertions about PHP. PHP has a terrible reputation because it used to be horrible.

To skim, just scroll for the TL;DR in bold.