Contracts are basically unit tests for whatever size of unit you're testing. How do you capture all the dynamic behaviors of a system without some sort of end-to-end test? Delayed timers, queues fill, missed interrupts, locks are held for too long, dead lock, live lock, priority inversion, dropped messages, out of order issues, etc. These things are not captured by contracts and are often exactly why the end-to-end tests were flakey in the first place.
People aren't good at hydration, at least I wasn't, so at the risk of self promotion I have an iphone app called Max Hydrate - https://apps.apple.com/us/app/max-hydrate/id1575744883#?plat... - that calculates how much you should drink to stay hydrated. It's based on research and the most important parts are free.
I had thought about it mostly for working out and athletes, but perhaps in warmer temps it has more general applicability. I've learned older people often suffer from dehydration without realizing it.
It has a WUT test to test for dehydration and uses your sweat profile to suggest hydration products. There are a lot of options these days beyond Gatorade and Pedialyte.
Most people don't get enough salt, so that's something to watch out for, especially if you are a salty sweater.
The internet gets along quite fine without DNS. Packets route from network to network. DNS is an application-layer protocol. People often confuse the web with the internet. We use phone numbers for phone calls. It's conceivable with IPv6 you could nail up your IP address and use a QR code to make the addresses accessible. In a hundred years will DNS still be necessary? I don't think so.
This is just depreciation. It's an accounting thing, not a tax thing. Everyone gets depreciation. Any dollar you spend to make money you usually get to deduct. Propublica seems to hate depreciation. These articles are hard to read sometimes. Depreciation is a real thing. It reflects the use of the underlying asset.
Rapamycin – Increased mean and maximal lifespan in both males and females when initiated at 20 months of age (Harrison et al., 2009) and when initiated at 9 months of age (Miller et al., 2011). Females responded more robustly than males at equivalent doses; when ~ equal blood levels were achieved, response was also about equivalent in females and males (Miller et al., 2013).
If you read the article, they are calculating a fictitious thing they call the “true tax rate”. This is the tax paid compared to the growth in assets.
That is not an income tax. It’s a wealth tax. It feels like conflating the debt and the deficit. Effectively you would have to have a deemed sale of all assets at the end of the year and pay tax on the gain/loss.
I agree that the rich have access to tax planning machinations that most tax payers do not. But this doesn’t bluster their argument.
The @MainActor is nice. It was always bewildering to me that we still had put UI operations on the main thread by hand. I still don't get why we need @MainActor. The compiler should do some sort of flow analysis and do the right thing.
The usual approach when management is this dim is to give a well couched opinion as to the reality of the outcome and then say sir yes sir or mam yes mam and that you'll give it all you got captain. The bug will take however long it takes to be fixed. Schedules will slip out as necessary and life will somehow magically go on. If you have reason to believe adding more resources of various types will help, then by all means ask for them, but there's usually no dealing with this kind of management dictate and arguing up front will just put you in an even worse situation than not making the deadline. You will be labeled the obstructor, not the realist.
Nicely explained. I like the idle operators/row dichotomy. At a system level push based systems suffer from the same weakness as event driven systems: incompleteness. You can never be sure you haven't missed an event because it was dropped during system startup, network partition, failover, queue full, buffer overflow, packet drop, etc. This doesn't always matter, but with a pull based system you know the result is based on all the data, but as you point out, that has a cost too.
No mention of the nutritional value. Which is my concern with Beyond Meat as well. It's great that it's not meat from factory farming POV, but it's not nutritious food either.
That does get to an issue I was wondering about: how long does it remember and does it associate each ping with a geo tag?
We live the mountains with poor coverage and a dog who at one time was a wizard at escaping and getting lost.
Yet we do have people all around, so I think the iphone solution would work, even if it was delayed. At least I would have an idea of where to start searching. I bought every lower than professional level device and they all just didn't work here.
Unfortunately Whistle doesn't work in areas with poor coverage. And then there's the battery issues. A tag would at least be a good redundancy solution.
Which in the US means waiting for Medicare. Doesn't it? For most Americans there is no part of retirement and growing old that doesn't revolve around access to Medicare.
I'm curious what other people think when they take over your code? We all have a bias to think our way is simple and obvious, yet it rarely works that way in practice.
Abstractions are a way of trying to find a common ground conceptually. Agreed, abstractions should not be multiplied unnecessarily, but in the same way it's easier to learn Newton's Laws than read Kepler's data, a few well chosen abstractions help others organize and understand what's happening in a code base.
Once you have actors it helps to have a priority mechanism, latency guarantees, a scheduling abstraction so work can be partitioned, some sort of boost mechanism to prevent starvation, a timer abstraction, and a state machine abstraction to carry out work flows.
Not really. There is no objectively true unarguable definition of life. When in silico life becomes reality and humans do their human thing of devaluing anything that's not like them, it won't matter what human consensus deems as life. I'm not worried about determining what "indeed will be life forms" no more than I worry about objectively defining what is a good meal or which is the most beautiful color. Humans have no standing it determining what true life is. What's important is developing an intentional stance towards whatever is not us.
#3 removes the whole class of AI based life forms that would not need to replicate. Our future AI citizens may not appreciate not being thought of as living.
My wife is a tax accountant. From a software perspective taxes are a nightmare. I made a service BasisCalc (https://basiscalculator.com/) to automate just one little part of the big multi-dimensional elephant that is the tax code and it was terrifically hard to implement. I can't imagine doing the entire tax stack. There's local, state, federal, and international. The code changes all the time. The dates change all the time. There are real substantial penalties for being late. There are so many data sources to integrate. She spends thousands a year and many hours of her time simply on tax code updates. She has serious legal liability for her work. So will your software. I would pick an easier target, like solving world hunger or world peace. Taxes will be simpler when politicians want them to be simpler and there's no profit in that.
Loved FoxBase PRO. In college I traded a gym membership for foxbase programming. I sometimes wonder that we haven't progressed much at all from those days.