When everything was working fine yesterday, but today your CI screams at you: Error manifest for bitnami/* not found: manifest unknown

TIL: #Terraform's `regex()` and `regexall()` functions use #Go's RE2 engine, which means it does not support lookarounds (positive/negative lookahead/lookbehind). This means it's not possible to use more complex regexes, but it's rather required to build compound conditions.

Participating in Matthias Noback @[email protected]'s Domain-Driven Aggregate Design workshop today/tomorrow, and even as an attendee I am in a code review mode 😆. github.com/matthiasnoback…

With support for custom rulesets you can now prepare your own Composer package that: - requires PHP-CS-Fixer - defines your rules as a ruleset Then in your projects you can require that package and have super-small config file that registers your ruleset and uses it 😍.

When unit tests pass, but there are no integration tests 🙈.

It's a nice addition, however I'm still against putting NPM (& other non-PHP) stuff in Composer scripts. I believe you should think in an encapsulated way, assuming there are no NodeJS/NPM on your PHP runtime. High-level project orchestration should be shipped with e.g. Makefile.

Today I drove ~900km to bring this little buddy home. It was my wife's and my daughter's dream, and if life isn't about fulfilling these, then I don't know what it's about 🤷‍♂️😅. Tired, but happy! #tearsofjoy #bordercollie

I am soooooo used to #Composer's scripts, that today I wanted to add grouping script (with `@` references to other scripts) in `package.json` file... 🤦‍♂️ How #JavaScript/#TypeScript folks can work without this feature?

#Prettier does not have ability to print diff with fixes found in --check mode 😳. Feature was originally requested in 2018... Do people really apply everything blindly? I know it can be reviewed before committing so it's basically the same, but still... github.com/prettier/prett…

Yesterday #ChatGPT wasted few hours of my life/work suggesting many approaches to fix Backstage test (React), while the actual fix was to add `auth: { environment: 'development' }` to `process.env.APP_CONFIG.data` 😩. These tools are so smart & so dumb at the same time.

Did you know that you can prepare GitHub URLs that point not only to specific line of code, but also to specific part of it? Just add anchor in `L2C14-L2C28` format to highlight subpart of line content 😊! Great way to point out some typo, bad wording or the most important part.