bfuclusion

Hi All, since our last posting my cofounder and I have revamped our messaging and the product to be easier to understand and use. We would appreciate it if you'd give it a whirl and tell us how you liked it.

If I had to guess: Release that Witch

Correct me if I'm wrong, but I think that scheme will protect you from at most one erasure.

Fail D1 and P1 There's no way to recover D1s data since P2 has no data from D1 in it.

I have a Pinephone, and I can tell I've been really conditioned by Androids flow. Haven't quite figured out the UI yet, but I'm going to put KDE on it and see if my desktop muscle memory helps things. The hardware is a bit slow, but man is it fun to have Linux in my pocket:)

The $799 Librem isn't in the same marketplace as the $200 Pinephone. I can't see Pine64 charging $799 for a very very long time.

Why do you care? And why is that any business of yours?

This algorithm basically works when the number of elements to compute the median for is at least as large as the true median, and you've a fairly normal distribution of element values.

To get a rough idea of the numbers if this was a rail gun and accelerating linearly: 1G is 32 feet/second 32 feet /second is ~22 mph They're accelerating to 5000mph so they need to crush things at 1G for ~230 second or just under 4 minutes.

If I understand correctly, this would hold for angular acceleration too, since they'd just release at some point. Can someone correct me if I'm wrong?

I don't think it can be broken down so simply. It's clear that the constitution has provisions specifically covering this (ex: 4th amendment), so the Federal courts at least have an interest in seeing the cases. As the highest law in the land, it's also pretty clear the 14th gives SOME federal oversight of violations of citizen's rights.

Got it. Thanks for taking the time to fill me in. If I ever do 2d stuff I'll take a look at skia

Yep, that makes a lot of sense. Skia appears to be BSD licensed which is good. Not having used either, are the capabilities of Skia a superset of Cairo?

IMO 10.5 was peak OSX. Every other later one has smacked me upside the head with something going wrong.

In the spirit of discussion, why do you say this?

I'm surprised this isn't codified in the law instead of left up for administrative regulation.

Yeah, this is the second article I've run across with a non-sequitur link.

What made those computers cool was that you could do things with them than you could NOT do with the run of the machine. Yes, today is a bit boring, but we've all got super computers on our desks. This is awesome.

I like the Xerox Workcenters. Speaks PCL + Postscript, can netcat a job to it. Automatically shows up in CUPS and Windows, and has a full duplex scanner to boot. I got mine for 400$, which considering it's monthly duty cycle is 10x my yearly output I don't really mind.

Mass does not change. But the effective pressure on the tires is as if the weight (which can be defined as the force required to support something) is indeed higher.

The only reason an Ekranoplan can't fly higher is it's wings don't generate enough lift out of ground effect. Load a 747 up high enough, and it too wouldn't be able to get out of ground effect, but I'd still say it was flying.

From a pure engineering standpoint, you're correct. But after starting my own company I have a different opinion: The idea that any work is "Worth doing" more than 10 minutes ahead of time is kinda specious. Everything needs to be evaluated against what's going on RIGHT NOW. People aren't necessarily being unreasonable to interrupt, it's just that the whole picture might not be obvious. Of course there are those who interrupt when they know better, but no process will stop that.

You're conflating not knowing (or caring) what's going on with a meeting. You absolutely should care what's going on with a team, because if you're work isn't affecting each other there's little reason for you to be a team. That communication shouldn't be every day though, it should be constantly available to whoever needs it at the time they need it.

Software can achieve this, and it's what my startup is trying to make happen. The key is to unify status-as-in-state with status-as-in-active-communication so the two can inform each other.

Standups in low performing teams degenerate into managerial oversight and "reporting". That's both demoralizing, and forces people who hate it out of the company. Standups in high performing teams are usually less useful because it doesn't really matter what process you use. Your best bet is one that lets them collectively agree on what to do, and then get out of their way.

Your comment is a symptom of a larger problem. Sprints make the assumption that you've got some set block to "work on these things". It's just not true. Business is a live environment and priorities change quicker than that for both good and bad reasons. You should be asking the question "Is this something I should be doing" EVERY time you take a task, so doing that once a sprint isn't often enough.

Yeah, that's why I built my startup. Status is not a discrete event like standups pretend, but you also need a tool set that lets you raise issues without breaking people's flow. The proper way for this to work is to have your workflow system enforce some structure on severity and types of communication, and just notify you in priority order when you're ready to handle stuff. Shameless plug: my startup is Uclusion (https://www.uclusion.com)

Or bothering to pay attention to cooking methods. Sunday roast is awesome by itself, if you cook it right. No extra seasoning needed.