HNHacker News
TopNewBestAskShowJobs

somedudetbh

334 karma · joined October 9, 2016

submissionscomments
somedudetbh··on How to Win at the Stock Market by Being Lazy
Locally, that's a drawback.

Globally, the unsexyness of passive index investing is the best thing about it. A huge percentage of the angel / seed / FFF capital in the world comes from bored people who don't want to talk about their Vanguard Target Retirement 2050 investment and so put 10% of their portfolio into crazy startups that will sound impressive to their friends.

Consequently, for the posters on this site, the boringness of passive investing is a huge creator of jobs and opportunities for us!

somedudetbh··on Could a Peasant Defeat a Knight in Battle?
"In the Annals of St Bertin…"?
somedudetbh··on Netflix boss: Remote working has negative effects
>-- For the working parent whose productivity has been slashed by 50% and stress has gone up by 50% due to parenting obligations, WFH might be terrible.

Yeah, this is one of the things that keeps coming up in this discussion that bugs me. There's working from home, and then there's working from home during a global pandemic that has shut down large swathes of the economy.

I wish everyone writing these articles or trying to analyze wfh performance data would acknowledge that "not being in the office" isn't the high-impact change: "having to take care of children while doing my full time job" is.

If we brought everybody working from home back into the office, but also had them bring their kids along and try to help them through zoom class and make their lunches and stuff, it would be chaos.

somedudetbh··on Myths About Failure
> I'm pretty sure he just had access to X.com, plus it's a cool domain. Is it really a strange fascination?

I just think it's funny that he went out and bought the x.com domain for a consumer finance startup in the 90s, and then ended up running a company called SpaceX, and then ran an electric car company whose top-of-the-range model is called the "Model X", then he had a baby, and named the baby "X Æ A-12 ", or "X" for short. The dude is crazy for X!

somedudetbh··on Myths About Failure
> Fortunately, Max Levchin had an answer: ”Oh, that’s easy. We can sync payments for email.” Scott Banister (who was the other outside board member) and I looked at each other and said, “That’s a great idea.” Email payments turned out to be the product that made PayPal a success, and about a year later, the company quietly dropped its PalmPilot application.

> Max, Peter Thiel, and the PayPal team didn’t need to run an experiment to realize that the PalmPilot approach wasn’t going to work, and to switch to a different thesis (email payments) in which they had much greater confidence.

Maybe they didn't need to run the experiment, but they certainly did: https://www.paypalobjects.com/html/pr-121799.html

Of course, I have no idea what actually happened here (other than it certainly seems like PayPal spent a lot of time building the palmpilot app, going so far as to doing a classic corny '90s splashy launch with a nerd-celebrity built entirely around the beaming concept.

The tale told in the paypal wars (https://www.amazon.com/PayPal-Wars-Battles-Media-Planet/dp/0...) is essentially that

1) The initial vision of Confinity/PayPal was an alternative currency enabling cross-border/cross-currency low-fee payments (similar to a lot of bitcoin/blockchain rhetoric)

2) The go-to-market strategy was beaming on palm pilots

3) Musk & Co had raised a bunch of money to build a vague "consumer finance" portal called "x.com" (Musks's strange fixation on the letter 'x' goes way back)

4) (not remembering this part for sure as I read the book a long time ago) PayPal/Confinity was running out of money because the beaming product was a flop and no one cared about their alternative currency payments usecase. Musk's company was also a slow-motion trainwreck because there was essentially no product vision and no actual customer pain being solved, but they had more money in the bank so Confinity agreed to sell to them to extend the runway.

5) The email payments thing was built as almost an afterthought to allow graph completion to enable the palmpilot beaming usecase to actually work

6) A random PM noticed that a surprising percentage of their traffic was coming from eBay users.

7) eBay, being the worst-managed incredible first-mover opportunity of the 90s dotcom boom was incapable of building a functioning payments product, despite the massive first party advantages and huge incentives to round out their core offering

8) PayPal was very popular but was burning cash at an insane rate that scaled at least linearly (possibly supralinearly) in engagement. They basically were able to survive due to a fortunate massive fund raising just before the 90s window closed (very similar to stamps.com). They might have been able to get the business to work but instead eBay acquired them so we never found out.

Of course, I read this in a book, and I read the book well over a decade ago, so I'm sure I'm not remembering things right, and I have no idea what particular axe to grind the author had, etc.

But there is evidence online that they at least believed in the beaming thing long enough to build the product and hire Scotty from star trek for a stunt launch. And this might be a minor detail, but if it's true, then Hoffman's point doesn't hold up, and it undermines the whole thesis of the post.

In general, I don't think there's much reason to believe that people who did really hard things are particularly able to explain why they were able to do them. It's great that they were able to do them, and maybe that even predicts that they'll be able to do more of them in the future. I think in Silicon Valley, if you asked a bunch of these guys to flip a coin ten times the guy who got heads ten times in a row would immediately start a Medium account to explain how his unique perspective and grit and determination enabled him to do it.

