Holy shit. Can't believe that one of my projects would get this much attention. Thank you all for using, reporting issues and providing new ideas and feedback. 🙏 #php #composer #opensource #1000stars

So exited for that game, its a rough start. But man: one thing I have to give props to @pathofexile, you guys know how to share information about what going on. As a software developer myself, I love when devs are just upfront with what is going on without business slang!

As the porn spam posts and spam posts overall are getting ridiculous now, I decided to leave this platform once and for all. You can find me on bsky with the same handle. I will leave this account active tho, but won't get any notification 😉

"Start simple" is the key. Find the way you need in your application first. If you would start with a provider (or any concrete dependency for that matter), you tend to implement way more than you actually need. We implemented a simple hard-coded flag provider where you register flags by header/cookie or on by default. Then a second service that checks the current request if any of the flags are enabled. Simple as that. What we might change? We can probably swap out the local provider with one in the cloud, or combine both in a transition.

That is a very good point. I have been doing that for over a year now and I think it works pretty well. We have a CI/CD that blocks everything that breaks existing code. So there is no merge happening. If something breaks we fix it before merging. After that we immediately deploy to another environment with even more tests before going to production. If by all means something that line anything fails, nothing will hit production before it's fixed. Also. Even IF production breaks, there is no blame. The fix will go out immediately which can happen, even with review. So #NoRequiredCodeReview for me. If you want a code review you can certainly request one 🙂.

Playing around a little for #composerUnused #php. Let's see where this might lead 😉

Release version 0.2.3 of the symbol-parser for #composerUnused This adds support for @nikita_ppv php-parser v5 and some other optimiziation and bug fixes. Thanks to all contributers. 💪 github.com/composer-unused/s…

Hold your horses! #PHP Generics are worked on 🤯 youtube.com/clip/UgkxKSi-JMg…

Interesting approaches of this tool. I also had some ideas to combine the results of composer-require-checker and composer-unused into one tool. Don't know how the quality of results are without using the AST at all here. As I haven't tried it out yet. But another tool people can choose from, which oss is all about 👍 #oss

Anyone in my bubble wanting to start our new year's meetup? We are also going to have the capability to have you brought in remotely, but ofc would love to do it in person 😉

I think most people have a wrong understanding of what "pairing" means. Often people see it as 8h non-stop "sitting together" on the exact same file. You can do that, and I think it makes sense in short iterations, but ultimately what works best for me: Get together, make the first rough layout what needs to be done, iterate together. Split up and work solo. Get back together an hour or two later. Sync up, repeat until you are done. No "after-the-fact" review needed.

You can find me now also on @instagram threads. 🙂 threads.net/@icanhazstring