How much production code have you written that PHP already has built-in?
Classes like SplQueue, SplStack, SplMinHeap, and SplFixedArray have all been in PHP since 5.1.
Most of us discovered them after we'd already built the same thing ourselves.
#PHP #PHPDev
How do you track your podcast guest outreach?
Spreadsheet? Notion? A dedicated booking tool? Or are you piecing it together from memory and sent emails?
Genuinely curious what's working for people.
#Podcasting #ContentCreators #TheSteadyPack
Your memory is not a system.
It can't tell you who you emailed last week, what's actually in your backlog, or whether that change made it to production.
Build the system. Stop making your future self reconstruct things from scratch.
#DevLife #SoftwareDevelopment #CareerGrowth
`git rebase` doesn't move your commits; it replaces them with new ones. D and E become D' and E'. It's the same code, but different commits. That's why rebase breaks things when others are involved. #Git #PHP
https://www.phparch.com/2026/06/how-to-use-git-rebase-without-breaking-your-teams-history/
If you run `git log --oneline` on a merge-heavy project, you'll see that every line is a merge commit. Teams that rebase before merging get a readable changelog instead. That's the whole argument. #Git #PHP
https://www.phparch.com/2026/06/how-to-use-git-rebase-without-breaking-your-teams-history/
Merge or rebase? Both get you the code. They leave your Git history looking completely different. Which you pick matters more than most devs realize. #Git #PHP
https://www.phparch.com/2026/06/how-to-use-git-rebase-without-breaking-your-teams-history/
You found the perfect guest, but did you already email them?
That moment of uncertainty is why podcasters stop booking guests. Not motivation. Friction.
A guest tracking system removes that friction.
#Podcasting #ContentCreation #TheSteadyPack
`git merge` keeps every commit and every merge point visible. It's honest history, but on a busy team, `git log` turns into a wall of merge commits. #Git #PHP
https://www.phparch.com/2026/06/how-to-use-git-rebase-without-breaking-your-teams-history/