ggruschow

I think you're reading the "SAMPLE LEGAL APPRAISAL" which is an appraisal for a different item. I think it's just to give you an idea of the form of appraisal they'd provide for insurance purposes.

Impressive paint & decal restoration. I've spent a little time trying to restore some of these finished before and given up. This gives me hope. Maybe I'll try again.

Not as of 2 months ago. It took days of crashing or hanging programs to get the photos off my wife's iPhone. I tried everything mentioned including Image Capture on a new MacBook, and the problems were at least as bad for me. I had to change the sleep settings on every device involved to multiple hours because a 30 minute hang was on the good side. In the end, what ended up working best was a full backup of the phone to a PC with iTunes, and extracting the photos out of the backup with iMazing.

For perspective.. I remember downloading and installing Linux off floppies. That sucked too, especially with bad disks or download errors, but it was less frustrating than this.

It seems like they don't improve it because iCloud seems like it works smoothly, and they get an on-going profit stream out of it. The process was so brutal I almost broke down and paid for a ton of iCloud storage.. but didn't because getting lots of photos out of iCloud is also painful.

Geez. You'd think that the letter N, being at the very center of both GNU and Linux, would warrant a space on a Linux user's keyboard.

Some things to think about:

  - 50mb is >> total cache on most systems you'll use.
  - This is far from the only function you need to optimize.
  --> The best performing algorithm in a micro-benchmark can be sub-optimal in real use.

  - You've got a fixed-for-the-day list of <10k <9 letter unique upper-case strings
  - The bulk of them you'll process are <= 4 letters (CMCSA/CMCSK be damned).
  - The median is 3 and the mean is <3.6.
  - The symbols aren't anywhere close to uniformly active
  --> Benchmark with a typical data stream, not a uniformly distributed one.

  - You're likely not even considering trading most of them.

  - How much better is your algorithm than the obvious binary-search?
  - Or worse -- plain'ol front-to-back linear search?
  - Are you sure you understand 100% of how the computer works?
    --> Yes? Mail a check to Goldman and find a better line of work.
    --> No? Test it with a quick benchmark.

  - Is binary search cache friendly?
  - Why not? Plot out the memory accesses if need be.

  - What's wrong with taking a linear-interpolated guess?
  - Is that cache friendly? .. or could it be?
  - When your guess misses, what's that cost?
  - Can you think of a cheap modification to lower that cost?
  - Is the distribution really linear?

  - What's wrong with a "perfect hash function"?
  - Does it need to be perfect?

Incidentally, hardware wins at this function. You can just generate logic to do all the if symbol == "XYZ": return 3's in parallel.

People have to be more satisfied with their jobs to work from home.

Panning would work fine since the objects in this projection don't change anything but position with panning. Spinning would only work in 90 degree increments, but that's fine for many, maybe most cases you'd be doing this. Most isometric-ish projection systems I recall seeing don't spin / change perspective. I'd imagine that's because it's disturbing to look at since things don't get smaller as they get farther away. For whatever reason the static version doesn't induce the same reaction.

What did I say that called for downvoting?

You could skip all the CSS transformation stuff and just serve the browser the images in the orientation you want them. In this projection and buildings-of-cubes, there's only 2 perspectives for a wall and 1 for ground/roofs.

Smartphones are replacing standalone cameras, but the analysis in the article is busted. Popular camera models are constantly being replaced with newer shinier models, so of course every model trends down a little while after release. It'd probably be a lot more enlightening to do the analysis grouping usage by family (e.g. Canon G11, G10, G9, etc) once and then doing an age analysis for each family.

I like his approach - get others to help him create content to drive traffic and pay them with ebooks.

He just taught me that I'm supposed to uses two spaces after a period when doing most of my writing.. in programs.. which are still usually viewed with fixed width fonts.

It's easy to be wrong when it's so hard to make out what's right. Algorithmic traders are unusually secretive about their modes of operation. The primary knowledge dissemination mechanism is via employees moving.

There were tablets on the market before Macs.

Perhaps they'll just use voice recognition to listen to your conversation to improve their ads.

To be fair, if you've got a budget that supports a multi-developer team and you fundamentally need their solution, you can afford their prices. They're not insane, and if you just ask they're not opaque.

On the other hand, did you know you can turn off the garbage collector on CPython?

I'll pay more with far less onerous terms. Seriously. I'll happily sponsor grammar aid work too. Get in touch: http://gruschow.org

