Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.

The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.

This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.

"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.

Some people really benefit from hearing advice that everyone knows, for the same reason we keep schools open despite every subject in them having been taught before.

In that spirit, here's some quick Things Many People Find Too Obvious To Have Told You Already.

Your idea is not valuable, at all. All value is in the execution. You think you are an exception; you are not. You should not insist on an NDA to talk about it; nobody serious will engage in contract review over an idea, and this will mark you as clueless.

Technologists tend to severely underestimate the difficulty and expense of creating software, especially at companies which do not have fully staffed industry leading engineering teams ("because software is so easy there, amirite guys?")

Charge more. Charge more still. Go on.

The press is a lossy and biased compression of events in the actual world, and is singularly consumed with its own rituals, status games, and incentives. The news necessarily fails to capture almost everything which happened yesterday. What it says is important usually isn't.

Companies find it incredibly hard to reliably staff positions with hard-working generalists who operate autonomously and have high risk tolerances. This is not the modal employee, including at places which are justifiably proud of the skill/diligence/etc of their employees.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.

It’s underremarked upon that stablecoins accomplish basically all of the original design goals for Bitcoin qua a transactional mechanism (instant free value transfer anywhere), but that nobody cares about this because nobody ever cared about that part of the pitch.

“Why do people care about stablecoins then?”

A mix of “they encourage dollar-denominated liquidity in the cryptocurrency ecosystem and discourage withdrawal of the same” and “they’re good for money laundering.”

“But they make value transfer between exchanges much faster!”

This was a solved problem in traditional finance, too, mostly through the extension of credit. (It doesn’t matter how long settlement takes if there is sufficient trust to enable credit.)

The Bitcoin ecosystem is *positively allergic* to credit, so you have to call it a coin for them to accept it. And after you call it a coin they ignore everything the world has learned about credit, like risk management.

“Stablecoins aren’t credit!”

They’re pretty much exactly credit? A tether is a zero-coupon Bitfinex bond with a non-functioning call option. I

If an employer is willing to be abusive to you prior to hiring you, when you have maximum leverage and they are maximally incentivized to play nice, I think that gives you *extremely actionable* signal as to how they'll treat you when you're working there and dependent on them.

For candidates: evaluate prospective employers accordingly.

For startups employing e.g. engineers: given that your candidates should evaluate you accordingly, be *extra special* careful to operate like professionals with regards to e.g. interviewing, offers, and negotiation.

"Can you be more explicit about 'abusive' here?"

Not without violating a confidence, but as someone who has been on hiring side of table and is a capitalist, there are *clearly* things you could do which would be "sharp operating, but we're all sharp operators" in some contexts.

Hiring employees is often not one of those contexts. The nature of the relationship, the asymmetry in power, and the social contract strongly counsel you to be a lot better there than you are minimally required by law / contract.

A thing which aesthetically frustrates me is that a lot of the things I've heard companies do here serve *no legitimate business purpose.* In some cases it's getting tens of dollars of advantage. TENS! On an engineering candidate!

Bitfinex files discovery in "Yo bro, where did our $800 million go?" action and it is every bit as interesting as you'd expect it to

Here's their CFO describing their agreement (which we know from other litigation was never contractualized because, presumably because money launderers hate paper trails):

Bitfinex's CFO was shocked, shocked to learn that the money launderer they engaged to provide money laundering services while I-swear-to-God-this-is-an-actual-quote "we learned to bank like criminals" may have from time to time lied to banks.

"Institutional constraints" means, here, "We were attempting to avoid velocity checks placed by our banking partners to detect fraud and money laundering, which would have detected our fraud and money laundering."

Money at the speed of code, yadda yadda yadda, the Bitcoin economy is surprisingly blasé when several hundred million dollars is in an interstitial state for months.

In a situation never before encountered by a financial institution: the check was not, in fact, in the mail.

FAQ: “How do I get better at writing?”
Me: Write a million words.
Follow up: “Hah but seriously.”
Me: Start with 20,000 words. Everyone gets to that 50 times in their first million.
Follow up: “No seriously.”
Me: Nobody expects 10 Quick Tips To Play Violin At Carnegie Hall.

The Internet is so much better at teaching writing than the traditional educational system principally because it removes an artificial and limiting constraint on output imposed by ability of gatekeepers’ limited time to evaluate output.

(Interestingly in fields where we actually care about performance we’re good at encouraging students to practice when no one is watching but for writing we basically assume all the value is created by the teacher-minute of attention. Teacher-minutes are scarce and rationed.)

If you ever want to be deeply, deeply disillusioned about the state of the world, compare what we do where we care about output quality and what we do where we don’t, and which domains sort into which column by revealed preference.