I once got a contract, early in my career, migrating marketing landing pages to a new format in which the contents of the pages (anything inside of the tag) were moved into `marketing_page_name.tmpl` files in a directory. From there they'd be pulled into a shell, and all kinds of tracking and link magic could happen from there. A few things like anchors needed new template variables instead of hard-coded links. I rea…
Hey everyone, look at this guy! With his moral compass and stuff. Ain't never gonna get your own space rocket with that attitude. All jokes aside, being trustworthy/ethical pays dividends over the course of peoples lifetime and will often times reward you in surprising ways.
I automated my job over a year ago and haven't told anyone
361–370 of 510 posts
Re: I automated my job over a year ago and haven't told anyone
#362Earlier quoted context omitted.
Is that really bullshit work? I seriously doubt you’d be able to completely solve the problem of lost luggage. You could cut it down, yet you can’t scale down the number of jobs dealing with it very easily (one per airport at least, and you can’t hire half a person if there’s only half a workload). A similar thing could be said of bloated code.
I know nothing about luggage transit, and any idea of a solution for lost luggage I could come up with is more likely naive than not. Could you define why lost luggage is an unsolvable problem? What makes it so difficult?
Re: I automated my job over a year ago and haven't told anyone
#363Earlier quoted context omitted.
I worked at a company that operated like that. Each manager could only put in so many high marks. Company had something like 5000 employees. I felt good that I often got the highest mark, but others were doing well too, they deserved more. I finally asked my boss, he told me. “I figured out that other being told in an email how to award perf reviews… nobody checks… so I give everyone the highest reward.”
Managers who just give everyone the highest rating are generally the reason that these forced curve policies are created.
Re: I automated my job over a year ago and haven't told anyone
#364I once had a coworker who told me the story of someone who fell through the cracks and quite literally get lost in the bureaucracy of a fortune 50 company.
To set the stage, my coworker was an investigator who primarily focused on physical security, legal and HR investigations. We worked at a very large company (around 140,000 employees) and during the 90s/early 2000s one of the primary ways they grew was through mergers and acquisitions.
Well, during this time period the company went through an acquisition spree, purchasing hundreds, maybe even thousands of smaller companies in very high margin, specialty products. They would then optimize their costs (read: layoff a good portion of their workforce like R&D, HR, finance, IT) and basically let the product run the course and then sell it off for about 60-80% of what it paid for it once it no longer was profitable.
As you can imagine this could make things a bit chaotic at times, where people were coming and going all the time, with constant org-changes and layoffs happening all the time.
Meet Tom. Tom was came to work at this company in the late 80s after his small company was acquired by the large company. Tom had been working at the company ever since and when he hit his 20 years at the company, he opted to retire with a full pension. He did what every good employee does, notified his manager and let him know that at the end of the month he would be retiring.
The Executive VP whom Tom reported to, who had just started about 6 months earlier asked his admin "who the fuck is this guy, I don't know any Tom that works for me". The admin replied, actually he does report to you and he has been here for a very long time. The EVP was confused and asked what he did, which nobody could really answer. So he reached out to HR and was like "hey, I have no idea who this is or what they do, can you look into this?".
Tom had a very inflated title when his old company had gotten acquired. Something to the effect of "Senior VP, Engineering" but his role was effectively customer support, providing customer support for some legacy industrial systems that the company had manufactured and deployed in the 70s/80s. Right after the acquisition his immediate boss (the acquired companies old CEO) quit, which kicked off a bit of a perfect storm. After his boss left Tom was told that he would report to one of the executives, lets call him John, of the large company, while they figured things out and that he should coordinate with some of the other customer support people to align the way the work with their customers.
A few weeks later, John was then promoted to run one of the other divisions of the company as part of the yearly promotion/review cycle. Before John had moved on though, he had written the performance review for Tom which consisted of your doing a great job, keep working with the support team and going forward, they will have a better feel for your performance and manage your workload. When Tom tried to meet with his new boss, the new boss cancelled several meetings and then said "Just keep doing what your doing, only let me know if we have issues".
As the company bought and sold companies like playing cards, a culture of keeping your head low while looking busy took hold of the company and nobody wanted to be the sqeaky wheel about anything. Tom had a set of tasks and reports that he was responsible for and he worked diligently on those tasks. Since there weren't any issues that he couldn't take care of, he never needed to meet with his direct manager. Other people in the company saw his title and who he reported to and generally thought he was some sort of bigwig and avoided talking to him for fear of getting on an executives radar. Each year, his boss would rate him as meets expectations and his admin assistant would ask the customer support people how he was doing, which would always respond with "no issues".
However, about 2-3 years after Toms old company was bought, they stopped selling the product and put the things Tom supported went into a maintenance only status. Weeks, months, years and then decades went by and every week Tom would sit in his office, waiting for support phone calls and deliver his report on Friday.
From the investigation, they had found that over the last 10 years that Tom was employed at the company there were only 2 customers who paid for support. 2 years before Tom retired, one of the customers didn't renew support and when they reached out to the other customer they responded "we have no idea what this is for, we just pay the invoices when we get them".
They estimated over the last 10-15 years at the company, that Tom worked approximately 20-30 minutes/week but had otherwise followed all company policies and procedures.
Re: I automated my job over a year ago and haven't told anyone
#365Earlier quoted context omitted.
Why would he be rewarded? They would likely try to save that $90k by replacing him, or give him a lot more work with very little increase in comp. If there's anything I've learned in 10 years, you keep your mouth shut when things are easy because if you speak up they screw you with more work and the same (or nearly so) pay.
This is a very cynical way of looking at things. And maybe rightly so given your experience. Every job I've ever had though there's never been a shortage of work - the few examples that I can recall of whenever one of my engineers frees up a significant amount of time I gave them harder things to do and a recommended a raise (Im a lead not a people manager) to go along with it.
Re: I automated my job over a year ago and haven't told anyone
#366Many subreddits are simply themed containers of creative writing. With all the media attention the AntiWork subreddit has gotten lately that brings more karma farmers and therefore more fiction. It's an entertaining read, but not likely true.
Many subreddits are simply themed containers of creative writing. One really annoying trend I am seeing in some mainstream news publishing online is repackaging social media clips and "reporting" on them as if NewsWeek breaking a story, Reddit and TikTok seem to be the current darlings of this form of phone it in journalism.
Re: I automated my job over a year ago and haven't told anyone
#367Once upon a time, long ago, there was a company of Lisp programmers. It was so long ago, in fact, that Lisp had no macros. Anything that couldn't be defined with a function or done with a special operator had to be written in full every time, which was rather a drag. Unfortunately, the programmers in this company--though brilliant--were also quite lazy. Often in the middle of their programs--when the tedium of writing a bunch of code got to be too much--they would instead write a note describing the code they needed to write at that place in the program. Even more unfortunately, because they were lazy, the programmers also hated to go back and actually write the code described by the notes. Soon the company had a big stack of programs that nobody could run because they were full of notes about code that still needed to be written.
In desperation, the big bosses hired a junior programmer, Mac, whose job was to find the notes, write the required code, and insert it into the program in place of the notes. Mac never ran the programs--they weren't done yet, of course, so he couldn't. But even if they had been completed, Mac wouldn't have known what inputs to feed them. So he just wrote his code based on the contents of the notes and sent it back to the original programmer.
With Mac's help, all the programs were soon completed, and the company made a ton of money selling them--so much money that the company could double the size of its programming staff. But for some reason no one thought to hire anyone to help Mac; soon he was single- handedly assisting several dozen programmers. To avoid spending all his time searching for notes in source code, Mac made a small modification to the compiler the programmers used. Thereafter, whenever the compiler hit a note, it would e-mail him the note and wait for him to e-mail back the replacement code. Unfortunately, even with this change, Mac had a hard time keeping up with the programmers. He worked as carefully as he could, but sometimes-- especially when the notes weren't clear--he would make mistakes.
The programmers noticed, however, that the more precisely they wrote their notes, the more likely it was that Mac would send back correct code. One day, one of the programmers, having a hard time describing in words the code he wanted, included in one of his notes a Lisp program that would generate the code he wanted. That was fine by Mac; he just ran the program and sent the result to the compiler.
The next innovation came when a programmer put a note at the top of one of his programs containing a function definition and a comment that said, "Mac, don't write any code here, but keep this function for later; I'm going to use it in some of my other notes." Other notes in the same program said things such as, "Mac, replace this note with the result of running that other function with the symbols x and y as arguments."
This technique caught on so quickly that within a few days, most programs contained dozens of notes defining functions that were only used by code in other notes. To make it easy for Mac to pick out the notes containing only definitions that didn't require any immediate response, the programmers tagged them with the standard preface: "Definition for Mac, Read Only." This--as the programmers were still quite lazy--was quickly shortened to "DEF. MAC. R/O" and then "DEFMACRO."
Pretty soon, there was no actual English left in the notes for Mac. All he did all day was read and respond to e-mails from the compiler containing DEFMACRO notes and calls to the functions defined in the DEFMACROs. Since the Lisp programs in the notes did all the real work, keeping up with the e-mails was no problem. Mac suddenly had a lot of time on his hands and would sit in his office daydreaming about white-sand beaches, clear blue ocean water, and drinks with little paper umbrellas in them.
Several months later the programmers realized nobody had seen Mac for quite some time. When they went to his office, they found a thin layer of dust over everything, a desk littered with travel brochures for various tropical locations, and the computer off. But the compiler still worked--how could it be? It turned out Mac had made one last change to the compiler: instead of e-mailing notes to Mac, the compiler now saved the functions defined by DEFMACRO notes and ran them when called for by the other notes. The programmers decided there was no reason to tell the big bosses Mac wasn't coming to the office anymore. So to this day, Mac draws a salary and from time to time sends the programmers a postcard from one tropical locale or another.
[0] https://gigamonkeys.com/book/macros-defining-your-own.html
Re: I automated my job over a year ago and haven't told anyone
#368I once almost completely automated my job, and didn't hide it. The job was to load data files into the backend system. The problem was there there were almost as many formats (~80) as there were partners sending data (~120), not just in structure but in content (deltas, full replace, etc.). This job was burning people out every 6 months, and I was the hapless next victim who was just looking to break into a tech posi…
Re: I automated my job over a year ago and haven't told anyone
#369Earlier quoted context omitted.
Even if that were true, no harm done… But imagine for a minute it isn't. What's the point of farming karma on a throwaway account ? Plus, we are social creatures, and sometimes we just need to offload our personal stories. Quite often there's a new fun thing that I wish I could write about or tell the world, but I don't because of real consequences to some people, or even myself. Recounting these stories is cathartic…
The harm done is that impressionable young people on /r/antiwork are given false hope in their dream of getting paid to do nothing so they can play more video games.
Re: I automated my job over a year ago and haven't told anyone
#370I once almost completely automated my job, and didn't hide it. The job was to load data files into the backend system. The problem was there there were almost as many formats (~80) as there were partners sending data (~120), not just in structure but in content (deltas, full replace, etc.). This job was burning people out every 6 months, and I was the hapless next victim who was just looking to break into a tech posi…
That’s a bit sad, the way you told the story sound like you didn’t make the place better even though you could have.