Hello World: Why I'm Starting This Blog

The Obligatory Introduction

Alright, let's get this out of the way. My name is Jeffrey Davidson. I've been building things on the web for over fifteen years now, mostly with PHP, and for the last decade-plus, almost exclusively with Laravel. I live in Florida with my wife Cassie and our daughter Viola. I'm a Jayhawks fan stuck in Gator country, I play way too much poker, and I'm pretty sure I've been to Walt Disney World more times than some of the cast members.

I'm also launching a YouTube channel and two podcasts, Coffee with The Laravel Architect and Embracing Cloudy Days, and this site is where it all comes together. Blog posts, video tutorials, and everything in between.

Why a Blog? Why Now?

Fair question. I've been a developer for over fifteen years, and for most of that time I've been learning from other people's content: blog posts, conference talks, tutorials, podcasts. At some point you stop just consuming and start wanting to contribute back.

I chose to start with writing because it forces clarity. You can't hand-wave in a blog post. You can't say "you know what I mean" and move on. You have to actually organize your thoughts and say what you mean. That's a discipline I think every developer benefits from.

Written content is also the most useful long-term format. It's scannable, searchable, and linkable. You can bookmark a heading and come back to it six months later. Try finding a specific tip buried in a 45-minute video. You'll be scrubbing back and forth for five minutes. A blog post? Ctrl+F.

Video and audio are coming too, and I'm genuinely excited about those formats. But the blog felt like the right place to start. Get the ideas down in writing first, then bring them to life on screen and in conversation.

What You Can Expect

This site is the home base for everything I'm building. Blog posts to start, with video tutorials, live coding sessions, and podcast episodes on the way.

Here's how I see the content mix shaping up:

• Written posts for architecture deep dives, opinions, and reference material. The stuff you want to scan, bookmark, and come back to.
• Video tutorials for walkthroughs, live coding, and anything where watching someone build it makes more sense than reading about it. Some blog posts will have companion videos, and some videos will have companion write-ups.
• Podcast episodes for longer conversations: interviews with other developers, discussions about the industry, and the human side of building software.

What I will cover:

• Architecture and patterns. How I structure projects, how I think about responsibilities, when to reach for certain patterns and when to keep it simple.
• Opinions. I have them. Sometimes they're spicy. I think the Laravel community could benefit from more honest, opinionated writing instead of the same "10 Tips" listicle recycled across forty blogs.
• The human side of development. Career stuff. Burnout. What it's like to be a developer and a dad. How I manage my time. The unglamorous reality of freelancing and running a brand.
• Technical deep dives. When I learn something interesting or solve a gnarly problem, I want to document it so you don't have to fight the same battle.

I'll try to publish weekly (written, video, or both) but I'm not going to stress about a rigid schedule. Quality over frequency. I'd rather put out one genuinely useful piece a month than four forgettable ones.

My Philosophy on Teaching

Here's something I feel strongly about: the best teachers are still practitioners.

I'm not writing from some ivory tower. I'm actively building Laravel applications. When I tell you how I structure a project, it's because I structured a real project that way last Tuesday. When I recommend Pest over PHPUnit, it's because I actually switched and lived with the decision. When I say something doesn't scale, it's because I watched it not scale.

I also believe in being honest about what I don't know. The tech industry has this weird culture where admitting uncertainty is seen as weakness. I think that's garbage. If I'm not sure about something, I'll tell you. If I changed my mind about a previous take, I'll own it.

A Bit More About Me

I'm not going to write a whole autobiography here. I'll save some of that for future posts. But a few things that might matter:

I'm a person of faith. I'm an ELCA Lutheran, and while this isn't a religious blog, my faith is part of who I am and it informs how I treat people and approach my work. I believe in grace, for myself and for junior developers who accidentally drop a production database.

I'm also a Type 2 diabetic, which has taught me a lot about discipline, routine, and taking care of yourself when your job involves sitting in a chair for ten hours. I'll probably write about the intersection of health and desk work at some point, because it matters more than most devs realize.

I'm a photographer. I'm a poker player. I'm a dad who will absolutely destroy you in Disney trivia. I contain multitudes.

Let's Do This

I'm genuinely excited about this. I've spent years consuming content from developers I admire, from podcasts to YouTube to blogs. Now it's my turn to contribute. The YouTube channel and both podcasts are in the works, and I can't wait to share them with you.

This blog is the first piece of the puzzle. Another format, another avenue, another chance to be useful to someone.

If you've made it this far, thanks for reading. Seriously. Subscribe to the RSS feed if that's your thing, follow me on social media if you want the updates, or just bookmark the site and check back when you're bored at work. I won't judge.

Rock Chalk, and welcome to The Laravel Architect.