@CapnFelix@mastodon.social avatar

CapnFelix

@CapnFelix@mastodon.social

Co-Founder/CTO @pirateship

This profile is from a federated server and may be incomplete. Browse more on the original instance.

CapnFelix, to random
@CapnFelix@mastodon.social avatar

Wanna be a Fancy Frontend Engineer?
Team Fancy is looking for another React Developer to complete their crew and set sail!
Thanks for sharing 🏴‍☠️ ❤️
https://pirateship.tech/jobs/react-developer-senior

alice_i_cecile, to opensource
@alice_i_cecile@mastodon.gamedev.place avatar

is regularly the #1 barrier to contributions IME: very easy to get yourself into trouble, hard to help with remotely, merge conflicts are baffling for beginners and recovering from mistakes is endlessly painful. It's often easier just to start fresh on a new branch!

In related news, I have a new contributor struggling with Git: https://github.com/bevyengine/bevy/pull/12640#issuecomment-2019243271

Anyone have better advice than "I would just redo the changes" for them? Because that's what I would do at this stage.

CapnFelix,
@CapnFelix@mastodon.social avatar

@alice_i_cecile
I am wondering if it would be an option to hop on a screenshare and resolve the problems together?

CapnFelix, to random
@CapnFelix@mastodon.social avatar

Interesting story of self organization

https://www.agilealliance.org/resources/experience-reports/self-organization-eats-agile-at-scale-for-breakfast/

CapnFelix, to random
@CapnFelix@mastodon.social avatar

Hamburgs Ladeinfrastruktur Konzept ist 10 Jahre alt - gibt es da ernsthaft nichts aktuelleres?
https://www.hamburg.de/ladeinfrastruktur/

heydon, to random
@heydon@front-end.social avatar

I've been meaning to write an article about how toggle buttons tend to be extremely difficult to interpret. Fortunately, this in-depth piece already exists: https://axesslab.com/toggles-suck/

CapnFelix,
@CapnFelix@mastodon.social avatar

@heydon turn it on or no? Huh 😃

CapnFelix, to random
@CapnFelix@mastodon.social avatar

Uhhh, that was too fast.
Nice installation @raum2ev including SMS printer service

ramsey, to random
@ramsey@phpc.social avatar

Problem: I have two DB tables, and I’m trying to select from the first table for records that do not exist in the second table. Over time, as I process each record, I’ll write to the 2nd table, and then those records will be excluded on subsequent queries.

Pretty standard stuff. The queries are easy to write, and there are several ways to write them (e.g. left join where is null, where not in subquery, where not exists subquery).

1/2

CapnFelix,
@CapnFelix@mastodon.social avatar

@ramsey
As we’ve had these problems quite often some learnings I made during the last years:

  1. Split scheduling and consuming. The scheduling query is quite heavy as you mentioned, so if possible per your use case, run it only once a day or so and have another job to execute the jobs.
  2. If possible, schedule the jobs on events, so you don't need a scheduler
  3. Use a dedicated queue for consuming
  4. The scheduler: if possible delete processed jobs after x days to keep it performing.
CapnFelix,
@CapnFelix@mastodon.social avatar

@ramsey
A similar use case we just discussed in our team:
We needed to process exactly one job for every record in A and first tried the approach you described, which got pretty slow pretty fast. We ended up just storing the last record id and made sure the jobs are processed in order. So now we just need to query table A for id > x and don't need a join at all.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • Leos
  • rosin
  • InstantRegret
  • ethstaker
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • thenastyranch
  • Youngstown
  • tacticalgear
  • slotface
  • Durango
  • khanakhh
  • kavyap
  • megavids
  • everett
  • vwfavf
  • normalnudes
  • osvaldo12
  • cubers
  • GTA5RPClips
  • cisconetworking
  • ngwrru68w68
  • anitta
  • provamag3
  • tester
  • modclub
  • JUstTest
  • All magazines
    •