I mention this because I completely don't understand why these puffy VC content-marketing articles are on the front page of hackernews every day. There is very little evidence that there's any more value in them then say calling the psychic hotline and asking them for startup advice, and they're essentially just ads for VCs and SV thinkfluencers.

somedudetbh··on Britain has gone two months without burning coal to generate power
> Coal-related air pollution causes an estimated 10.000 extra deaths each year across the continent. Radiation caused one direct death in Fukushima.

What's the rationale for comparing indirect deaths from coal to direct deaths from radiation?

somedudetbh··on Online Jamming and Concert Technology
Latency is kind of funny in the context of jamming. Sound only travels about a foot per millisecond. An orchestra pit is thirty or forty feet across. A big festival stage can be thirty feet across.

So we have these pretty ordinary situations where there's about thirty milliseconds of latency between when a drumstick strikes a head and a guitar player hears it. Of course, in a modern live pop performance there's all the crazy monitoring and latency compensation to try to make a football stadium acoustically comprehensible, but there is still the physical reality of how people normally play music together.

If I ping google.com from my house, on my crummy wifi, right now I'm getting about 10ms. This is roughtly the latency a guitar player experiences standing at the end of a 10 foot cord from their amp between their pick plucking a string and the resulting sound striking their eardrums.

Reality has latency.

somedudetbh··on Why Is Facebook Not in the Cloud Business?
There are many conflicting stories about the origin of AWS, but the whole "our infra is underutilized except during Christmas, let's rent it out!" is one that I never hear repeated by anyone with any claim to knowing what was actually happening. I think it's an "Omidyar Pez Dispenser"-tier story: fully bullshit.

It kind of doesn't even withstand a moment's scrutiny. What was Amazon going to do during Christmas? Like, if they lease all this spare capacity during non-peak, what happens to those customers during peak? There are spot instances now, but the first two AWS products, S3 and EC2, didn't come with some sort of, "Except during peak" contract. So Amazon needs exactly as much hardware to meet demand during Peak as it did before, and now it's got a bunch of customer workloads it also needs to serve during peak. I don't see how this would've solved any problems.

Most stories about the origin of AWS have a few things in common: (1) There was limited support for the idea of AWS at senior executive levels (2) The early AWS products were not used by for any significant Retail workloads within Amazon for quite a long time (as in, several years) (3) As recently as a few years ago, there were major organizational pushes to move legacy Retail workloads onto AWS (4) As recently as last year, there were still so many teams on Oracle that everyone with an Oracle dependency was required to have an OKR to get off it. I include this because IIRC this is public-- after Oracle was making hay with the "Amazon sells Dynamo/RDS but runs on Oracle" campaign, Amazon publicly released information about their Oracle Annihilation roadmap. So it supports the theory that it's taken Amazon quite a long time to shift certain Retail workloads to AWS, even in cases where an AWS product that's suited to the workload has existed for quite a long time.

I've never worked for Amazon, so I don't know, and it's impossible for all the stories I've heard from ex-Amazon people to all be true, but I think there's a pretty good argument against the "we should put this spare off-peak capacity to use" AWS origin myth.

somedudetbh··on My Emacs Productivity Tricks/Hacks
Being emacs, there's a bunch of different ways to do this.

I use Cask: https://cask.readthedocs.io/en/latest/guide/installation.htm...

Let's consider Homebrew bundle etc outside of scope and assume you have some workflow that works for you to init a new machine with emacs and some other apps, and you're just worried about the zillions of little emacs packages you are testing or using.

So, I have a file called at ~/.emacs.d/Cask, that is just a list of packages on which I depend. This is the only way I install packages. Update the file and do "cask install".

This also means if you're packages get weird, or you have some sort of transient .elc problem you can just blow away ~/.emacs.d/.cask and do a 'cask install' (basically .cask ~= node_modules)

somedudetbh··on Things I’ve learned in 20 years of programming
It's so interesting to read different people's perspectives on here. I very rarely comment on here, but it's just wild to me how wildly different the conclusions we can all draw from looking at the same set of pretty simple factual data are.

I've been working in this industry in a serious way for about 15 or 20 years? So not exactly close to retirement but I'm not straight out of school, either.

> The stack is to deep. Nothing is easy anymore. The technology count is staggering.

To me, it's insane how much easier literally everything is, and how wildly more productive people can be.

I remember when I was young, first of all, it was impossible to just get access to technologies so you could learn them. Compilers cost money. Databases cost money. Operating systems cost money. It was hard to even get to the point where you could mess with stuff, for financial reasons. Now, to a first approximation, there isn't really a tier of basic software you'd want to develop on/with that you can't get essentially for free. It's not like they're running some totally different "production-grade" operating system or database at the big tech companies, or that the well-funded machine learning labs have access to some sort of special super computer with totally different characteristics than what you have access to. They basically have the same shit. That's bananas!

