Just came back from my first day at cloudflare. I've already removed quite a bit of dead code.

Another coding test that takes 2 hours.

Yaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay.

Things that we should collectively refuse to do while job searching:

- AI interviews and live coding sessions
- Working with recruiters who don't know shit about tech
- "What is your Github" (I don't use github, retard, they're microsoft. Beside, I don't have a strong portefolio because I had an actual job, you should try it).

Was frantically trying to figure out where an unwanted full stop was coming from, next to a dropdown in my UI. It was some dust on my screen.

Reddit is so very dead... Today, I read a post in /r/webdev or /r/rust, not sure which one, but both are full with AI bull, that was clearly written by AI. Then most answers were also clearly written by AI. And some of them had answers written by AI.

I wish that was the dead internet theory. But that requires bots to answer to bots. I believe those are people who answer other people, by putting a few bullet points into AI and have it generate their comment.

And yes, I think so little of my fellow humans that I do strongly believe that most of them are unaware that they answering AI with AI.

First it was Amazon region-wide service issues. Now it's Cloudflare having issues.
https://www.cloudflarestatus.com/

Fuck sake man.

Got a customer right now who constantly finds new technologies with which the whole app will be built faster and be more flexible.

Oh joy...

update: oh boy, spent the whole day in the hospital - bronchopathy. They did some exams and you know that propylene glycol thingy vape liquids use to produce all that vapor? It seems that while that shit's safe to eat, your lungs can't digest it, obviously. Therefore I am now stuck puking that shit out the next couple of weeks. Don't touch ANY sort of vape, friends

First time filing for unemployment after the layoff. I didn't even know it was something I was eligible, so I'm lucky I spoke to my friend the other day.

After coming back from vacation, seeing that the project manager has used AI to try and do some of my tasks, completely failing and running performance and code quality/readability into the ground I must confess that I am strongly in favour of completely banning AI for non-tech people

devRant is crawling again. devRanters are truly the members of society that face the most unjust lives.

Gamers should boycott Nvidia.

They abandoned us for making crypto mining machines, leaving gamers with expensive and hard to get cards.

They abandoned us for making AI bubble machines, leaving gamers with expensive and hard to get cards AND crashing our economy.

No more Nvidia cards!

What is this preemptive "You're not a good fit for our team" bullshit replies from employers upon simply applying to a job on a webform?

You haven't even met me, not spoken to me, just saw my CV. Tf is this weird shit.

"Our site works better in the app," they claim. But I can't magnify text in their app, can't zoom into images and can't select and copy text?

Your site only works better in the app, because you make your developers restrict the web app on purpose to deceive and effectively force your users to use a native app for no other reason than to collect more data and push unsolicited spam notifications into their face more easily.

Offset pagination is one of the biggest collective failures in software engineering.

Who wakes up one morning yearning to visit page 7218 of 100000 in the dataset?

No one, right? Because that’s not how it’s supposed to work. That’s what the search feature is for. Not that developers don’t fuck it up too, but that’s the not the point of this rant.

The truth is, most developers are lazy and don’t want to properly handle stuff. It’s even made worse by ORMs, where some dumb ass will use Django to make a shitty API without a care in the world about the underlying database.
Then after a few months of ever increasing data, they start experiencing very slow queries and response times.

Gee, I wonder what it could be! Could it be that the DB is having to go through hundreds of rows just to return the 100001st row? 

Designers also defaulting to Page 1 of 2322222 UI like the NPCs they are, is a big problem.

Pagination UI, if not done right, is a performance nightmare masquerading as a feature, solving a user problem that doesn't exist.

Fuck whoever came up with this bullshit.

I’ve had 3 side gigs where my task was to speed up the system and it always ended up being an issue with pagination. Once worked on a project where the dashboard toook 8 minutes. Yes, you read that right. 8 minutes to load. The company had accepted it as normal until a new manager joined and said, fuck that. Brough me onboard to unfuck the mess. No issue with Django devs, but bro, learn how to deal with databases properly for fuck's sake.

Before you came at me with, “well, what if I want to give users the ability to jump between pages”. Bro, that’s what search is for! If search is not allowing users to access the exact data they want, then it’s broken.
Pages are not deterministic anyway, because page 4 today won’t have the same data tomorrow.

I just fucking hate badly implementation pagination. Fucks up my day.

I told my landlord that his rent is so high that I can't eat every day. I think he actually believed me. Fingers crossed. Last time he raised with 50 euros and I'm without warm water now for almost two weeks. That's not very common in the Netherlands. He came a few times and delivered half work. You would expect a few times half work would mean a completed job.

This rant is IT related bevause it limits me contributing to open source.

I don't really understand the flow that my senior dev wants to do for graphql. Normally graphql should be 1 request for your data with what you need but this is proposed flow.

1) Get all custom fields/columns of "products"
2) Append the custom fields in the frontend by all hardcoded default fields in my object
3) Fetch the relationships
4) Fetch the custom fields of the relationships
5) Add hardcoded default fields + Append that to my "master object"
6) Fetch the custom fields of "secondary key" that is not included in step 4 or step 1
7) append that to my master object
8) Fetch data

So the frontend needs to be rebuild the database structure and send 4 (or 5) graphql requests to load in 1 table... I don't know how to describe it anymore lol

This flow has to be redone for every table

GUYS THE WOKE DID IT AGAIN

https://phoronix.com/news/...

I just had a really great conversation with a Co-CEO of a startup, and I've never seen someone's eyes light up like this before. As soon as I asked:

"How did you see the need for (company name)?"

They spent a good 20 minutes talking about it and how they got there. Sometimes people force a square peg into a circle hole, but this person really sees and feels the need for the product. Very refreshing.

"The burnt pen-is mightier than the sword."
- Vaporator User ostream

"Mind if I smoke?"
- Concentration Camp Inmate 107984

"C++ is made for segfaults."
- Flaming Rust User @sucksemballz

"LSD is a key component to vibe coding."
- @retoorii

"If you are not offended then I will try harder next time."
- some asshole on devrant