> They did it within a system of laws and regulations that government admittedly does create for fostering such wealth creation. However, this still often requires strenuous effort by these people for their own ends.
You are confusing two things thinking they aren’t highly related but they are. This statement could otherwise be written “government created a flawed system and motivated individuals achieved wealth by taking advantage of that system”. That implies a flawed system was causal. We don’t need bigger government, we need the right government. No one wants to say that those who worked hard - even by benefitting from a flawed government - should not have high wealth, but by your same argument, what did the wealthy children of these individuals do to justify their wealth? Their children? How long do we believe this chain of inheritance is sensible?
I believe the previous poster was arguing that taxation still exists at a macro level, i.e. money is sucked out of the economy. It doesn’t matter so much who paid the taxes. The wealthy pay the interest.
Part of me wonders if doubling down on taxing transactions (which tariffs is categorically) can thus work. It seems like an elegant way to avoid having to deal with wealth vs income.
> Yes, the only thing that genuinely scares the rich is wealth taxes
Why though? We’ve already established the end game if we don’t do this. It’s hard to imagine society willingly regressing back to feudalism. What we likely need is a sensible plan which gradually adopts wealth tax rather than a radical step change.
That's the issue right? No one knows what access they have, so you should assume the worst. They've already been claiming that they are making writes, so full write privilege isn't off the table.
It's not even the access that's the issue though, it's the lack of oversight. If I login to a Prod database, my commands are logged which allow the team to go back and figure out what happened if something didn't go as expected. We have backups and response processes to deal with "oops" situations. I strongly doubt the DOGE team has any fallback plan, and it would be irresponsible to simply assume they've thought fallback through.
This is more troubling with the systems being tricky legacy systems. You might have the best intentions, but it is really easy to make mistakes in brittle systems even if you are careful. We've already seen evidence that the team may have no idea how to interpret the data they're seeing. It'd be reckless to start making edits while only having a partial understanding of the system.
The story from DOGE is "look at all this fraud we've found, we're going to fix it now". It's not "here's a bunch of things we want to investigate further". It's not "here's how we're going to test whether this is actually fraud". It's not "here's what we're going to try and how we're going to revert if we are wrong".
I’d like to see better controls for keeping diagram components from colliding. I’m sure that’s a nontrivial ask, but I run into poorly placed components quite frequently, and I feel like that’d be a major selling point for Mermaid for me if you could solve it
If you are doing anything serious, then yes. OTP is a top tier framework for writing any sort of complex parallel/distributed processing. I’d pick OTP over ActiveJobWhatever any day. Elixir code is also easier to maintain at scale due to stronger packaging and typing. OTP’s application abstraction is genius.
Ah, the B type developer. Knows enough to find exciting and interesting problems but doesn’t know how to distinctly separate a type C (who can’t solve the problem at all) from a type A ( who knows the problem in and out and knows “it depends”). Not all that different to me from midlevel dev who learns about concurrency/metaprogramming/etc and starts using it as a tool for everything. Just enough to be dangerous.
Every database has issues and quirks whether they be about how you design your application, how you need to scale, or how you need to maintain your database. You can play this game “just use XYZ and have no problems”, but it isn’t realistic. Production databases at scale require heavy dedicated infra to stay highly available and performant, and even out of the box solutions require you to understand what is going on and tune them else you run into “surprises” which are almost always that no one RTFM. Pretty much every mainstream database is capable of both highly available and highly consistent workloads at scale. The storage engine largely shouldn’t matter as much as the application tuning.
You are confusing two things thinking they aren’t highly related but they are. This statement could otherwise be written “government created a flawed system and motivated individuals achieved wealth by taking advantage of that system”. That implies a flawed system was causal. We don’t need bigger government, we need the right government. No one wants to say that those who worked hard - even by benefitting from a flawed government - should not have high wealth, but by your same argument, what did the wealthy children of these individuals do to justify their wealth? Their children? How long do we believe this chain of inheritance is sensible?
reply