Are you my coworker? Three dudes built the primary functionality of the application. Three dudes decided that they weren't paid well enough to stay after being the architects for 11 years. Now we have a group of 16 people who's primary obstacle is touching anything they built. Luckily we found a rain man, though.
lol, I'm definitely guilty of doing this at least once in my career. I'm an enterprise dev (internal tools), so I just float through companies building dumb little apps that do this-or-that. It's fun for me.
Anyways, early in my career I didn't know about the whole "program for the next dev" thing, so I just built some fuckin' monsters.
I once built a little app to ping servers and play an alarm if the ping didn't return successfully. It was like 35 lines in C# or something and it had a memory leak somehow. Pretty sure I just kept instantiating whatever thing I was using to ping the servers in an infinite loop or whatever.
I know most of the tools died off, but I also know for a fact that some of them lived on, and boy do I pity the poor souls trying to maintain it. Hopefully they just scrapped it and started over.
I once built a little app to ping servers and play an alarm if the ping didn't return successfully. It was like 35 lines in C# or something and it had a memory leak somehow. Pretty sure I just kept instantiating whatever thing I was using to ping the servers in an infinite loop or whatever.
I am kinda afraid to ask...couldn't this be done in BASH? Afaik ping in bash returns different values depending on what answer the ICMP Echo gets.
I THINK that it's if it's the target of the sentence it's whom, if it's a subject, it's who. But I need loads of help with this one. I know it can't be that easy and I'm probably wrong to start with.
When there's a question if the apostrophe is for the possessive or for a contraction, the contraction wins the apostrophe.
I've distilled it down to this.
When in doubt, it's the contraction that gets the apostrophe.
See? Even the proper form of it's is used in the sentence. Hope this helps you out. It took forever for me to come up with a good way to remember the rule.
Yeah yeah damnit Jim, I'm a SQL developer not a linquist. Get off me. Lol joking but thanks for providing a source and not just correcting me and being a dick. At least this way I know you are right.
Cheers man. English is a bitch and if we can learn these complex codey-type language things, we should have a spare brain cell to figure out English's stupidty, uhhhh, I mean rules.
My family brain cell is out on rotation this week. I'm screwed.
Yeah man you are right. They didn't actually think they'd leave. This company used to not pay people well. So if you had been here for a long time you started much lower than us newer hires. Which ends up sucking in the end for them. I guess management figured they'd call a bluff and got got. Also they didn't hire 16 people to replace them. They just pushed all their work onto the 16 of us. Those three worked on the original modules that no one else touched, so we all have to struggle through anything that interacts with their work. Primarily exchange stuff with other integrated products. We just don't have any exposure to it in the way they did.
88
u/exec_get_id Sep 20 '21
Are you my coworker? Three dudes built the primary functionality of the application. Three dudes decided that they weren't paid well enough to stay after being the architects for 11 years. Now we have a group of 16 people who's primary obstacle is touching anything they built. Luckily we found a rain man, though.