Blog

If you find yourself about to say “we’re a family” to a new recruit joining your dev team, this entry is for you. Managers, you should stop considering or calling your team a family. Here’s three simple reasons why.

When given a choice of methods and ways to do something, it might not be clear which way is the best. As programmers, we tend to pick the easiest, then. However, the easiest can have security implications. Let me illustrate why we should use more stringent controls in a Laravel project.

I’ve seen a lot of high-performers enter slow-moving companies, make great progress, but then get upset. They can’t seem to move the company along anymore. What’s going on? Is it ok to move on? I’ve got a theory about all of this.

Since you’re a programmer, you’re always looking for ways to be a bit more efficient. Because of this, it can be easy to fall into the trap of being too programatic, too calculation-heavy in your unit tests. But, this isn’t a test then - its just another block of quite fallible code. Let’s talk about why and show what to do instead.

When interviewing a junior programmer a couple weeks ago, I was asked a very insightful question: “Who can I tell ‘I don’t know’ to?” At first, I wasn’t sure what they were exactly aiming at with the question. But, as I formulated an answer, I realized this was a great question. Let me share a longer version of the answer with you.

When your unit test suite gets larger, it can take quite a long time. One of the many ways to speed this up is to hunt down and fix slow tests. Let’s use PHPUnit’s test listeners to do just that.

It’s great to run code coverage at the very end before you push your changes. This gives you some idea what’s tested and what’s not. But you don’t have to wait till the end; code coverage can help you all throughout writing your test suite, too.

When talking to junior developers, I hear the same question over and over: “how can I demonstrate what I know, or show experience, if I haven’t had any gigs yet?” Old-timers tell you to build a portfolio, but how do you do that? Where do you get ideas? How do you choose a project that’s not overwhelming? Let me explain my rationale as well as demonstrate how I might make my first portfolio project.

CSS contains custom properties or variables which make style reuse a breeze. But, when you use the inspector on your favorite browser, you only see a definition of the variable, not the value itself. If you want to see the value of the variable, it just takes an extra step or two in your favorite browser. Let me show you how.

I’m a sucker for those little badges at the top of the README files in GitHub repos. I know you can get them from external services, but could I host my own? Let’s find out.