Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@retoor Fucking hell, right? Just despicable...
-
@retoor legit don't know how we're not at the singularity of brain rot rn. I think we are. surely something has to break soon
-
@whimsical But is it a bad thing if the internet dies? If their interaction in reddit, facebook, instagram, ... is not longer human-to-human or human-to-business. Then there might not be a use anymore and smaller niche communities might start to thrive again. Maybe we will see local forums again, hopefully.
You can say what you want but at least devRant feels like a more human-to-human experience than reddit at this point. Even if the users of devRant is a bit weird. -
> "Readable > Clever"
I'm fighting this right now.
My boss (probably an IQ in upper 3 digits) developed all the security for our blazor (WASM) apps (including all the custom backend authentication and authorization). In order for an app to login, there is no less than 10 required nuget packages and all them have indirect or direct dependencies on each other. Once you have all the planets aligned, everything 'just works'.
Looking into utilzing the new~ish Interactive feature of Blazor to speed up some page loads, I'm finding how the security context is passed around only works in a WASM project because he decided to write his own javascript library framework to manage the user's state, which doesn't work on Blazor Server (yes, he wrote his own state state mgnt framework).
I can't any sense of what's going on and I'm afraid to ask him for help. He'd likely write his own browser to get around the problem.
Related Rants
It changed my life, really. 😁
The only expressions devs have
10 Things I Wish I Knew as a Junior Developer
After a few years in tech, I’ve realized that most growth doesn’t come from new frameworks — it comes from mindset shifts. If you’re just starting out, here’s some advice I wish someone had drilled into me early:
You’re not competing with anyone but your past self.
Forget comparing your code to that genius on your team who breathes JavaScript. You’ll get there — and faster if you focus on consistent growth over ego.
Google is your best mentor.
Asking questions is fine, but make them good questions. Try solving things first. Seniors love helping, but they respect those who’ve clearly done their homework.
Readable > Clever.
Fancy one-liners might make you feel smart, but clear variable names and simple logic make you a great teammate. Code is for humans first, machines second.
Reviews aren’t attacks.
A pull request comment isn’t criticism — it’s collaboration. Listen, learn, and keep the good discussions going both ways.
Never fake knowing something.
“I’ll check and get back to you” will earn you way more respect than pretending you know the answer. Engineering thrives on honesty.
Think before you type.
Rushing code just to “finish it fast” often leads to rework. Taking time to plan saves you more time later than you’d imagine.
Document like someone will use it tomorrow.
Because someone will — maybe you. Nothing feels worse than debugging your own undocumented code months later.
Soft skills aren’t optional.
People remember how you made them feel, not how you formatted your code. Be kind, patient, and reliable. Those qualities get you rehired.
Run toward the scary stuff.
That weird legacy code? The new API nobody wants to touch? Take it on. Growth hides in discomfort.
Keep learning, even when your job doesn’t require it.
Your company won’t future-proof you — you have to do that yourself. Read, build side projects, and stay curious.
At the end of the day, being a great developer isn’t about knowing everything — it’s about always being willing to learn.
rant
story
developer