4 ms·

I worked there for 10 years. What is this test env you speak of? /s We had dev and prod. No version control and no testing requirements. Was a while ago for su

• tarotuser 4y ago
  Oh, we always have a test environment :) Sometimes its also called prod. Ive had the displeasure of having another team write the Cloudformation scripts, and they wrote them in such a way that none could be redeployed, or changed. And since they're domain joined windows machines, effectively un-redeployable. My first start, which died in situ, was to do the work to get stage up and running, and then clone stage into prod and changing the DNS and naming bits. Since this was a no-go, ended up piecemealing everything. It still stings too. We're nearly done and ready to go live as well. Ive been pushing for live since November. But when a single person speaks out, "delays get delayed by meetings to discuss in meetings to have meetings about delays" (note: I'm not making this up)... I shouldn't complain too much. A good 4h a workday is filled with gaming and stuff, since the enforced delays and "hurry up and waits" require me to literally do nothing. But when I do work, I'm going at the 5-10x speed I'm accustomed to going. But when it takes weeks to open up SMB from internal machines to other internal machines... there's not a lot I can do to fix broken process. And, I'm just a lousy contractor out of hundreds of thousands.