Live data from Hacker News

Mistakes You Should Never Make

sethbannon.com

131–140 of 348 posts

Re: Mistakes You Should Never Make

#131
post #83

I know this is a minor point of the article, but as someone with a degree from Harvard Extension I need to weigh in on that part of the story. I hate people who make this lie of ommission. Harvard Extension isn't Harvard College or Harvard Business School, but it still provides a very good education with great flexibility at an even better price. However, there is a small minority of people that continuely try to pas…

I also took a few Harvard Extension School classes (mostly Greek and Latin, but also Distributed Computing). I didn't earn a degree, just took a few things that interested me. It's on my resume as Harvard Extension School, and I have to actively correct people who think it's more than it is. My jokey way of putting it is that HES "takes anyone with a credit card." What's really embarrassing is when someone introduces me as someone who "went to Harvard." They were great classes, especially the ancient Greek, and I'm very grateful for the opportunity to learn what I did, but it's not like I did my undergrad there. I fact I applied and didn't get in. :-)

Re: Mistakes You Should Never Make

#132

> In the early days I would often let potential customers think we already had a feature they wanted What. How is this even remotely acceptable? If discovered it destroys your credibility. Among your employees it destroys your credibility. If I was an employee and found out that this was happening, I'd be extremely upset. I wouldn't trust a thing you say. If you'll lie to customers, you'll lie to me.

It's called vaperware and it's part of a lean strategy (that way you only build what people actually want). It's extremely common, in fact I believe New Relic was founded using this type of strategy. Take this with a grain of salt because this is an old passing memory of mine, but I believe Lew Cirne called up business owners and sold a bunch of them on the original new relic product before even developing it.

I don't think it is necessarily unethical if you know that you can do it (so long as you can deliver before they start paying), if it is some sort of technology that you aren't sure is possible or not that is certainly different.

Re: Mistakes You Should Never Make

#133

Earlier quoted context omitted.

What. How is this even remotely acceptable? If discovered it destroys your credibility. Among your employees it destroys your credibility. If I was an employee and found out that this was happening, I'd be extremely upset. I wouldn't trust a thing you say. If you'll lie to customers, you'll lie to me. Your optimism is endearing, but the vast majority of companies I've done business with do this. Often companies I've…

Since you are competing against people who will tell you that the feature they want already exists, people who are too honest in this area will quickly get filtered out of the marketplace. It sucks, but there are lots of markets where the customer says "please lie to me" and gives their business to the person with the most reassuring lie.

On the flip side I'm sure you've heard the phrase "nothing gets done until someone sells something."

There's a lot of cases where you are certain you can build what the customer needs, but you can't spend resources on it until you have a sale in hand.

Re: Mistakes You Should Never Make

#134
post #31

Earlier quoted context omitted.

I worked for a founder who did this all the time and it's incredibly stressful as an employee. It would be fine in the limited case where the features are fast and easy to implement: say two days' work at most. I enjoy my paychecks clearing every other week, and losing a sale over small amounts of effort is dumb, particularly since sales where relatively large (low hundreds of thousands of dollars). But this founder…

having to do with distributed markov chains I'm guessing you mean distributed Markov Chain Monte Carlo ? Sounds like an interesting problem, I'd really like to hear more about that. I'm really interested in "difficult" problems with significant commercial applications. (My contact info is in my profile if you don't want to post publicly).

Parallel MCMC implementations exist. My favorite is emcee - http://dan.iel.fm/emcee/current/ which has excellent support for parallelism.

Derail aside - I completely agree that lying about features is horrendous and I'd never ever work for a boss that did this on a regular basis.

Re: Mistakes You Should Never Make

#135

Earlier quoted context omitted.

That would result in mass unemployment in some sectors of industry. The problem is that as long as your competitor says 'yes' and you say 'no' the competitor will get the customer. Customers should be firing companies that provide false information during the lead-up to a sale. Then the sales people can stay employed and everybody comes out ahead.

> That would result in mass unemployment in some sectors of industry. Are you making an implicit suggestion that we should tolerate fraud because it employs people?

http://en.wikipedia.org/wiki/Gresham%27s_law

Re: Mistakes You Should Never Make

#136

Earlier quoted context omitted.

As a developer, I've been on the receiving end of "we promised the client we could do this, and they've already paid us, so get to it" more times than I can count... it's my least favorite salesman trait, by far.

And the salesman gets a nice commision from the sale while the developer gets to work an extra 20 hours that week at no extra pay.

New rule: developers, let's demand 50% of the sales team's commission for contracts sold on promised features.

Re: Mistakes You Should Never Make

#137

Earlier quoted context omitted.

That's very dangerous, no matter what the reputation of the firm. The thing to do is to use separate accounts for reserves like these and to pay directly into the coffers of the tax man, lest the party that you do business with unexpectedly goes bust (they do) and you end up being liable again for the same amount of tax that you already paid to the payroll company. Don't for one second think that you're off the hook…

This may be good advice in NL, but it's sort of diametrically the opposite of best common practice in the US. Payroll being handled by payroll firms is the norm in the US, and the stories about terrible payroll withholding screwups hurting companies are, as far as I can tell, invariably the result of people trying to handle this themselves, paying "directly into the coffers of the tax man".

Regardless of the company always keep the payment certificates/receipts

Yes, dealing with the tax authorities directly is usually more complicated (might be simpler for a sole proprietor/small number of employees)

Re: Mistakes You Should Never Make

#138
post #135

Earlier quoted context omitted.

> That would result in mass unemployment in some sectors of industry. Are you making an implicit suggestion that we should tolerate fraud because it employs people?

http://en.wikipedia.org/wiki/Gresham%27s_law

You should expand on this.

Re: Mistakes You Should Never Make

#139

> In the early days I would often let potential customers think we already had a feature they wanted What. How is this even remotely acceptable? If discovered it destroys your credibility. Among your employees it destroys your credibility. If I was an employee and found out that this was happening, I'd be extremely upset. I wouldn't trust a thing you say. If you'll lie to customers, you'll lie to me.

As somebody who has been on the developer side of that, I'd say that it depends on the feature, and on the available time. If you are sure that it's viable (as I'm assuming the author was), why not?

I'd still prefer to frame it as "that's on our roadmap, and will be done by the time we close the contract", but then, there's little practical difference.

Re: Mistakes You Should Never Make

#140
post #28

Earlier quoted context omitted.

What. How is this even remotely acceptable? If discovered it destroys your credibility. Among your employees it destroys your credibility. If I was an employee and found out that this was happening, I'd be extremely upset. I wouldn't trust a thing you say. If you'll lie to customers, you'll lie to me. Your optimism is endearing, but the vast majority of companies I've done business with do this. Often companies I've…

This cannot be overstated. If you give the sales team any room or freedom, they will make your life hell trying to keep up with "features" that outdo everyone else just so they can get their commission check. They don't have to deal with anything beyond signing of the purchase, so they don't care that it sinks everyone else to get that purchase.

You're absolutely right in this specific case.

The sales people will go crazy, so don't let them sell anything.

Have the technical people evaluate that.

Post reply on HN