Hi everyone,

After spending a few years at my first developer role I decided to take a year out of work to go travelling in Asia, now I'm back and ready to enter the job market once again. I'd like your help to get honest feedback on my resume before I start applying for jobs.

I'm mainly looking for feedback on:

• Whether my bullet points are strong and impactful enough.
• If my experience comes across as real engineering work vs. just surface level tasks
• Anything I'm missing and red flags or weak spots in my resume?

Thanks!

https://preview.redd.it/qpz1n91x0jzg1.jpg?width=2550&format=pjpg&auto=webp&s=db848eecdb4e5795aad8467bf1b9ee0f245cdaab

First time posting here. Sharing lerd because it has solid Drupal support and might be useful for folks who want a Podman-based alternative to DDEV or Lando without Docker Desktop, especially on Linux where the usual mac-first tools are awkward.

Lerd auto-detects Drupal projects via composer.json, handles the web/ document root, and gives you .test domains, per-project PHP version isolation (Drupal is strict about PHP requirements), one-command HTTPS via mkcert, MySQL or Postgres with one click, and Mailpit for email testing. Drush, Composer, and PHP commands all work through container shims so they pick up the right PHP version per project. Everything runs as rootless Podman containers, nothing touches your system PHP, no sudo required after install.

Highlights:

• Auto-detects Drupal projects, including the web/ document root and the Drupal favicon path.
• Per-project PHP version isolation, useful when juggling Drupal 9, 10, and 11 across projects.
• Drush, Composer, and per-project PHP all run through lerd php so the right version is always used.
• One-click MySQL or Postgres (plus phpMyAdmin or pgAdmin for browsing).
• One-command HTTPS via mkcert, handy for OAuth / SAML / SSO testing.
• In-browser PHP REPL per site with autocomplete and live linting, useful for poking at entity APIs without writing a temp script.
• Full git worktree support with per-worktree DB isolation, so you can test a module update against a fresh DB on a feature branch without polluting your main one.

Would love feedback from Drupal devs, especially around Drush integration and module/theme dev workflows. If lerd looks useful, stars on GitHub help a lot with reach.

github.com/geodro/lerd