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.

I recently decided to start a Six Saas in Six Months project to showcase the possibilities with Parthenon while possibly creating extra revenue streams.

The idea is I build six different SaaS applications within a six-month time period. This will provide me with some solutions to problems I already have, SaaS platforms that can be bundled with Parthenon to provide extra value, and a chance to QA Parthenon fully with applications. If any of the SaaS gets traction and generates €500 revenue, then I'll stop and focus on that SaaS to build up.

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.

Sometimes people at work annoy you, and you feel like you need to get your own back. Make them pay for the imaginary slights they've committed against you. Often there isn't really a way. But if you work in software development. Then there is always a way; that way is code review! When done correctly, code review can be an excellent tool to help improve code quality and spread core knowledge throughout a team. But when done incorrectly, it can be the bain of someone's life. It is a fantastic place to get your own back via passive-aggressive actions. Are they too good? Do they never refill the coffee pot? Did they not say good morning to you one time 3-years ago when they didn't realise you were in the office? Now is the time to take it out on them during code review!