Until it's not, and you'll still look like a clown.
this post was submitted on 30 Aug 2023
395 points (96.7% liked)
Programmer Humor
32479 readers
310 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
What do you get when you cross an overworked dev team with management that sets stupid deadlines and treats them like resources?
The system you fucking deserve.
Not saying it’s sustainable (it isn’t), but Amazon has an insanely high turnover rate, partially because new employees bring a fresh perspective and new ideas. It brings new energy and creativity.
Ofc Amazon achieves that turnover rate by treating people like shit and sooner or later they’ll run out of new people.
Amazon has high turnover because their strategy is to burn through new graduates (the cheapest dev labor) before they get sick of the poor working conditions. This is identical to their warehouse employment strategy.
Yeah, that sounds significantly more likely.
Theses 2 guys are the same, at different period of life for each,
A pessimist is just a well informed optimist.
I‘m always the guy on the right. As a gifted, autisic person, I have a special view on things. I usually get the boot after 18 months because the boss or some other person in power doesn’t like me optimizing stuff. „We are not used to change our ways.“ was one sentence I often heard when being let go.
Do you get permission from stakeholders before you optimize or do you see a "bent pipe" and just straighten it? If you just do stuff to other people's stuff, right or wrong, I can see how you would get fired. Chaotic good is still chaotic.
Depends. I usually start out getting permission. But as time progresses, these permissions start to become very sparse. Something I repaired in the past (and did so correctly), I wouldn’t get permission later. Reasons were that people felt like too much was changing.
Me with a student teacher that begins to realize that 90% of the job is just passing out standardized tests and drilling for the next standardized tests:
don't try making changes as individual. do it when you have leverage, after organizing your coworkers collectively into a formally recognized union or an informal grouping of workers that take action together and are willing to take some risks. and I'm not just talking about technical changes to projects or ops, im talking about workplace processes, such as how much unpaid time you work, getting guarantees about not getting laid off, keeping or improving current pay and benefits, getting on the job training, getting to work certain types of skills without getting deskilled, etc.
Otherwise, for technical challenges, a lot of it boils down to how popular you are and internal politics and whether management will or will not get in your way. as a worker, i'm less concerned with how well the business performs and much more concerned with how my coworkers and I are treated. I do also dislike toil but realize that too much automation can also remove the need for myself to be employed. If you are working in the west it can also mean getting yourself replaced with outsourced workers, who will either also be de-skilled and only taught to use the automation you wrote and paid less or very skilled and without access permissions and still payed way less than you. Its a fucked system in every type of way.
I often wish my coworkers would care way more about working conditions and the way they are being exploited and used and less on technical aspects of how the work gets done. Not that a well organized work process and sane technology choices wont make things easier for workers sometimes, but this is traditionally the job of senior engineers colluding with management to figure out and not much of my concern, even if I do have good ideas on how to improve things, which will get ignored by the needs of the business and executive's silly decisions that they make that day
Agree, but it's usually easier to find a new job with better working conditions than to change them on your current workplace unfortunately...
not always (in tech sector). you could end up in a place that is worse or the same level of bad, also. its happened to me a couple of times already, though the opposite also has.
also, conditions in the sector as a whole will change, as more "belt-tightening" is imposed, as a result of an already stagnating industry that is relying more and more on extracting money through subscriptions and is less able to deliver on innovating tech promises that it was able to in the past.
i think the golden age of tech sector unionization is yet to come but will probably happen in the next 20 years, similar to how many telecom and electrical companies got unionized in the US in the last century, but only time will tell of course. that said, imo, we should strive to do what we can to push unionization in this sector along at all points in the process, even if that means doing so at another job and not the current one. hell, google workers are already doing so, as are grindr, kickstarter and some other places
Completely agree with all that, the only way to improve things effectively is through serious labour organization. United we stand, divided we fall.
united we fight, divided we beg for sure
Lol I didn't read the community name and for just a second thought I was back on r/kitchenconfidential. Wish they'd make the move over here already!