Titles feed the ego. Effort feeds the soul.

I first met ikigai when I was 13 years old. Fortunately in the right time before I was looking for my first job. Since then, I never looked for "a job". I always looked for ikigai 👌

A new version landed in client's composer... a feast for Rector 😁 In two mins, we've upgraded readonly properties to readonly classes ↓ What's your favorite PHP 8.x Rector rule you enjoy applying?

Don't just read the easy stuff. You may be entertained by it, but you will never grow from it.

This GPT HR bot? just lost me. It would be very easy to write a prompt that separates name and surname with a space, and would look much more like human interaction. Also, create a raport first, a human-like trust, instead of action step → my response → ignored, action step

In times of AI and GPTs, practical UX is still the king. I wish everytime I copy-paste any class name in project, PhpStorm, a JetBrains IDE would be able to fill the FQN use import, instead of me pressing CTRL + spacebar manually every single time 😅

Appearently there is an option for that 😅 I had it disabled all these years 🤦🤦🤦 x.com/VotrubaT/statu…

Rector 2.1.3 is out now 🎉🎉🎉 Huge thanks to Caleb White and Matthias Schmidt, who took our pull-request by storm 😁👌 * early deprecatoin fixes in PHP 8.5 * 30+ fixes in type declaration and dead-code sets * and more... 👇 github.com/rectorphp/rect…

I just recently installed and configured Rector after knowing about it for years---I'm kicking myself for not installing it sooner, this would have saved SO much time! This should be a MANDATORY install on any PHP project, stop nitpicking conventions and let the tool

Sleep, walk AND add a coach to get best results. Got mine around 6 years ago, and 90 % you see is thanks to my interactions with a coach. Great at kicking me outside of my comfort zone 😊

Build codebases that will be able to withstand earthquakes

When you use advanced CI tooling, your coding is faster. When your coding is faster, you have more energy to write tests, improve code-review by custom tool or PHPStan rule When you automate every booring step, you can focus on fun parts you enjoy and learn new tools 🚀

Pest, Pint, Rector, and PHPStan are a ridiculously overpowered combo. Shaved ~7 seconds off a test suite just by getting to PHPStan level 4, and the rest make sure it looks the way I want, and still functions correctly 🥳

8. Kaizen In Japanese the term is made of two words: Kai meaning change. Zen meaning good. It is about constant and never-ending improvement. It urges that even small changes accumulate to impact your life in a big way.

I'm using and consantly improving an "Intro Analyzer tool" as part of every legacy upgrade we do. With every project, couple new rules are added, to provide quick, fast, reliable feedback and weakspots of the project. This gives me more time to dig into the right mess fast. Such