ownagefool
Joined 14 years ago
Joined 14 years ago
Only needs to work once for him to get a passive payoff. Sitting in your lane usually doesn't buy you that.
I guess my question there is, is DHH ignorant to who Tommy really is, or is it a full endorsement.
It's a fact in British politics we refuse to publish crime stats per ethnicity, but the Danes do, and it's fairly obvious that certain types of immigration aren't good for your society.
Of course, these are cultural problems usually linked to specific regions and socioeconomic backgrounds rather than actually race related, but we've been in a weird space for many years where it's racist to discuss the problems, and ergo when you do find people willing to discuss them, they do tend to be actually racist.
Which makes it hard to jump to defend DHH here, because you're unsure what you're missing. The sad thing is, the denial drives actual racism, because it's the only outlet to actually discuss the problems.
For those not aware, British population growth is about 10m in 20 years, largely immigration ( Births are below replacement rate ) and largely pushed to depress wages and expand the tax base to fund pensioners. There's also a lack of investment in services, we can no longer easily find a GP, Dentist, School spots, and house prices have become unreachable. It's more class warfare than race related.
However, it doesn't need to be exclusively negative. The data will both show where you can price gouge but also simply where demand is.
Put your coffee shop near a metro stop and sell sourdough bread and people will buy that because they want it isn't exactly negative.
Way back when, you'd see a lot of people stuff their jenkins in their dev account. There's no way that the system that builds, publishes and deploys your application should be treated as anything but as sensitive as the production system itself.
( To be fair there are mitigations such as reproducible builds, but you're now doing a bunch of engineering to tie in your deploy system. )
You can decide whether that was better or worse.
Internal hosting teams ( cloud or on-prem ) should work more like public hosting environments and should focus on:
- Segregating workloads. If amazon can host a hacked service on their hosting stack without every tenant immediately being compromised, you can too.
- Self-Service. Teams should be able to just get accounts and do stuff without asking anyone.
- Building assurance. Now you've made it easy for teams to do small things, you're more likely to get more users and have less shadow-IT. You can now try and build organizational assurance without making teams suffer.
A team just needs petty cash and a cost code for a small amount of space in dev land.
What everyone does instead if ask for the planning to be done and completed upfront, which isn't realistic for a team you just stood up trying to do UR and a POC.
With a cloud provider, you can get an account by filling out a sign-up page and handing over a credit card. Internal teams will often hide behind Bureaucracy and a ticket system, with processes that make hosting a simple web app take multiple quarters.
Now there are layered reasons for that, some of them with legitimate basis, but at the end of the day they're usually low skilled teams click-ops-ing some VMWware, delivering a terrible service.
It's entirly possible that the experiment fails because of politics, but it's also possible that the amount of politics is simply lower because people are simply more reasonable.
The last part will come down to vested interest and ideologues.