I suspect it’s a big contributor to the low morale in the NHS. Hard to feel valued when a regular conversation is “They don’t even pay me correctly.”
696 karma · joined July 16, 2021
https://ellen.dev/
Email: hn at my domain
I suspect it’s a big contributor to the low morale in the NHS. Hard to feel valued when a regular conversation is “They don’t even pay me correctly.”
I’d guess (and it is a guess) that big companies like to outsource that kind of work so their devs only have to deal with the tidier data? And perhaps also because dev salaries in the UK are so much lower.
Tying in with the original post, what companies pay seems to be as much about the company’s business model and profit margin as it is about the developer.
Thinking about the dreaded “What salary are you looking for?” question, I wonder if it’s worth specifically asking the manager / recruiter about the salary range. E.g. “Other companies I’ve spoken to are offering £n-m. What’s the salary range for this position?”
and
> If you can drive the cost of doing business and your inputs toward zero almost any business idea could theoretically make a profit... but real markets are not so accommodating.
I agree with many of your points, but these vary by product. For example, FAANGs sometimes have applications where some inputs don’t scale well, e.g. the local knowledge that goes into mapping apps. But the company often provides the service for free and benefits from volunteers (free labour) adding valuable information like “this road is closed”. That product feeds into the ads part of the business, which does scale really well.
I’ve also noticed that FAANGs sometimes outsource work that doesn’t scale as easily. The contracting companies are either in cheaper countries or they’ll accept a smaller profit margin. Or both. The devs and analysts at those companies indirectly contribute to the FAANG’s product, but don’t get the bumper salaries.
Put another way, I think big tech companies do often try to “drive their inputs toward zero” (to paraphrase a little) but US-based devs don’t often experience it.
Say probate is taking a long time, so someone logs into the bank account and withdraws money for everyday essentials. That’s probably one reason the deceased person left the cheatsheet. But what happens when a bank notices money being withdrawn from the bank account of a dead person? Presumably it gets flagged as fraud. And if the estate is still going through probate, the person withdrawing money might not have a legal right to do that.
Another is “My company has been bought by private equity, who’ve given us N years to make the company profitable.” I’m not sure why it happens, but sometimes the recently purchased company goes on their own buying spree. (Maybe they’re given money to spend buying companies?) During the buying spree, the post-acquisition phase isn’t necessarily thought through and some companies get closed.
More info in the Compute Engine row of this table: https://cloud.google.com/free/docs/gcp-free-tier#free-tier-u...
[0] There’s no time limit, but presumably Google can withdraw the offer.
First reason, product managers at a company start getting pulled into a lot of client management stuff. They have less time to spend on the product itself and the resulting vacuum is often filled by the lead dev. The lead dev demonstrates they can fill the vacuum, so starts getting asked to fill other vacuums relating to management and hiring.
Second reason, management doesn’t have a clear image of what a “developer” role should look like in their company. E.g. at tiny startups a dev might be entirely responsible for a product and even help answer customer emails. (I’ve done that and I actually think it’s fine, as long as you and the rest of the company know that’s the deal.) At the extreme opposite end, a dev might have little autonomy and be practically writing the Python syntax version of tightly specified business logic. But most companies operate in the fuzzy middle and I think many struggle to define their concepts of dev / QA / product. In those companies, it’s easy for a dev to become someone who is officially “a developer” but with a bunch of semi-official hats.
I might have to add a third reason to my theory, now that you’ve reminded me about cost cutting.
I recently started playing with Phoenix and the intro to channels and LiveView has been a bit confusing. E.g. a few days ago I wondered if it was worth using something like Svelte for the frontend and then realised I could just use LiveView. As a newbie to the ecosystem, it’s taking a while to get the lay of the land and start understanding the options.
The author meant responsibility for the product’s impact on society, I think, but it could also apply to responsibility for technical decisions.
[0] https://www.greatercambridge.org.uk/smart/autonomous-vehicle...
- choosing and setting up an image registry
- learning how to write CI pipelines (e.g. the ins and outs of gitlab—ci.yml) to build images and push them to the registry
- learning how your cloud provider can be trigger to deploy when there’s a new image
- thinking about many deployment considerations (e.g. Do you need to avoid downtime? Do you have multiple servers sharing one database? If yes, are there changes to data structure that will cause errors if only some servers are running the new code?)
With that in mind, learning about general deployment practices (blue-green deployments, rolling deployments, etc) is probably going to be more useful than learning about Docker.
To be honest I only skimmed the article because there was so much pain and unkindness in it that I didn’t want to carefully read the whole thing.
More broadly, I tend to stay out of these threads. The first of its kind that I read on HN (about divorce, I think) shocked me a little. I left with a feeling that some people commenting both loathed women and really wanted female attention. It was strange and uncomfortable. It was also quite sad because I realised that someone behaving like that probably would struggle to get dates, because it would scare the women they want to date, and that would feed into the feeling of anger. So now I tend to avoid these threads.
The tech industry can be strange for women. I’ve often been the only woman in a meeting, for example. And as an interviewer at one company it was disheartening to see how few women applied for dev jobs. (That wasn’t a problem at my previous job, which was a startup with an education focus and attracted many female dev candidates.)
Some women find being in that minority hard, I think. I’ve never particularly minded, though I still notice it sometimes. E.g. I was in a meeting where someone made a very mildly risqué joke about a sunbathing neighbour and was obviously embarrassed when he looked at me and thought through the fact a woman was in the room. But it was mildly risqué, quite funny, gentle humour and not bothersome at all.
I have been careful when looking for jobs to emphasise that culture is important to me. I don’t want to work places where people play silly, back stabbing games. The closest I’ve come to a bad experience was working with a recruiter, who I liked a lot, who told me about a company and then hesitated. I prodded gently because he’d been excited about this company and thought I’d find the work interesting, but seemed reluctant to send me. After a while, he told me that he didn’t want to send me because the last two women he’d sent had a bad time and he didn’t want that to happen again. It was horrible to realise there was a local company treating female devs so badly, but it was also kind of the recruiter to have that awkward conversation with me. And, frankly, I’m happy to avoid the unpleasant bits of the industry.
Overall, I find I have a lot in common with the men I work with and have rarely felt like I was treated differently because of being a woman. But I have also made an effort to work in smaller companies and prioritised things like a collaborative company culture. There are icky companies in the industry still and I’m glad that I haven’t ended up in one of them.
I do think there’s value in thinking through (and discussing) strategies to use when facing discrimination or harassment. That’s something young women struggle with, because having your bum grabbed in public is just so bizarre. It’s hard to know what to do. But I would be sad if those discussions left young women feeling worried and reluctant to do things. I feel much the same about cautioning girls about the tech industry — we can spend too much time talking about the companies that are awful, when there are many welcoming companies that are wonderful places to work.
Apologies for the wall of text. As the thread is about young women going into tech, it seemed worth presenting a different experience and perspective. Hopefully it will prove useful (or even encouraging) to someone.
Best of luck to your children and to the OP’s daughter.
Of course it’s difficult to know how much management change was due to him. E.g. I’ve seen claims that he influenced the re-building of Japanese industry after World War 2, but I don’t know if it’s true.
The British Library has interesting pages about Drucker and other people they describe as “management thinkers”: https://www.bl.uk/business-and-management/management-thinker...
My few experiences with Rust made me realise that I’d become used to dropping into a Python shell to sort of explore and actually experience what was happening. Even in toy programs in Rust, I had to change my approach and also ensure I wrote one small, working chunk of code at a time. (Rather than roughly sketching out bigger sections, for example.)
I quite liked it, but changing habits isn’t easy and now I’m wondering if maybe it will limit the wider adoption of Rust.
Did you mean a few hundred thousand units? Wiki says there were 24,459 Chevrolet Sparks sold in the USA last year, plus a similar number of international sales. Total US sales were roughly 285,000 units[0], so that would fit with “a few hundred thousand”.
If more software developers used examples like those, maybe more people would consider software as a career? If nothing else, seems like I should give it a go when I have those conversations with people.
[0] Adafruit have an image of a 1967 article in Cosmopolitan, which quotes Hopper. https://blog.adafruit.com/2021/03/12/a-1967-cosmopolitan-art...
Best of luck, whatever you decide.
Some comments on this post mention the irony of diversity initiatives that discriminate. Kendi’s argument, I think, is that there’s no good reason for occupations to be skewed towards one race or gender or age or whatever, so additional / opposite discrimination simply undoes the initial bias.
I think that’s a challenging POV for a couple of reasons.
First, for those of us in well paid or high status jobs, like software development, it’s a POV that suggests “maybe you don’t deserve it quite as much as you imagine”. That’s a tough thing to consider, doesn’t feel great and probably isn’t going to be popular.
Second, it’s really hard (impossible?) to know the extent to which culture has affected distribution into occupations. But some people seem confident that our status quo is natural and fair and some people seem confident that it’s unnatural and unfair. When people with those different POVs talk to each other, they’re starting with a big gap in how they understand the world.