invite responseComments 1 - 2 of 2 Search these comments
1
Tenpoundbass
2023 Jul 11, 12:32pm
Tenpoundbass
2023 Jul 11, 12:32pm
These out sourced IT companies that dominated by Indians, go out of their way to sabotage contractors that don't work for them, to make them look bad to the employer. So they can creep in more services or get people they are connected with in those positions. They get away with it, because the company's management are brainwashed to think that if it wasn't for that IT company their network would be in grave danger.
I wonder if these companies are the ones who send out the exploits, malware and ransomware so they can appear to be of value to companies they manage..
That was the experience I had. Not only did they phase me out, but the team that integrated my suites to some crappy Cloud ERP CRM, were also Indians affiliated with them. They still aren't fully live some 3 years later. After giving me shit trying to throw my apps and methods under the bus, talking shit about it. At least I made a working solution in a few months not years..
It's why I have decided to leave the Enterprise until a lot changes and comes back full circle. I just have way too many "Go Fuck Your Self!" left in me to put up with the way shit is now, in the Enterprise. Take that shit from no talent asshats that has to sabotage others to create job security for themselves. .
I wonder if these companies are the ones who send out the exploits, malware and ransomware so they can appear to be of value to companies they manage..
That was the experience I had. Not only did they phase me out, but the team that integrated my suites to some crappy Cloud ERP CRM, were also Indians affiliated with them. They still aren't fully live some 3 years later. After giving me shit trying to throw my apps and methods under the bus, talking shit about it. At least I made a working solution in a few months not years..
It's why I have decided to leave the Enterprise until a lot changes and comes back full circle. I just have way too many "Go Fuck Your Self!" left in me to put up with the way shit is now, in the Enterprise. Take that shit from no talent asshats that has to sabotage others to create job security for themselves. .
2
fdhfoiehfeoi
2023 Jul 11, 12:40pm
fdhfoiehfeoi
2023 Jul 11, 12:40pm
That reminds me of another place I worked at. Really good company overall, although the pay(at the time) was low for the industry, and benefits were pretty poor. Anyway they had the bad habit some larger companies have, of relying on a lot of contractors for their software engineering. I noticed a few times that pull request reviews seemed to take almost no time at all. Spoke with a newer junior dev who was permanent, and he confirmed that as soon as a PR went up, within seconds there were eight approvals.
Same company working with another permanent employee once, we pulled up a repo we wanted to investigate, and noticed a warning in the IDE about code being nested 97 levels deep!? I-shit-you-not...
Same company working with another permanent employee once, we pulled up a repo we wanted to investigate, and noticed a warning in the IDE about code being nested 97 levels deep!? I-shit-you-not...
Pros
Loved the people I worked with on my team(for the most part). Company pushed a lot of newer tech. Pay and bonus are very competitive for the industry.
Cons
I was hired as a remote employee, living out of state. The laptop I was shipped did not have permissions that would allow me to install or configure any settings on it, and no one who remoted in was able to fix it. Not the worst thing, but the fact that I was left unable to perform my job for a MONTH is what really set it apart. I constantly brought up the need to my team, my boss, and IT/helpdesk, and after a month they finally figured out I needed to be shipped a new laptop. During my time there the company pushed out several different security products and updates that did everything from removing permissions, slowing down computers till they were almost unusable, to bricking a senior software manager's laptop. It was as if they never tested anything. The permissions limitations where so bad more than a few engineers quit over them, and people on our team said he was hesitant to recommend the company, or even take part in interviews without warning people about the ongoing permission problems.
Despite using private Azure Devops agents that basically served as containers, the automation leadership still included Docker in CI, with the explanation that it was easier than installing dependencies directly on the machines. What they never included was instructions or training on how to properly setup Docker, causing CI collisions due to same named containers, a problem that plagued automation for a year before finally installing the dependencies. Nothing was built to scale. The QA leadership also allowed Azured Devops to serve as our CI tool, despite it's lack of reporting support for Karate, the framework chosen for API testing. It seems that no one in the company ever bothered to ask if a SW choice was really best, or just the latest. As a result, there were numerous problems throughout the SDLC due to choosing tools the company was not mature enough to use, or did not work well with other selected technologies.
The quality was so poor that our team routinely spent entire months shipping no new features due to production outages. And this was not isolated to just our team. It was clear that pushing out new features was the priority, not properly testing them, and never cleaning up tech debt. The team also had no concept of what the purpose of a sprint was. Tickets were routinely closed as completed when the work was never released in order to make the points look good. Features would linger for months, making releases unstable, and dangerous because whether it ever released or not, it was merged to master. The scrum masters job at the company seemed to be enabling the teams bad habits, the opposite of what what the role should do.
In a little over a year I transitioned between four different bosses. The company had to shutter an entire division due to Medicare payout changes. But they also laid off a large number of people outside the division, seemingly in order to boost the stock price, as without the sale to CVS, they would have likely gone under. And this is a company that had just IPO'd a year and half prior. It was clear the issues I saw were systemic, and came from the C-level. Blame and problems always rolled downhill. Management made decisions without consulting their employees. Issues were constantly raised, but no one in leadership listened, or had the power to act.
Leadership was extremely change resistant, despite seeming to embrace the latest and greatest. Employees were routinely discriminated against, and let go for pushing for adoption of industry best practices, or suggesting the current methods were not the best way to do things.
Other corporate issues: I was paid late in violation of California state law twice, a practice so common(paying employees late) the HR slack channel was riddled with examples. Also, at the end of 2022, social security was not withheld from anyone's paycheck for two months. And finally, right before I left, someone asked me about forcing an evaluation through the system that was out of date, and needed to be re-done. I mentioned the only way to process that evaluation would be to change the evaluation date, but doing so would constitute Medicare fraud. I never heard from the person after that.
Advice to Management
If you get an opportunity to go somewhere else before people realize what you've done here, count your lucky stars and take it.