Then, there's the utterly massive revolution in programmer productivity that has been caused by the internet + automatic memory management. In the olden days, there was very little code reuse, for several reasons, but one of the reasons was that it was too hard to pull in random libraries and start thinking about who would own the storage for the error string they wanted to return to you out of every single api.

Everyone bitches about how javascript programmers think nothing of adding "left-pad" to a package.json along with twenty thousand other dependencies, but the fact that you can do it is nuts! And it makes everything SO MUCH FASTER AND EASIER.

The other day I was just curious if I could point my webcam and my whiteboard and have it pull in the lines I drew on the board with a marker and save them as some sort of curve in the computer. I have no experience in computer vision or anything like that. I don't even really know Python. I was able to get this roughly working in like half an hour with Python + OpenCV + some driver that already made my camera work + some tutorial that came up in DDG. It's like being a freakin REAL LIFE WIZARD.

Take building Android or iPhone apps. I remember trying to write apps for the Palm Pilot a thousand years ago. Just getting the toolchain to work at all could eat up a couple days. This is reminding me what it was like to try to write a win32 app w/ OWL or MFC, starting from the auto-generated code. Anyway, now, you get a tiny computer with shockingly powerful cpu+gpu+a zillion radios+gps+multiple cameras+gyros+compass+accelerometers+gigs of storage + gigs of memory + a super high rez touch screen. You can assume that to a first approximation, everyone in the high-GDP/capita countries has one of these, essentially everyone in the mid-tier, and the low-tier is growing at a shocking speed. Further, they are all exposed to your code through a more or less universal set of interfaces so you don't really need to worry about drivers and hardware support hardly at all. You want to run some code on here? Ok, you can distribute it for free over the air, and you can write your code in an automatically memory-managed language with a freaking gigantic standard library. Oh also the SDK is free. And there's an emulator that runs on x86. Oh and there's a visual multithread debugger that you can attach to the process...from your computer..remotely. Oh you don't need a dev sdk, all the normal units everyone has, those just work.

But you want to build a network application? Something that needs to talk to some sort of service? Well the good news is you can get a database, an operating system, and incredibly powerful web servers and application servers, and they all cost nothing. In fact, they're already installed, on the computers that you can rent by the minute, and the lowest tier if you just want to mess around? It's free.

Mainly what I feel like is extremely JEALOUS that I wasn't born later. Imagine all the cool fucking shit you could have built as a kid instead of wasting your life trying to find a cracked version of Borland Turbo C that worked right. Choosing between the horrendous performance / security / etc of perl cgi-bin vs. the unattainable per core licensing fees of a "application container" or whatever those special jvm things were called. Oh, here's one: DATABASE FREAKIN DRIVERS FOR JAVA. jdbc drivers used to cost money! And they sucked shit!!!! ahahahahhahaha.

I agree that programming is a ridiculous career path because I can't believe ordinary-talent-level programmers in Silicon Valley get paid into the low seven figures a year to essentially work on their hobbies. This has to end at some point. I can't believe this is a real job. It's like your whole life, you love legos, and you're always trying to build bigger things out of legos, but you always run out of the pieces you need. And the someone comes along and says, "Ok kid, here's the new rules. Legos? Legos are free. Every single type of lego, in more or less unlimited quantities, you can just have those." What's the catch? "The catch is you get paid to play with the legos." Wow thats crazy but it must be like...a barely survivable wage. "No in fact total rubes who just graduated from school are gonna get paid 3x the median income for a family of four in their first year out of school. People who've been around for 10 or 20 years will make like a million bucks or so." But only in like weird big risky situations, right? "No that will be the deal if you work for the most stable boring companies where you get six weeks of vacation and all your meals taken care of etc."

??? How is this possible?!!?!

somedudetbh··on How Fragmented Is Android?
From the article: "So the Android ecosystem is split between at least 1,728 combinations of OS - Brand - Device Model"

It's actually _much worse_ than this. Here's a review of the "Samsung Galaxy S10+": https://www.anandtech.com/show/14072/the-samsung-galaxy-s10p...

This "device model" is actually two devices with completely different SoCs. There is no meaningful sense in which these two phones are one device. Sometimes the manufacturers document this, sometimes they just start selling a phone that identifies itself by the same name as an existing phone but with a GPU that has completely different performance characteristics.

somedudetbh··on Things Got Weird for Stablecoin Tether
> For example in 2008 the CDS market alone was at some point "valued" at close to $36 trillion [1], while for comparison the US GDP back then I'd say was around $14-15 trillion

People say this all the time, but regardless of whether or not the CDS market was or wasn't a shitshow at the time, comparing the outstanding notional to GDP is meaningless.

