In the business world, the terms "turnover" and "revenue" are important and are sometimes used in reference to the amount of money a company generates. Depending on how the terms ...
United Kingdon vs. United States Definition
Depending on where you are, these terms could mean the same thing. In the United States, businesses use the term "revenue" with regard to how much income they generate. In the United Kingdom, the term "turnover" is used for this purpose. Regardless of whether you are talking about turnover or revenue, you are talking about the amount of money a company brings in, without paying attention to expenses or any liabilities the company may have.
Why bother with DRM. Once you have the kickstarter money, just send everyone novelty dime store yo-yos, disappear with the money and leave a cryptic message suggesting the digital expansion for the yo-yo is on the way as future DLC.
Why bother shipping. Just send everyone a link to a webpage that's just a picture of a yo-yo hooked up to fa-spin, and and oscillating up/down motion.
Now you're thinking enterprise grade. We would only have to update the software in one place.
...right up until you try to run a select distinct operation and it fails, because there's no equality operator defined for the JSON type.
Seriously?!? How can this possibly be a problem, when JSON is textual data? The equality operator is string comparison; is there any reason at all why it needs to be more complicated than that?
Given JSON represents a not-necessarily-ordered serialization of an object, I could see a case being made that JSON equality should account for objects being the "same" but with fields in a different order. Or something like that.
There are two JSON data types: json and jsonb. They accept almost identical sets of values as input. The major practical difference is one of efficiency. The json data type stores an exact copy of the input text, which processing functions must reparse on each execution; while jsonb data is stored in a decomposed binary format that makes it slightly slower to input due to added conversion overhead, but significantly faster to process, since no reparsing is needed. jsonb also supports indexing, which can be a significant advantage.
Because the json type stores an exact copy of the input text, it will preserve semantically-insignificant white space between tokens, as well as the order of keys within JSON objects. Also, if a JSON object within the value contains the same key more than once, all the key/value pairs are kept. (The processing functions consider the last value as the operative one.) By contrast, jsonb does not preserve white space, does not preserve the order of object keys, and does not keep duplicate object keys. If duplicate keys are specified in the input, only the last value is kept.
In general, most applications should prefer to store JSON data as jsonb, unless there are quite specialized needs, such as legacy assumptions about ordering of object keys.
If I'm reading the documentation correctly, the regular comparison operators should work for jsonb type...
@timebandit Are you saying that Dodge should have predicted a psycho driving a car into a crowd weeks in advance?
This is called "looking for trouble". Let's browse every company site to see if any have references to car accidents, then point and laugh at them! Well there's like 12,000 corporations and a lot of them do stuff with cars, so congratulations you found one. But understand that people without the stupid-gene are just going to sit there going, "uh huh, so what?"
All I do is remember to add 11 to the current year for my age. Saves me the hassle of having to compute it from the day/month/year partwise, since it's unlikely people are asking for my age during the first ten days of the year...
They ordered me the World's Largest USB Wifi Adapter:
Amazon.com: NETGEAR AC1200 Wi-Fi USB Adapter High Gain Dual Band USB 3.0 (A6210-100PAS): Computers & Accessories
This thing's like Godzilla danging out from the side of your computer. Sheesh.
The World's Largest Wifi Adaptor is so large, natch, that when it's plugged in you can't use the DisplayPort next to that USB port. So convenient, this workaround for this busted-ass laptop which is shitty garbage.
Oh, you mean they don't include the USB Extension cable to go with it? That's... dumb.
@dkf here the persuasiveness varies by court. For example, the 9th circuit (most of the West coast) tends to be super liberal and it shows. They get reversed a lot and most other circuits disagree on a lot of things. Same with the 6th (I think?) on death penalty cases. They make decisions, everyone else ignores them, the Supremes overturn them.
State courts have even less respect for other states decisions, since the underlying law is often quite different.
On the S8, the only useful advantage Bixby has over the Google Assistant is always-on hotword support, but only because Samsung purposefully limited the Google Assistant. On many phones the "OK Google" hotword works all the time,
Home interior shots are hard, especially with windows with daylight coming in. All the settings and methods that work for "normal" photos tend to result in crap. Wide-angle + extreme camera positions + (HDR or carefully positioned flashes) work better.
When we sold our previous house, the agent made a big show of coming to take high-quality pictures. I was a bit suspicious at first ("yeah yeah, usual estate agent bullshit..."), but he did exactly what you say (good quality camera + wide-angle + HDR) and the result was indeed impressive. Of course, when you know the house, wide-angle pictures always look a bit weird, but in a good sense as rooms look larger than they are, and the pictures certainly stood out when compared to the average property listing.
Not sure it actually made any difference in the sale, but still, that was nice (and we even kept the pictures somewhere as a memento of our old house!).
I wonder what they make of it when you're in the kitchen making breakfast and the damn thing keeps bumping into you.
It gets filed under “House with occupants too stupid to lift up their feet."
Why should I (hypothetically; I don't actually own one) go out of my way to make things more convenient for a tool whose entire purpose is literally nothing more than to make life more convenient for me?
I want to know what the hell they came up with that the FDA shot down and THIS was the SECOND attempt.
I am not sure. It was just somebody telling me by the way since I am not here that long. However, I think it concerns a bit of hardware. The old application runs on a very old custom “notebook”. And there is a newer version of that “notebook”, which is still WinXP-based and runs the same application, but lacks certain specialized hardware, so it can be used for most things except one important action that needs that hardware.
I actually use 'bug' for both the problem in the code and the ticket to address that
Many do that. I find it to be problematic in many ways. I see it as..
A Bug is a simple statement of an alleged deviation from ideal. If has a lifecycle (which can vary) from creation, through verification, and possibly to remediation.
Work is required to address a bug. The (somewhat tool specific) Task item addresses this. Sometimes remediating a bug requires multiple tasks, other times multiple bugs are remediated by a single task.
No work [Task] should be done without providing an increment of Value. Thus a PBI/Story represents the value delivery. This PBI may involve multiple tasks (not all of which are directly associated with Bugs!)
A Test [TestCase] should be created which fails due to the bug, and passes once the bug is remediated. This is a defense against regression.
That the top 4, but should be a good start. The value received has been repeatedly demonstrated in multiple ways, with one of the most common being a much better understanding of "Technical Debt and the Related Interest".
What does this all have to do with the "...Git...terrible..." focus? Simple. Git is not designed for this level of tightly integrated information [aka a type of centralized information store].