3 ms·

I built software to track our traders. This was at one of the largest investment banks in the world and at the time they had a rudimentary system for tracking a

I built software to track our traders. This was at one of the largest investment banks in the world and at the time they had a rudimentary system for tracking and recording their in-house traders activities - orders, trades, and other order/trade related information. At the time, the rudimentary system was built mostly to comply with government regulations, and was later modified by someone else to capture and report a larger scope of information about the traders to a higher-up department. My system was built entirely from scratch because the existing system was antiquated, poorly structured, and really not conducive to future expansions. After testing and implementing my system, a handful of traders lost their jobs as a result. One criteria often looked at was their number and reasons for failure to delivers (FTD's). Other than that, it's mostly automating things that I almost sort of regret. A lot of folks in the bank were fired after I wrote a series of apps that could do the work they do. Mostly repetitive tasks. Still feel bad about that but if I didn't do it, they would have hired someone else and at the time I was really, really in dire need for a paycheck.

jiggawatts 4y ago
An ex-coworker asked me to do a 3-month contracting stint at his company where he was the head of IT. The task was to "clean up the environment" because the servers were crashing often and performance was poor. I quickly found the source of the crashes: misconfigured ethernet switch MAC address limits applied to VMware ESXi. I also cleansed the environment by finding the one working server in each cluster and then cloning it out to replace the faulty ones. These were all "pets" on life support, and I tried to make them more like identical "cattle". I went back a year later and half of the IT support team was gone. I asked what happened and the answer was: me. Apparently after I fixed up the platform the number of support requests plummeted, and a bunch of the helpdesk staff were made redundant. Oops.
- kelnos 4y ago
  I'm so torn about stuff like this. On one hand, yeah, it absolutely sucks that people lost their job based on a thing you did. But on the other hand, their jobs existed only because things were broken that didn't need to be. Essentially, bullshit jobs: it sorta feels related to the trope of someone going around a neighborhood breaking people's windows to drum up business for the local window-installation company, without the nefarious bits. I feel similarly about the rise of automation. At a global/society level, I think it's great that there are jobs humans don't have to do anymore. That leaves more people to be able to pursue "higher" things. But the reality is that some people who had jobs now don't, and might be suffering financial insecurity because of that. Our society should be helping people retrain, and keep them on their feet financially while they do so, but many places just don't have a good enough safety net for that, let alone specific programs for retraining when jobs become unnecessary.
  - jiggawatts 4y ago
    The worst part is that the helpdesk staff were nice. More than a decade later I can't remember anything else about them, except that they were all lovely people. I'm sure they got new jobs and whatnot, but I still feel bad about the whole thing. Intellectually, I agree with you that bullshit jobs ought to be eliminated, but I suspect that this process will continue to be morally a gray area until we have something like universal basic income.

jiggawatts 4y ago

An ex-coworker asked me to do a 3-month contracting stint at his company where he was the head of IT. The task was to "clean up the environment" because the servers were crashing often and performance was poor. I quickly found the source of the crashes: misconfigured ethernet switch MAC address limits applied to VMware ESXi. I also cleansed the environment by finding the one working server in each cluster and then cloning it out to replace the faulty ones. These were all "pets" on life support, and I tried to make them more like identical "cattle". I went back a year later and half of the IT support team was gone. I asked what happened and the answer was: me. Apparently after I fixed up the platform the number of support requests plummeted, and a bunch of the helpdesk staff were made redundant. Oops.

kelnos 4y ago
I'm so torn about stuff like this. On one hand, yeah, it absolutely sucks that people lost their job based on a thing you did. But on the other hand, their jobs existed only because things were broken that didn't need to be. Essentially, bullshit jobs: it sorta feels related to the trope of someone going around a neighborhood breaking people's windows to drum up business for the local window-installation company, without the nefarious bits. I feel similarly about the rise of automation. At a global/society level, I think it's great that there are jobs humans don't have to do anymore. That leaves more people to be able to pursue "higher" things. But the reality is that some people who had jobs now don't, and might be suffering financial insecurity because of that. Our society should be helping people retrain, and keep them on their feet financially while they do so, but many places just don't have a good enough safety net for that, let alone specific programs for retraining when jobs become unnecessary.
- jiggawatts 4y ago
  The worst part is that the helpdesk staff were nice. More than a decade later I can't remember anything else about them, except that they were all lovely people. I'm sure they got new jobs and whatnot, but I still feel bad about the whole thing. Intellectually, I agree with you that bullshit jobs ought to be eliminated, but I suspect that this process will continue to be morally a gray area until we have something like universal basic income.