Marcos M.

Over the past year or so, we’ve decreased our 30 day rolling average of errors from our primary frontend app at loveholidays by 70%. We’ve applied these same techniques to our other frontend systems as well and it’s resulted in a much better quality of errors coming through. This has considerably reduced the overall support burden of running these systems in production, so we've written up our approach to help other teams achieve similar results. https://lnkd.in/etc9-__k

59

3 commentaren

I found out about JobRunr at Utrecht JUG and i was surprised by the simplicity and robustness of this scheduling framework. It is very straightforward to use and only needs to dependencies to get started. I wrote a blog post about it but in a nutshell JobRunr is: -simple and robust -has built in retries -has a nice dashboard to check statuses of jobs -distributed by default Some pitfalls to watch out for: -keep job arguments simple -keep job lambda simple -do NOT catch Throwable or Exception, JobRunr needs these to know if something bad happened. Blog post: https://lnkd.in/eh4DTyGR JobRunr: https://www.jobrunr.io/en/ #JobRunr #UtrechtJUG #async #distributed #java

30

Great short summarizing a chuck of what's coming in PHP 8.5. It's nice to see this coming out of a user group talk. Great work Stiven! my slides from last month: https://lnkd.in/d6YTxWvn

7

Having a structured decision operating model that controls for bias and subsidiarity is something most organizations need and don't have. Many companies and regulatory bodies are organized to force decisions to the top of a context-independent pyramid. I'd be willing to guess, based on my anecdotal experience, that those decision-makers force the structure. Ultimately decision-making power drives structure as much, if not more, than plain-ol' conversations via Conway's Law.

12

When I joined group.one a few years ago, I told friends in tech I was joining a WordPress team. Several said I was giving up on real tech & quality. That landed. WordPress might have such a reputation. Tomorrow I'm on stage at the Dutch PHP Conference to make the opposite case. The tooling and the practices exist, but it is true that adoption could be stronger. With "Reconciling WordPress & Quality", I'll cover specifically for WordPress: static analysis, unit & integration testing, common pitfalls with WordPress development, and how we avoid them. 🤝 I had the chance to discover, learn, and apply those insights, while working with the great teams at WP Media, and in particular Rémy Perona, Ahmed Saeed, Mostafa Hisham, Gaël ROBIN, Michael Lee, Nicolas Mollet, Opeyemi Ibrahim, Laurent Molina, and Cyrille C. 🙏 #WordPress #PHPDutchConference #CodeQuality #PHPDevelopment #WebDevelopment

76

What's new at Private Packagist, August update: dependency usage tracking across your packages, automatic GitLab token rotation, and Conductor improvements with custom labels and smarter PR handling. Read the full details on our blog 👇  #php #composer #composerphp #phpc https://lnkd.in/efu-xDrB

10

1 commentaar

This post by Duncan Ogilvie articulates a shift I’ve been leaning into over the last 4–6 weeks. Two lines in particular stood out: “Your job is to write clear specifications, plans, and examples. Define what ‘done’ means, how to test it. Review outcomes, not lines of code.” “Your project setup is probably the single most important human time investment you can make.” This is increasingly how I think about AI-assisted development: the leverage isn’t in typing faster, it’s in clarity of intent, constraints, and definition of done. When those are strong, the code becomes a byproduct, not the bottleneck. Worth the read 👇 https://lnkd.in/gRfp5cB5

5

1 commentaar