Yes, I’m just elaborating.

deleted by creator

Politics is about influencing other people. Engineering is about managing constraints. Sometimes these constraints come from other people. If you want to influence a constraint you don’t like, then you often have to influence other people (i.e. politics).

I don’t see anything strange with this.

Speaking up against the manager is politics though.

It’s wild how ideas like Hyperloop were seen as reasonable ideas 10 years ago. The naivety.

This only checks that functions are called in the right order. Not that the functions are doing the right thing or if the functions are called with the correct arguments. Quite pointless testing IMO.

For example, it won’t capture cases where cmdChargeCreditCard returns a payment ID that exists for cmdCompleteOrder to use.

Set up an in-memory database, or test against a real database. You don’t test side effects by pretending that the side effects are correct.

After you’ve cloned everything you’ll Arc<Mutex<>> everything.

Linux don’t need anything to challenge Windows. Windows is doing great on their own.

TL;DR: this is an ad for CodeRabbit AI code review tool

Hah, wishful thinking

Dealing with memory usage will likely require significant rewrites and architectural changes. It will take years.

The ”memory optimizations” we’ll see is the removal of features but charge the same price. Software shrinkflation. Will require same amount of memory though.

The RAM shortage will end before any meaningful memory optimizations can be made.

This is kind of how it works in countries that haven’t been infected by Amazon Prime. In Sweden for example most e-commerce is done directly from individual stores. There are aggregation sites like prisjakt which lists prices of all different stores so you can find the best deal.

It’s not perfect and maybe not as convenient as Amazon Prime, but I don’t see how a fediverse alternative could do it better.

No idea, but probably Ubuntu ~15 years ago

Haven’t started a company myself, but I’ve worked with a few people who have.

The common theme is that you need to involve potential clients early. Understand their wants and needs. What you learn from the first interactions will likely surprise you, and greatly reshape your product vision.

Don’t build a product in isolation for two years. That’s a sure way to make something no one wants to pay for.

Part of designing large systems is to make research easier. Any question regarding the code base should be easy to find the answer to. No one can keep track of all 100,000 constantly changing lines of code, so make it easy to use the code as reference.

The problem is when the system is built by Rube Goldberg fanatics.

In short, it’s easier to manage your data if there’s one single source of truth for it.

.unwrap()

The legacy system. It doesn’t work, it’s slow, it’s incomprehensible, but you can’t do anything about it without making it worse.

Xbox 360 turned 20 this year