I'm using vagrant to work on our legacy system which is not fully migrated to docker, yet.
64 karma · joined March 12, 2017
The whole integration in composer with the symfony flex component makes developing even easier than before: https://symfony.com/doc/current/setup/flex.html
Worst thing I've ever seen was a class which inherited another just to keep the lines of code short (<2500). That said it wasn't just one time inheritance... It was up to four times. There was no logical split of the inheritance. It looked like someone simply split one huge file into some smaller ones.
We called that kind of inheritance "code sharding" and we had a lot of headache at that time.
+ doing some freelancing part time @ 100€/h
To solve that problem we started with a "doc" directory in each repository holding multiple markdown files for each topic. That way all of our developers are able to find the information they need (even without an internet connection).
<button>Sign Up</button>
I simply write
<button>{{ 'Sign Up'|trans }}</button>
That way I don't need translation files (EN is default). If translation is not found the "key" is returned which is fine. Once the app is ready I call a command to create my language files and simply translate them.
On topic: Testing gets worse if the codebase which needs to be tested is garbage. My experience with other developers who learn testing don't need to learn how testing works - they need to learn basic development rules: Components, loose coupling, dependency injection, ...
Google Chrome 61.0.3
The problem in my opinion with recipes is that there are too much and most of them are not good. A lot of times I started to cook anything by recipe just to throw it away after some minutes and "freestyling" the meal...