Sociopathy...
1,238 karma · joined July 10, 2010
Go away...
If corporate wanted to reduce the desire for remote - they would have smaller satellite campuses outside the great automobile slums of America.
The wealthy don't care about efficiency, they aren't being rational about this.
They go into the office - see an empty building and say "this is wrong".
But they put the cart before the horse - they should say "why is my company operating just fine without office space?" - that should say something about how horrible open offices are for productivity.
The intangibles that come with in-office work could be addressed by augmented reality meetings (a headset costs a lot less than a year of gasoline).
The ONLY problem I see that isn't addressed with remote work is junior development. This again could be addressed by much smaller campuses and augmented reality.
One rule set is Dungeon Crawl Classics - https://necroticgnome.com/products/old-school-essentials-adv...
Medicine shows that others are going to bat for you to keep you alive.
There's a lot of "memory" in housing prices.
Houses are just about the hardest item to build in America today. You need land, and you cannot make them in a factory. All cost cutting measures have been in materials (to the point where quality is degrading).
Regulations push new players out of the market - increasing prices.
Housing is a social prestige item like health care and education - so that will drive costs up too.
The US will have 100m more people in the coming decades no matter what - so demand will always be high.
Solution? There is none. It's how the power elite want it.
- Looks at github... :-/
But I can see the argument where you wouldn't want a "work relationship" to turn into a "friendship".
Friends might let things slip - and then there's resentment. That expectation of diligence might fade slightly in a real friendship.
I can see the argument to keep it professional in most cases. Having a work network and a friend network is an option.
Just make sure to maintain both...
You would have an idempotent queue + a circuit breaker pattern. If the queue depth is too large - you break the circuit.
But if your profit per request is higher than your infracost per request - why not autoscale till the cows come home? Within reason of course.
In America the pinnacle of collective action is the corporation.
Corporations are required by law to maximize shareholder value - not maximize communal quality of life.
There are other levels of communal action in the US - churches and family mostly.
Cities are a product of intense collective action. In the US - it's very easy to hobble the collective action of a city. The days of Robert Moses are gone - which is a good thing - he was a bastard.
Even if we adopt strategies like "Strong Towns" that's not a guarantee of non-squalid street conditions.
Nation states need to re-evaluate what their purpose is. Not likely to happen though.
If you're burndown chart isn't burning down, something is blocking your team. A manager finds out what is blocking the team and works on it.
If your team has a bunch of tickets in process- then your WIP is high - that's bad. Someone taking on more tickets to just get to work should be pulling the equivalent of an Andon cord.
Tasks should not have estimates - tasks should roughly have the same time to complete - a task that takes 10 days is not a single task.
A sprint meeting should only assign new tickets based off the previous rate of completion. Adding more WIP only fucks things up more than they are.
Management sees the rate of completion of features - and then calculates the time to project completion in sprints.
IF YOU HAVE A DEADLINE and you're missing it...
- cut back on features - or find out what's blocking your team.
Developers need to be told to emphasize and raise up items that are blocking them.
In any value stream - there is only one current constraint. The rest of the production process needs to be subordinated to the constraint. Is it pull request reviews? Is it the QA process? Is it ambiguous tickets? Are questions not getting answered?
https://www.lastweekinaws.com/blog/aws-cross-az-data-transfe...
If too many people do this - AWS will "just close the loophole".
There's not one AWS - there are probably dozens if not hundreds of AWS - each with their own KPIs. One wants to reduce your spend - but not tell you how to really reduce your spend.
If you make something complex enough (AWS) - it will be impossible for customers to optimize in any one factor - as everything is complected together.
Rent a condo, do a communal office, if you want more close collaboration - shuffle your teams to colocate them - not force them into 1hr commutes into a fucking empty office.
Our infrastructure is now ephemeral on the cloud - why can't we be more flexible with our work situation?
If you need to hire someone to manage stuff you have to build or do yourself because DO doesn't support a solution yet, then that's something you could have spent on AWS. Do you really have spare devops talent just waiting around?
For example - SQS is pretty good and reliable - but you could use something like a rabbitmq droplet https://marketplace.digitalocean.com/apps/rabbitmq
How much traffic can that droplet handle? What happens if it fails? How is the droplet maintained and patched?
Or I could just call boto3 sqsqueue and be done with it... are queue's really the top cost of infra? Probably not - your top cost is probably database.
People probably build up a solution using AWS tech - and see where things suck. Then they move off those bottlenecks or cost tent-poles. If there are none - then stuff is left as is.
I like that it's more efficient. Gas kicked a LOT of heat into the kitchen.
I like that it didn't scorch the side of the saucepans.
Ultimately I switched to avoid burning fossil fuels. Every bit counts.
If C++ is ok with being a small language used by and for geniuses - I have no problem with that.
If C++ wants to be popular - we need a breaking change between the world of 2023 and 1990 - they don't know what we know now.
I like some parts of C++... it's too bad the "good language" is shackled to a mountain of razor blades.