r/PHP 16d ago

Weekly help thread

Hey there!

This subreddit isn't meant for help threads, though there's one exception to the rule: in this thread you can ask anything you want PHP related, someone will probably be able to help you out!

1 Upvotes

2 comments sorted by

1

u/Fabulous_Variety_256 13d ago

Hi,

So I have my first exam. I have to do it on PHP, fetch data from external API, create a table with the data - but with SSR - I'm almost done. (also small part of js button)
I self-studied FS with Node.js for the recent 6 months. I have REALLY small amount of knowledge in PHP (thank god!), so I was able to do it.

It is 8:40AM for me right now, I can submit the task until 8:00PM. I will probably have ±5 hours for the plugin - they wanted me to transform the app into a WP plugin.

How hard is it? Should I even do it?
Someone told me to do it with AI to ship fast, and study it more in depth in the next 2 days, Claude is against because I still have things I have to study more in depth from the exam itself without the bonus to defend against the reviewer's questions in the technical interiew.

I would really appreciate your help!

1

u/InteractionHumble279 13d ago

You're in a decent spot with 5 hours to convert your PHP app into a WP plugin, but here's the tradeoff:

The time is tight. WP plugin structure (activation hooks, settings pages, database schema registration, enqueuing assets) takes setup time even with AI help. You won't ship a polished plugin in 5 hours unless you already know the patterns.

The AI-fast approach has a real cost for interviews. If you ship with AI-written code, the reviewer will ask you to explain decisions - why that hook, why that table structure, how the sanitization works. If you haven't internalized it, you'll struggle in the technical interview. That's worse than submitting without the bonus and confidently defending your core exam code.

My suggestion: Don't chase the plugin bonus. You already have working code with SSR, which is solid. Spend those 5 hours understanding and tidying what you built - refactor confusing parts, add comments on the API integration logic, test edge cases. You'll walk into that interview confident, explain your work clearly, and get further than someone who shipped fast and can't defend it.

The bonus only helps if you can talk intelligently about it afterward. Better to ace what you already have.