Good lord, fail2ban is not easy to get right.

Initially I didn’t like mold in my apartment, but since then it grew on me.

You know how LLMs always imitate expertise and understanding? That isn't specific to English, it happens in code as well. It's harder for them to get away with it because even the best guess isn't likely to be approximately correct, but they still try and it still sometimes works.

One of cucumber scenario tests now contains a deadlock somehow. We run them one at a time. I need some rakia.

Journalists reading tweets sent by grand ayatollah Khamenei live on argentinian TV is kinda surreal but I guess this is where we're at now.

Do you wake up in the middle of the night, found the solution of a bug in your dreams, go to the office, and the solution does not work ?

Sometimes, all you have to do is to yell “BACKSHIT!” and moonwalk into the sunset peppering first aid kits around.
— MTV life assistant

Laura Les is the only person in the world that can make a Die Antwoord track go harder than the original.
https://youtu.be/LFZZSSjKclA

My favourite passtime is asking awkward questions I already know the answer to and seeing how long it takes the person to work out that they fucked up, that I know they fucked up and how monumentally they fucked up.

Writing paragraphs on facebook is mightier than DDOS attacks

Lack of efficiency doesn’t come from people doing nothing but rather from people who are doing things that are slowing done everything else.

GoRetro.com has been a great tool for us to use at work… to run retros -hope the name didn’t give that away 😏

The product has been completely free for a while now. Their site even had a long message about how important it was to the dev community to provide the tool for free.

Now they are back stepping their position, and offering a free version and a paid subscription.

Honestly I get the move, but hate that this company has sold out its values for some extra cash.

is java code javanese

The most interesting thing about the GDPR training that we do is that very little of it is about our rights as employees and almost all of it is to protect our employer. Funny that.

Tomorrow I’ll post about how I narrowly escaped completely and irreversibly losing my mind

We "engineered a prompt" (in other words, crapped a very poorly written paragraph using only short sentences) that gathers many arguments pro and against the usage of AI to code our production data pipelines.
Most of the "pro" arguments are variations of "we'll get fired if we don't use this crap in something".

Prompted with the whole argument, even Gemini thinks we should not use AI to write our code. Nowadays, we use Gemini mostly to justify why we shouldn't use Gemini.

Seriously. We made the whole setup so that any PO who demands AI has to convince the AI it is a good idea. I'll admit, the AI is doing a good job to deter people who want to use it. It hasn't cracked even once. Not that it matters, anyway. POs just ignore what the AI says and organically write orders telling us to use it anyway.

So this recruiter reached to me. They supposedly like my profile and have a role in mind but need more info than what's currently on my CV

They want 15 bullets points for duties per role.

As in 15 for each job... My CV is already two pages long.

What the fuck do recruiters actually do

Well, dR just disappeared for a bit but glad it's back, but I can see that recent rants are gone (because I was trying to catch up on missing rants)

https://devrant.molodetz.nl/Screens...

I'm trying really hard to like Swift but every time I open the hood on this bird, it takes a shit on my windshield.

For example:

struct ContentView: View {

var body: some View {
let kFontPointSize = 25.0
var theFont: Font = .system( size: kFontPointSize )

theFont = .custom("Helvetica", size: kFontPointSize )

Text("Hello, World!")
.padding(.horizontal, 20.0)
.font( theFont )
}

}

... in spite of how wonderfully self documenting (🐂💩) Swift is, that dirty bird converts the 'var' to a 'let' and "theFont" cannot be reassigned after declaration.

3 things:

1. invisibly converting the 'var' to a 'let' and not indicating 'var' can't be used... really?! Suppose to just "know" these obscure inconsistencies? (sloppy design)

2. then the error Xcode presents on "theFont = ..." line is : "Type '()' cannot conform to 'View'"!? How about "can't use a 'var' here"? God forbid it should make sense. (sloppy design)

3. "var" means variable and "let" means letstant? If you are going to use "var", better use "const", or be consistent and use "set" and "let" instead of "var" and "let" (sloppy inconsistency)

4. and ".horizontal", who owns that? Self documenting?. It is owned Edge Set aka Edge.Set.horizontal and effectively a "global".

5. And reading the Swift coder's mind... No, you should NEVER NEVER NEVER use "25" as a constant literal passed like .system( size: 25 ). (magic numbers not aloud)

Have all best engineering practices been simply tossed out the window? Rule #1 in software "engineering": Globals are BAD. Corollary: magic numbers earn you a one-legged A on your project.

I am so incredibly disappointed in the Swift community right now. Swift designers are honestly earning a "script kiddy" badge of dishonor.

age++

asphalt is the only 99.9% recycleable construction material. When they need to renew an asphalt road, they just scrape it off, reheat it and lay it right back on. Bitumen that glues rock content together gets melted, essentially making what's indistinguishable from brand new asphalt.