6 ms·
> Engineering culture encourages workers to collectively improve the company’s effectiveness. It encourages them to share knowledge with one another. To train e
by neilv 4y ago
> Engineering culture encourages workers to collectively improve the company’s effectiveness. It encourages them to share knowledge with one another. To train each other. To build tools for one another. To bring new workers up to speed, and review each other’s work. To speed the company up. To seek out weaknesses in the company and fix them. / Engineers do this while they’re doing their actual job, the one the company thinks it’s paying them for: tending the machine that makes money.
No, I think most of these are usually part of the job of a software engineer, and it's part of developing solutions that work, rather than just gaming individual metrics. (And, at Staff+, all of these are.)
> There is no reason at all for engineers to continue performing this kind of free labor for entities that are trying to cut their wages. It is in their interest to do the exact opposite.
It's not free labor. It's part of the job for which we're paid.
Seems like anyone on a project team who doesn't share knowledge, help other team members, document, etc., would soon be disliked by team members who are focused on the project and team.
- 908B64B197 4y ago>> Engineering culture encourages workers to collectively improve the company’s effectiveness. It encourages them to share knowledge with one another. To train each other. To build tools for one another. To bring new workers up to speed, and review each other’s work. To speed the company up. To seek out weaknesses in the company and fix them. / Engineers do this while they’re doing their actual job, the one the company thinks it’s paying them for: tending the machine that makes money. Isn't it why any serious engineering job will have stocks as part of the comp package? That's pretty much the whole point: if the company does better, your stock does better...
- darth_avocado 4y agoThe company does better when they pay you less.
- WalterBright 4y agoThat depends. If they lose you to a competitor that pays more, then the company loses. It's that old Supply & Demand thing again.
- darth_avocado 4y agoWell if everyone decides to pay less, like it’s being argued here, then there is no supply demand, that’s just the cost of your labor.
- WalterBright 4y ago> if everyone decides to pay less That's called a "cartel", and the big problem with cartels is the members cheat on them under the table. They're unstable, unless maintained by force (i.e. using the law to punish members who cheat). I recall one job I had where I was offered X, and I said X wasn't enough. They said they weren't officially allowed to pay more, but they would if I kept my mouth shut. Deal!
- ClumsyPilot 4y ago> They're unstable, unless maintained by force What is the basis for this assertion? Is this why OPEC exists? Is that why in 2010 Department Of Justice had to step in to break up a wage suppression cartel between Adobe, Apple Inc., Google, Intel, Intuit, Pixar, Lucasfilm and eBay If it wasn't fpr the force of law, they would happily cooperate to drive you into poverty.
- leshow 4y agoAnd this wage suppression was direct collusion, corporations have such an oligopoly now they hardly need to explicitly collude, both on wages or prices. A company raises the price for something, and it's called 'price leadership', other companies recognize it is in their interest to follow suit and prices go up. The same dynamic exists for wages. Years of not enforcing anti-trust have left us in a pretty bad spot.
- darth_avocado 4y agoSure it’s part of the description. But it is also free labor when you’re automatically expected to do the work of two people for the price of one. Or when you’re expected to do more for less pay. Like the “job description” is often pretty vague which makes wage theft easy. If you’re working 996 without extra pay or less pay because everything that your “job description” has cannot be done realistically in a 40 hour work week, then it is by all means, free labor.
- nickff 4y agoIf you're getting paid to work on something, it's not 'free labor', unless you're unable to leave. By behaving as if you've agreed to this undocumented arrangement, you've formed a 'constructive contract'.
- darth_avocado 4y agoNo matter how you sugarcoat it, the extra hours you make people work for no extra increase in wages, is free labor. Just because you’re getting paid doesn’t mean the company doesn’t get free labor. The company paid for the regular hours and the rest was free labor.
- nickff 4y agoWhat if you get a pay bump for no increase in hours? Is that free money?
- andrekandre 4y agoits an interesting question, but im not sure what it has to do with the comment your replying to? they are just saying, if you are contracted to be payed x per hour at 8hrs a day, unless you work 8 + n hours, wherein n gives you no additional hourly pay, then its free labor to the company (above and beyond contracted work hours), not sure what is controversial about that?
- wpwpwpw 4y ago
- ergonaught 4y ago> Process improvement: Is this your job? Then no. This remark from TFA at least implies when it "is" part of your job, go for it. Perhaps you have rejected, or simply not engaged with, the "call" to recognize class warfare, however, or if I can be silly I'll call you a "capital sympathizer". From the frame of recognizing workers vs capitalists, you can't just say write off being exploited as "well you were paid to be exploited" without coming down hard on the "sympathizer" side. One of the points I assume the author was making is that much of this isn't your actual job, and voluntarily performing work that ultimately costs you is exploitative and adversarial and, well, stupid. Even if you're paid to do it. About 20 years ago my employer informed the entire company that we would be working December and January without pay and if we didn't like it we would be "laid off" (much of that work would be spent training team members of an offshore/outsourcing firm). State labor law disagreed with them regarding work without compensation so they were forced to pay "minimum wage" (for software developers and DBAs!). You can "well that's your job" all day long, and you're technically correct, but you're ...wrong.
- tines 4y agoI think his point was that it's the job that you signed up for, so either do the job, or don't work there. > You can "well that's your job" all day long, and you're technically correct, but you're ...wrong. Working for minimum wage wasn't part of the contract you signed ("your job"), so your example isn't valid.
- ergonaught 4y ago> I think his point was that it's the job that you signed up for, so either do the job, or don't work there. The article is, ostensibly, a call to recognize class warfare, and certain elements of "engineering culture" as aspects of same. Did you sign up for class warfare? If you simply refuse to participate in the notion of seeing this as class warfare, super!, but that's actively disengaging from the substance of the article.
- neilv 4y ago(Process improvement is often part of the official job of Staff+.) There seems to be lots of nasty class stuff going on, throughout society. But TFA just seems to hurt legitimate discussion of class issues. Imagine you're skeptical of the suggestion of class problems, but since a post about that was upvoted on HN, and you're open to being convinced, you took a look. Unfortunately, after reading it, you have to chalk it up as a data point: of someone who thinks there's class warfare on tech jobs also having very unfortunate idea of what the nature of that job is.
- ClumsyPilot 4y ago> No, I think most of these are usually part of the job of a software engineer, and it's part of developing solutions that work, rather than just gaming individual metrics. If you speak to people who work in trading or finance, they do none of those things. They view each other as conpetitors and don't help each other. They aim to outgame and outdo each-other. The culture in software is very different to most other industries. But if you look at other fields of engineering, you don't see people stepping outside their roles as much.
- neilv 4y agoEngineering teams are necessarily about collaboration towards a shared goal. I don't know in what aspects of trading or finance that collaboration is necessary (rather than applied game theory towards each other). Trading and finance are interesting examples, because those are two places where a lot of money-driven students would go, before tech jobs because easy money (rather than something nerds did for the love of it). Rather than "Greed is Good" Wall Street thinking taking over, we should say "Fine, we admit it, tech pays good money right now, but we do our best work by working as a team, and that's how we're going to do it." Then we follow through by making the messaging consistent in offers, raises, bonuses, performance evaluations, promotions, project management, metrics, etc.
- pelasaco 4y agopeople who work in trading or finance would never write open source code. Why should we compare our profession with them?
- ClumsyPilot 4y agoWho should we compare outselves to? Can't be doctors - they risk deadly infection to save a life. Lets not get carried away thinking we are specially noble.
- pelasaco 4y ago> Lets not get carried away thinking we are specially noble. The guy in Nebraska maintaining one of key dependencies of your project thanklessly disagrees[1]. Well, we build stuff. we praise the knowledge. We were called geeks, hackers, etc. I can just compare software engineering with science like math, * engineering, physics. Finance market as put by the other contributor, is just what we are not, and why Linux exists, why FOSS exists, why internet exists and services like github, trello, gmail exists (even though you want to scream at me, they are there for profit, they were all created with one goal in common: Collaborate openly with others). Egoist finance sharks aren't example of success, virtue and happy life, no matter what. [1] https://xkcd.com/2347/ https://xkcd.com/2347/
- xg15 4y agoFound that part odd as well. I think this would be the first labor movement I ever heard about that argues for less solidarity with your fellow workers. Protip: Organising collective action will become impossible if everyone hates each other and keeps information from each other for fear of their own job security. That will help capital in the end.
- jjj123 4y agoYour comment helped me put words to my feelings about this article, thank you.
- Karellen 4y agoI think it's worth highlighting that the author explicitly treats the idea of forming/joining a union with sarcasm: > Oh, yeah, we should also have a union. Sure. Let’s get on that one of these days. It seems like a how-to guide for how you as an individual can push the value of your labor down to match the price that capital wants to pay for it, rather than trying to find a way to gain some leverage over capital in order to raise the price of your labor to reflect the value you currently provide. (Leverage like, say, collective action.) > Once the company reaches the bottom, and capital starts suffering from the damage it is inflicting on the company, it will turn around. Well, good luck surviving the extra rounds of layoffs between now and then if you're the one who stands out as not working well with others, I guess.
- nbk_2000 4y agoPlease note the topic is "Class _Warfare_ for the Software Engineer" and NOT "Fulfilling Your Expected Role as a Software Engineer" This is the author's opinion of how Software's Labor can "fight back" If you're not in an adversarial relationship with your employer then this advice will not be particularly useful/advantageous.
- neilv 4y agoThe author seems to be making statements about what the job is. Are you saying we shouldn't take those literally, but as what the new (bad faith) thinking about the job should be?
- Gigachad 4y agoSeems these people are in an adversarial relationship with doing actual work. They advocate for doing noting beyond the absolute minimum you are directly instructed to do. So essentially taking out all independence from work and making it a dull box checking job.
- nmstoker 4y agoSo kind of like outsource workers but one might argue this has a social guided justification.
- somsak2 4y agoSounds eerily similar to how companies generally operate, by paying the absolute minimum to get the job they want done. Interesting how people don't seem to like when labor takes the same aproach.
- pelasaco 4y agoI don't have to defend any company out there, but that's not how in my 20+ years experience, i think it works. You do your work well, you show professionalism, does your manager think that you are important for the team? You are well paid. Are you just doing the regular stuff, not being active on meetings, not actually helping anyone, or doing anything other than what you think that "your job is": Then you are going to get just a regular salary. You do more, you get more. If you don't get more, you find a job where you get more. This weak man game like "oh i'm not going enough money, so i will stay here and do nothing", doesn't make sense in a market like ours with skill shortage. Worse developers are the spoiled one, that think that the whole world conspire against them.
- flashgordon 4y agoWas just about to say this. This act of "withholding" just gets you demoted or pipped or relegated stagnant perf categories. Why do you think "leadership" principles exist? Not to make you a better leader, but to make you hot-swappable".
- kiviuq 4y agoPeople are social creatures. It is very easy to take advantage of that. And actually, the best thing that can happen to you as an investor / capitalist. Let employees create their own peer pressured environment. The same phenomenon how coal miners used to conduct. You just lean back and enjoy the benefits of them controlling and supporting each other