AI rewrote this: Some people don’t speak English as their first language. Using AI to write is fine but they should indicate it. However, entirely AI-generated content without human review is poor. Conversely, non-native English speakers can jot down ideas and have them structured with AI. This benefits both parties as it improves communication.

Now the latter is considered entirely AI generated? Did the rewrite actually help or you like to read the raw version I wrote? Which feels good to read?

So you need to tell which tooling you want, and I might be able to configure it. I am no biologist, but an engineer who understands DevOps.

This lives in my academy atm - but you can signup for free and try it out. This is a DevOps infra for higher educational research - right now focused on Cybersecurity, IoT, Software Engineering, AI Workflows.

But this can be customised to whatever you want to run - because all I provide is a mini self-hosted AWS for EdTech that gives you MicroVMs, VPN, Hosting, AI Based learning and evaluation tools, all gamified. It can generate Roadmaps and link them to lessons you can then try on labs! So a lab can be anything you want to be!

You looking for something like this? Am I anywhere near?

Now the problem I would face by doing this is, accomplishing less in more time, instead of accomplishing more in less time. I am not questioning why... but if we want to do things old school, I'd say don't restrict yourself from using AI to do mundane tasks like setting up the environment or writing tests..

You can still focus on writing the main business logic yourself. Read documentation, start off with the examples.. And play with mutations of function calls to explore the technology. Build a mental map of what you are trying to do! But type the logic out yourself. Write your first Class. Second will follow.. and third. !

I myself is an ADHD guy and that is how I start with. The first one is always difficult.

The idea is to keep the simple Apache/LAMP style PHP mental model, but modernise the runtime: PHP can handle HTTP, WebSocket, SSE, sessions, shared memory, timers, and task workers from one long-running process.

Greenfield, it's working great. For legacy code, the migration model I’m exploring is:

OpenSwoole front-of-house, PHP-FPM-style back-of-house for legacy code, and a coroutine-native path for new code. Three lanes, one server.

So in one day, all existing traditional PHP apps can have an asynchronous runtime! Hoping that I am laying the right foundations? Or not? Help me understand!

I also made a handcrafted Learn section where you build a small Personal Notes + AI Chat app + Multi-Player Tic-Tac-Toe step by step:

https://php.zeal.ninja/learn

GitHub: https://github.com/sibidharan/zealphp

After feedback from some senior PHP devs, I tightened the framework core and it now passes PHPStan level 10. Actively developing!

Still looking for feedbacks before Show HN