Details
-
AboutI'm a software engineer.
-
SkillsJava, Groovy, Misunderstanding.
Joined devRant on 10/23/2025
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
-
ColdFusion is a bag full of pure, manure-reeking stupidity.
For example, some functions, like arrayIsDefined, return YES or NO - instead of true or false. I'm not kidding. Adobe == fucking lamers ? YES : NO. Definitely YES.6 -
I've enrolled in a language class of a niche language. We had to do our first homework and there is a grandma that wrote her test via Gemini.
What is the purpose of paying for a language class if you don't do the effort to actually learn the language yourself lmao8 -
Have you ever asked yourself: "Do I really want to be a dev?". Maybe one wants to be an artist, y'know.21
-
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.12 -
My morning:
Me: Why did you just delete the failing unit tests?
Intern: I debugged it for a while and found one of the other developers broke it with his recent changes. I couldn't fix it.
Me: Did you let him know he broke it?
Intern: No.
Me: So you just deleted it and decided to pretend the feature isn't broken?
Intern: ... No ... I mean ... well you told us yesterday we needed to have all the tests passing.
(I NEED a stress ball people)30

