10 ms·
Knowing where your engineer salary comes from
- bruce511 2y agoI work on a product that has been built over 25 years. Lots of the work I did years ago is to ensure the product longevity. Lots of the work I do now is to ensure it lasts another 25 years. Thats good, but its only the start of "my work". It's up to me to "sell" that benefit to upper management. There's no point in assuming they'll figure it out by accident. Part of my job is enumerating the value I add. By all means work on technical debt. But be sure to make a compelling case as to how the eradication of that debt will impact the project over the next decade. Try and throw in immediate results as well (faster, more reliable, reduced support) but more importantly translate that into terms that measure the improvement in cold hard cash.
- Fire-Dragon-DoL 2y agoHow do you put numbers in there usually? I'm facing an issue at work where an important factor should be done to correct a serious design mistake, but it doesn't get in the way of any feature. It's probably the cause of a lot of loss of development time over the lifetime of the project, but I don physically know how much of a boost will it give to development. I know it will, but I wouldn't feel comfortable without quantifying. I have some rough idea for approaches to this, but would appreciate some external input as well
- 6510 2y agoI only do small solo projects but the value from maintainable code depends on how often it needs to be updated. If management comes with new [crazy] ideas and/or feature [cruft] every other week it should be easy to prefer a warehouse with ready to use components over a scrap yard. If you need a set of usable tires a few times per year the scrap yard will provide. If you need a set of tires 20 times per day you want at least 200 sets of each kind stored in a convenient place. You probably live some place in between. edit: Also, timing is everything. Write down everything you want, add the pony. Wait for the right moment when their head is not raging with 50 deadlines. Most important imho is to not want anything but explain what options they have. If they want faster results they might be able to get them by attacking the technical debt.
- pjc50 2y ago> How do you put numbers in there usually? Make them up. If you're uncomfortable with this, ask ChatGPT to make them up for you. Most places don't have any real way to measure productivity or rate of feature delivery, so as long as you promise a reasonable number (5-10%) they have no way of contradicting you. Incremental refactoring is also the other classic way to do this. Slip bits into other tickets until you've slowly dragged the ship around. But it's not always possible.
- jeffparsons 2y agoOne way to communicate this is in terms of _schedule risk_, rather than straight-up lost productivity. E.g. for a particularly troublesome design flaw, you might estimate that for any given 4-week project there's a 20% risk of the project blowing out by an extra week due to that flaw. Depending on the stakeholder(s) you're dealing with, approaching it like this (as risk assessment/management) might help to convey the short-term impact of a long-term problem.
- bruce511 2y agoIt can be tough, and in some cases measurable numbers are hard to find. That can make prioritization hard. It's worth keeping open the option that "now is not yet the right time". One key way to understand the situation well is to explore both thd upsides and downsides of the issue. Its almost never an obvious decision and being acquainted with all points of view really helps both to figure out what is right, whether it's worth doing, if now is the right time, and so on. If it was obviously necessary it would likely already have been done, so it may be necessary, but it might not yet be time. Sometimes it comes down to groundwork. Finding out who us affected, and how. (And if you can't find those people, that's a clue too.)
- Fire-Dragon-DoL 2y agoIndeed, I was the one suggesting to not do the refactor because I couldn't find a reason. Today at standup though, a task that would take 1 hour once the refactor is done, will probably take about 2 days instead, so i'm back thinking about it (the refactor would take longer than 2 days)
- hansmayer 2y agoI get your point at the basic level, but as engineers and managers, we need to stop this nonsense. Think deeper about why do you need to "sell" your work inside (some) companies ? Could it be because those companies are full of people who somehow occupy important positions without understanding the basics of the engineering work. What's the value such busywork managers are adding, besides the anti-value of layers of explanatory communication and wasted time? The busywork folks should be working to understand where their salaries are coming from, not the engineers. Note that I am not saying all managers are useless (its also a part of my job), it's the people-and-ideas-managers who are useless in the technical setting. The point about technical debt should be a non-issue, why the hell would you have to explain that the technical debt is a bad thing? Did we not clear this issue many times over and establish zero technical debt as an engineering ideal a long time ago? Well it is because some person with 1/4 of your experience and competence somehow got lucky and talked themselves into one or two hierarchical positions above you. We need to start a pushback across the industry and stop allowing former accountants and humanist science graduates into "leadership" roles in IT.
- dave4420 2y agoThere’s a difference between management knowing that it’s worth paying off tech debt in general, and management knowing that now is the right time to pay off this piece of tech debt in particular. Why pay off tech debt A and not tech debt B? Is this really more urgent than implementing feature C? I have some financial debts, but I prioritise paying off some over others, and even allow myself to buy myself nice things instead of paying off the mortgage early. The same principle applies with tech debt, except I have to justify my choices to my bosses instead of to my girlfriend.
- dagw 2y agoCould it be because those companies are full of people who somehow occupy important positions without understanding the basics of the engineering work. Every company I've ever worked at has more work that they would like to do than they have engineers to do it. The problem often isn't that they don't understand why fixing technical debt is important, it's to decide if fixing that particular technical debt right now is the best use of these resources right now. Also they might also know things that I might not know, like long term plans for and the relative profitability of different projects, which will affect how they make decisions. No point in spending effort fixing technical debt if that project/department is already slated for closure. Also maybe it's a US vs EU thing, but at every engineering and IT company I've ever worked in Europe, the person two steps above me was basically always an engineer or at least has a science or technical background.
- moduspol 2y ago100%, although also: Try to be as objective as possible when evaluating that tech debt. It's possible (in many cases, probable) that the tech debt actually isn't as bad for the business as an engineer perceives, and it's quite possible there are other engineering efforts that are more worthy of development time and resources. Being willing and vocal about acknowledging and accepting that reality is also quite helpful.
- lesuorac 2y ago> They throw themselves into various pieces of work that don’t make money ... better screenreader support Truth hurts lol. This I think is where Capitalism is at odds with a lot of people's intrinsic values. Accessibility unarguable improves people's lives and many people are in software to make the world better but yeah if you want to make as much money (or maybe just more money) doesn't mean working on even a useful item; just a much demanded one.
- nthingtohide 2y agohttps://x.com/ben_el_baz/status/1908063819966067048 https://x.com/ben_el_baz/status/1908063819966067048 Corollary : This is also the reason why people (i.e. Wall Street) who are close to / handle the money earn more money. Drinking straight from the firehose.
- jakelazaroff 2y agoThat is why laws like the ADA exist: to give companies a financial incentive to make their products accessible.
- ajuc 2y agoI worked at a company that makes machines reading books/press/whatever to people with impaired vision (or altogether blind). It wasn't the best paid job, but the satisfaction when you can talk with someone who uses your product daily for obvious life improvement beats any cozy bank job. This is a huge underdeveloped market BTW, and as the populations worldwide age it's only going to be more and more important.
- qweiop 2y agoThis line triggered me a bit, but later on they do give examples of how accessibility can be profitable. I think "not getting huge fines" due to (very important) laws, is a great example.
- mirawelner 2y agoThis sort of thing is why I decided to do research so I could work at universities and small startups! I figured that way I could be away from the corruption and selfishness that exists in large tech companies. Then my whole department got defunded. More fool me.
- 52-6F-62 2y agoEven many of those small startups are in the pocket of some unfavourable characters.
- BobbyTables2 2y agoI’ve also found some small companies have even worse politics and infighting than large companies. Having a great boss+team in a large company is probably the most ideal — at least while it lasts.
- FirmwareBurner 2y ago>I’ve also found some small companies have even worse politics and infighting than large companies. Also matches my experience and I think I can explain why. Small companies usually have tight social cliques (for better and for worse) which also translates to group think, more gossip, and less diversity of though as most people working there likely know each other form before or went to the same schools, worked at the same company before, etc. Therefore if you don't click from the start with the core "gossip" group on all wavelengths, then your career prospects in the company are fucked.
- em500 2y agoSayre's law: "Academic politics is the most vicious and bitter form of politics, because the stakes are so low." https://en.wikipedia.org/wiki/Sayre%27s_law https://en.wikipedia.org/wiki/Sayre%27s_law
- kbrkbr 2y agoWell, I left academia 20 years ago, because of the perceived corruption and selfishness. I guess you just need to be lucky, no matter where you go. Good luck anyways, I hope better times are on the horizon.
- beacon294 2y agoReplace "profitable" with "popular with management" and you're right on the money. Just don't get caught holding the hot potato when the wind shifts. And good luck figuring out when that is.
- kubb 2y agoPositioning is key in sports and in corporations.
- suyash 2y agoHaha, that's the most practical way to put it compared to the theoretical blog post.
- dagw 2y agoAnd make sure your bosses boss knows who you are and how good you are, so that they'll want to keep you when your boss ends with said potato.
- nialv7 2y agoI have no words. this is just… so sad.
- sauercrowd 2y agoWhich part?
- poincaredisk 2y agoIf you don't want to feel like a cog in a heartless money making machine, all of it.
- t43562 2y agoI wouldn't take it quite as seriously as it takes itself. These articles like to lay down a view of the universe as if it was the first and last word but I don't think it is at all. We couldn't function at all if all companies failed to do work properly because of some odd decision about what's a cost and what isn't. If you have a toll bridge then fixing the bridge isn't a cost....unless you actually WANT it to fall down.
- woah 2y agoIt is not the responsibility of the rest of society to pay you a handsome salary for a programming hobby. If your code isn't generating enough value that someone wants to pay for it, it's about as useful as model trains.
- poincaredisk 2y agoI never said it is. I responded to the question about "what's sad about it", and having idealistic ideas about the IT is common among newer/fresh programmers. And (almost?) nobody wants to feel like a replaceable money making pawn, most[1] people in IT value self-realisation at least a bit. And some successfully gaslight themselves into believing that their backend work on their ad-sponsored e-commerce CRUD is somehow making the world a better place. Having said that, "value" doesn't have to be measured in euros. I personally work in a semi-governmental institution, and the main focus of my team is reducing the amount of cybercrime in my country. I still need to provide that value to earn good money, but I enjoy that more than working to make investors rich (there's nothing wrong with that though, and it usually pays better). [1] anecdotal, among my social groups, I don't really have hard data about this.
- sanitycheck 2y agoIt's very surprising to me that this needs to be said - but maybe that's because I've mostly worked in, let's say, 'resource constrained' environments. You focus on the stuff that keeps the money coming, or people start losing their jobs.
- t43562 2y agoIs that on the things that make money now or the speculative things you might make money on later? Almost everyone is resource constrained in that the ambition of non-dev management is always 10x what they have the money to pay for. I take that back a bit - I haven't worked for FAANG so perhaps they do have more people than real work.
- thundergolfer 2y agoThe author works at Github, so yes not so much a "resource constrained" environment. It matches my experience at a high growth company, Canva, where in places it was easy to see the connection to profit and in other places quite hard. There were people that didn't care about their connection to profit, and there were expensive employees doing "good work" done merely because it was good to do. Canva could do that because its margins are 80+% and it made almost $1B in revenue at the time.
- cjs_ac 2y agoI think this is a problem that arises from people working in these gargantuan organisations where individuals can't see how their work contributes to the success of the organisation. They perceive the organisation as a construct built around social relationships rather than a construct that exists to drive some change in or generate profit from the surrounding economy, because they can't see how their work drives that change or generates that profit.
- cess11 2y agoMy pet peeve in this area that pretty much always gets overlooked by technical people even if they're somewhat experienced in management and business, is compliance. It's always good and profitable to adapt to and preferably implement representations of laws and regulations, including 'soft' rules, like standard contracts, established business practices, non-compulsory laws, things like that. Even if no customer today cares about something, a form of employee compensation that is a bit unusual, say, or 'reversed' VAT declaration in invoicing, or whatever, if large actors in your segment do, and that's most likely the case, then you should at least build things based off the formalities in the local jurisdiction so that when your sales people get a big prospect on the hook you'll have an easy time adding what they need. It can also shield from legal or financial liabilities if someone gets angry at you, and your lawyer will be happier and possibly cheaper if they know you understand your legal environment. If you're doing an exit buyers will also appreciate good compliance, just like they appreciate other forms of risk management.
- CrossVR 2y agoRunning companies like this is how you end up with the current state of Boeing. Only valuing engineers who are directly earning you profit and firing the ones who only have an indirect role in your profit centers. > If your work isn’t clearly connected to company profit, your position is unstable You know what really makes your position unstable as an engineer? Delaying a product over "safety" concerns, thereby doing work that's clearly connected to preventing company profit. Only young, bright-eyed engineers would be naive enough to bring up safety concerns right?
- bravetraveler 2y ago> Or even worse, engineers who are preventing you from making profit over "safety" concerns. Ugh, this. After doing SRE for nearly a decade and being utterly pigeonholed, I've come to believe it's more accurately placed in the "controlled opposition" bucket than anything about either reliability or engineering.
- salawat 2y agoQuality Assurance reporting in. Everybody talks a good game, then when you bring up compliance it's straight to the executive override.
- aaomidi 2y agoYeah. Company culture like the one mentioned in this document is toxic and will inevitably cause the company to fail.
- timestep 2y agoI usually tell new hires this often; understand how this company makes money. Is engineering seen as a necessary cost or income multiplier on the balance sheet. In most companies, it falls in the land of IT, a cost center.
- PeterStuer 2y ago"At successful tech companies, engineering work is valued in proportion to how much money it makes the company" You would think that, but decades of experience have disproved that. Most of management, past first-gen if the company was founded by engineers, is non-technical. Most are (more or less) aware that somewhere technical engineering in software is needed, but they feel that as a threath rather than an asset. If engineering is not a commodity, they fear being called out for not being in touch with the grounded reality of the business, and fear the unpredictability this entails for their own operation. So they will tend to treat engineering like a commodity, generic and interchangable at will, and even deliberatly not recognize differential contribution by engineers to the company's success. This is also why once non-technical management has consolidated, rising from engineering into management will become very difficult, often requiring you deny your technical competences.
- ozim 2y agoBut also company actually is much better off when it is not held hostage by couple of technical employees. Also every employee should be able to quit at any time and not affect business. So I disagree describing all like it is some evil scheme - that’s how businesses work.
- saagarjha 2y agoIs it better when it's held hostage by a couple of non-technical employees?
- ozim 2y agoNon-technical employees are by definition replaceable. Unless they are sales reps that have good relations with customers.
- disgruntledphd2 2y agoIn that case, all employees bar sales reps are replaceable (and the reps are too, you just see the pain more).
- tybit 2y ago> At successful tech companies, engineering work is valued in proportion to how much money it makes the company If you look at what it actually takes to get promoted at most tech companies I’d say this isn’t generally true at many big tech companies. Being on a very lucrative part of the product may not get you as much “impact” on your promotion packet as if you are working on a platform/infra touching the whole org. Even if that platform isn’t generating the company much money even indirectly.
- jgeada 2y agoOK, now explain where management's salary comes from. They don't produce anything, at best they're taste arbiters and at worst parasitic middle men that happen to control the budget; funny how that always means they get more of it. The best long term performing companies are run by technical people that happen to be competent managers. As soon as the professional managerial class takes over they quickly figure out their most profitable move is to cheapen out on engineering and trade in the future for bonuses right now; they'll be long gone when the company craters.
- t43562 2y agoAbsolutely. Some genius outsources IT to Malaysia....I ask for an IP address to be statically assigned to a test machine and the ticket is opened and closed.....next day the IP has changed. Repeat x20 till we give up - telephone calls and complaints notwithstanding. Someone closes 20 tickets and looks productive because that's the way they're being managed. I bet the MBA who made this happen got a promotion and wouldn't understand how they crippled everyone. I admit this is an old story but IMO it does show you how management by people who don't know and don't care screws a company quietly. That's a famous company that did in fact have a major problem.
- agentultra 2y agoMackenzie’s analysis holds a grain of truth and remains too simplistic. If you work at a company whose notion of value is purely dividends, get out. The aviation industry didn’t get profitable without regulation. Safety is a big part of the value generated. Spending on safety is not spending money putting more butts in seats and selling more tickets faster. But few people will choose to fly if the risk to their safety is too great. Software does have similar responsibilities. People hate losing their money, having their private data leaked, having their entire production run screwed up because of a software error. It can cost a business a lot of money. Cutting corners to bring new features to the table doesn’t exactly add to the value the company brings to their customers. You also need to respect their privacy, do what's required to avoid security errors, programming errors, etc. Update: This article, and Mackenzie's advice, is decent if you're trying to survive at such a company and you can't get out yet.. for reasons. But I would aim your career towards getting out at some point because such a company will never value your work.
- BJones12 2y agoThe profitability problem in the aviation industry was not a lack of regulation. The profitability problem was simply that there were a lot of countries pouring money into their flag-carrying airlines to enable them to operate at a loss. Since many competitors wanted to operate at a loss, the entire industry operated at a loss.
- t43562 2y agoI have often ended up working on the billing system - nobody cares if it functions and I don't know why. It pulls in the money every month and if it makes mistakes the company loses money.........!!!!..... In the same companies people do care about the UI ...even when it has about 2-3 unique users per day. I won't explain how this translates to being able to function as a company at all - just to say it does because most selling is actually through salespeople. So what I get from the OP's dose of "realism" is that everything is about perception and hopes for the future etc. The things that are making money now are assumed to be able to carry on doing so forever without attention. Just as some people buy a car and never look after it. When the day of disaster comes they're surprised. Some companies implement new features to make a sale. So there's a continual struggle to complicate an already complicated system......but you're not allowed to refactor or spend time upgrading from gcc 4.3 or whatever because that's not work that leads to a sale. So each new feature takes more and more effort of course....and when you lose developers their replacements don't understand the convoluted codebase so bugs can't be fixed and customers don't renew their contracts. So you do need to work for profitable companies rather than the kind of slow motion car-crash companies that are trying to do something which cannot really support itself.
- teddyh 2y ago> nobody cares if it functions and I don't know why. It pulls in the money every month and if it makes mistakes the company loses money.........!!!!..... But no individual manager loses anything compared to their colleagues. There is nothing for them to lose by not caring.
- cdavid 2y agoThis article makes the naive assumption that "what is making money" is an objective thing. Once a company reaches a certain size, basically once it has a financial planning department w/ different VPs owning their PnL, who is making money increasingly becomes a social construct. "how to get promoted" by spakhm is much more closer to how a large, successful org works IMO: https://spakhm.substack.com/p/how-to-get-promoted https://spakhm.substack.com/p/how-to-get-promoted I've seen this in my career multiple times. For example, when I was involved in search for some companies, we would demonstrate through A/B testing that we would make X more money per month. Executive team changed, they decided that "A/B test does not work and slows us down", the definition of making money changed, we overnight went from a money-aking org to a cost center. Nowadays, most companies are pushing GenAI everywhere. Most of those things don't make money, and yet a lot of promotions will be obtained across the board until the tune ends.
- t43562 2y agoThank you. "Spearheading" is always valued and the way to do it is to leave for some new initiative somewhat before everyone realises the current one is a turd. The blame then attaches to the people left holding the turd.
- Hjack 2y agoBut still there are objective metrics by which you can track which products are making money and which are not. You can do ALL the financial manipulation to an extent, but everyone above bragging VPs/Directors know which product lines are making money yoy
- cdavid 2y agoSay you are meta. You know that a big stream of revenue is ads. You are an engineer working for one of the myriad ML model around feeds, ads click prediction, whatever. Those ML models are in production, and cost a lot of money to maintain / operate. How much you are a cost center or a money maker will depend on a lot of non objective choices. The essential issue is attribution, which fundamentally requires some choices about how money is actually made. Even when everybody is in good faith, there are reasonable ways to agree. And people are rarely in good faith around those things.
- 1970-01-01 2y agoWell said. Young engineers must understand that there is no problem more sales can't fix. Your brilliant solution to problem X must pass the sales test for it to be considered a true success story for your company.
- xivzgrev 2y agoOof this article hits like a kick to the nuts. Ive been unhappy with my career growth in past several years, and basically it’s because I worked on products / projects that did not make a ton of money. I knew this intellectually of course, work on revenue generating things, but emotionally I gravitate toward such reasons that it’s good for customer, or this is high risk / high reward, it’s more interesting, etc. If I had kept this heuristic as my North Star, I would be further ahead and making more money. I’m not sure if emotionally I could have done it - I was offered a management position if I moved OFF a high revenue product, so that would’ve been hard to say no to. But in the long run, with hindsight, it would’ve been the right choice.
- tonnydourado 2y ago> It’s easy to fall into the trap of thinking that you get paid for work because it’s important Is it? Maybe I'm out of touch, or used to a different work culture (non-US, consultant), but that's kinda obvious, you're paid because you make money. Also, no one that knows a single teacher or nurse would ever fall into the trap of thinking that salary is proportional to job importance.
- hiddencost 2y ago[flagged]
- sandbach 2y agoThese Silicon Valley folks really ought to read some Marx. If low-level workers are a 'cost centre', why don't companies just get rid of them? Wouldn't they be more profitable if they removed everyone outside the 'profit centre' of senior management? Obviously not.
- thundergolfer 2y agoI'm not sure you understand Marx. The author probably has read Marx during their philosophy training. 'cost centre' does not mean a place that a capitalist is unable to perform exploitation. A cost center in Marxist terms can be understood as a department that participates in the money-commodity-money' (MCM') flow but doesn't directly complete the circuit to M'. For example, delivering and receiving mail does not realize profit for most companies, but is an essential part of the business. If they spend $1,000,000 on the mail department in Q1, spending $2,000,000 in Q2 is likely to waste the extra $1,000,000. But spending zero in Q2 would cripple the company. That's a cost centre.
- woah 2y agoMarx was a techno-utopian sci-fi author who insisted his fiction was non-fiction and was proven wrong 100 years ago. Where is the dictatorship of the proliteriat?
- shireboy 2y agoInteresting article. I’m currently trying to justify “tech debt” to upper management. The way I try to communicate it: we can move faster and better on business requirements if we delete unused code/upgrade legacy dependencies/etc. Both need to happen at the same time, though, and that’s where it gets hard: “this feature request would be so much easier if I upgraded to Angular vlatest” runs the risk of always paying tech debt and never providing value.
- snozolli 2y agoI mean, I've never worked with a project manager who generated one iota of business value... Just stirring up drama, inserting themselves into decisions that they can't understand, and calling unnecessary meetings with management that they should be handling on their own. I think there's a lot to be said for simple visibility to management. Also, ignorant overconfidence seems to be something that management loves.
- esafak 2y agoThis article offers advice for ICs. Well-meaning managers should remember to set up the analytics to connect work to revenue. That which is not measured is not valued, so be sure to measure what matters.
- stego-tech 2y agoThe article makes good career advice in general: understand what pays your salary, and contribute enough such that your costs are offset by your labor. For engineers, that means understanding how the company makes money, or how you can save the company money, and then focusing on those things. As many, many others have pointed out however, modern companies, especially modern tech companies, aren't operating from that mindset. Presently they're all championing products for the sake of the product itself, rather than sticking to their profit centers. It's why everyone for the past decade or so has engaged in a "checkbox race" of adding the latest fad to their product suite, regardless of its value to said product or its customers in the first place. Likewise, internal politics has shifted to prioritize those working on the "right" product, as opposed to recognizing those who create the most value. It's a large reason why enshittification continues to grow: leadership doesn't care about value, product, or engineering, so much as they want the latest shiny thing to add to their sale sheet and make the Board and/or Shareholders "happy". My own data points supporting this theory: * Cutting a cost-center's AWS costs by 60% and saving the equivalent of my TC every 2.5 months (~$1.3m/year) got me sent to the Private Cloud team * Building multi-cloud showback wasn't recognized because I wasn't on the Public Cloud team (a new team rebuilt it two years after I'd finished it) * Building a Cloud-as-a-Service model with AI Agent hooks got me RIFed So to add a caveat to the OPs own article for others based on my own experiences: if your organization isn't prioritizing value regardless of origin, your position is unstable. In those cases, you need to either find a way onto the "right" team if the company is important to you, or you need to brush up your resume and find an exit post-haste. Creating value in a company that doesn't acknowledge or respect it is a huge red flag that I naively thought tech companies ("we're a meritocracy!") wouldn't display, but I was gravely mistaken.
- 0rzech 2y ago> At successful tech companies, engineering work is valued in proportion to how much money it makes the company (directly or indirectly). I really wish it were like that, but IMHO it's more of an exception to the rule than the rule. At least this is my experience of being an engineer and a manager.
- sakex 2y agoThe anomaly here are AI researchers
- dabrorius 2y agoI vaguely remember the engineering code of ethics, I'm pretty sure it goes against most things expressed in this post.
- napierzaza 2y ago[dead]
- teddyh 2y ago> If your work isn’t clearly connected to company profit, your position is unstable In my experience, only salespeople are clearly connected to profit. Everyone else is percieved as a cost. > In other words, you’re probably depending on a kind-hearted manager (or CEO) who personally values your work. Yes, this is the position for everybody except salepeople. Which means, in turn, that focusing your efforts to make the company profitable, as the articles advocates, is a grave mistake. You should focus on making your immediate manager profitable and successful. (For those who are fresh out of school, this is often a wildly different goal.) The only situation in which the article’s advice makes any sense is if your immediate manager is also the company owner, who benefits personally and immediately if the company’s profits go up.
- groone 2y agoMy software engineer job is to destroy my own position by solving all the problems and automating the job away. I have done it multiple times over my career.
- black_13 2y ago[dead]
- keybored 2y agoFrom the perspective of the business, you need to generate more money than your wage plus whatever else expenses that are associated with your employment. This surplus is what adds up to the profit. Let’s just put the simplistic “be a profit center” thing at face value. The funny thing is that you can generate 10% surplus or 5X surplus. The difference in benefit to the company is large. But your benefit might not be much. Maybe a wage increase, maybe not. Maybe better job security. Now others have already questioned the “profit center” line here. With so much alienation in the work force it becomes laughable to claim that you can point to a group of individuals as “the profit center” or “the cost center”. This reeks of political jockying. Is Sales the profit center? Without Sales nothing would be sold... but without Engineering there would be no product. What ends up happening is that the people who insist the loudest are the ones who get promoted to Profit Center. Maybe.
- Hjack 2y agoThe whole trend of cracking FAANG/MAANG interviews has made this notion of not having self-awareness/understanding of where money comes far more entrenched. Folks who crack these interviews feel like they are passing sermons from top of 'tech' hill to other noobs, not knowing in effect that their minuscule value is as long is company is making profit. The day that stops, everyone's job is on the line and especially folks who are away from centers which make money.
- utbabya 2y agoMetrics for things like FCP, better screenreader and refactor are less straightforward so having the capability to correctly evaluate the cost and benefits, making the right judgement calls and communicating it to everyone is vital. Not mentioned in the article but this implies the importance of hiring. Having the right people to build the culture together, sitting in the room to discuss the priority of these things can turn a filibuster popping clown fiesta into productively working out actual competitive advantages for the company.
- mathattack 2y agoAre any jobs really secure? You still need to show output if you’re in a profit center, and sometimes things happen outside your control. More commentary below: https://open.substack.com/pub/therosen/p/knowing-where-your-engineering-salary https://open.substack.com/pub/therosen/p/knowing-where-your-...
- 0xTJ 2y agoReading this from somewhere that "engineer" is a protected title (Canada), this is a weird read.
- nitwit005 2y ago> I regularly see stories like “I convinced my idiot bosses to finally let me do only tech debt work, and would you believe they fired me after a few months?” > “it’s so unfair that I haven’t been promoted - look at all this amazing accessibility/standards/open-source work I’ve been doing!” Stories like these might exist, but I genuinely haven't seen a story like either case.
- folkrav 2y agoAnecdotally, working in profit centres (and being a productive member of said centres) somewhat protected me from large layoffs, but that’s pretty much it. There isn’t much otherwise that ever shielded me (or any of my team members, as a team lead somewhat involved in these decisions) from being expensive line items, in the eyes of people some levels above my pay grade taking business decisions looking at a balance sheet.
- Fruitmaniac 2y agoI think the biggest career mistake engineers make -- myself included -- is assuming your contributions will be automatically recognized when in fact the amount of credit you receive is equal to how much you contributed multiplied by the amount of attention you draw to it.
- 1vuio0pswjnm7 2y ago"What are tech companies?" The author never answers this question. He suggests that small groups of people run them but he does not elucidate what are tech compaines. If a so-called "tech" company is not profitable, and this may comprise the vast majority of them, then the "engineer salary" comes from VC money. Essentially, a loan. The author omits this simple truth as well.
- musicale 2y ago> If you want your work to be valued (i.e. you don’t want to be reshuffled or fired), and you want to work on personally-satisfying features like accessibility, or UI polishing, or anything else not directly connected to profit - you need to go and work for a very profitable company. "When we work on making our devices accessible by the blind, I don't consider the bloody ROI." -Tim Cook Except that not-very-profitable Apple of the 1990s still cared about accessibility, UI, industrial design (PowerBook, Duo/dock, Newton, eMate...), and sustainability, even before the return of Steve Jobs and their subsequent meteoric rise. In the short run it probably looked like bad business, but Jony Ive started out on the Newton, after all...