matt

At one of my previous jobs, we acquired another company that was a good idea but only had a couple of customers. Once we started upselling their app to larger customers, their backend immediately folded under the weight. It was a code red situation as more on-boarded and we needed a solution fast.

After 2ish years, the business called it a wash and stopped selling the app. The acquired founders stayed the remaining period of their contract and left the second they could. Every engineer who helped out felt so defeated because it was a lot of work for it to all mean nothing.

At one of my previous jobs, we acquired another company that was a good idea but only had a couple of customers. Once we started upselling their app to larger customers, their backend immediately folded under the weight. It was a code red situation as more on-boarded and we needed a solution fast.

Unfortunately for the engs assigned to the project, as they fixed things they also needed to add tests. I don't mean they needed to add regression tests, they needed to add tests *period*. Every change was a gamble and nobody knew the full effects of what they did since it was all so intertwined.

At one of my previous jobs, we acquired another company that was a good idea but only had a couple of customers. Once we started upselling their app to larger customers, their backend immediately folded under the weight. It was a code red situation as more on-boarded and we needed a solution fast.

Of course, they used mongo (which they didn't know how to use) and also didn't have any indices set up so the DB was always on fire. And they were already on the highest tier of Heroku, so they weren't paying their way out of these issues. Especially not with the few dollars coming in.

At one of my previous jobs, we acquired another company that was a good idea but only had a couple of customers. Once we started upselling their app to larger customers, their backend immediately folded under the weight. It was a code red situation as more on-boarded and we needed a solution fast.

IIRC the way this endpoint worked is that you always got some base data that it returned. You could add some stuff to the request to either expand one of the fields, add a new field, or slice some fields out. You could call this endpoint multiple times in completely unique ways on the same page.

At one of my previous jobs, we acquired another company that was a good idea but only had a couple of customers. Once we started upselling their app to larger customers, their backend immediately folded under the weight. It was a code red situation as more on-boarded and we needed a solution fast.

To start, this was a large Node app, written entirely with callbacks with only a few large files. The nesting was so deep in parts that you could scroll for 1m and see literally nothing. To make it even better, they (unintentionally) added *recursion* between some of these deeply nested sections!!!

At one of my previous jobs, we acquired another company that was a good idea but only had a couple of customers. Once we started upselling their app to larger customers, their backend immediately folded under the weight. It was a code red situation as more on-boarded and we needed a solution fast.

Since their team was basically two engineers, my company took some people from our side of the fence and assigned them to work on the other codebase. Easy right? Well, when you tried to talk to people about the problems the app was facing and root causes, you were met with exactly this reaction:

I don't support edits but I think this site majorly needs a first class retraction feature. A lot of misinfo/miscomm is spread simply because some post gets large reach and the correction happens in the replies or a separate post. I can't think of a good reason why we shouldn't do this like asap.

I know we're always at each other's throats over one minor thing or another on this site, but there are definitely a lot of people who act in good faith. When it comes to stuff like this, your only option is to really delete a post... ... but that loses point-in-time criticism / context. Not good!

Excited for the next *2shell to drop so my team and I can once again traumabond during remediation into the early hours of the morning 🙂‍↕️

Man, I miss my old T-series Fujitsu Lifebook. Wish there was a modern version. In HS I installed Jolicloud and then Crunchbang on it. A bunch of things didn't work because of driver issues, but I was able to squeeze so much life out of the thing and set up a basic programming env to mess around.

Yo this SUCKS ASS

Like a significant portion of the original artists and animators did NSFW stuff and SG itself leaned heavily into the "sexy" aspect. Fucking ZONE worked on the game... WTF is this shit man?

I really don't understand why people are clowning on this. It's obvious that copyright is one of the very few tools that small artists have to maintain the moat that keeps them fed; without copyright it's significantly more of a gamble whether or not you'll turn a profit off of your creative work.

Like, I am very anti-copyright but I understand that in current society it's a necessary evil to some degree. It's not crazy to think that we should have an uneven enforcement of copyright for small artists vs large corporations until such a time as we have UBI. How is this even controversial?

> One union-supportive person pointed out [...] the union would have been able to negotiate with Microsoft for severance like the other unions were doing. However, that same person acknowledged that a union may not have been able to secure as good a deal as Schafer had. Unintentionally hilarious

Like I am very pro-union, but this whole ordeal was a clusterfuck and frankly embarrassing. It really feels like CWA's unionization approach was a bad match for DF's company culture and created a lot of mistrust from day one. Not seeing most would be ineligible and flagging it as an issue is bad.

This guy is weird as shit but nobody on this site could ever get me to hate him. Like, his fellow 1%ers are focused on a global fascist project, meanwhile Bryan is just like "erm, actually, I've been measuring my wife's morning clit length for the last 128 months and you are mistaken." Amazing.

Bought produce, unpacked it, and realized it was all slimy. Tossed it, but decided to do the responsible thing and go back to let the store know so they could check the others just in case. Don't want anyone to get sick, you know? The staff were, unfortunately, teens who couldn't have cared less.