Rygu

Github repo (mirror): https://github.com/deuxfleurs-org/garage

Here's the official blog: https://symfony.com/blog/cve-2022-23601-csrf-token-missing-i...

FLOC stands for Federated Learning of Cohort.

Wow that's on-point, agree that in many past projects "inertia to larger changes" is exactly how I would describe so-called Clean Code.

It's that small changes like adding getters and setters give an easy-to-follow PR, a false sense of accomplishment for both the author and the reviewer, and ton of dopamine with that. While important changes, that actually deliver business value or repay technical debt, become increasingly difficult to do without replacing massive amounts of code and redoing the file structure.

Inertia is the biggest demotivator.

Am not getting AMP Reddit links anymore in search results. In Europe.

I like zero-bullshit, engineer-targeting We're hiring pages like this one: https://texts.com/jobs

Why Zig?

I think it's sarcasm, but rather hard to tell.

I enjoyed how Rick and Morty inserted this theme repeatedly (robots, clones).

Don't forget to use Partial Indexes on jobs/tasks tables with queries like WHERE status = 'pending'

More: https://use-the-index-luke.com/sql/where-clause/partial-and-...

Yes that's the theory, yet currently any company with sufficient capital or geopolitical advantage can be an effective market leader, while at the same time operating inefficiently at a loss.

A competitive market may become efficient, companies therein not always.

Understand the frustration, but it is incomparable.

> Retool positions itself as a tool for technical folks, and you’ll need to be comfortable with basic SQL and Javascript to get the most out of it.

> An interesting reminder that PMs aren’t always in the driver’s seat. In fact, sometimes they’re not even in the car .

If you're building a technical tool for technical folks then you probably don't need product managers, until late game anyways. Though you'll probably already have a few product engineers and product designers, who fill in that role.

Vrolijk Kerstfeest allemaal! :)

Polymail for mac and ios.

If you do web development, you should definitely try out the MacBook 12 inch.

I'd prefer to use .js for configs.

Found the NodeJS bindings in the 5.0 branch: https://github.com/apple/foundationdb/blob/release-5.0/bindi...

Seems dated as it requires NodeJS either 0.8 or 0.10.

Maybe it's Blue Monday. https://en.wikipedia.org/wiki/Blue_Monday_(date)

Although I don't agree with the overall sentiment of your message, I do understand your situation as a professional. In fact I believe by far the largest (less vocal) group of React users only use it at work, and never wilfully agreed to spend their spare time on GitHub because of FOMO, or fear of dependency upgrades (FODU).

And I believe there should be a better way to prepare your users for a major version upgrade (React 15 -> 16) than to update the current branch with all kinds of deprecation warnings. Even if a library - as popular as React - doesn't plan to provide lifetime support for any major because they like to to move fast, I understand that, it's simply not okay to ruin older branches this way, madly assuming everyone is surely going to upgrade to React 16 in the immediate future.

Ideally, I'd imagine there could be a separate optional package that adds these warnings dynamically. If that's not possible technically, then an optional build flag would be nice. Or two separate releases: react-15.5.0 and react-15.5.0-upgrade-support. Even better: go back to semver, and treat major upgrades as optional for the first 6 months. This allows other libraries like routers and style libs to catch up, so app devs can upgrade even more smoothly.

Maybe after all, DX is about when to provide helpful errors and warnings. And when not to?

Captain only works for the recent "Docker for Mac" packages. It doesn't detect Homebrew or "Docker Toolbox" installations yet.