Tell them to give you 17 more people or be ready for it to take a while. Do a weekly or monthly progress email out to the stakeholders with a rough ETA on completion.I've been given a task recently that can be paraphrased as "this other team made this, we want to do it as well, make it happen." But upon further examination of it since February I've come to realize that what this other team made took them over a year and they have a team of 18 people. With 15 of them actively developing it. I've been saddled with it because my team is mostly older people with loads of experience in old school database infrastructure and no knowledge whatsoever of object oriented programming, Not even of coding languages other than SQL, COBOL, and some straight C from back in the day.
I don't mind working on this team but the result is that I get thrown anything that requires understanding python, java, or anything inbetween. Like it stunned my manager when she saw I had reduced a bunch of their ancient stored procedures to a few python functions. They finally embraced that so I made a python function library for them.
But anywho, this project becomes worse the further I get along. I've gotten pieces of it working but the overall solution this other team developed is fairly insane. They have 5 different code repos that support it. That all build off of eachother in this convoluted deployment staging script. The worst part about it is that they have tons of python scripts that are executed by the CI/CD pipe itself and serve no other purpose other than "pre-loading" other parts of our infrastructure.
Like, they want to add in some feature that does X. This feature requires servers, databases in other locations, etc but the primary application can't make any of this. So they have their infrastructure repo where they onboard a dozen python scripts that go reach out and create whatever they added to the primary application to make use of. This executes only when they merge to master on the main application. But also requires them to add in tons of custom things each time they want to make a change the primary thing can't even do. It's really hard to keep track of and I can see why it breaks constantly.
But I dislike leadership being all "why aren't you done yet?" when I am the only person in our entire org working on it. Seems silly. On the plus side I am not tasked with any of the older database infrastructure stuff at all.
Anaconda. IT sent an email out at 6pm on Friday about the situation; apparently there's some deadline and all accounts associated with our domain are going to be blocked.lol, someone get audited by microsoft?
God damn we hire lots of Indian people in corporate America
You can actually get away with this for quite a long time. But once you're on the radar they will fuck you hard.Apparently, no one thought that as an enterprise we needed to have proper licenses instead of everyone just using the free tier.
dumpsterfire.gif
Yeah, I’m not sure how long people have been using Anaconda, but I’m sure it’s been a good 5 years.You can actually get away with this for quite a long time. But once you're on the radar they will fuck you hard.
I had a massive solution for Data Build Tool that I had built out using DBT-Core, their free offering library. Like any other package. I had a single "lol developer free seat" in DBT cloud for like 3 years. Where I heavily utilized its scheduling, error handling, and notification features.Yeah, I’m not sure how long people have been using Anaconda, but I’m sure it’s been a good 5 years.
It makes sense, they’re going to spend time on larger offenders first. I know we’ve been ramping up on ops functionality built in house. Around 18 months ago they went live with using ML to process images for damage inspection of equipment in the field. There’s been a general increase in getting our collective asses out of the 90s. 100 yr old companies few.I had a massive solution for Data Build Tool that I had built out using DBT-Core, their free offering library. Like any other package. I had a single "lol developer free seat" in DBT cloud for like 3 years. Where I heavily utilized its scheduling, error handling, and notification features.
They only caught on recently. At least it is quite cheap for an enterprise platform so I didn't get many complaints.
That’s awesome. A bit surprising though as H1B1s are usually the easiest to abuse since they’re so afraid to jump jobs or just quit. I wonder what their reasoning was for this. Any ideas?Company which acquired mine (Broadcom) has explicitly started limiting H1B renewals. Its interesting to say the least. VMware was very liberal with H1Bs.