The Laracasts Snippet

One thing I love about Laravel is how, for any given project or feature, there's already a clearly defined pathway I can follow to complete it. For example, we take it for granted that a robust queue system with model serialization is always at your fingertips. We take it for granted that a powerful event dispatcher with automatic event registration is available for free. We even take it for granted that the decision of where to store your secret API keys has already been solved and documented.

My wife recently paid me a compliment. "You're a good troubleshooter" - to which I replied, that's because it's all I do every day. Programmers are professional troubleshooters.

After you've maintained a popular open source project for any length of time, you begin to notice a pattern. Certain issues and pull requests bubble up to the top of your todo list, and certain issues...are ignored or discarded. Let's talk about why that's often the case.

We recently pushed a new "goodbye" landing page for the Laracasts website. In an effort to not succumb to the usual, boring "Goodbye, hope to see you again" copy, I opted for a different approach. Unfortunately, it didn't land for everyone the way I thought it might.

I recently hired a new instructor for Laracasts. Now that the team has grown to four people, including myself, I thought it might be interesting to discuss my personal hands-off approach to running a small and low-stress team.

Four words can derail any programmer's day. Those four words are "If I could just..." Ask yourself if you frequently fall into this trap. "If I could just configure my code editor properly, then I could get some work done." Or what about this one? "If I could just get my office the way I want it, then I could begin this new feature." Have no doubt; this is a form of procrastination that infects most of us.

As parents or teachers, if you want to instill a joy for learning or reading, it's important that you meet them where they're currently at in life. The goal, as we've discussed in past episodes of The Laracasts Snippet, is to get them excited.

I recently came across a month-old YouTube channel with two million subscribers. The content...was fine. The audio...was fine. And, yet, two million subscribers! Often, the way in which you frame your content is significantly more important than the content itself.

Few topics in the programming world spark debate quite as much as TDD. There's enough dogmatism from the evangelists of TDD to warrant an equal and opposite reaction from those who aren't on board and are tired of being told they're doing it wrong.

We're living in an interesting time, when one person - anywhere in the world - can start a business without leaving their bedroom. Even better, this business has the potential to bring in revenue while the person sleeps. This is the secret sauce to wealth, and it's now available to anyone with an internet connect and a decent idea. As a result, we have now regular folks - often with little business sense - running highly profitable small businesses.

Every open source project begins with the best of intentions. In fact, they usually begin with excitement. One developer has an idea, and thinks, "Hmm - I can do this!" So why is it that, more often than not, these projects eventually spiral out of control?

We can all surely relate to the sense that our ability to focus has slowly deteriorated over the last decade. If this scares you as much as it does me, let's talk about how we reverse the process through habit forming.

I think you'll find that intermediate-level developers tend to be the most passionate and rigid of the entire community. It is at this stage of your learning when you are most susceptible and attracted to programming "rules," or instructions from above that, when followed, lead us to clean code. But that's okay. While we all eventually realize that rules are meant to be broken, in certain phases of our training, rules very much serve an important purpose, and we'll talk about it in this episode.

To offer something different this week, let's tear down and inspect a recent conflict on the US presidential debate stage.

In this episode, I offer a brain dump on the intricacies of raising two little kids, and fatherhood in general.

Too often, we hear politicians spew the tired "learn to code" slogan in response to difficult questions related to disappearing jobs in remote America. Let's talk about the logistics and practicality of a middle-aged coal miner making this switch.

I've thought quite a bit about types in the last year or two. I know - borrring - but I find it interesting to observe how intensely talented developers can disagree with one another on this particular issue.

Developers passionately disagree with one another on most programming issues. For every tutorial on class inheritance, duck-typing, naming conventions, and mutability, I'll show you another resource that argues vehemently in the opposite direction.

Every developer should develop and manage at least one project themselves. Doing so not only harnesses your discipline, but it also forces you to flex product-related muscles you've never used before.

One of the more frustrating aspects of front-end development stems from the fact that even the smallest of alterations has the potential to derail your entire week. In this episode, we'll discuss how to track browser-specific CSS performance issues.