639 karma · joined May 27, 2019
I have lived and worked in a foreign country. When I got my first job there, my new boss joked I'd gotten the job because of diversity quotas. I was horrified at the idea that my skills wouldn't matter but only my status of a being an non-native. So I can see where you're coming from with the "quota-thing".
I am sceptical, like you. Quotas are inherently discriminatory, but I am open to the idea that if the entrenched elite is bigoted or biased too it might be the only way to break things open.
To me, what matters are the strategic patterns, i.e. how you think and talk about your domain. What a lot of (microservice) software gets wrong is bounded contexts and APIs, which can be improved through event storming (discussing what kind of things happen in your domain) and context mapping (how that [sub]domain interacts with others). And then there's ubiquitous language, or calling the thing what it is to the business, not some programmer gobbledygook.
If the money is supposed to go towards people preventing damage, wouldn't that include devs?
> How much of this is due to liability law and how much is due to natural aspects of the relevant technology?
I can only speak from my own experience in biotech, but moving slowly was due to a lot of compliance box-ticking that didn't actually contribute a lot to either safety, reducing defect rate or meeting requirements. Conway's law applied: since bio engineers and lab techs move slowly, so did the software org.
Only if you limit privilege to negative reward (suffer less discrimination and exclusion) instead of positive reward (getting actual benefits) and as you say, the tide is turning. Positive reward is still mainly tied to class and generational wealth.
> I'm not mad
Do you think it makes sense for a for-profit enterprise to have hiring policies based on the political sensibilities of the staff, let alone mainly those of SJW middle class white women?
Simply saying no to cars doesn't solve the problem of transporting goods of any kind, e.g. a family load of food shopping for the week, furniture or building materials when doing a house renovation.
And while covid has nudged employment towards a more decentralised model, some countries (the US comes to mind, especially in rural areas or AFAIK cities like LA) don't really have a public transport alternative, for instance.
Covid became a very partisan issue across the world, despite the numbers being clear. So have climate change, incarceration versus rehabilitation, drug legalisation versus prohibition, increasing minimum wages, single-payer healthcare systems, quantitative easing or austerity. It doesn't seem to me the data was ever the problem. Are you arguing basic scientific literacy is?
This is also something you can learn through techniques that fall under what HR might call mindfulness. After a while, you have a mental git stash that you can just pop. It's not entirely lossless, but the benefits to life are immense.
Except the competition isn't between services but between streaming services and local TV channels. It's between artificially maintained "content regions" that have no basis in technological reality. The choice to host content isn't up to consumers. The period of availability is hardly ever displayed. There are platform and operating system constraints.
Finally, the pricing model doesn't allow you to say you want to watch one series and that's it, either - you'd have to sign up for a month of services, a cable package, etc. In fact, it can't reflect the price of individual content at all given that everything is a package.
You have the right to disagree, but calling a dissenting opinion ridiculous is uncalled for, given that there are actual service and distribution failings in the sector.
It's just that a lot of companies are employing dark patterns or getting it wrong on purpose, and it's working because people are now annoyed at GDPR instead of the companies doing this.
For most backend programming jobs, the challenge is not in writing complex code but figuring out what the business wants, needs and should have in the first place and distinguishing between them. Figuring out how to integrate with existing systems, processes, fiefdoms and code. Knowing when to say yes and no, how to make code future proof, etc. This is a task fundamentally unfit for what we currently call "AI", because it's not actually intelligent or creative yet.
On the frontend, it becomes even more nebulous. Maybe Copilot can suggest common themes like Bootstrap classes for a form, CSS properties, the basic file structure and implementations for components in an SPA, etc. As I see it, the main challenge is in UX there, not the boilerplate, which again makes it about understanding the user, figuring out how to make UI feel intuitive, etc. Again: unfit for current AI.
I cannot offer any opinion on the utility for actually complex, FANG-level code, for lack of experience.
In my opinion, employers should start investing in their employees again, as they once did. It's neither morally laudable nor enlightened self interest to throw someone in the deep end and expect them to swim. And in our capitalist system, it's self-indulgent to say that you want something without paying for it. That is ultimately what the article is proposing: that open source contributors sacrifice their spare time to be the mentors companies should provide.
> I told my client - apologies, but I don't want to work on this task because it's a dark pattern. And they reply - no, no, we are just sending people 3 email reminders. And then I try to explain that it's basically saving email addresses secretly.
Perhaps because this is a short post, but it seems to be missing context. The email addresses are saved, which may or may not be questionable. It's unclear whether there are any mechanisms to auto-remove the email addresses once three reminders have been sent.
It doesn't seem immediately obvious what the dark pattern is here. What am I missing?
Companies tend to pay people for their commute here in Belgium. This can take the form of paying your train pass, a reimbursement per kilometre travelled or even a company car + fuel card.
That doesn't cover the hours spent travelling, of course.
Only when the abstractions proposed actually have a pragmatic use. As developers, for a lot of us, the immediate instinctual reaction is "add another layer of indirection". Each of these makes the software more complex, adds cognitive load and increases tech debt, making it a risky proposal.
Those risks are often glossed over for purely philosophical benefits and - for lack of a better term - personal taste. Maybe you don't actually need factories, strategy patterns or even DI just because the Gang of Four book mentions it. Maybe worry about problems when they occur, not because the might occur.
YAGNI is just a concrete implementation of KISS. I prefer the approach it proposes: question everything, say yes only when it makes sense. That is what YAGNI symbolises and reduces use cases, scope, feature creep and abstraction creep. For most companies, code isn't what's sold and merely enables (parts of) the business. What matters is whether it's fit for purpose, not whether it smells nice.
If a company became less efficient due to a lack of "drop everything" taps on the shoulder, it wasn't efficient in the first place.
That statement is a bit of a truism, isn't it? If you squint hard enough, you can call most things a competition. If all else fails, in the sexual marketplace because financial success is an indicator of romantic success for males, who happen to have driven a lot of the innovation up to this point.
It also ignores the nuance to be found in whether and where to focus on public investment versus private investment, for one. I don't think you can really sensibly frame all public investment as competition, unless you're stretching it to the amorphous "international competition", in which case the principle is dangerously close to being unfalsifiable.
I'm not saying competition has no role to play, but where are inspiration, the joy of creation, altruism and wanting to abolish frustration and greater problems? We don't just have selfish genes.