At the time, the CDS market worked like most derivatives markets: you face a small set of players and you are constantly offsetting existing transactions and subjecting them to netting rules on a master isda.

So like, let's say Foocorp has 100m bonds out there. I want to buy protection on 1m of this (basically, I want to buy default insurance). You agree to sell this to me. Ok, there's 1m in CDS contracts' notional value outstanding.

Now, our views, other risks, whatever changes. Maybe I sell the bonds, and holding this CDS is too risky for me now because it's just a naked short of bonds I'm not long. Maybe you buy a bunch of these bonds, and now you're not only facing the default risk of the bonds but paying the default insurance to me.

So you decide to buy another CDS offsetting your existing one. I'm also trying to flatten out here so I sell a CDS offsetting my existing one. Now (mutatis mutandis) we're both at 0 CDS risk. We each have entered into 2 swaps, they're directly cancelling.

But the total notional? Now it's 2m. Contracts expire, so the number doesn't strictly go up, but given how the products are bought and sold, it mostly does. It would be like looking at the stock market not in terms of the market cap of all the companies, but as the dollar value of all the trades made in a certain time period. It's not that this number is meaningless, it's just that it does nothing to explain how much is "at risk".

Of course in reality this is all much more complicated, but the basic principle holds.

Anyway, I know this isn't your main point.

somedudetbh··on Party is over for dirt-cheap solar panels, says China executive
This is a well-studied phenomenon known as Cartel Theory: https://www.cambridge.org/core/journals/business-history-rev...
somedudetbh··on Ask HN: How do Google's iOS apps track your identity even after reinstalling?
There are basically two ways this can work: the old way, and the new way.

In the old way, an implementation detail of the Keychain was that data saved in the Keychain would not be purged on app uninstall. Basically, the Keychain can be thought of as a fancy key-value store where your keyspace is further scoped to your app's bundle ID. It's intended to provide a secure place to generate and store keys, etc., but you can also just stick a bit of data in there.

So, user logs in, save their username to keychain. User deletes app. User reinstalls app. On app start, try to read the key you saved the username under. Is it there? Ok, this is a reinstall. No? Ok, this is a new installation or new phone.

There is no Apple documentation that says that this is the way it works, it's merely a quirk of how it's implemented. Obviously, it's a privacy concern. Apple closed this hole in one of the betas of iOS 10.3, but then restored the old behavior. I don't know why, but it's possible that many user workflows were relying on this behavior, or that it subtly broke something else (e.g. app groups).

The second way is using App Groups: https://developer.apple.com/library/archive/documentation/Mi...

In more recent versions of iOS, Apple introduced support for "app groups", which basically means a bunch of rights and privs that were scoped to the bundle id in the past are now optionally scoped to the bundle prefix (team id) or to a whitelisted set of apps that share a bundle prefix.

This allows for Facebook to share login session with Facebook Messenger, for instance. If you're Google, and you have multiple Google-owned products on the user's device, you can add them all to an app group. If up to all of the apps but one are deleted, and the last maintains user login data in the keychain, reinstallation of the other apps will allow them to recover data shared by other apps in their app group.

I don't know if there's a way a user on a non-jailbroken device can wipe the keychain without resetting the device. (You should also look into iCloud Keychain.)

somedudetbh··on Magit Kickstarter fully funded
Magit is really an incredible piece of work. Thanks so much for it. I mean, I already use emacs, but I feel it would be a legitimate reason to switch to emacs, or even to use emacs just when dealing with Git operations.
somedudetbh··on Remacs – A community-driven port of Emacs to Rust
IMHO, as someone who absolutely loves emacs, this is the biggest problem with emacs.
somedudetbh··on Clojure for the Brave and True (2015)
I agree.

I think this book and a lot of others fall into the _why's Poignant Guide to Ruby which i still totally don't understand the appeal of if you already know how to program.

I mean, _why is an interesting dude, who did a lot of interesting things, but (1) the whole 'chunky bacon' thing just is not my cup of bacon smoothie and (2) it was not really a great book for people who already know a lot about programming.

More broadly, I feel like _why's Poignant Guide to Ruby is an example of what I call John Bonhamization. John Bonham plays drums in Led Zeppelin. His whole style is crazy: rope-a-dope with the beat, playing mostly with the singer, playing "lead drums" and it's awesome! It's so good! It really, really works in the context of Led Zeppelin because John Bonham was a freak of nature and it just went along with their band in a magical way.

But it works for almost no one else ever. It's exactly the wrong thing to copy. It's like when people in Silicon Valley are like "well, Steve Jobs was rude as shit, I'LL be rude as shit and then *I'LL invent the next iPod!!" And then you have generation after generation of people trying to copy someone else's magic and not hitting it, when they'd've been better served trying to do the normal thing and, maybe, if they were lucky, finding their own magic.

