E161

Is the traditional code review workflow holding you back?

about 12 hours ago

15m

E160

Write better requirements or pay for it later

Aug. 29

13m

E159

Which layer of caching does your slow app actually need?

Aug. 15

11m

E158

Where do credentials end and configuration begin in your env file?

Aug. 1

9m

E157

Running AI agents on your production server is the new FTP

Jul. 18

15m

E156

Why having a human partner still beats relying on AI alone

Jul. 4

13m

E155

What is really inside the AI tools you blindly install

Jun. 20

13m

E154

How much logic is too much logic in a PHP enum

Jun. 6

13m

E153

Your codebase is not a museum for old code

May. 23

13m

E152

Do you actually own the code you ship?

May. 9

14m

E151

Do you actually need a multi-tenancy package?

Apr. 25

14m

E150

Local and production should match even for Laravel tools

Apr. 11

13m

E149

When weird code needs to explain itself

Mar. 28

11m

E148

Are you testing your app or just the framework?

Mar. 14

12m

E147

Being anti-hype does not mean being anti-AI

Feb. 28

10m

E146

Three ways to plan an upgrade when your codebase is a patchwork

Feb. 14

9m

E145

Stop doing math in your config files

Jan. 31

9m

E144

What could be worse than having no tests?

Jan. 17

9m

E143

Why I changed my mind about down migrations

Jan. 4

16m

E142

Why senior developers feel wrong more often

Dec. 20

10m

E141

Should you ever hand-format code?

Dec. 6

7m

E140

Discussing different ways to model data

Nov. 22

11m

E139

Read outside tech to expand your horizons

Nov. 8

9m

E138

Rewriting without a map: shipping an MVP from a legacy app

Oct. 25

11m

E137

A composable, versioned toolkit for Laravel projects

Oct. 11

13m

E136

Should you use DTOs in Laravel?

Sep. 27

10m

E135

Sunsetting a company app without loose ends

Sep. 13

13m

E134

When building a UI makes more sense than bloating your seeders

Aug. 30

11m

E133

Blade includes vs components: how we decide

Aug. 16

15m

E132

Changing your mind about when() and unless() in Eloquent

Aug. 2

11m

E131

Finding a code-review style that fits your brain

Jul. 19

16m

E130

Never take hostages: give clients control from day one

Jul. 5

10m

E129

Balancing test coverage without chasing 100 percent

Jun. 21

15m

E128

Exploratory coding when requirements are fuzzy

Jun. 7

15m

E127

Understanding how Stringable works inside Blade views

May. 24

10m

E126

Finishing up our discussion on not having time

May. 10

11m

E125

Why “no time” really means “no priority”

Apr. 26

11m

E124

When validation can protect your app's performance

Apr. 12

12m

E123

Stick with conventions and avoid overengineering your Laravel app

Mar. 29

8m

E122

When to bring in outside help

Mar. 15

10m

E121

Why two databases are better than one

Mar. 1

14m

E120

Dealing with being a beginner again

Feb. 15

14m

E119

Making short demo videos count

Feb. 1

9m

E118

Examining test layering in multi-tenant requests

Jan. 18

13m

E117

When to step outside of Eloquent's comfort zone

Jan. 4

12m

E116

Feature flags: Temporary tool or permanent solution?

Dec. 21

10m

E115

Deciding when to use a new piece of technology

Dec. 7

14m

E114

Taking liberties with value objects

Nov. 23

12m

E113

How to deal with things outside your control on a dev project

Nov. 9

10m

E112

Should we use a JSON field for this?

Oct. 29

14m

E111

A balanced approach to static analysis in Laravel apps

Oct. 15

11m

E110

Why do we like testing so much?

Oct. 1

12m

E109

What does it mean to "know" something?

Sep. 17

9m

E108

How to approach being wrong

Sep. 3

12m

E107

Where do you go when you need help?

Aug. 20

14m

E106

What does it mean if someone says your app is slow?

Aug. 6

13m

E105

Why we have a separate test suite for external services

Jul. 23

18m

E104

API specs aren't just for giant teams

Jul. 9

14m

E103

Slowly introducing static analysis without changing everything

Jun. 25

15m

E102

Troubleshooting an empty session

Jun. 11

12m

E101

Magic methods are okay in the right context

May. 28

12m

E100

Should you let your admin do that?

May. 14

10m

E99

Don't get overwhelmed by errors in your application

Apr. 30

11m

E98

Does it matter how your code looks?

Apr. 16

11m

E97

The life cycle of database hosting

Apr. 2

16m

E96

Are you really going to need that abstraction?

Mar. 19

11m

E95

Should you change application code to support a test?

Mar. 5

11m

E94

What is the point of design patterns?

Feb. 20

11m

E93

Move that logic out of your view

Feb. 6

10m

E92

Is it worth switching to another tool?

Jan. 23

19m

E91

How we use seeders in our applications

Jan. 9

15m

E90

Don't just get mad at some tech, dig in and learn!

Dec. 26

15m

E89

Making a case for consistency

Dec. 12

13m

E88

Different approaches to upgrading to a new major Laravel version

Nov. 28

16m

E87

Maybe you don't need to write code this time

Nov. 14

15m

E86

Should you manage roles and permissions with a UI?

Oct. 31

12m

E85

The changing value of books throughout your career

Oct. 17

12m

E84

Some reasons to write a down method in your migrations

Oct. 3

14m

E83

Managing a micro-manager

Sep. 19

14m

E82

A couple handy features in PHPStorm

Sep. 5

10m

E81

Tools should work for you, not boss you around

Aug. 22

15m

E80

Harnessing that post-conference excitement

Aug. 8

13m

E79

How do you tell a teammate they might be wrong?

Jul. 25

9m

E78

Lots of different ways to test record creation

Jul. 11

10m

E77

How do you avoid distractions?

Jun. 27

15m

E76

When should you use final classes or private properties?

Jun. 13

13m

E75

Is it ever ok to delay writing tests?

May. 30

12m

E74

Should an Eloquent relationship include soft-deleted records?

May. 16

13m

E73

Interviewing other developers like a human

May. 2

15m

E72

The benefits of working with other developers

Apr. 18

12m

E71

Changing our mind about queues in testing

Apr. 4

13m

E70

Too many rules?

Mar. 21

15m

E69

Keeping an open mind with other languages and tools

Mar. 7

11m

E68

What we look for in a package

Feb. 21

10m

E67

Blogging versus tweeting

Feb. 7

11m

E66

Knowing when to use new language or framework features

Jan. 24

14m

E65

Going on a bug hunt

Jan. 10

13m

E64

Thinking about the user, even in the details

Dec. 27

12m

E63

Why do you write your tests like that?

Dec. 13

14m

E62

Avoid painting yourself into a corner

Nov. 29

10m