.

your boss sounds like an idiot. he absolutely should be telling her to fix the scripts.

about ~30 mins after i left work, she implemented all the fixes i had made, pushed/merged them like they were her own, and made some snarky comment on her PR. Lol. Luckily I had emailed my boss with a list of my fixes from my branch and ways the scripts could be improved - maybe he forwarded it to her.

But yea with my boss - who's better to fix these scripts, some guy who spent an hour reading and understanding them with basically 0 experience, or the person who wrote them? She's busy doing something else for a different project this week (one that I don't touch at all), thank god. So maybe he thought she should focus on that.

They are REALLY important scripts though. Stuff we're eventually gonna deliver to customers. So yea, I don't really want these things fired off in some haphazard manner, I review basically everything that gets pushed now and run tests of my own. I almost always can break something. That's kind of my role lately. Break and troubleshoot.

Usually i get this irritated by thursday so this isnt a good sign for the week

Crystal looks cool. Will research.

I had a first today... one of my teammates has gone on rampage mode removing any validation logic I put in place (or replacing it with a much less flexible version). Naturally, I had already wrapped it all try catch, error checking, etc so apart from api requests that were working now failing there wasn't too much damage. This is the same person who claimed in a previous team meeting that adding validation was too much work with too little gain. My manager asked me to merge main dev branch into the feature branch I've been working in. After seeing the rampage this dude has gone on I actually had to revert a merge... the first time I've ever done so.

Several things wrong with this.

Why are two people burning time working on the same issue?

Why are you emailing your boss changes? Make a PR and have him and her in there to review.

Also it's weird that people blow off meetings. Did she accept the meeting invite? If not, perhaps she didn't even see it.

Do your coworkers have 1-1s with their managers? Leaving snarky comments is really unprofessional.

In case you're wondering how you're supposed to catch errors, this is how you're supposed to do it (/sarcasm)

This is from someone on the verge of retiring that has been working in this kind of role for many many years.

wtf, run run run run

ok whewww where do I begin. I typed up a long post but it probably won't reflect well on me at all so I deleted it.

2 people weren't working on this, I brought this to the attention of my coworker and boss on friday, boss told me we'd deal with it monday, monday AM she just never shows up, so we fixed it.

I wanted to giver her a chance to review the changes b/c they're her scripts. I guess she finally did - but she just copy pasta'd all my stuff into her branch and pushed it, with some modifications of her own (some of which I know for a fact are going to break tomorrow).

There was no meeting planned, it was impromptu, but she'd told people she'd be there around 10:30 and didn't come til 12 so we just kinda waited around for her. But on the topic of blowing off meetings, yea even if they're scheduled that's known to happen.

My boss is kind of timid, he doesn't have a lot of 1 on 1's.

Basically this job sucks and I need to have an exit strategy but I like the challenge it brings and it's a really unique position to be in so I want to ride it out, even though I'm positive it's going to end in near certain failure.

I've had this happen before. Maybe slightly different process but the same in the end. We use a visualization js library called AmCharts. In chronological order this is what happened:

1) My teammate was not handling unsetting of existing AmCharts instances correctly
2) I create a branch off the main dev branch
3) I wrote some code that does correctly unset it
4) I created a merge request into his branch and asked him to review it just to make sure I wasn't breaking something he was working on.
5) He deleted the source branch of the merge request
6) He rejected the merge request
7) He copy pasted what I had done then pushed it as his own updates

Did he at least throw and catch his own error, like a Professional?

Well, I guess you are lucky you avoided:
8) Murdered someone and planted my DNA at the scene of the crime.

Man some of you guys work or have worked in toxic places.

Actually I guess my side job had some of that. Not fun.

Here's something part of his latest commit

That's solid right? I mean, if the proceeding logic is now counting on validation having passed then just logging out the error should be fine right?

Craggoo,

Between the amount you are paid and the coworkers you are given I feel like you are not being provided anywhere close to a proper environment. You should be putting all your effort into finding a new job. The market is actually insane right now you can def find something way way better.

Well the other part is why even have it in a try/catch? It's just an if/else. Unless data is null I guess.

HELP - I have this zombie EC2 instance that I'm about to get billed for on my personal test account. I cannot for the life of me figure out how to kill it. I tried terminating and stopping it. But it just keeps coming back to life. Google isn't helping either. Any ideas?

Ok looks like maybe I started it with elastic beanstalk - from some tutorial like a month ago. It's trying to shutdown now. Hopefully I didn't launch elastic beanstalk from some even more macro wizard or something.

Does AWS have somewhere you can see all the stuff you have running?

I was talking with a recruiter recently and he mentioned that "cs degree or experience" generally equates to (without a cs degree) 4-6 years of experience. I have 3 and no cs degree. That could explain why I have such a poor response rate. I feel my resume is about as good as it can be right now. I asked in a previous post for some feedback on it but only adios ever offered some advice in pm. In case it's not obvious, I have been spending a lot of time the past few months job hunting and having very depressing results.

Data will always be an object. I only showed showed you what he put in place of what I had. Previously, I validated it was an object. He now assume that it is. If I were to pass through (for example) a NaN, undefined, null or something else whacky it would now super fail. It would have previously thrown an error.

What ultimately caught the error before? Is data something that you control? If so I'm not a fan of throwing errors for internal conditions like that. Although his patch job on your throw is definitely much worse

Beanstalk has a separate console that creates "apps" and will auto restart a dead EC2 instance (thats basically the whole point of beanstalk).

Go to the beanstalk section, and either kill the "app", or stop it or set the min amount of servers to 0. Anything really

billing on aws is such a beating.
every month it's a complete ****show here when we get our portion of the bill and my boss freaks out and we spend time trying to clean **** up.

We've asked for weekly updates so we could shut stuff down but that would be too much work for our finance people. I offered to write a script to make it "live" so everyone could see their current charges and they got super defensive. If everyone could see their current charges at our company we'd probably save hundreds of thousands a year. But no, some schmuck in NJ has to keep his job.

Yeah, AWS billing is a **** show at the best of times. You can get regular CSV updates of all of your billing details put in S3. We use to use CloudHealth (which was pretty decent - but had a few flaws) but now we process the data ourselves and can explore it. It's super useful and definitely saves a ton of money by seeing stupid **** right away and finding obvious places to optimize.

How do people get away with this is amazing. You don’t have to do any work, just steal credit from your teammates. What could go wrong?!

Thank god we are not the only ones. We are getting ****storms for spending too much on AWS, yet it's impossible to get any good estimation on where the costs are coming from. First of all, not everybody can access billing info. Then, we are receiving a weekly report on costs that covers the whole company, where costs are not segregated by anything. If we ask our finance people for help with specifying the cost report, they have no idea who even created it.

What I am going to try is to change a couple of tags that seem to coincide with what appears in these mysterious reports, maybe the "LoveThee's team line" will change to "LoveThee's server1" "LoveThee's server2", etc...


It's almost as if Amazon were benefiting from the opaqueness of billing.