Static typing is very useful and time saving. I can rename something, knowing my IDE can propogate the change. I can call a function and know what it expects, not just "a thing, hope they added a comment so I know what type/shape wont blow it up!".
Here I am talking about the basic static typing, and maybe some generics use occasionally, but obviously people also go overboard sometimes with type features and that hinders understanding for newcomers to the codebase.
Property-based testing and model-based testing are closely related. Both ask the developer to state the expected behavior of a system (whether you call it a property, invariant, model, specification, or contract) and then validate that behavior over arbitrary inputs and arbitrary sequences of operations. Property-based testing frameworks also typically provide fuzzing and shrinking.
Where we felt there was a gap was in expressing rich stateful behavior: models involving non-determinism (e.g. a timeout where the write may or may not have committed), concurrency, and eventual asynchronous completion, and then checking that an observed execution trace conforms to that model. Accordant aims to make those kinds of specifications concise and readable.
Once you have such a model, it's possible to integrate it with the fuzzing and shrinking capabilities of existing property-based testing libraries. We'll have documentation on that integration soon.
https://www.useorganizer.com/ helps you organize stuff primarily but can also double as photo album and private log. Open source and local storage. Not so much working on. It is complete and does what I wanted it to.
Seems reasonable that the area needed would be less than the solar panels. Since it sould be more efficient to dump heat than collect energy from light.
It seems to me that there’s a lot of math in the middle of this that just doesn’t matter that much: every photon hitting every part of the array is going to add energy. Whatever percent we transform into data doesn’t matter — all the energy from all those photons minus energy used for station keeping needs to be radiated away. I guess if some is used for station keeping so much the better.
I was hoping to read about what exactly these ‘heat pump radiators’ look like, but I guess ultimately they’re going to be lasers or flashlights or some such thing.
A relativity course question I recall from my youth asked how long an astronaut stranded 1km from a ship would need to point the flashlight away to return to the ship based on the mass of the photons leaving the light — spoiler - this can work in time to save an astronaut’s life — double spoiler: if you’re really accurate, it’s better to throw the flashlight if you’re in a hurry.
As I write this I realize my physics model is super weak, because I’m not sure what percent of the energy used to make a photon turns into the photon’s mass (and therefore is pushing against the laser), and what is in light and therefore just, you know, carries on for billions of years until it hits something else.
I /clear all the time out of habit. I want to be able to get the thing done with minimal context. It also means you can do it again slightly different if needed, you know the seed conditions for the task.
https://www.useorganizer.com/ helps you organize stuff primarily but can also double as photo album and private log. Open source and local storage. Not so much working on. It is complete and does what I wanted it to.
More specifically: aim back, and where the left side (as you now face) starts to ramp down there aim for the spot where it starts to slope down. Full power.
No, I mean they don't show it at all in their API to prevent distillation. The reasoning is encrypted and only accessible by their server. They sometimes show a summary of the reasoning, but it's not the same as the actual contents of the reasoning.
Here I am talking about the basic static typing, and maybe some generics use occasionally, but obviously people also go overboard sometimes with type features and that hinders understanding for newcomers to the codebase.
reply