dkarlovi
Joined 7 years ago
Karma
134
Submissions
28
Member since
Mar 7
Recent submissions
Comment · 5 years ago
Invest time in GH actions, they are actually really good once you get over the initial hump.
Comment · 5 years ago
I love puns and this one was excellent, thanks for the chuckle.
Comment · 6 years ago
Enforce by code style tools.
Comment · 6 years ago
> It took an hour to read, I thought it would take an hour to write.
Comment · 6 years ago
Backup codes on a paper in your wallet. Multiple devices.
Comment · 6 years ago
That's fair, I guess.
Comment · 6 years ago
You're right, Symfony 1 -> Symfony 2 was definitely a rewrite, but from then on, the general design was kept almost intact (again, not counting the evolution and streamlining of the framework).
I guess the first attempt is always tricky, let's see if Go 2 can find a smooth upgrade path.
Comment · 6 years ago
Can't say for the rest, but Symfony 2 was a resounding success. Current Symfony 5 is very similar to Symfony 2, with just a ton of refinements and facelifts.
Comment · 6 years ago
Of course, that's why the list is sorted, he might never make it pass 1 :)
Comment · 6 years ago
PHPStan and Psalm support what they call "array shapes", basically you can treat the array keys as a type, similar to how TypeScript does it.
Comment · 6 years ago
Roughly in the order you should do it. Hopefully it's at least PHP 5.3 code:
1. Definitely get a PHP IDE: https://www.jetbrains.com/phpstorm/
2. Get a step debugger and hook it in: https://xdebug.org/
3. Fix the code style: https://github.com/FriendsOfPHP/PHP-CS-Fixer
4. Run the code through some static analysis tools https://phpstan.org/ https://psalm.dev/
5. Upgrade the code with an AST fixer (might help you update to newer PHP version): https://github.com/rectorphp/rector
6. Add tests to it: https://phpunit.de/
7. Run mutation tests: https://infection.github.io/
The "0 budget" is rough, though.