I also think there's a bigger problem with people not writing books for people who know about programming. Odds are, if you are reading a book about a programming language, you already know a fuck ton about programming languages, but most programming language books fall into one of two categories: - Books that try to teach programming via the language in question. - Books about advanced techniques or exhaustive library documentation, cookbooks, etc. for people who already know the language.

The overwhelmingly most common case of someone reading a PL book (for a language that's not one of the world's ten most popular) is "I know a dozen other programming languages but don't know this one." Only fairly advanced programmers even bother reading books about Clojure, or D, or Rust, or Dylan, or Self, or Racket, or Julia...

Personally, I really like the Joy of Clojure. If I had to compare it to another PL book tough it would be the Matz Ruby book, not Crockford. It's pretty good though.

somedudetbh··on Sears reports $748M net loss [pdf]
Ha I just thought/posted the same thing!
somedudetbh··on Sears reports $748M net loss [pdf]
Every time I read something about Sears troubles, it makes me remember this metafilter comment from 2007: http://www.metafilter.com/62394/The-Record-Industrys-Decline...

Excerpt:

"...In 1984 [Sears] starts a joint venture with IBM called Prodigy, an online computer service, sort of a prototype AOL. In 1985, Sears launches a new major credit card, the Discover card. For the next eight years, the only credit card you can use at Sears is Discover.

At this time, the early 80's Sears is the largest retailer in the U.S.

By 1993, the 100th anniversary of the Sears Catalog, Sears had built up considerable goodwill in the mind of consumers. They weren't the lowest price, but they had what you needed at good prices and the service was second to none. […]

This is 1993. In quite possibly the greatest example of corporate shortsightedness, Sears shut down it's mail-order business in a cost cutting measure. It spins off Allstate that same year, and soon dumps Dean Witter and Coldwell Banker.

In 1993, Sears had the most extensive and sophisticated mail-order retail operation on the planet and they closed it.

Two years later, Amazon.com launched, and was soon selling everything that sears sold through it's catalog. By the late-90's Walmart's push of low-cost China imports killed Sears retailing. Online banking takes off. Credit card use surges as mail order and retail purchases are shifted online.

Sears had its own computer network in 1993. They had access to IBM, they should have understood the power of the internet. All they had to do was shift the catalog online instead of killing it off, promising in store returns and the same Sears satisfaction guaranteed. Discover could have been the credit card of choice for security and protection online. Dean Witter could have been what Schwab, E-Trade and Ameritrade became. Back in the mid-late 90s when many people were hesitant to use credit cards online, Sears could have been a familiar face online."

somedudetbh··on Kafka: An End or a Beginning?
Wow. I'd like to see you solve the dining philosophers problem without a robust distributed messaging system.
somedudetbh··on Why Many On-Demand Platforms Fail
it doesn't. My point was only that lots of technology entrepreneurs view 'generalizable web of trust' as a good opportunity, when it is not, similarly to how they view 'tools to make it easier for non-technical people to build apps' as a good opportunity, when its not.

SOrry if that was confusing i was writing pretty stream-of-consciousness

somedudetbh··on Why Many On-Demand Platforms Fail
(HN made me split my comment)

This is why the marketing pages for even the most generic products in the world almost always talk more about 'solutions'. Like, companies don't even know they need a database. They know that they need something to keep track of products. They know that they need to keep track of customers. They know that they need to keep track of resources, inventory, etc. Customers think in terms of 'screens', not the fact that these are all fairly small things built on top of very complex database software.

So you start out inventing the RDBMS or the...SAN storage fabric...durable event queue...whatever it is. But you can't sell it to companies until you explain that no, it's a customer relationship manager. No, it's a way to store all your digital assets. It's a way to capture all your customer interaction data so you can make your digital marketing more effective. It takes an enormous amount of work to go from 'well-engineered technical solution to a general problem' to 'thing people will buy'. Imho, this was one of Marc Benioff's most brilliant moves: the company is called salesforce dot com. It's for your salesforce! If you have a salesforce, get this. We make CRM. Salesforce, of course, is really just a little lego box of hosted database configurators and form-builders, search engines, form hosts, etc. It's kind of like a cloud Microsoft Access that runs at larger scale, but that product would've fallen flat on its face (in fact it has, several times. the most elegant of these was probably Dabble DB) because no one wants a cloud-hosted form-builder + a database. They want a CRM system you don't have to install. They want to see the pipeline view, the contact view, etc. _on the website_. Not a video presentation where a guy at StrangeLoop shows how easy it is to make a Todo List.

It's an old dumb airport business book cliche to say "customers don't want drills, they want holes." These tools tend to be more like trying to sell customers a modular motor-and-battery-and-gear train set that can be used to create any tool: a drill, a saw, a sander..._they're all just battery-driven small motors with different gearing and tool-holders!_

