51–60 of 126 posts
Earlier quoted context omitted.
The depth of the stack is not a very good metric for code quality.
Why is everyone quibbling with him about that. He just wants to express his opinion that the codebase is very bad in a more colorful way than by simply calling it doubleplusbad. Let's just take his word for it and move on.
Earlier quoted context omitted.
I should clarify that's over 20 deep of our code , not counting all the framework stuff.
The depth of the stack is not a very good metric for code quality.
The overarching problem is trying to reinvent the wheel because the management thinks we can do things better than the language designers.
The end result is a buggy and generally bad reimplementation of core libraries. ORM, math, dates, full text search. There's a half-baked custom version of everything.
If you were lied to, that is reason enough for leaving. If they lie about the role from the start, they will lie about other things.
"..hope I don't get fired for underperforming?..." What kind of passive language and thinking is that? Everything is legacy once it is written. Imagine you, the trailblazer, only having to write new code and not having to maintain the crap you wrote. The actual problem here is your attitude and way of seeing things. Legacy? Sucks? Fucking write a better version and show some initiative instead of just hoping of being…
The code isn't just old, it's very badly written and has zero documentation.
Sounds like someone likes 'collecting' programmers from different languages and technologies and giving them jobs =] Learn it love it or leave it, you're still making money right now so....
If it's not that you guess is as good as mine :)
I suggest you start looking for a new job, but in the meantime work hard on your current job. Take pride in your work. No matter where you go there will always be a legacy system you will have to work with. New or different technologies to learn.
Earlier quoted context omitted.
Relo isn't a problem and I definitely want to stay in this town. I can't really mark it as time off because I already did that a while back, I don't want to end up with a lot of gaps :) I was thinking I could just apply to other places and be honest with them... But some may also frown upon me saying bad things about my current employer
I'm looking for a React guy. Remote work is fine as long as you're on USA timezone.
I find it impossible to replace a legacy system without first understanding the legacy system. It's easy to say "X is old" or "X sucks at Y" but keep in mind that applications have a strong survivor bias. Ask yourself, "what does X do that is awesome" or "how has X lived this long" and you'll find a lot of hidden scars and requirements. Start documenting those requirements and create a plan to map those to technologi…
Yes. Thats what the college-lecturer tells you. But in the real world you should not stay longer than necessary in a company which lied so hard into your face.