HackerTrans
TopNewTrendsCommentsPastAskShowJobs

flux293m

no profile record

comments

flux293m
·8 mesi fa·discuss
Everybody forgets Jules.
flux293m
·9 mesi fa·discuss
That's definitely the right way to do it, I've had exactly the same experience.
flux293m
·12 mesi fa·discuss
Congratulations on launching the front-end, but I don't see how it can be made for developers and not have a Linux version.
flux293m
·anno scorso·discuss
FWIW, I have the book and I've found it a really good read so far.

Stylewise, It reminded me of reading the original PragProg Rails book back in the day.

It's mostly finished. I just saw it's 40% off this week with the code 2025PERSPECTIVES at https://pragprog.com/titles/ldash/ash-framework/
flux293m
·anno scorso·discuss
Something I've noticed is that Gemini through gemini.google.com or through the mobile apps is vastly inferior to Gemini through aistudio.google.com. Much worse handling of long contexts amongst other things. Very odd that a product that is free (AI Studio use is free), is much worse than the product I am paying 20 quid a month for.

I find this to be especially true for the newer models like "gemini-2.5-pro-preview-03-25", so if you haven't tried AI Studio yet, I'd give that a go.
flux293m
·3 anni fa·discuss
An approach I moved from this to, was to use the DB trigger to write jobs directly to an Oban oban_jobs table.

Oban jobs run almost instantly when they are queued so there's no perceptible difference in speed, but you get all the benefits of resilience that Oban provides, so your webapp connection can go down, such as during a deploy, and still catch up reliably.

It's also handy to be able use the oban_jobs table for debugging purposes.