So, the really messed up and interesting part is that the difference in the sort of 'consumer surplus' if you will between "cloud-hosted form-builder + database" and "cloud-hosted form-builder + database + we already made the contact-entry form and the pipeline view" IS FRIGGIN HUGE. No one will pay for the cloud-hostable database + form-builder. Or within epsilon of no one. That's also 99.9999% of the work. TONS of people will pay for the same thing with the contact form and the pipeline view ("the CRM system").

This is known as "The Software Industry". It's a completely messed up place! You see this all the time on HackerNews: commentors complaining that YC/A16Z keep investing in "things that are just skins on a database" instead of "hard tech". It's because no one pays for hard tech anymore. Operating systems are not a business. For decades, they were a multibillion dollar industry, but now they exist only as a loss-leader. Oracle survives because they sell the forms on top of the database (Peopleware, etc). HDFS, Kafka, HAProxy, Hadoop, Hive, Spark, Linux, Memcached, are all free. MIXPANEL costs tons of money.

The venture capital industry essentially exists now to exploit this huge bizarre situation: it costs a very small amount of money to see if you can add the last 5% to the collective pile of software that's free to make a very large amount of money. It wasn't always like this, but it is now. People will point to cleantech funds and health care investments, etc. but as of now, the total return on all invested VC with IT subtracted out is 0. The entrepreneur's tendency is to want to build the free 95%, but the economic return is in the last 5% you can charge for.

Tableau is also very interesting. I'm curious how people are using it in practice. In my experience, there are generally tons and tons of business people who say things like "i want to see the X and Y correlation blah blah blah which customer bought this that also went to one of our events..." and they have no ability to answer these questions. So they pay Business Objects Microstrategy or some big BI vendor to build a 'business intelligence' system...70% of the cost is consulting...and they end up with a handful of fixed reports and no ad-hoc querying.

Then they hire some sort of programmer-with-a-different-title to write reports.

Alternatively, they keep dumping the data into Excel and some clever 'non-technical' person muddles through using macros to clean it up, some combination of index/match/offset to prepare it, and pivot tables to make the final reports.

My curiosity about tableau is, in actual, real-world deployments, how ad-hoc are people's queries really? Also, how do they handle what used to be called ETL? It seems like an ongoing and challenging problem. It would be relatively easy to build a friendly-if-limited query and visualization platform on top of perfect data, but there is no perfect data in the world. In my experience, getting to the point where you can do ad-hoc queries on transactional business data means 90% of your resources will have been spent on ETL-ish problems, and about 10% on the 'fun part'.

But Tableau is obviously killing it so they must have found some magic combination of the right amount of query flexibility and manageable data...management. I haven't like, talked to their sales people or used the product in many years though so I'm not super familiar with where it is now.

OK LONGEST COMMENT IN THE WORLD OVER NOW!!!

somedudetbh··on Why Many On-Demand Platforms Fail
So, first of all, I love Excel. I think Excel is the most incredible piece of shrinkwrapped software ever sold. I often joke that I don't have any tattoos but if I got one, it would be the excel logo. At least, everyone thinks I'm joking: I'm actually somewhat serious.

My argument is not that these tools are bad, or that there's absolutely no market, or that it's fundamentally impossible. My argument is that this market represents a trap to the kind of people who start technology companies: it looks very shiny and appealing to people with the exact psychological makeup to launch technology companies, and that makes it harder for them to see the challenges.

