1,297 karma · joined August 19, 2013
Watery tart!
A lottery to set the initial order is fair to everyone.
If you want to find out what the actual cash value of picking first, second or third is then do an auction.
That's pretty awful.
Do early buyers pay a premium? Do late buyers get a discount?
Why not do a lottery? Or an actual cash based auction (proceeds go to maintenance fees... which is good for everyone)?
Huh... what folks need is a way to rollup their copper wiring and take it with them at the close of business.
It primarily focused on configuration tables, and optionally a slice of the main data tables.
The tricky parts were:
1. Write code to write out DDL. This is easier than it sounds because not every DDL feature is actually used by the application.
2. Write code to dump out DML. Again easier than it sounds because not every datatype is used by the application. The tricky parts where automatic identity columns and large binary table.
3. The code from #1 and #2 has to be done in topological order (least dependent scheme objects to most dependent). After the DDL is write, write the DML.
4. A bit fancy streaming to ensure the webserver doesn't build everything up in memory before zip filing it and beaming it down the wire.
5. Some care needs to be taken for confidential information. User passwords (even bcrypted/scrypted) shouldn't come along. Nor should thinks like outgoing email server settings. Or incoming email server settings. I'm lucky as no PII or credit card details exist in $DAYJOB application.
If done carefully the code should be insensitive to simple schema changes (new fields, new configuration tables).
The goal behind it all is to produce a single (big) .SQL file that will recreate a working database.
So worth the time and effort to create.
It strikes me that "balance" is probably one of the rules of legged animals (thinking of rules in terms of the boids rules of separation, alignment, and and cohesion).
I was wondering if that would make a good story for a TV show/movie. The UK government protecting a secret village is the Scottish wildlands, an intrepid investigative journalist, and ... well I never did get much past the idea :)
This is the biggest pet peeve of mine. Over the years I've spent too much time ensuring I can get a stack trace *WITH* line numbers. A stack trace without line numbers makes support much more difficult.
For .NET why I need to generate and include .PDB files just to get line numbers I dunno. I've never ever used a .PDB for anything but stack trace line numbers. I'd bet that I'm not alone in this. Why the runtime could include them in the DLL (ok driven by a switch) I don't know.
And for JS those .MAP files can turn out to be larger than the original source files. Which is a bit mind boggling. And don't get me started on .ts -> js -> bundled to get the map files right. And the JS client libraries to handle unexpected exception capture and logging. And the server side parsing of the client side error and map files to get back to an original error line number in a .TS file.
It's downright shameful that the most assistance a runtime can provide is a stack trace without line numbers.
(from Red Dwarf)
I don't ever want to have a card number in my database or via a administration system (my own or my provider's).
So I care... but just perhaps not in quite the way you're thinking :)
Selling a bugged phone to a known criminal is likely fine (cite: The Wire).
But is it acceptable to sell a bugged phone to unknown/unidentified/random people and then use the phone's communications to determine if the owner is a crook and the owner's identity? The sole basis of suspicions seems to be "bought phone", or maybe "bought phone using bitcoin", or even "bought phone on TOR using bitcoin".
It will be interesting to see how many of these cases hold up in court.
C# https://docs.microsoft.com/en-us/dotnet/standard/simd and https://devblogs.microsoft.com/dotnet/hardware-intrinsics-in...
So the normal excel formula in cell b1 of "=sum(a1..a26)" has it's output written to b1. But with calc you could in cell b1 put "b2=sum(a1..a26)" and the result would be written to b2.
This became super powerful when dealing with ranges. You could have 1 formula that that calculate the row-wise total for each row... and it would be in 1 cell, so for example "$1..$10=sum($1..$9)" (forgive me I can't recall the addressing specifics for relative/fixed/named ranges).
It was pretty amazing at the time.
> The judge demanded an explanation “about what exactly Google does,” while voicing concern that visitors to the court’s website are unwittingly disclosing information to the company. “I want a declaration from Google on what information they’re collecting on users to the court’s website, and what that’s used for,” Koh told the company’s lawyers.
Someone had a bad day at court :)
Holy cow.
I remember looking at an e-ink reader years ago and thought it was unusable because of the weird page refresh/slow page turn.
(there are about 4 completed saw tooths above the screen)
Made me snort.
What can you say... the man liked worms.
:)
How would a judge distinguish the two?