Have the ranters mellowed out in years? I rejoined devRant after 3 years and i see normal rants. Where the fuckety fuck rants at? Where the anger at? Where puke of abusive words at? Whereeee?

There is AI in Mayonnaise!!!!

Advice to new coders? I got multiple, unrelated to each other.

1. Start with the FUCKING BASICS !! Invest some time with fundamentals, don't just directly jump on frameworks like React or Angular.

2. You and everyone else are always going to blame your technical skills if you're unable to land a job. But you have to realize that is not always the case. Your attitude and energy towards the interviewer plays a vital role too.

3. You're gonna have to take a hit to your salary expectations starting out. It's just the way this industry works.

4. Think of yourselves as a freelancer working for companies. Those who call themselves Employees get stagnant and dependent on their company pretty fast.

5. Your objective is either to learn or earn. If there is both, amazing job. If there is either it's good enough. If there is none, time to jump ship !!

6. HR is there to protect the company from you not the other way around. Be better at spotting crocodile tears.

7. Try to find a WFH job over a WFO job. If you have an urgency, then either works but keep applying to WFH jobs. It's the best thing.

8. Focus on what you're building instead of what you're building it with. Devs have a tendency to fight over what tech stack they should use instead of focussing on the larger picture.

9. You're gonna get overwhelmed at some point when you're gonna get terms thrown at you like XML, JSON, API, Figma, Git, SOAP, REST. Don't worry though you'll get there.

10. You should know how to google your solutions, like really. This is like 60% of the job.

- I'm trying to connect to the server at your location. What's the IP address?
- You can just write localhost there.
- 🤦‍♂️

Legend says that if you concentrate and listen for it, you can almost hear @kiki conjuring up the next few words that will start a riot on this cursed land of devRant.

How do we feel about documentation?

Fucking lies, lies and more lies.

If you are not going to keep it accurate don’t even fucking write it down you goddamn morons!

I would rather look at the source code then be led down the garden path by your fucking lies.

Just recycling

Look, I can be an efficient developer or I can be a Java developer

Please excuse the "photo of my monitor" picture, but it really was the easiest way to do this...

So, I'm finally getting around to that to-do list item of wrapping my head around Nrwl Nx workspaces, and I stumbled onto this little gem: https://itnext.io/easy-typescript-m...

I didn't take long for the "what the fuck" moments to start cropping up, and then I decided to check what comments might have been left on Daily.dev regarding this one (see attachment).

THAT little nugget there is what led me to the ultimate "what the actually fuck" moment, which is only truly appropriate for DevRant..

Create an Nx workspaces, only to initialise a project with `npm` directly, using a path under a new `libs` folder, next to the `packages` folder, only to build the library, and literally install it into the Nx workspace's `node_modules` folder, b order to import it into the app that exist in the same workspace.

So, seriously.. like.. WHAT THE ACTUAL FUCK? What is this guy smoking?? I need to know so I can stay the fuck away from it! Wow. My brain hurts now.

Reject original specs. Do the bare minimum MVP that works and solves problems people actually have, and not problems you think people have.
Improve it if needed.

In my experience, software projects don’t live long enough to outgrow the MVP. If they do, it happens way down the road. At that point, business will change, and the original spec will become irrelevant.

It’s a paradox: 90% of the spec was discarded, but the business is happier than if we followed the spec word by word.

Also, static typing and unit testing solve nothing. I’m sorry.

I've built multiple profitable SaaS apps in my career, from scratch, by myself...

...but it's sure damn important to know wether fucking Cindy or Bob or neither can fit into a parking lot after muddling through stupid obtrusive rules that don't mean anything

"its to understand how you think"

yep, clearly don't know how to do that, that's why i'm taking this labrat, i mean, cognitive test

🐀🤡🐀🤡🐀🤡🐀🤡🐀🤡🐀🤡

#1 life lesson I learned from coding?

Maybe not coding specifically, but I learned the difference between problem solving and solution finding.
Its helped me in a lot of areas of my life. Made friends and made enemies.

"our placeholder shows an @ symbol, but please don't use an @ symbol!"

i'm so happy knowing that the devs and designers who created this app are earning 20x what i am

🤡🌎

Now, this is a cringe.

People who write Rust are just not smart enough for C++

I don't want a personal assitant who helps me to google. I don't need a program that writes text for me. I don't need an AI wich invents cooking recipes. Or discovers new music for me. Or plays my virtual girlfriend. All of this is shit. It's giving away the parts of life which are actually fun.

I need a robot that cleans up my fucking flat, clean the fucking dishes, and buys fucking grocerys while being cheaper and socially and environmentally better that paying some humans.

