#phsptan pro tip for code that is not perfect yet (legacy, huge, growing, not on level 6, with 100+ ignores...)
If you want to get the most out of PHPStan, without going through 1000+ of reported errors of different types, start with one rule at a time.
"But how to do that? These levels so huge!"
1. disable the levels using "customRulesetUsed" magic word
2. start with effective rules like CallMethodsRule
This yields ~11 errors of one type our codebase (against 150+ on level 0)
I can fix it now. It brings instant value without stress.
It's easy to review, even if you're busy and your codebase has no tests.
Do you have more time? Add next rule the same way.
How to figure out how particular rule is called?
Just ask your favorite GPT :)
@IanLandsman@IanLandsman I just want to see a dark gritty movie about Vader in my lifetime. Show us why he was feared across the galaxy.
In a similar style to the joker in the Nolan dark knight trilogy
@Yuchenj_UW The google we grew up with it gone and its shell of its former self.
It will be be used in case studies to describe mismanagement.
They haven’t had an original idea in over 10 years.
Hey @yusukebe!
I was inspired to see that you went to Laravel Japan.
I decided to give hono a shot and wrote an article about it.
Keep up the great work dude <3
https://t.co/0WK8KH5GaV
I've just launched a production-ready Laravel SaaS starter kit with Paddle billing baked in, so you can skip the boilerplate and ship your actual product.
https://t.co/ahNV9Ckaz5
Completely free.
@nico_jeannen When dealing with freelancers you probably want a payment schedule.
10% deposit.
50% when they produce proof for deliverables
Final payment for delivery.
@freekmurze That's an awesome idea @freekmurze . Id really love to hear more about your success stories building your consultancy along the way too! Might have to buy you some beers at a laracon one day!