Notes On Work - by Caleb Porzio

You think you're done with your little landing page, but then you want to actually share it with the world. Go the extra mile and put on the finishing touches: here are mine.

Open source is weird. Nobody is patenting any of their innovations. What if we could?

Let's talk about people ripping other people off.

I'm a day away from giving a conference talk. I have more thoughts on what is most important to a good talk.

Let's talk about ownership, innovation, entitlement and other tricky things to navigate in open source. (Part 2)

Let's talk about ownership, innovation, entitlement and other tricky things to navigate in open source.

I'm way less active on Twitter than I used to be. And not because of any intentionality, I just don't have as much to say anymore. I don't even understand it really.

The more I reflect and explore the world of web, the more I find common ground and universal experiences. This is a warm feeling.

I'm speaking at Laracon Online soon and planning my talk. Here's my process.

There are two mentalities when you're programming. The more you live in one of them the better.

I've spent more brain cycles on x-transition than maybe anything else in Alpine. It's funny because it appears so trivial. Let's talk about it.

This episode covers the fundamental concept that spurred me to rewrite Alpine and Livewire. We need to understand reactivity FIRST before we talk about the new exciting things I've been up to.

Ryan Singer once told me: Tools Don't Matter. Let's talk about it.

You can make so many mistakes as both a fly fisherman and a programmer. Knowing which direction to err is incredibly valuable.

Isolate variables, speed up feedback loops. This is the way.

Get off youtube, put your feet on the ground.

I've been doing a lot of fly fishing. Let's talk about it.

If I had to re-write everything, i'd be tempted to double down on a technique that feels icky and some people would hate me for.

Wanna hear a fun story about a bug I fixed this week?

Just tagged 2.3.0. Let's talk about it.

You guessed it!

Livewire is death to boilerplate, but when is it too far?

I have an idea that I want your opinion on. Feedback here: https://laravel-livewire.com/consult

Wanna hear how ridiculous Safari is with it's autofilling system? Life is hard.

...

...

Come at me bro.

Maybe THE most identifiable pattern of the internal experience as a web developer

I just gave a talk at Laracon Online. Let's talk about what went into it.

I created an inner circle for both projects. I'm dismantling it. Here's why.

I know, I know. Refactor incrementally with a test wall at your back. To that I say "pssshhhhhhaaaaa".

I'm making a refactor I've wanted to make for a loooooong time right now in Livewire's JavaScript: De-object-orientifying it

I just launched a course on VS Code. Let's talk about the money.

I accidentally killed controllers.

The title says it all

I'm building a landing page for my upcoming course. It's hard.

The music that shaped me

What's the future of Livewire? Well, here it is.

Slots. The people have spoken. They want them. Here's why it's hard.

I've been struggling to do the work that matters most. Here's why.

Let's talk Dusk (The Laravel browser testing framework)

No

I know you probably read "Lunch", but unfortunately, this episode is about treating everything you do like a product launch. Even if it makes you no money, if for no other reason than it's way more fun that way.

I used to build things in the exact opposite order that I should have: Build thing, then market thing. It's a huge mistake lots of people make. Today I'll tell you a story about how I'm validating an idea I have before putting any effort into actually building it.

This is a question I encounter in every single codebase I've ever worked in. Do we group things by "Function" or by "Feature"? The Livewire codebase is no exception. Let's talk about it.

Let's talk about the current refactoring I'm in the middle of.