AggressivelyPassive @ agressivelyPassive @feddit.de

Posts

16

Comments

1,465

Joined

2 yr. ago

War and peace aren't that simple. Russia already shot a passenger plane down and nothing happened.

Especially since being immune to censorship is kind of the point of the fediverse.

If you're even a tiny bit smart about it, you can start hundreds of sock puppet instances and flood other instances with bullshit.

Damn planned obsolescence!

Not getting dressed at least somewhat is a sign of depression.

When I still went to the office, I wore the exact same cloth I would wear when I was just going outside. Clean, not significantly more holes than intended.

I have to say, I find it weird how focused Americans are on dress codes in offices. In Germany that's pretty much not a thing, unless you have direct contact to customers (bank teller, etc).

Granted, as a developer standards are lax anyway, but I don't even own a dress shirt or suit.

The clear answer is: don't use subversion. There's really no reason not to use git, since you can use git just like subversion if you want to.

Same. Teams isn't exactly good, but it works pretty okayish most of the time. I absolutely don't get the love for slack, it seems to be more like an "I use Arch, BTW" thing.

It's directed at Iran. It basically sends the message "We don't want to attack, but if you do, we will defend our interests". This makes it clear that the US is not interested in aggression, but will make any attack on Israel extremely expensive for Iran.

As the other comment already stated: it's extremely complicated and, in my experience, causes weird splits between client and server logic. Maybe I completely misunderstood the idea, but it seems like every use case requires some code in the server to do all the traversing, which also means, that every use case needs to have logic added at both ends of the conversation, which kind of defeats the purpose of loose coupling.

All that may dissolve itself if you're having hundreds or thousands of different clients and use cases, that all boil down to a relatively small set of traversing methods in the server, but who actually has that many clients/use cases?

It all seems like it's again one of those "but Google does!!!!" technologies that simply don't make sense for 99% of projects.

Absolutely. I barely touch code anymore, but I talk about how to touch code a lot.

I think for two simply have different use cases for Reddit.

The old ui is great if you see Reddit as a text aggregator. You want text or headlines and click on the content to see it. Images are almost meaningless.

The new ui puts a focus on visual connect. Images and videos are the focus, you don't have to follow links most of the time, because the content is embedded.

Those are two very different approaches. Neither is doing a great job of achieving their goals, though.

That actually looks quite promising. You don't happen to know of a similar project for Gitlab runners?

But why?

Am I secretly a towel folding genius? I don't see how that's remotely required?

What?

So you're into BDSM as well?

You can design it to be changeable at all, though.

In the simplest case that's just proper abstractions. You can't change details in the rest controller, if the persistence layer absolutely needs to call methods from the rest controller for no reason.

Finding the right balance between YOLO and YAGNI is almost impossible to get right. But you can at least try not to land on the extremes.

I have to say, pretty much every CI/CD tool, build automation or whatever you want to call it, sucks.

Somehow they all manage not to offer boilerplate actions since that would be too restrictive, yet they also stand in your way if you want to have advanced features.

I often end up writing pipeline steps/jobs thinking "how is that not already built-in?".

And my absolutely biggest pain point: why the fuck is there not a single tool that lets me execute pipelines locally? Why do I have to have 200 commits all saying a variation of "pipeline test"?

At least the hardcore Christians seem to see him more as a vessel or tool. God's tool doesn't have to be perfect and in typical Bible reverse 4D backwards logic, being imperfect even shows how much of a chosen one he is. I forgot the name, but there's actually a precedent in the Bible itself.

So they acknowledge that he is the antithesis to anything they claim to believe in, but they also think that he somehow will bring God's will or something.

Depends. If you're working in a well lit environment, like you should, dark screens are harder to read.

And if you've got astigmatism, like you shouldn't, the color-on-black contrast is really hard to read.

Very little substance or conclusions. While technology is improving, you're not reading into account AI investment is a bubble.

AI can certainly help, but not a single one was able to consistently deliver good results. A technology that needs constant supervision by an actual expert isn't really all that useful. And this is not just a problem of scale. It's a limitation of the current approach. Throwing billions at a problem to save a few millions just isn't worth it.