I will never forget the candidate around 2010 who came in claiming PostScript. Well, our interviewer started asking about stacks and clipping paths, and it quickly emerged that the candidate knew how to click Print > To File.
The key is working incrementally, not sitting idle for months and then hammering production as hard as possible trying to get all the deferred work done in exactly one batch.
Unfortunately USPTO takes "non-obvious" to mean that it wasn't already suggested by combining patents or other written work, so if you are the first to work a problem you can claim easy solutions that anyone with a clue would have quickly reached. Land rushes to fence off new fields seem inevitable.
The JVM provides a lot more flexible concurrency abstractions, but they're now appearing in the standard library instead of hardwired into the language. This lets us extend or reimplement them.
(Synchronized blocks/methods are primitive and haven't been deprecated, but they recommend using java.util.concurrent.locks instead.)
It sort of worked when there were expectations to stay on topic, but at this point a revamped Usenet would need to draw users away from brand-safe social media feeds curated with machine learning funded by advertising.
Was this a workaround for frequent exception handling being too expensive on some platform? I like how Java lets some exception instances be reused without stack frames, so performance issues are less likely to compromise API design.
Cross contamination includes stuff like fragments of sesame seeds stuck in a corner of a conveyor belt or air duct since yesterday's production run. I don't think cleanroom baked goods would be affordable.
Kind of surprised to see Blais is considering a rewrite from Python (with type hints) to either C++ or Rust. For accounting using structured text, performance doesn't seem like it should be a showstopper.
Yeah, imagine digging up red clay, throwing it in a charcoal furnace, and then hammering it for a while. You can tell you're getting wrought iron, but would you know from one batch to the next whether it's good?
I learned some TLA+ and started reading about Coq, but I was pretty disappointed to learn of the "verification gap" between the the algorithm to be delivered in a normal programming language and the manually-restated algorithm that passed the checker. We need to make a checker's input language ergonomic enough for daily use and then "synthesize" something that runs efficiently while still being known correct, or make a checker understand everyday programs (which, not being so minimalist, probably have a much larger space of reachable states to check).
https://www.mikeontraffic.com/numbers-every-traffic-engineer... says one lane peaks around 1,900 vehicles per hour. Even if we assume each vehicle only carries one driver, we need 38 busses per hour (one every 95 seconds!) to match that capacity. In practice we're lucky to see two busses per hour scheduled.
git log --first-parent shows the merges but not the complete history of each merged branch. git log --first-parent --patch displays all the changes that came with a merge as if it were one big squash commit (in general git log --patch diffs trees, not single commits).
I stash half-baked work to keep it separate from quality commits. When I come back to the stash, I may or may not like where it was going and decide to build on it.
> tied to the "system is being factory reset" special state
These should have been handled by the distro's installer. They're warning signs of scope creep; their init is trying to do so much that qualified sysadmins can't fully understand it all.
If one mass is 1.0 kg ± 40 g, and another mass is 1.000 kg ± 0.4 g, are they close enough to equal? Maybe, and if you round them to the same precision you get whichever answer you wanted.
Each mock needs to be maintained, sanity checking against the latest behavior of the actual dependency. And CI costs hardware, not developer time if he has anything else to work on.
Looks like the host started returning errors after this version from 2018, and then in 2022 someone bought the domain or host and did not preserve any content.
This. Automatically doing it well (clarifying the intent of the code) is an AI-complete problem. That's not an excuse for automatically doing it poorly and forcing everyone else to live with it.
If the brain actually used language to represent ideas in use, we should have succeeded in finding its https://en.wikipedia.org/wiki/Universal_grammar. Instead it seems more like language is a kind of lossy compression we keep reinventing for ideas, to export them from a brain in some tangible way and get them into another (even in the future).
Earnings reports happen once a quarter between the company and the public. A couple of business days after that, employees (without material nonpublic info) may trade company shares for the next month or so. Maybe you can't sell April shares until mid-July, and then you have to decide whether to wait until next July to minimize tax on gain.
Sometimes you can elect to sell every released share in a quarter, or file a 10b5-1 plan with a schedule, but you have to do that during a trading window.