texaswhizzle
Joined 5 years ago
Joined 5 years ago
Kicks off a media shitstorm by refusing to talk to the media. Risks tens of thousands in fines, a WTA investigation, default from the French Open, and expulsion from future Grand Slam events.
I’m sure all that is great for her mental health.
The total supply of Bitcoin is 21,000,000 coins. However, every single coin is 100,000,000 individual assets.
21,000,000 sounds pretty finite. But 21,000,000,000,000,000 sounds a tad less finite. The price of Bitcoin relies on the fundamental false premise that it’s scarce.
Disgusting.
The really sad thing is the children. Parents uploading their kids entire lives and the kids have absolutely no way to opt out. Permanently giving your kid an online identity before they can even talk. Horrible thing to do to your child.
This is also true for Amazon business purchases. I have returned items around $600 and have never been asked to put a code in the box.
But I’ve never returned anything over $1,000.
The market is so wild that it doesn’t even make sense to make a down payment. Just take the PMI.
Short term rentals are lucrative. Owners can earn many multiples of their costs per month on the short term rental market. Significantly more lucrative than traditional long term rental properties.
...and finally, the ridiculous bonus depreciation rules.
Borrow at low rates, secure cash flow into the future, and write off 100% of eligible improvements the year you spend. Yeah, no shit the housing market is going ballistic.
I also think people tend to strive for too much purity. It's okay if you want to avoid the replication and event bus complexity of microservices and choose a monolith-esque database architecture. Just split your APIs across business domain, leave your database as it is, and be done with it.
Just make sure you stick to the fundamental principles of microservices. Scoped, fault tolerant, independently deployable. Fault tolerant does not 100% have to include database failures. Don't ever directly cascade API calls from one service to another.
The biggest "why not" is that you should choose the architecture that best solves the problem. Don't treat architecture as a playground to try out random shit. Solve the business problem in the simplest way possible. In most scenarios you probably don't need isolated, fault tolerant, distributed services. I would guess that 75% of microservices implementations fall under the premature optimization anti-pattern.
It reminds me of when my college required linear algebra for my degree. Learning things that I knew without a shadow of a doubt I would never put to use again.