I always write it as a select, before turning it into a delete or update. I have burned myself too often already.
I always write it as a select, before turning it into a delete or update. I have burned myself too often already.
With Influx 3 the preferred language is gonna be their SQL dialect. Flux is on its way out and I suspect it will get deprecated in the near future. Flux saw very slow adoption and SQL can do everything as well.
The one that blew my mind is that plate tectonics is only a widely accepted theory since the 70s.
They’re nice if they also migrate your db schema. That way you define your schema once and use it both to setup your db and interact with it via code. I do write raw sql for more complex queries, e.g. when there’s recursion.
Check out the Law of One for some funky spiritual stuff. There might be something in there that makes sense of this reality for you.
It knocked my shoes off
Definitely dead here.
Did not know about that seeder. Super useful tool! Thanks for sharing.
I like the concept of reducing cognitive load for the stream-aligned teams. This means all efforts go towards enabling them as much as possible in supporting the business. It also makes it relatively easy to judge if a platform team is doing the right things.
I exclusively use Lemmy via voyager.
Have you seen how meta does business?! Talk about a straight up evil corporation.
They don’t know how to play nice. They have no interest in playing nice. They’re out to make as much money, whatever it takes. They either buy their competitors or try to kill them. The fediverse is not for sale and we need to keep a healthy distance so they don’t get a chance to kill us.
Do not federate with meta.
Given how evil they are, this definitely seems plausible (although threats isn’t available in the EU and they are actively preventing usage in the EU). Another option is that they’re still out to kill the fediverse. That one honestly seems more likely to me, given how they’ve acted in the past (buying up platforms before they could outcompete them).
When smart watches came about I thought it would be cool to be able to look at your watch when a notification comes in. Never ended up buying one and when I see how some people behave, I’m glad I never did. Some people will just glance mid conversation at their smart watch, which imo is just as bad as grabbing your phone mid conversation.
I’m happy with my cheap Casio. Looks heaps better too.
I work in IT and we have truly self steering teams without formal hierarchy. Not everyone is used to it and IT people can be interesting characters, so it’s quite a process to get the team to perform well.
To shreds, you say?
I see some tourists wear one in Amsterdam. Very rarely a local, of which I always assume they’re ill themselves or easily get ill (immunocompromised and what have you).
It’s not just a personalized feed, it’s also that the algorithms of commercial social media are created to keep you engaged for as long as possible, so you see more ads.
Turns out that people are more engaged with outrage than puppies, so the feed can easily become a super negative thing full of false information, which affects the person viewing and eventually the whole of society. E.g. I am certain that the fact that youtube’s algorithm so easily takes you into the conspiracy territory has caused a lot of people to end up on the fringes of society, causing shit like storming of the Capitol.
How do you differentiate between a small instance where 10 votes would already be suspicious vs a large instance such as lemmy.world, where 10 would be normal?
I don’t think instances publish how many users they have and it’s not reliable anyway, since you can easily fudge those numbers.
The name of the function, what goes in and what goes out in most cases should be enough to get a good idea on what the function does.
It also helps to make a diagram of how everything ties together. Just boxes and arrows is enough.
When writing your own code, it takes a bit of experience to know when to put something in its own function. It’s very obvious when you’re replicating code. It’s also very common to cut things up when a function gets too big. Look for bits of functionality that you can give a good name.