Daniel

Per la mi prima volta ho tenuto un talk tecnico. E per di più era su #traefik e #Docker Compose. Se interessati lascio qui il video YouTube del talk.

https://youtu.be/5fUe7xIEmdw?si=lUN-O08WKBjEhI94

In the incoming wave of #AI dev, having a trustworthy directory is critical.

For agents to build reliable software, they need to be able to pick healthy packages.
If the data source is cluttered with abandon-ware, AI will produce broken implementations.

This is a motivation behind my work on https://LaraPlugins.io. We aren't just organizing packages for humans; we are organizing them for the next automated tools too.

My thoughts on the future of the #Laravel and #Php

https://coz.jp/knr8Tr

HI everyone! I am a Senior Full Stack Developer and DevOps consultant with 8 years of experience and I currently have full time availability from February (next monday) onward. I help teams design, build, and monitor scalable Laravel and Vue.js applications, from MVPs to long term production systems. I work hands on with Laravel, Vue.js, FilamentPHP, Traefik, Docker and FrankenPHP, with a strong focus on clean code and observability (New Relic). Some example projects I have worked on: Custom platform for an Italian utility company. Payment request and information portals for Italian municipalities. (pagoPa) Custom SaaS applications built on Laravel and Vue.js Monitoring and observability setups for consumer and security companies using New Relic Monitoring and code quality improvements for a large Italian consulting enterprise If you are looking for someone who can both ship features and keep your systems observable, secure, and reliable, feel free to reach out and share what you are working on. #programming #fedihire #freelance #business #developer #laravel #php #vuejs #typescript #docker #mysql

"If you could wave a magic wand and improve one thing about the #Laravel ecosystem today, what would it be?"

I asked this to 200 #developer. The recurring theme was a desire for a centralized, standardized way to evaluate packages.

"Standardize package info ..."
"Reduce the number of duplicate packages."

This feedback was the inspiration for https://LaraPlugins.io. We need a directory that focuses on health, not just download counts.

Full report https://coz.jp/knr8Tr

#programming #PHP

My mcp server to search #Laravel packages is finally working correctly could you give it a try?
Find the instructions for it here: https://laraplugins.io/mcp
#programming #php #developer

I saw a direct debate in the survey responses regarding the frontend stack.

When asked what they would improve about the ecosystem, requests for "More #Livewire support" sat right next to simple demands to "Get rid of Livewire."

The community has strong, mixed feelings about the TALL stack versus other approaches.

Beyond the framework wars, the survey revealed deep insights into what #Laravel devs actually want from the ecosystem.

Read the community responses here https://coz.jp/knr8Tr

Where do #Laravel devs actually find their tools? I was curious if my personal habit of just Googling everything was normal.
It turns out, it is.

74% of developers rely on Web Search
51% use Packagist directly
49% trust Newsletters/Curated News

Interestingly, GitHub Search (42%) and Socials (19%) ranked significantly lower. We seem to trust curated editorial content and algorithms much more than raw repository searches or social feeds.

See the full data:
https://coz.jp/knr8Tr
#developer

When needing standard functionality like SEO or Media handling, what is your default reaction? Do you reinvent the wheel or look for existing solutions?

My recent survey shows a massive consensus: 96% of #Laravel devs immediately look for existing packages . Only a tiny fraction start by building from scratch.

This confirms that the modern dev is an integrator first. We focus on business logic and offload the plumbing to the ecosystem.

Read the analysis: https://coz.jp/knr8Tr
#programming

It is a statistical tie for the top frustration in the #Laravel ecosystem.

70% of developers cited lack of docs or usage examples as their biggest pain point. It ranks exactly as high as abandoned packages.

This sends a clear message to authors: You can write the cleanest, most performant #PHP code in the world, but if your Readme doesn't explain "how to," the community will view it as broken.

I dive into the full developer wishlist in my report: https://coz.jp/knr8Tr
#software #developer

The packagist search Api only returns up to 100 pages at 100 elements per page.
even if there are more results in the set, per their count.

The Italian term "grilletto facile" (quick trigger) perfectly describes how a modern #developer selects dependencies.
I asked 200 #Laravel devs how long they spend researching before typing "composer require".
61% spend between 5 and 30 minutes.
19% spend less than 5 minutes.
For the majority, the selection criteria must be scannable instantly: update recency, docs quality, and popularity. We rarely do deep code audits anymore.

See the full breakdown: https://coz.jp/knr8Tr

#technology #php

We have all experienced searching for functionality and finding 5 packages that haven't been updated since #Laravel 8
In my recent survey of the ecosystem, 70% of devs cited "abandoned or outdated packages" as their number 1 frustration. It is a statistical tie with poor docs.
The vibrancy of our community creates noise.
Filtering through that noise to find maintained tools is becoming a significant operational cost.
The full data here https://coz.jp/knr8Tr

#PHP #developer #programming #tech

How much "baggage" is currently in your composer.json file?

I surveyed 200 active developers to gauge the average weight of a modern Laravel application. The results highlighted a distinct split in the community regarding the "Build vs. Buy" mentality.

Over half of the respondents (54%) fall into the 6–15 package range. Given standard best practices today involving tools like PHPStan, Pint, and Debugbar, this feels like the industry standard.
#Laravel #PHP #developer #programming #technology

A very persistent LLM scraper just gave my website a free stress test: 10k+ requests to a non-existent endpoint in under 24 hours

The result? Zero downtime. Zero performance degradation. And if i did not check the analytics I wouldhave missed it.
This is why I advocate for modern stacks like Traefik paired with FrankenPHP. The ability to handle high concurrency with minimal resource usage is a game changer for #PHP applications.
#developer #programming #technology #business

decided to open an account for the #saas I'm trying to #buildinpublic find it here if you want to suport: @coz_jp@mastodon.social

My objectives for the weekend:
Finish API support for @coz_jp@mastodon.social
Study Japanese conversations
Finish an article on umami and Laravel.
Study MCP and Laravel again