“Your obsession with and constant annual threats to move Dreamforce to Las Vegas is ironic, since it is a fact that Las Vegas has a higher rate of violent crime than San Francisco,” Conway wrote. “San Francisco does not need a federal invasion because you don’t like paying for extra security for Dreamforce.”
Benioff has mostly avoided discussing Trump, ICE, H-1B visas, and immigration during Dreamforce this week—Fortune’s Jeremy Kahn was on the scene, and asked Benioff about this directly—but he said Tuesday that he just cares about everyone’s safety.
Benioff is now in on the tech fascist trend of endorsing lawlessness and violence. I guess he's really needs those government contracts. David Sacks is cheering Benioff on with his militarism.
Benioff needs those sweet army contracts so much he's got to vouch for calling in the guard to SF to glaze Trump. Of course he won't be there. He'll be in his billionaire bunker in Hawaii playing with his 'ohana'.
Benioff and Diddy were business partners on a 'Black Enterprise' venture when Benioff was a DEI fanboy. I guess he's got a lot of Trump bootlicking to do to make up for it.
There will be AI agents building super viruses, actively attacking the power grid, and stealing every dime out of your bank account. All of this will not be done on you behalf.
Yet another hypocritical tech fascist's mask falls. Benioff who has made his fortune by outsourcing jobs to India and passively abusing his employees with his family 'ohana' bullshit now wants to see his money making SF drones at the end of some kid's M4. Funny he didn't mention sending the guard to Hawaii. He is sucking up to Trump because he needs government contracts for his agentic enterprise bullshit, which isn't selling well, to make money. If you needed a reason to sell CRM and tank the stock so Benioff learns to shut his fascist mouth well now you've got one.
85% of Trump's base think this is a bad idea. Trump is not that impervious to public opinion. Especially from his allies. Trump can't escape the laws of political gravity and isn't militarily strong enough to control the country. If he was Congress would have been jailed by now. He will resist and bend the rules as much as he can. But he needs the system to not break do the barrons don't overthrow his ass.
Of the 200K workers laid off in the past year why are close to 40% according to the article Indian? In the US a predominately non-Indian country where Indians make up 1.35% of the population almost half of the laid off were from a single nationality. What factors explain these statistics?
In my experience reliance on feature flags tends to turn any application into a mess of interwoven state. Feature flags are hardly ever removed and unintentionally creep more and more into the development future features as they depend on older features guarded by flags. If you use feature flags you must have a process of deprecating them to maintain sanity in the codebase.
What I've learned of "good" program design in my career has come mostly from watching people maintain systems after the original authors have left the project. Compositional systems with well defined abstractions and ownership boundaries seem to fair better over time. They are generally easier to extend while maintaining the abstractions. Unfortunately, most systems in production aren't designed this way. The majority of systems designed at the companies I've worked for are done so by entry or junior level developers. This usually has do with how the promo process works at these companies but thats a separate discussion. Dealing with the pain that poorly designed systems cause really highlights the properties that make certain systems well designed. To gain the experience here get on a project team that has an oncall rotation, preferably a 24hr rotation. If the team has a group of dedicated support engineers even better. This to me is an indication that the team's systems have a high operational load which is usually caused by poor design choices. You'll quickly start to identify the pain points in the system. Next, try to address those pain points. Rinse and repeat for years and you'll understand "good" design.
I think this is an X/Y problem. The problem isn't pinning to latest. The problem is lack of automation that makes builds reproducable. In at least one FANG company I've worked for if you aren't building from latest no one will listen to your issue. Too much software changes to quickly to be pinning to specific versions. However, the build system keeps track of the build audit details and can rollback any build to any state. Teams are required to add the necessary layers of unit, integration, stress, crush, and chaos testing to validate each build. Its not cheap but when you need to do a monthly firedrill of 'emergency update this dep because of Z vulnerability' its worth it.
I have no problem with the 6% number for URA. The problem I have is that the 6% never seems to include managers. So when your manager bad hire bungles the OP1, constantly randomizes the team, and then jets to another team in 18 months the manager keeps their stock grant and the poor pleb dev that worked under those conditions gets the axe for their 'poor performance'.