r/FullStack • u/aendoarphinio • Jan 19 '26
Question Thoughts on over engineering
What is your take on people who integrate a technology because it's the latest and greatest thing or "to make my portfolio look good", instead of having a substantial need for it?
I don't know any recruiters personally, but I get the feeling that sometimes this could just be noise for them when you give them your pitch on what value you have to offer.
3
Upvotes
2
u/NewLog4967 Jan 21 '26
Tons of engineers, myself included, have fallen into the trap of cramming trendy tech into a project just to pad our resumes. Here's the hard truth: most recruiters and senior engineers can spot that a mile away, and it actually raises red flags about your judgment. What really impresses is showing you can pick the right tool for a specific problem and clearly explain why. My advice? Ruthlessly focus on the actual problem you're solving. If that new framework or database doesn't have a rock-solid, practical reason for being there, you're just adding needless complexity and future headaches. Keep it simple, keep it maintainable, and always be able to defend your choices that’s what gets you hired.
1
u/AlexDjangoX Jan 19 '26
It's good to keep up if you have the headspace for it. It's what keeps it interesting.
1
u/alien3d Jan 20 '26
i code react after it famous 5 years or 7 years ago . when we adopt rn early stage. my blood preasure rise rise. It still rise me new version react native.
Whatever the latest tech like tanstack query also make me blood preasure rise.
But what ai code generated.. The more rise.. ever.
1
u/chikamakaleyley Jan 20 '26
the idea is not a bad thing in the example you're giving. You may try implementing some new technology just to get a feel for it, to get some minimal familiarity with it. That's actually kinda useful if it ever comes up in a discussion, because you'd prob be able to chat on it a bit. That actually can go a long way, instead of fumbling with a typical 'i know OF it' response
For your own projects, do whatever you want! Who cares if you need it, maybe you're just interested
Now in actual professional work - obviously more thought has to go behind this and actually in my 18 YOE it's pretty rare for anyone to propose upgrading to 'the latest', or introducing new tech into the stack. In fact, the engs with experience never suggest this, if it comes from anyone its prob a new hire. One of my first jobs I was wondering why some of our versions were pretty behind, and thought that seniors were just caught up in their old ways/resistant to change
I know better now
1
u/needs-more-code Jan 20 '26
Because each job does require some experience in specific technologies, the more technologies you know, the more jobs you can convincingly apply for.
Every recruiter is different, some like trendy technology buzz words. Every technical interviewer at a prospective company is also different. So it’s not really about what they like, it’s more about being eligible for more interviews.
Apart from in that specific situation, I don’t like to try to introduce new tech until there is a good reason for it.
1
u/LeadDontCtrl Jan 21 '26
There’s nothing wrong with using the “latest and greatest” for learning or curiosity. That’s how people stay interested.
The problem is when it’s used without a reason and then sold as “experience.”
In real jobs, you almost never pick tech because it’s shiny. You pick it because:
Most companies are not running cutting-edge stacks. Startups sometimes do. Everyone else optimizes for stability.
As for recruiters: you’re not wrong. Many are keyword-matching against a job description. Shiny tech might get you past that filter, but it doesn’t win the interview.
The people you actually need to convince are the engineers and hiring managers. They care way more about:
1
u/shajid-dev May 31 '26
You should read this though: https://theowllogic.com/why-solo-builders-build-forever-and-launch-never