Is LinkedIn still a good site to apply for jobs? It's been almost 2 weeks since I've been applying for jobs, but still no luck yet unfortunately.

I used to use Indeed but typically got scams instead of real jobs.. I've also tried a few company websites directly, but no luck yet.

Any suggestions on the best platforms to apply?

Also, a side note, I'm wondering if it could be my resume isn't good enough as well? Any suggestions as far as how to go about improving my resume? I.e. Go to a particular agency to improve it, etc?

I'm a full stack developer with 6 YOE in PHP/JS (Laravel, Vue, & React primarily). Some AWS experience as well.

Thanks in advance!

Hi r/PHP 👋

I'm opening the beta of Arco Cloud and I'm looking for Laravel devs who want to try running their apps on AWS Lambda, without managing the AWS side themselves.

What it is

Arco is an open-source CLI (https://github.com/multi-api/arco) that deploys Laravel to AWS Lambda Web Functions with FrankenPHP + Octane. Arco Cloud is the dashboard on top: connect your AWS account and GitHub repo, push, and it deploys. Your app runs in YOUR AWS account. We never proxy your traffic or hold your data.

What you get in the beta

• Push to deploy, with queues, scheduler, storage and cache set up for you

• X-Ray tracing: every request and job broken down step by step (boot, routing, each SQL query, AWS and HTTP calls)

• Monitoring: errors grouped by type, live log search and metrics

• Alerts on Slack and email when something fails

• AWS cost per environment

• Run artisan commands from the browser

• Failed jobs and one-click dead-letter queue redrive

• Managed Aurora DSQL databases (IAM auth, no passwords)

• Private networks with a static outbound IP

• Team 2FA, and a Laravel starter template to get going in minutes

How to join

1. Sign up at https://staging.arcocloud.app

2. Click "Request beta access" and tell me a bit about your project

3. I review every request myself, and I'll personally help you move your first app

What I'm asking in return: honest feedback. What's confusing, what's missing, and what would make you switch from Vapor, Bref, Forge or your own setup.

Questions are welcome here, in our Slack (https://join.slack.com/t/arco-equipo/shared\_invite/zt-4fi2aejbq-fzwl8U\_4qeqSOxO6TtNoPg) or on GitHub Discussions (https://github.com/multi-api/arco/discussions).

Thanks! 🙏

Hi everyone,

I'm the developer behind SemiAuto Invoicing, a WordPress plugin I've been working on for WooCommerce.

The project started from a fairly practical problem i faced while building a client eCommerce restaurant: invoicing in WooCommerce can get complicated once you move beyond generating a basic PDF. Different stores need different document types, receipt formats, invoice adjustments, and, depending on where they operate, structured e-invoicing formats as well.

I wanted to build something that could handle more of that workflow without store owners having to piece together several different plugins.

Some of the things it currently supports:

• PDF invoices and customer receipts.
• Thermal receipts for POS setups, with different paper widths.
• Packing slips, credit notes, advance invoices and final invoices.
• Country-specific e-invoicing profiles.
• Structured e-invoice generation and hybrid PDF/A-3 documents.
• Customer document downloads and email attachments.
• Connected transmission workflows through StoreCove and A-Cube.
• WooCommerce HPOS compatibility.

There's a free version available in the WordPress plugin directory search for: SemiAuto Invoicing

I'm sharing it here because I'd genuinely like feedback from people who work with WooCommerce.

I'm particularly interested in whether the feature set makes sense, whether the setup is straightforward, and what you'd expect from an invoicing plugin that also handles international e-invoicing.

I'm the person building it, so I'm happy to answer technical questions and hear criticism. I'd rather know what needs improving than assume I've got everything right.

Thanks!

I took on this project for my mom... Trying to build a website for her HOA. I really love the "HOAT" template, but I cannot make the content go full screen. I had deleted the parts I didn't need, but now it just won't go full screen. How can I fix this?

Not gonna lie ive been bouncing between a few diffrent strategies for b2b saas leads and curious whats working for others right now.

We're at 18k MRR selling to mid-market teams. Cold email used to be our bread and butter but response rates tanked hard this year. Now doing a mix of LinkedIn outbound (manual not automated), some content marketing thats starting to pick up, and testing paid search but the CAC is brutal honestly.

For cold outreach we pull contacts from Apollo and a couple other databases then personalize based on thier tech stack. Getting maybe 8-10% reply rates which feels low. My cofounder keeps saying we should try Prospeo becuase someone in his network swears by it but havent pulled the trigger yet.

What channels are driving most of your pipeline? And if your doing outbound, what kind of response rates are you seeing lately? Trying to figure out if we need to completely pivot our saas lead gen approach or just optimize what we have.

I'm comparing a React site against an Astro rebuild of the same page. In mobile Lighthouse, both sometimes sit blank for a long time before first paint, and other runs of the exact same page paint fast.

Setup: Lighthouse 13.0.1, Chrome 156, cold loads in separate fresh profiles, default mobile simulated throttling. I kept the traces, network logs and filmstrips.

Here's one matched pair (observed trace timings, not Lighthouse's simulated FCP):

Astro

• CSS done: 203ms
• Last preloaded font done: 286ms
• DOMContentLoaded: 426ms
• First Paint: 1301ms
• FCP: 1320ms

React

• CSS done: 573ms
• Last preloaded font done: 494ms
• DOMContentLoaded: 584ms
• First Paint: 1525ms
• FCP: 1540ms

The filmstrips stay blank right up to those first-paint times. Once painting starts, Paint to DrawFrame is only 10-13ms. So on Astro there's close to 900ms where everything's loaded and nothing shows up.

I don't see a long task on the renderer main thread covering that gap, though I know that doesn't prove the browser was actually idle.

I wondered about animations, so I ran one normal-motion vs reduced-motion pair on the Astro page. Both came back fast (FCP 318ms and 311ms), and the normal one still had its reveal animations, so that told me nothing either way. Desktop loads and a different page also painted quickly in the runs I checked.

One more thing: the fast traces show Scheduler::SetDeferBeginMainFrame events with short true-to-false spans. But the slow traces were captured with Lighthouse's default trace categories, which don't include those scheduler events, so I can't compare yet.

Has anyone run into this? A few things I'd like to figure out:

1. How do I tell whether the page is causing the delay, or whether it's Chrome's scheduling or something in the test environment?
2. Which trace categories or events would show why the first paint starts late, and not just that it did?

My current method is by using register_block_style(). I believe it's future-proof, but I hate seeing a lot of options in the WP Button Style tab. Also, I do not like registring new style just for the icon. For example, the client asks to add a Download icon. I have to edit the theme code, ask the client to test on staging, and deploy to production. It's a small addition, but takes a lot of effort to do so.

I am wondering if you guys have any method for adding icons in WP Buttons block you can share.

Link to the tool: https://gauge-generator.niralsei.com/

Debian restarts php-fpm when PHP updates, and a reload replaces the workers. But queue workers, supervisord programs and PHP in containers keep the old binary in memory until someone restarts them, and package scanners still report the CVE as fixed.

I hit this patching client servers last week, so I wrote a small open source check that lists PHP processes still running a deleted, pre-upgrade binary and checks the installed version against the vendor’s fix: github.com/asifh0ssain/stillmapped

How are others handling this? Do you restart workers as part of every PHP update, or rely on deploys to do it?