Post

No, and just now it occurs to me I didn’t post about it. Eep, sorry. Nothing dramatic, I got an offer elsewhere I really couldn’t turn down. It was sad to part ways when things were going so well, but I think the content team at ngrok is still extremely strong. I’ll be joining Laravel in November.

Tell me more! What’re your trepidations about Laravel?

0 reposts3 likes

I have to be a bit careful here because I know I have a skewed experience. On the one hand, it makes me a significant but not overwhelming amount of money cleaning up after slop shops (pre-AI term for low quality fast work).

On the other hand, it hides so much complexity under the hood which has allowed the complexity to grow. It robs intent from the dev in a number of ways. Example: `$service->street_address` Is that a property or a method? It requires a lot of work sometimes to find out. How much time you got? lol

Isn't that specific one more php than Laravel? (Totally a valid point though). I've used Laravel quite extensively and never could get it to sit right with me but I'm not a php fan so mostly put it down to that.

Carry on! All good to know. The whole “prop or function call?” thing always bothered me about Ruby, too.

Laravel has always done an above average job of focusing on documentation and onboarding. And the ecosystem in general is very robust. You being a part of that to help improve devs in general makes me want to pay more attention to Laravel as you tuck in.

Laravel and other frameworks that gained ground during the "EVERYOEN SHOUDL TEH KODE" fad suffer from the notion that writing code was hard and so make writing code fast. Bring in packages, &c. Those folks never had to maintain a codebase. Laravel apps start breaking down about year 3.