Designer: Need to file a bug, I'm not getting an option to login with FaceID

Me: Oh weird bug. Is it setup on the phone you are testing with?

Designer: yes, use it in all other apps

Me: Did you get an error during onboarding on the FaceID screen?

Designer: nope no error

Me: ..... hhhmm, can you show me your settings?

Me: ... eh, says you have FaceID disabled for this app ... did you click "No" to FaceID during onboarding?

Designer: Yes, to test edge cases

Me: ................ ok ........ if you setup the app and told it to not allow FaceID to login ......... you won't get the ability to use FaceID to login .......... like .... by design .... on purpose ...... cause .... you told it to do that

Designer: No no, it needs to have a setting on the login screen to allow me to turn that back on incase I forget my passcode

Me: the fuck it does. Yeah we can't have anything on the login page that says, without authorization, change my settings

*Deep breath*

Me: Remember we had this conversation previously, where you didn't want the user to create a passcode during onboarding as it was too much friction, and wanted to do FaceID only. With your backup plan being to allow the user to create a NEW passcode on the login screen if FaceID failed .... remember that discussion we had about security? ... and how its important? ... and that we like having any? Ok so its the same reason as that, just with a different setting this time

Designer: ... hhmm i'm not sure I like this

Me: ... tough luck then, not happening

Me: oh and btw, remember we had that other talk about reproduction steps for bugs? Like when the app crashed and you told me it was because its in light mode, and nothing else at all? So disabling FaceID, is very relevant info to the problem of "I can't login with FaceID", please tell me these things first

I starting to get pissed when I read "New X tool bla bla bla MADE IN RUST"

I'm not sure is it a container technology or a zoo...

Docker is Whale
Docker Compose is Squid
Podman is Seal
Linux is Penguin

Are we live in the Arctic?

Damn, I hate it if asking a question leads the counterpart to telling long background stories. Please: Just. Answer. The. Question.

I have my own thoughts and reasons why I ask and don't need your interpretation of my question. If I was not specific enough, please ask back.

Yet another CharGPT ad. Motherfucker had to close comments…

you wanna know what the most hilarious shit is? hackernews users AKA the 6 figure startup bros that "rule the world" in terms of code and software...

trying to argue the best way to build a website 😂😂😂😂😂😂😂😂😂

here's some select quotes:

"I believe the most minimalistic and productive way is to just use php"

^ this guy must not know its 2023 now

"Unless you are a web developer I don't see the point of a CSS framework, it's much easier to roll your own."

^ this guy must not know the pain and suffering that is 'rolling your own' in CSS

"Sadly, I just don't have the time to generate the content I wanted to do, so the site sits."

^ this guy just... wait, what?

but you know what? these guys clearly know WAY more than me in terms of software, it's good they get infinite salad bar and prime rib every day at silicon valley's best and brightest!

please fucking kill me i want it to end

"I hate corporation, they hate us, they collect data on us", says the person who supports increasing the government, aka the largest monopoly and bureaucratically run corporation.

how do you know your dumbass linting rules have gone overboard?

this is how

Why React is soo complicated? Seriously why do we always need to use some stupid shit like this

const [state, setState] = useState();

what the fuck is this? Who designed it that way, why it should always look like shit for no reason? Why its API feels like spaghetti? When i am comparing other front-end frameworks they feel like heaven in their structure.

AND WHAT IS WRONG WITH ME HAVING A QUOTE ON A PARAGRAPH ELEMENT, WHY DO I HAVE TO USE FUCKING HTMLENTITES FROM 2000?

FUCK'ERE

If you are leaving devrant (or any other site) make sure it includes as much drama as possible:

Maybe in special dedication to @kiki.

I cut the unit tests down in LOC size by roughly 50 - 60 % in most projects.

It's really easy once one sees unit tests not as a dunking pile of copy pasta wild west, but rather as a code base that needs architecture and design.

Some extensions, some annotations, some good old helper classes.

Pooooof.

Why I did this? ...

Because it's fucking annoying when you read a PR with tests and need a fucking diff tool to spot the difference between two tests cause they're 80 % the same.

Yeah. Thx for giving me brain cramps, motherducker.

I'm not an expert in unit tests, but if all test codebases look like the "usual stuff" in our projects...

It's no wonder bugs exist...

Welcome to the age of race-based equity. Merit is out.

Climate change activists

People in SO be like: "I don't understand why I'm not getting any answers. All I want to do is to twist this ORM to do something it doesn't support and I haven't even explained the nature of the models and nested relationships in the question"