For every Excel there are a 1,000 Lotus Improvs. For every Ruby on Rails there are a thousand Google App Inventors. For every Hypercard there are a thousand Runtime Revolutions. For every IFTTT there are a thousand Yahoo! Pipes (and I'm not really sure if its fair to call IFTTT 'successful').

The linking feature of technology entrepreneurs is they are people who see problems everywhere that can be solved with technology. They are also generally 'generalizers' or 'lumpers' (which leads to other antipatterns: http://www.joelonsoftware.com/items/2008/05/01.html). These are necessary preconditions to being successful in this line of work: identifying problems, classifying them as tractable with existing or adjacent-possible technologies, generalizing disparate-looking issues into something solveable with one approach.

But almost no one else thinks like this. The stereotypical tech startup founder's favorite toy as a kid was lego. Now, lego is a popular toy. But most people when they get legos build whatever was in the picture on the box. Lego almost went out of business around 2000. They turned it around by getting aggressive on IP development and licensing that does some of the imagining for you.

Let's say you could invent the ultimate 'non-technical person app-maker' tool. It's a magic helmet. You put it on, imagine the software feature by feature, and then it 's in your Dropbox, seconds later. Most people would have absolutely no use for this helmet. This becomes really clear if you do a lot of consulting. People have the most insane descriptions of their problems and really have no idea what they need. It's sort of like Henry Ford's "if I'd asked the customers they would've said they want a faster horse". In technology we've seen this a million times. The most famous examples are probably why didn't GE or IBM own the photocopying industry, or why didn't IBM own RDBMSs before Oracle got out there. The classic explanation of this is the Clayton Christensen model: the new product threatens existing revenue streams and the company's internal culture protects them.

As a quick aside, I think there are a lot of issues with this bit of Silicon Valley religious orthodoxy: The Innovator's Dilemma i think has a lot less explanatory power than we generally accept. There are many, many markets where successive waves of technical development been captured by market leaders. The largest shipping company in the world by TEU capacity _or_ ship count is A.P. Moller-Maersk Group. Founder Moller-Maersk bought his first ship in 1886. This is the ship: http://media-cache-ec0.pinimg.com/736x/48/68/db/4868dbcbadb6... Not only did these guys survive the crazy waves of disruption that have hit the shipping business recently, they started with a break bulk _steamship_. Diesel, containerization, automated ship management...they're the dominant player in international shipping. 130 years later.

IBM owned 100% of the technology, theory, and experience in the RDBMS world then. They could have charged whatever they wanted for it. It was no threat at all to their existing database business. It could have expanded it above or below. Same with photocopying. IBM didn't have a large segment of...crummier...document duplication?

The problem in these cases is the fail to understand what customers need, and to explain it to them. It's much more basic.

But it also gets at the broad Silicon Valley disdain for 'marketing'. Marketing is both incredibly difficult and incredibly important. Packaging up a new, abstract concept in a digestible way that makes people change behavior is as important to driving the adoption of a new technological solution to an old problem as engineering.

Anyway, I'm getting really off-track and burning up my Sunday afternoon here.

The short version of my point is: It's easier to make non-technical people technical than it is to make non-problem-solvers problem solvers.

It is _insane_ what 'non-technical' people manage to get done with Excel, if they have the correct problem-solvey mind. Physics majors who end up as analysts at investment banks and build incredibly complex modeling and information-management tools in Excel.

But if you are the kind of person who can clearly identify an issue and envision a reasonable set of tools to solve it, there are tons of technical people around who can help you solve it, and if you want to learn yourself, its generally not that hard to get started.

The typical technology entrepreneur gets a job doing _literally anything_ and is surrounded by things that make them think "jesus christ! I can't believe we're still doing that X way! We should have a system that takes the foos from the foo queue and automatically bar-izes them..." And they are limited by the speed at which they can build software. Their implementation speed can not possibly keep pace with the tons of ideas they have! But imagine if...instead of solving the specific problem with the foo queue...they solved _the problem of solving problems_! Then they wouldn't need to build a messy salesforce to address the foo queues in this small backwards industry, they would just use a no-touch sales strategy to sell directly to teams who will bring the domain experience to solve any of these problems themselves!

somedudetbh··on Why Many On-Demand Platforms Fail
This is a pretty naive look at how services in this space work from someone who wants to build one.

Uber is fundamentally unlike all of these other "Uber for X" startups. First of all, @paulsutter made a great point: the CAC is > LTV. How many times in your life are you ever going to have to hire a...home decorator or something? A painter? The reason why Geico advertisements are on all media literally all the time (they have like five completely different mascot strategies!) is because you almost never make a choice about car insurance, and when you do, they need to be top-of-mind. This is the same problem that affects a huge swathe of terrible startup ideas, not just on-demand services: the whole category of travel management, niche social networks, event-oriented tools, and yes, most "Uber for X" products. It works for Geico because the LTV of a Geico customer is high enough, because Warren Buffet is an amazing capital allocator and amazing at identifying and retaining operational talent, so Geico runs at roughly break-even on the insurance product, but frees up a large chunk of float for BH to deploy and earn high returns. That business requires doing like 10,000 impossible things right and they do it. An app that lets you summon a guy who trims trees to your house the one time you realize you need a tree trimmed has none of these qualities.

A lot of comments here are about how 'the jury is still out on Uber' because it loses money. But cabs don't lose money, collectively. Uber's aggressive money-weaponization growth strategy is certainly high-risk, but there have been tons of businesses that direct requests-for-transit-via-car to independent contractors and clip a fee: virtually every taxi dispatch company, say (contractor vs. employee depends heavily on the history and regulatory structure in a given market). The idea of having for-hire cars distributed through the city and used on an on-demand basis is also profitable for zillions of people. The idea of adding on an app that summons the cars more efficiently, handles payment, and clips a fee is not that hard to believe in.

OP frames the issue about the lack of variance in quality of an uber ride vs...what? Hiring a plumber? Do any of us have the ability to identify a quality plumbing job vs. not quality? I mean, the toilet flushes now, or it doesn't. I think this is _close_ to the issue, but the issue is more about 'what adds value': being close to me right now, and able to get to me immediately, on a pre-determined price schedule trumps everything in ride-hailing most of the time (sometimes you want a limo, or something special, and maybe you won't use Uber. Maybe you want to hire a driver for a month while you are in India. You probably won't use Uber. Different parts of the value equation are changing value). Most of these on-demand apps operate in markets that don't have this quality. Other things are important.

The post also goes into the 'Trust' question. This is a classic trap for technology entrepreneurs, right up there with 'building tools that makes it easier for non-technical people to build apps'. So many zillions of dollars and hours of smart-people-work have gone down the drain building web of trust, chain of trust, and other trust management products, and they basically don't work at all. What works is "Does this thing have a lot of five-out-of-five star ratings from real-seeming people compared to how many one-out-of-five-star ratings it has?"

This is essentially 'word of mouth' online. The ratio of 5:1 star ratings over a threshold. This is basically how all real-world functional trust systems work: ebay, amazon, yelp, etc. Yes they have enormous problems. Yes they are really stupid. Yes they can be gamed. Yes it weights all sorts of idiots equally. But guess what? It works well enough for most people to make purchase decisions. Every fancy smart thing we've ever come up with that's more sophisticated than this is basically useless (e.g. the global tls cert web of trust, the various pkis, every product that builds a FOAF trust web underneath arbitrary objects).

Afaik, on-demand 'uber for x' products work one of two ways, mainly: - as a marketplace, where they fail because of all the normal chicken/egg problems, but basically because the ltv of a customer is very low and the cac is very high (once you run out of VC cash to subsidize the service to extremely low prices.) - as an ONO service with employees, where the unit economics supposedly become good with crazy scale, but it's extremely difficult to get there again when you run out of subsidy cash . The classic example here is Kozmo. I'm sure Kozmo's model predicted that eventually, when a delivery person was delivering a candy bar to five people in the same building, the unit economics turn the corner, but it consumes insane volumes of cash to get there, if there's even a 'there' (I'm not aware of any company who has ever gotten to this point. It is possible that Postmates will be the first, if they survive).

Postmates is an interesting play because unlike most of these on-demand services, there's at least a world in which like you could _imagine_ if there was a small but positive way to get the unit economics to work, the LTV outstrips CAC because people need to order food and stuff all the time. Many times a day possibly. Even if Postmates made a penny/order on each active user, you could have a very high order volume over a very long time that would eventually get over the CAC cost. BUT the idea of the unit economics getting there is...hard to see. I have a friend who orders coffee from postmates _every morning_ instead of making it or going out. He just has a postmate drive up the hill to his house from starbucks. Starbucks! It's not even like a fancy coffee place. It's interesting to think about a world in which that postmate is running like, a hundred starbucks orders on an optimized loop, and they're still able to charge $5 or whatever for the delivery. That starts to look _possible_ but insane. As it is, it's twenty minutes up the hill, twenty minutes down, never mind the starbucks time.

The other world of on-demand stuff I think is interesting to think about is grocery delivery because I think grocery delivery is basically doing something different than what it thinks its doing: the on-demand delivery aspect of it is a vehicle for grocery price discrimination.

It's an old joke that rich people don't know how much food costs: George Bush Senior at the checkout counter, Lucille Bluth saying, "it's one banana, michael, what could it cost? Ten dollars?" That 30 rock episode where Jack Donaghy says something about the "grocery concierge" telling you a sack of potatoes is four hundred dollars.

But groceries remain an insanely low margin business. Grocery chains operate at around 2-3% margin. Independent grocery resellers in immigrant neighborhoods are even tighter. Costco's grocery business is run near break-even (they make money on the membership fees. This is also why, long run, Amazon's non-AWS business best comp is Costco.)

I've shopped for groceries on amazon pantry. Sometimes I'll type something in like "soy sauce" or "rice". Is that a good price? I sometimes literally don't know if its 2x the normal price or .5x. There are things I know the price of well: avocados, milk, liquor, coffee. But there are tons of things I don't know, and i've been buying these staples for years!

Grocery stores have very little power to raise prices, but if they could segment the market to provide a service like delivery to a price-insensitive consumer that allows them to charge 20-30% more for certain staples, the excess margin in the groceries completely dominates the cost of the delivery business.

This is the Instacart strategy. It's very interesting. A lot of the unit economics problems of these businesses go away if you just...make things expensive. What if coffee was $30? Sure, postmates would work fine, if anyone would pay. But groceries have larger tickets where a 20-30% increase in price might not be objected to by wealthier price-insensitive consumers. Instacart basically is selling coffee for $30.

I'm very curious to see if this works. I mean, it seems insane, but less insane than say HomeJoy, Rinse, Washio, Homee, Handy, the 'uber for kids', Lugg (this has gotta be the worst idea of the bunch), the one that parks your car, the one that washes your car, the one that fills your car up with gas, the (multiple!) ones for private jets, the massage one, etc.

← PreviousPage 2 of 2