sastraxi

Cool! More digging to do. I used ALARM to build some rpi images, it worked really well but alas we ended up going back to the base rpi os (Debian) due to the rolling release schedule making reproducible builds more difficult. I’m still thinking through the conceptual correct solution for an appliance…

How does this compare to https://archlinuxarm.org/? I'm surprised to not see a reference to this prior art in the article.

Thanks for sharing your workflow. My question is about why two databases on the same server would need two separate postgres instances.

Yeah, that's the one. My use case is largely for local development, so the active connections thing isn't a limiter for me.

Yes, that's what I'm referring to.

You're still making the assumption in this comment: why does my 2nd (cloned) database need a separate postgres instance? One postgres server can host multiple databases.

I’ve done experiments using BTRFS and ZFS for local Postgres copy-on-write. You don’t need anything but vanilla pg and a supported file system to do it anymore; just clone the database using a template and a newish version of Postgres.

Looking at Xata’s technical deep dive, the site claims that we need an additional Postgres instance per replica and proposes a network file system to work around that. But I don’t really understand why that’s needed. Can someone explain to me my misunderstanding here?

Yeah, I understand it's hard to find the balance here. I'd imagine you feel the need to ship at the same time as writing about it. For me, the post you shared in your reply as well as in the OP have been expanded to be about 3-4x as long as they need to be, and I'm going to assume you're using AI to generate them due to the writing style. My feedback is to consider writing shorter posts, but doing it by hand -- your prose style here is friendly, engaging and direct. I wish that your articles were the same.

TL;DR: I feel like my time is being wasted when I read AI-written articles, so I stop reading. Do with my anecdote what you will!

The idea is interesting, but have some more respect for your potential readers and actually write the post. There’s so much AI sales drivel here it’s hard to see what’s interesting about your product. I’m more interested in the choices behind your design decisions than being told “trust me, it’ll work”.

Contrary to some of the other anecdotes in this thread, I've found automated code review to discover some tricky stuff that humans missed. We use https://www.cubic.dev/

I find their SQL database’s latency to be absolutely unusable, though I haven’t tried in a few months. Otherwise I agree, great free tiers for what I’ve used it for.

Looks good! I might have missed it but it would be helpful to have a link to the jujutsu home page in your README.md.

Great writing style and articulation of thought! That was a fun read

DRF-spectacular is an okay choice here, you have to manage consistency with return types yourself but the docs and customization options are well done.

Can anyone recommend a guide for full stack devs that have mastered other stacks (e.g. django) and want to learn how to use rails correctly?

Perhaps this is the answer to the question “how do we combat the epidemic of loneliness?” —- once the internet truly cannot be trusted, we’ll be forced to once again connect offline (where, at least for now, deepfakes are not possible).

I’d prioritize finding someone else in the company that can give you another viewpoint on the situation. These types of situations make us feel isolated, so see if you can find a way to be “seen”, even if it’s by someone who has no way to help you professionally.

The get the heck out of there and find somewhere that is willing to treat you with more respect.

The "ongoing maintenance cost of software" can also be the additional complexity in the mental model of developers that have to deal with nearby parts of the codebase. Even if no maintenance is needed for a specific feature, it doesn't always make sense to keep around.

There's also knock-on effects, e.g. an offering like this could attract the type of user that would add a lot of additional support burden for the value that the company _and_ the user gets out of the feature.

Agreed re: there being randomness with each hit in a live performance. I wonder, though, if the distribution of one hit is in fact independent of the previous -- perhaps the inner feedback loop of "am I falling behind / speeding up" in a musician causes the next distribution to be skewed differently or centered at a different instant.

In which case I can understand the thought process of it being uninteresting, in a way. And you're absolutely right that when the randomness is applied into a short loop and repeated it falls into a strange uncanny valley (at least to my ears).

Perhaps another aspect of this is that the randomness, added based on e.g. a seed to the whole track, would be hard to control as an artist. I know when I apply randomness to MIDI I tend to go back with a fine-toothed comb and re-distribute hits that don't go where my mind wants them to.

At this point I'm just worried about debt collectors / credit score type stuff. What an absurd and unethical move by the new owners.

I'm going through something similar and was able to negotiate some time off with my employer. In my experience, there's no way to push through burnout, and you're not going to be doing anyone you work with any favours by trying to "be there" through it.

I'd love to hear more about the lightmapping interpolation for moving objects. I wonder what kinds of efficiencies the author had to find to make it performant.

Really impressive site, thanks for sharing it! Bonus: I'm just used to sites not having data / support for Canada; this was a pleasant surprise.

UX observation: clicking to create a start and end was relatively intuitive, but it took a while to find "Close route" to reset it (and be able to click for start / end points once more).

A couple years ago I built toy backends for the same app using both technologies so they could be compared as-directly-as-possible. The code* takes you through the architectural decisions: https://github.com/sastraxi/great-bear-postgraphile and https://github.com/sastraxi/great-bear-hasura

Edit: I forgot that I was trying a "learning repository" pattern where I put longform comments throughout the code. A little more difficult to discover than markdown, as I've learned.

One of the things I liked about this submission was its tone: the lack of vindictiveness.

We are quickly made aware that we are reading an article made by the author of faker.js. The facts are laid out, mostly without embellishment. Though we understand the author is biased, they leave it to the reader to form their own conclusion. Overall, I appreciated how I was treated as a reader while reading this piece.

As for the matter at hand: despite the MIT license's permissive attitude in this case, it just speaks to the company being complicit somehow in... I don't know what to call it? Shady-ness? I hope you find a worthwhile resolution.

I've done exactly that with a sample food delivery project. Same frontend, but two different backends (one with Hasura, one with Postgraphile).

Feel free to check it out: https://github.com/sastraxi/great-bear

0.10.6 is released with a fix :-)

Just a note for anyone trying to download this -- please first try `pgsh@0.10.1`. The `.2` bugfix release caused a regression that I'm working through now. Thanks :)

Such is life in the npm world, unfortunately.

I've tried to be minimal with my dependencies while providing a rich user experience, but I'm sure we could do better still. Any dependencies in particular you'd like me to look into removing?

Feeling seriously inspired by your post. Thanks for sharing!

Good shout; the README is kind of a brain-dump of usage instructions and motivation right now. Anything giving you trouble in particular?