48
010001111
308d

It's enough. I have to quit my job.

December last year I've started working for a company doing finance. Since it was a serious-sounding field, I tought I'd be better off than with my previous employer. Which was kinda the family-agency where you can do pretty much anything you want without any real concequences, nor structures. I liked it, but the professionalism was missing.

Turns out, they do operate more professionally, but the intern mood and commitment is awful. They all pretty much bash on eachother. And the root cause of this and why it will stay like this is simply the Project Lead.

The plan was that I was positioned as glue between Design/UX and Backend to then make the best Frontend for the situation. Since that is somewhat new and has the most potential to get better. Beside, this is what the customer sees everyday.

After just two months, an retrospective and a hell lot of communication with co-workers, I've decided that there is no other way other than to leave.

I had a weekly productivity of 60h+ (work and private, sometimes up to 80h). I had no problems with that, I was happy to work, but since working in this company, my weekly productivity dropped to 25~30h. Not only can I not work for a whole proper work-week, this time still includes private projects. So in hindsight, I efficiently work less than 20h for my actual job.

The Product lead just wants feature on top of feature, our customers don't want to pay concepts, but also won't give us exact specifications on what they want.
Refactoring is forbidden since we get to many issues/bugs on a daily basis so we won't get time.
An re-design is forbidden because that would mean that all Screens have to be re-designed.
The product should be responsive, but none of the components feel finished on Desktop - don't talk about mobile, it doesn't exist.
The Designer next to me has to make 200+ Screens for Desktop and Mobile JUST so we can change the primary colors for an potential new customer, nothing more. Remember that we don't have responsiveness? Guess what, that should be purposely included on the Designs (and it looks awful).
I may hate PHP, but I can still work with it. But not here, this is worse then any ecommerce. I have to fix legacy backend code that has no test coverage. But I haven't touched php for 4 years, letalone wrote sql (I hate it). There should be no reason whatsoever to let me do this kind of work, as FRONTEND ARCHITECT.

After an (short) analysis of the Frontend, I conclude that it is required to be rewritten to 90%. There have been no performance checks for the Client/UI, therefor not only the components behave badly, but the whole system is slow as FUCK! Back in my days I wrote jQuery, but even that shit was faster than the architecuture of this React Multi-instance app. Nothing is shared, most of the AppState correlate to other instances.

The Backend. Oh boy. Not only do we use an shitty outated open-source project with tons of XSS possibillities as base, no we clone that shit and COPY OUR SOURCES ON TOP. But since these people also don't want to write SQL, they tought using Symfony as base on top of the base would be an good idea.
Generally speaking (and done right), this is true. but not then there will be no time and not properly checked. As I said I'm working on Legacy code. And the more I look into it, the more Bugs I find. Nothing too bad, but it's still a bad sign why the webservices are buggy in general. And therefor, the buggyness has to travel into the frontend.

And now the last goodies:
- Composer itself is commited to the repo (the fucking .phar!)
- Deployments never work and every release is done manually
- We commit an "_TRASH" folder
- There is an secret ongoing refactoring in the root of the Project called "_REFACTORING" (right, no branches)
- I cannot test locally, nor have just the Frontend locally connected to the Staging webservices
- I am required to upload my sources I write to an in-house server that get's shared with the other coworkers
- This is the only Linux server here and all of the permissions are fucked up
- We don't have versions, nor builds, we use the current Date as build number, but nothing simple to read, nonono. It's has to be an german Date, with only numbers and has always to end with "00"
- They take security "super serious" but disable the abillity to unlock your device with your fingerprint sensor ON PURPOSE

My brain hurts, maybe I'll post more on this shit fucking cuntfuck company. Sorry to be rude, but this triggers me sooo much!

Comments
  • 2
    Holly.... I'm with you for the leave
  • 2
    Run while you can. This is one of the worst stories I heard in years!
  • 1
    I don't wanna sound rude, nor am I saying that I know your situation than you do...

    But, the project shouldn't matter to you, as much as it should matter how much you can make out of it for yourself. I'm not sure what exactly your role is in the project, from your description it's front end I guess... but anyway you sound like you're trying to solve all of it in one go.

    No company will ever agree to 90% refactoring. Except Uber lol, they actually did a 100% refactor in parallel to their legacy project.

    I was in a similar situation myself. I came to an agreement with the CEO that each ticket would be over-estimated. With the "over" time being spent on code-cleanup. O a ticket that takes a day, we'd be allowed 1.3 days, 0.3 days for code clean up, unrelated to the ticket itself.

    If you can manage to pick up your front end team together, and at least clean the front end up, step by step. Then you'd be in for a great reward in the long run.

    ...
  • 1
    That "tech lead" means nothing. No company would ever be like "don't fix my shit". If you manage to throw in some good examples here and there. Eventually your team will pick up.

    At any rate, you have nothing to lose, you're leaving. So it might as well be the time to try an bypass that shit tech lead you're talking about.

    Oh and screw React...
    Native + Reactive architecture ftw. Just not React.

    We are currently using RxKotlin/java with Android. And RxSwift with iOS. All native, with an architecture similar to Redux and MVVM (kind of a mashup), and it's been smooth sailing after a year of absolute garbage.

    I wrote too much and forgot the point haha...

    I wanted to say, that if your company realizes how shit the project is (mine did), and if you somehow manage to at least make a dent. The reward maybe worth it.
Add Comment