(Replying to PARENT post)
(Replying to PARENT post)
For a non-manager in a large organization, the choices are pretty much accept your work environment or leave it. Fighting the entire company's culture as a low level employee is like trying to move a mountain by pushing harder.
To OP: Accept the pace your department moves at, and look for little victories. Your never gonna get to write a new app in a week and be a hero in your current company/department, but there is still some satisfaction to be found in ironing out little wrinkles one at a time.
If/when you leave, look for a job you want to go to, rather than just looking for a way out of your current job.
(Replying to PARENT post)
(Replying to PARENT post)
You're meeting expectations, which is great, but don't stop there. You recognize that you (and your teammates) could be doing more, so make it happen. You're entirely capable and empowered to do so:
- Fix that technical debt. - Identify better tooling and demonstrate it's value to your teammates. - Proactively find things your software could do better and write about them. Don't be discouraged if people don't bite on the first few, you'll find one eventually that's too good to not pursue.
Sure, you could accept the status quo and coast like some of your teammates, but you'll be unhappy (and bored). Do what makes you happy -- identify, evangelize, prototype and build.
All of this doesn't mean you're lazy for having posted this -- just that you need encouragement to make the things happen that'll make you happier and more fulfilled at the end of the day.
(Replying to PARENT post)
Totally deranged protestant work ethic run amok to think otherwise.
It's also extremely not this guy's fault other people have to work exploitative shit jobs during a pandemic, and his working harder (for FAANG!) isn't the thing that will fix it.
(Replying to PARENT post)
Do you know how demoralizing it is to work in an organization where the people trying to lead have no power to effect change, and the leaders are incompetent and force bad decisions on a constant basis? Where there is no real vision for the company?
The OP is describing being trapped in a tar pit, and you're saying "run faster".
(Replying to PARENT post)
(Replying to PARENT post)
FAANGS employees are salaried, and not paid by hour, because you are compensated for ROI. If it takes you one hour and you bring in lots of value, that's still a good deal. On the flip side, you could also work 60 hours week if that's what it took you to meet and exceed on the value expectations.
Still agree with much of your comment though. Since they're complaining about the situation, something does feel off.
(Replying to PARENT post)
That “million people would kill for a chance” to be at a FAANG is not the employee’s problem anymore. The moment the company extended the job offer already created “a million” job applicants who didn’t get an offer. Behaving in a way that suggests continually begging “to stay in” just to get to create the net gains for other people, the investors and top management, deserves a therapy session on personal self-worth, which is a personal problem not a business matter.
Now, as for the matter of personally going above and beyond, that’s actually a separate matter - no need for emotional entanglement of the the business reality and personal reality. If the employee wishes, as they’ve expressed, to go above what is satisfying the business (given they’ve reported no management has complained) then by all means, find more work with outside teams within the company, tactfully speak to the manager about the concern, or just leave and start a new job or venture.
The moral guilt argument over the transactional relationship between an employee and the business, though, is at best naive, and at worse unevenly extracting more energy from the employee than the business. If the company has continued to pay the employee without complain, that’s their own moral dilemma for allowing it.
(Replying to PARENT post)
I'm always impressed at how much American culture promotes labor vs. labor infighting instead of recognizing that the issue is not the 1%. It's the top 0.1% (and 0.01%) that's causing this problem.
https://review.chicagobooth.edu/economics/2017/article/never...
(Replying to PARENT post)
Lets say he decides to start being more diligent and taking the initiative to do as much work as is possible. His company is the only entity that benefits from this arrangement, and the benefit is marginal at best. Ultimately, this literally provides the resources for the company to pay the salaries of more useless workers and perpetuates the issue this post is trying to address.
(Replying to PARENT post)
Every worker's duty is purely to themselves, not some sort of bizarre worship of their employer.
Your duty to yourself under capitalism is to extract as much capital and benefit as possible from the market in exchange for your labor. If you can commit a line of code a week and still get paid your salary, you're working EXTREMELY efficiently. Even better if you manage to get a job where they're failing to get any labor from you at all.
Conversely every employer is focused on extracting as much production as possible from their employees. Efficient companies will cut off under-producing workers without a second thought and will continuously strive to minimize the cost of any employee.
(Replying to PARENT post)
You feel the bar is being set very low. The hard part of your job is working within the established environment (the technical debt?). You're choosing to put the effort in 1 day a week because you're comparing your contributions to your coworkers.
If you're unhappy in this dev environment that's one thing, and if you're unhappy with your contributions that's another.
I would try setting expectations for yourself if it's easy to impress the company. You could be a huge asset even assisting your team. It's concerning that you aren't aware of why their progress is slower and that no one has spotted your complacency. Perhaps you have something to offer as a mentor and maybe that will give your work more meaning/value (something to consider).
As the guy above me said, a lot of people are facing crisis right now. I honestly don't blame you for having an easier time of it if most of the week you're just collecting money.
PS: I learn best by teaching others. I think you should get more involved with your team to help them :-)
PPS: I have grown SO MUCH as a developer by forcing myself to "do as the Roman's do". Watch your mental health. If you feel like you're losing your identity you should walk, but otherwise try immersing yourself in understanding your companys' stack and design decisions. Make your contributions indistinguishable from all that code that together makes something amazing. It's bad to measure progress by SLOC. You can always switch to Sprite if you don't like the Koolaid.
PPPS: You may be able to be honest with your supervisor and ask for time at work to work on passion projects. They care about your meaningful contributions and would likely do whatever you need to keep those rolling in. A FAANG company would accomodate this.
(Replying to PARENT post)
If you do good work, they'll fear managers might notice, and it'll make them look bad. So they won't be happy with that. They'll sabotage you, bully you, not proactively tell you things you don't know you don't know, etc.
Before you start that fight, make sure you want to fight that fight, and that if it happens you stand a good chance of winning.
Otherwise you'll just put in more effort than now, and the result will be that more people than now will hate you, and eventually you'll get fired because your work will suck because your colleagues have deliberately withheld information.
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
Situation: "I only have to work one day a week to keep up, and so I only work that one day and slack off the rest of the time".
Possible causes:
1. Depression / Mental health issues
Seek help. I know: depressed; so hard to do.
2. Doesn't actually enjoy programming.
Wait till the pandemic is over and get a different job or start a company doing something you enjoy.
3. Enjoy programming, Team sucks.
FAANGs are huge companies with thousands of teams. Find a different team.
(Replying to PARENT post)
I was an extremely motivated worker in scenarios 1 and 2. I had a lot of "momentum" and worked extremely hard. Burnout was a consideration not just because of long hours, but because I liked working so much that it was easy to overwork over the course of a couple months. In scenario 3 it is a constant struggle to remain motivated and I constantly feel as though all of my momentum is lost.
Here are some differences I noticed: Scenarios 1 and 2: a. Extremely aggressive goals and deadlines. Deadlines constantly missed, but our velocity was impressive. Goals were very short term - few goals were more than 1 business quarter in the future. This changed once we were acquired because the acquiring company demanded longer term deadlines.
b. Scrappiness and the pride in your work and yourself that accompanies scrappiness
c. Iteration speed prioritized highly. Build and deploy times to a staging environment often less than 3 minutes.
d. I wore many hats. DBA, sysadmin, full stack software engineer, product guy, security person, devops. Worked in many domains - search, distributed systems, building in the Cloud, etc.
e. Hard work and ownership are seen and rewarded.
---- Scenario 3: a. Smaller goals. Every goal was designed to be hit, since missing goals is anathema in my FAANG company.
b. No scrappiness whatsoever. Just meet the deadlines.
c. Iteration speed barely prioritized. Since your tasks have been mapped out months ahead of time, what need do you have to iterate quickly? Just build to the spec. Build times were extremely long. Deploy times were often 12 hours (you think it wouldn't take that long to deploy something, but when your company has strict rules about only deploying to 1 region at a time and taking 30 minutes to monitor metrics in each region before moving to the next, it adds up). Many of the best tools or tricks I used to iterate quickly in scenarios 1 and 2 don't work due to security measures, or more likely, due to the FAANG company leveraging their own tools rather than open source ones I used in scenario #1 and #2.
d. I wear 1 or 2 hats.
e. Hard work and ownership aren't really seen unless you're in the right project.
I can't tell you how many times I've told my manager I feel like I haven't done a lot of work recently, or feel like I could be doing more. I'm always assured that I'm doing very well in his eyes and meeting all my deadlines. From my perspective I've done a disgustingly tiny amount of work since I started.
Anyway, I wrote all of this out to try and illustrate that it is really hard to work hard in a scenario where you are actively discouraged from working harder. I didn't really do a good job of doing that, but I hope I've kind of hinted at the problem. Most of your teammates at FAANG companies have worked at FAANG or other large companies their entire careers and have no idea how slow the entire freight train is moving. They have no idea that in other companies the role of being a software engineer is much more dynamic than their experience has been.
There are a lot of compounding issues other than just unimaginative deadlines that I don't have time to touch on. Legacy systems, defined promotion processes that make it so that you know ahead of time which projects actually stand a chance of promoting you, a strong hierarchy, entrenched politics, etc etc.
I just want to say that I have been in scenario 3 for a year and it has taken about that long to build my momentum up again to where it was in scenario #1 and #2. It is really, really hard to keep your motivation to work harder when almost every part of the job is incentivizing you to just sit down and meet your pathetic deadlines.. Trying to motivate someone by shaming them is never going to work here.
(Replying to PARENT post)
Now there may be laws or authoritarian morals around how I should lick the boots of my boss and give away more hours or outperform the KPIs, but basic capitalism says that's just a thing for suckers.
(Replying to PARENT post)
@faang0722, you're being a slacker, and not doing right by either your company or yourself.
You're at one of the top companies in the world, and are safe from the jobs disaster that's gripping the entire country. Millions of people are desperate to receive $600-1600 from the government this month because they are unable to work. Millions are putting on shitty facemasks and still showing up to work at grocery stores and warehouses and wherever, risking disease because they have no other choice. Meanwhile you can't be bothered to work at home on your laptop more than one day a week, because the build system and tech debt makes you sad?
You say the company is evidently pleased with your work and that may be true, but now you're part of the problem. You think the company tolerates shitty work, so you've decided to tolerate shitty work. Don't.
Since you don't think what you're doing is ethically wrong, have you told your manager that the work assigned to you is so simple that you only actually work one day a week? Of course not.
So either start putting in your best work, or switch teams or company and see if it suits you better... or else accept that you're being a freeloader and pretending to do more work than you really are.