Surely driving the vehicle in a manner that was certain to break the transmission within 4 months caused no other excessive wear in the vehicle, right? Sounds like a terrible idea, really.
371 karma · joined January 24, 2013
Not when they get to simply turn off the half of the market moving against them they aren't.
We even had a 20% bump in gross revenue while bringing our costs down, and that's after 2019 was flat for us (prior to that we were hitting 30%+ for a handful of years in a row).
https://voxeu.org/article/stable-coins-dont-inflate-crypto-m...
No, absolutely not.
The size of your testicles is in no way indicative of your testosterone production.
While a shorter period of use generally has a higher chance of your natural production restarting after ceasing exogenous testosterone, your natural production of testosterone shuts down immediately with the introduction of exogenous testosterone.
Market makers and trading shops with 7-8 figure funds playing with riskier cryptos or trying to tap worldwide volume.
It's not MicroStrategy and Mass Mutual Insurance using Tethers
That's not the primary use (by dollar volume, it is also helpful to streamline participation in the entire crypto ecosphere regardless of local regulations).
But Tether's for market making. Arbitrators need a way to transfer USD denominated amounts between exchanges to operate.
On top of market making, you'll have smallish (7-8 figure USD) trading shops running strategies across multiple cryptos that just don't have fiat ramps, or they want to tap into volume across exchanges that don't have fiat ramps. If you're one of these customers, you can get in touch with Tether and make redemptions, but you probably don't need to do that anyway because you're working through a prime broker.
This activity doesn't care if the market's bull or bear, so it continues to grow over time in either trend.
I pay 0.15% and the exchange has been around for a decade without ever losing funds. It's even now licensed as a bank in the U.S.
Kraken, Gemini, and Coinbase are all quite trustworthy, if any of those are available in your locale.
Buying and holding for 4+ years has produced amazing gains in Bitcoin since its inception. Trading often and fooling around with alt coins has caused many great losses and pain. Don't invest more than you can stomach losing or holding in the red for a few years.
Not just voters, large portions of our representatives are also from that demographic.
I could create a blockchain and issue a quintillion coins and if I manage to get it listed and sell some for a fraction of a penny it'll have a bigger market cap than the rest of crypto combined.
I ended up with the L-Tek one you linked. The buttons seemed awfully futzy to me, and she says they're ok but not great - plus her toes hit against the edges of the raised non-button squares and hurt.
Pure proof of stake is fantasy. That's not "Bitcoin" and it never will be.
My personal hope would be that mixed proof of work and stake with on-chain governance, like Decred (their devs have built much of the Lightning Network tooling, performed the first cross-chain atomic swap, etc.) - could be adopted; but, realistically, I think that's also a fantasy.
Earlier than that, I might sell a little bit in the upcoming year to free up some cash for a home purchase.
For those true to the _original_ Bitcoin Cash chain. lol
"A mile is so big that the entire planet is only 25,000 of them around. That's definitely not a whole lot of them for something as big as the entire planet."
Feature work is such a smaller part of my individual contributions at this point - I do some here and there so I don't get too out of touch with the front end and user experience - but much of my coding work these days is reworking existing core functionality.
Thankfully we understand the necessity of deep maintenance for our system that we fully expect to still be running in 10 more years, but even with that it's damned hard to keep up. I can't imagine having developers come and go every couple/few years and little or no leadership support for code and systems improvement.
> a better solution isn't obvious. You can hand it to someone fresh, and after significant effort (on both of your parts) they agree with the inconsistency, but they won't propose a solution that's any better
> Once you've contributed enough of the main functions of a code base, you just never lack for something to do.
Hello, friend, I see we know each other well.
Could you?
It's like an hour to copy/paste a reference implementation and set up unit tests. Maybe an hour or two fine tuning the implementation for your language and benchmarking some use cases.
I'd been using the same C# Boyer-Moore impl for like 15 years, and happened to have just recently updated it for Span support. I doubt I have 8 hours into it in total, and it's thoroughly benchmarked and tested.
And not just a little bit more value..
Is an index fund a store of value? Would you recommend someone store their value there if they wanted it back out in less than 4 years? Gold? Property? Or would you suggest those stores of value are only suitable for longer time frames? How much more value does someone who stored it in Bitcoin 10 years ago have now?
Curious to see if there are any recommendations in this thread.
I would guess poster above doesn't yet have 30 years experience. Perhaps 10 or less.
My experience echoes both yours and the above poster's - following a sort of bell curve - after initial ramp up, there was a significant period where every question led to several more. At some point that peaked, and by the time I'd been writing code for 20 years the rate of questions was dropping quickly.
Also the character of problems changed a lot. There's a point where QA sites like StackOverflow become largely useless for your problems, as they're too broad, complex, and dependent on specifics to fit the QA format. Even relevant blogs and academic papers become thin after 20 years.
Thankfully, however, fiber _finally_ became available on my block this year.
Ten years working on a code base that serves near-StackOverflow levels of traffic and 5% would be a _huge_ win. I don't come across those, or even 3%, very often.
Our app has dozens of routes all seeing hundreds to thousands of requests a minute. To get a performance boost that big it has to be in some foundational code that's used nearly everywhere, and that code's already been poured over every way from Sunday.
Occasionally we'll run into a bit of code that sneakily becomes a significant drag on the system as traffic through that code grows slowly over time. A fix might result in a large % load drop, but only because there's some pathological problem, which I hesitate to call an "optimization" rather than a "bug fix".
We did also uncover many significant optimizations after migrating from dedicated hosted bare metal boxes to the cloud, when our network latency assumptions got thrown out the window - but the bulk of those optimizations were simply "cache it".