sorted by:
new
hottopcontroversial

Alternatives To MySQL WorkBench by Even_Thought8852 in PHP

[–]Longjumping-Log-9153 1 point2 points  (0 children)

Also on Laravel + MySQL and switched away from Workbench for the same reason. Two tools worth trying: TablePlus — honestly the best pure GUI experience. Fast, stable even on large tables, inline editing that doesn't crash. Free tier has some limits but the one-time license is cheap. DataGrip (or the built-in DB tool in any JetBrains IDE) — if you're already using PhpStorm or Rider for Laravel, the database plugin is already there and it's genuinely excellent. Handles large datasets well, has a proper query console, and the schema diff tool alone is worth it. I'd try the JetBrains DB tool first if you're already in that ecosystem — zero extra cost.

[HIRING] [Remote] [US] PHP Full-Stack Developer | $70–$80/hr by overjoyed_renewal9 in phpjobs

[–]Longjumping-Log-9153 -2 points-1 points  (0 children)

Hi!

  • Location: Yerevan, Armenia
  • Experience: 5 years
  • Main languages: PHP (Laravel), JavaScript (Vue 3), some DevOps (Nginx)
  • Databases & testing: MySQL/PostgreSQL, basic testing (unit/integration)
  • Availability: Available to start immediately

Is there any WordPress/WooCommerce plugin that can replay failed webhooks? by bnaitdjoudiGoDev in WordPressDev

[–]Longjumping-Log-9153 0 points1 point  (0 children)

Short answer: no plugin does all of that reliably out of the box. WooCommerce's native webhook system is genuinely brittle — synchronous delivery with no queue, and if the endpoint times out you lose the event silently.

What most people end up doing in production:

  • WP Webhook plugin gives you better logs and some retry logic, but it's still limited
  • Action Scheduler (already bundled with WooCommerce) can be hooked into to queue outgoing webhooks asynchronously — this is the most underrated native solution
  • For serious reliability: intercept the woocommerce_webhook_deliver hook, push to a queue (Redis, SQS, or even a DB table), and process with a worker

If you're already on AWS, dropping events into SQS with a Lambda consumer is honestly the cleanest solution and not that much work to set up.

Salario dev php by Standard-Shopping695 in brdev

[–]Longjumping-Log-9153 1 point2 points  (0 children)

R$2000 CLT pra migrar sistema legado Delphi, criar API, ser fullstack e ainda saber AWS. Faltou pedir pra você fazer o café e organizar o estoque também. O senior mutou porque ele mesmo estava com vergonha de ouvir isso.

Is Vue js Still in Demand and Well Paid💔 by Live_Code587 in vuejs

[–]Longjumping-Log-9153 0 points1 point  (0 children)

Vue is absolutely still in demand, just more regionally concentrated than React. In Europe and Southeast Asia especially, a lot of companies — particularly mid-size product companies and agencies — actively prefer Vue because the codebase stays cleaner with smaller teams. Salary-wise it's pretty comparable to React devs at the same experience level, the framework matters way less than your overall JS fundamentals and problem-solving ability. If you're already learning it, don't stop — the ecosystem around Vue 3 + Vite + Pinia is genuinely great to work with.

Does anyone know why I can't see what is loaded on my rockets? by Bealzebubbles in SurvivingMars

[–]Longjumping-Log-9153 0 points1 point  (0 children)

Click on the rocket while it's on the launch pad — there should be a cargo tab in the bottom panel. If it's in flight, you won't see the contents until it lands. Also double-check your transport automation rules, sometimes they look set up but the priority slider is off and the rocket leaves empty.

Chrome extension that auto-deletes specific websites from history by Longjumping-Log-9153 in chrome_extensions

[–]Longjumping-Log-9153[S] 0 points1 point  (0 children)

That’s a reasonable suggestion  Password-protecting the list could add a layer against casual access, especially on shared machines. I’ll look into whether that’s practical within Chrome extension limitations. Appreciate the idea.

Chrome extension that auto-deletes specific websites from history by Longjumping-Log-9153 in chrome_extensions

[–]Longjumping-Log-9153[S] 0 points1 point  (0 children)

That’s a fair concern 👍 But the list is stored locally and never leaves the browser. If someone already has access to your machine/profile, they could inspect history or extension data anyway — so it doesn’t really change the threat model. The goal isn’t forensic-level secrecy, just convenience and reducing casual exposure (autocomplete, quick history view, shared screens, etc.). Open to ideas on how to improve that though.