HFT provides liquidity which reduces everyone else's cost and/or exposure to short term risk.

Low-latency trading though costs everyone. Nobody actually needs anything faster than a fill in a blink of an eye. The only people who think they do really need smarter match engines or to stop taking advantage of people

I didn't say it was just a webcam. I said it should cost in the ballpark of 2x of them. Adding a $1 LED with hundreds of little holes in front of it doesn't change that.

Note: I'm not making any statement about the possible awesomeness or lameness of the system. All I'm saying is the parts aren't expensive.

How can 2x low-res low-framerate webcams cost $150 when I can buy as many as I want new, shipped for $6 apiece?

I wasn't arguing it was more secure. It could be made equivalent, but that misses the point. You don't always need a deadbolt in addition to a lock in the door knob.

You could just make min(len(secret_username)) = 1 + min(len(username)) + min(len(password))... if that's what you wanted.

Not all systems need to have the same level of security though, nor do they all need to assume their users are ignorant.

Alternative: There's no reason for my username to be public on the vast majority of sites/apps/crap that I use, so I'd rather just have a username, no password.

The secret username can be associated with a display name, real name, physical/email addresses, etc. You can use the latter to look up the former along with a password/probing question/ping (email, text, phone) to retrieve the former.

It seems to make more sense to me logically anyway: I'm not anonymously entering a secret club with a password. I'm identifying myself, and based on my identity I'm allowed to do something.

Maybe you could run in the background and just pay attention to what the users actually use? It seems like the pattern of use is going to be more indicative of what the rest of us should take a look at than the people-who-bother-to-rate-bias will allow. For example, a few basic things I'd like to know: if someone downloads it, tries it, and uninstalls or never touches it again after a couple days, if it force closes a lot [on a class of devices], and if people are using it consistently over time, like multiple times a week for months.

That said, I don't really need recommendations as to what to try, I just need something that doesn't present me with a zillion clearly crappy options (and this applies to Apple's too.. Stupid-compiled-pamphlet-of-information I'm looking at you). After eliminating those, there's not so much left in the Android Market that I can't go through it in a reasonable amount of time.

From the blog post:

  These early numbers show up to 60x speed improvement 
  over the current version of Google Chrome.

Hm... I don't need my browser to be 60x faster if it can't figure out that (60/1) < (35/.5).

I use a dell mini 9 for my business. It sits in a closed ventless cabinet and hasn't overheated. It uses <7w with wifi and screen on, but mine are off. Also, there are no moving parts and it's got a built in UPS... I got it new for $199 last year.

I didn't say it was a smart way to go, just that it's my way.

Taking the risk before knowing there's a reward is probably the riskiest way to go. For me though, it's fun.

To be fair, that was my way 5 years ago. I guess now I try to make sure everyone's working together with similar risks and rewards. I work better with people than against them.

My present way isn't necessarily the smartest or most profitable way to go either.

Idealist: Explain to the customer that nobody knows how long it'll take, and then sit down with them to work out a deal that balance both of your interests. Odds are they need some portion of the project done, so focus on how to deliver it incrementally to reduce risk.

Suit: Don't waste your time trying to work out what you expect the schedule to look like. Figure out what they can bear, and negotiate a deal that guarantees you get most of the money they can spend with the least risk to you. Your liability is in what you promise contractually, so hire a good lawyer to help you minimize your legal liability.

Me: Race to do the project before negotiations need to wrap up. Then write a beautifully detailed schedule with visible checkpoints, negotiate with confidence, and deliver checkpoints slightly a head of time on average. Use a little of your spare time to meet their mid-project change requests and build in a feature that tickles your interest and will delight them.

Coder: Negotiating a schedule is like negotiating how long it'll take to produce a baby. It'll be done when it's done, but if you get me a girlfriend I'll get it done faster.

Software Engineer: Charge your customer a standard hourly rate to record their requirements and break them down into function points. Estimate function point complexity and risk based upon your organizations prior prior projects function point productivity. Schedule a week with the customer 3 months from now to present your analysis and estimates including confidence intervals and costs in each scenario.

Use it more, and as you're working think of things that could be repeated.. or actions that seem too take too long (finding the definition of a function, moving the cursor to the 2nd parameter of the function call on the next line, etc, reformat some data, etc).

Try reading :he instead of HN. I've found far more in its built-in docs than I do with google or books anyway.

No bother.. Most cutting edge game devs wouldn't jump into Android right away either.