mfw when clang decides my NSDictionary changed its type somehow to the same type as my block pointer thingy and now I can’t assign to it

On the day nyc is eclipsed by a large mushroom shaped cloud the gods will smile

I am legendary

For the past two weeks i had a task: to clean the web server.

This task was passed to me after being failed by every other person in the history of my company, i finished it in two weeks.

I have reduced the code-base to 1/5 it's original size, deleting over 6000 files. For now on, this day shall be known as the great cleansing, dates will be counted from before and after this day, and one name will remain forever in the commit history of this company: dotnethostage.

If I have to write one more uber-complex, goddamn Google Optimize test, I will literally piss and shit and throw up on my computer and then throw it out the window.

Stakeholder: We have users who are putting like “John and Mary” on their membership’s first name field. Can we restrict that field so they can’t do that?

Me: But what if that user does identify as “John and Mary”?

Besides, what’s to stop any user from taking out the “and” and making it “John Mary” so they can get around input validation for words like “and”?

OK So I've got pretty much everything I can think of right now done for the tokenizer. Now I'm gonna do the rest. So happy this time around writing my own programming language is working. :D

P.S. Some douchebag keeps downvoting comments that nobody would downvote. Stop it. Cunt.

Node 12 to 18 app migration this week. It’s been interesting 😌

Who wants to be my dev buddy :)

Are you serious... I didn't even move the methods they are literally next to each other

I FUCKING HATE MICRO$OFT AND WINDOWS SO SO FUCKING MUCH THEY CANT EVEN MAKE UPDAYES WORK PROPERLY IT LKTERALLT JUST MADE MY PC DISPLAY A LITERAL FUCKING RECOVERY SCREEN FUCK YOU MICRO$OFT

It's been like a decade since I first heard of Kotlin. So wanted to ask:

Kotlin, Yay or Nay?

I had to install the app and register a user and fill in a bunch of crap... So I can rant about how the webpage for devrant required you to do said things to rant.

another update on my tokenizer. i've almost finished it i believe. i can already parse everything except for actions (think functions or methods) and action calls. :D

God is a Civil Engineer, a troll, and has a twisted sense of humor.

Why else would He put a sewage line through a recreational area?

I think if I was doing the design, I might go the same way. Sorry, not sorry.

What to do as junior, if multiple seniors (4) aren't in sync with each other. Following different convention on same client's project. Even after 3 years they didn't able come up with seemless infrastrure. The code is getting ugly day by day. No review happens. Is that normal? As they are not in sync, we, juniors are frequently getting confused what to do. What could be done? I'm planning to leave the project somehow. Don't know what to do. 😑

Company Emails that tell you
who they are
what believe in.
How they were the market leaders since the stone age.
what their values are
what their holistic approach to life is. How they are diversifying inclusiveness to include diversity.
And how all of this bull shit ties into you being a ideal employee of the organisation
Just to get you to fill a damn form.

Makes me wish the next attempt at human extinction succeeds.

Why useImperativeHandle in React is bad?

I have component A. I have component B which is a child of A.
I have button in component A that should change how component B is displayed.

Usual approach is to set state in A, change it upon click and pass that state as flag via props to B.

But there is another approach via exposing ref to component B using forwardRef() + useImperativeHandle().
And then calling method that belongs to B from A. Like this: bRef.current.changeDisplay()

https://stackoverflow.com/questions...
https://reactjs.org/docs/...
https://github.com/reactjs/...

People on SoF and Docs say that the first way is preferrable. But no one explain why.
Does anyone know why calling child method from parent is considered bad?

This is just straight up a joke. Head of data science has had us implementing something based on a paper.

I raised some "concerns" about it a while ago. Found out today they'd not even read the paper. We're pretty sure what we've been asked to work on doesn't solve the problem it's meant to solve...

I woke up screaming today. I had a nightmare where I ran git pull on the project I work on every day, and it had become a .NET project.

Google Docs suggested I change:
Wraps existing get drop off

with:
Wraps existing git drop off