Building Principles:

↓

Hindsight in 2020: (10 thoughts)

Relationships > everything:

My relationship with @celiapreihs is the foundation of all the good things in my life, and has amplified the quality of hundreds of relationships with people I've got to know and learn from this year.

Shiny objects make us duller:

The grass is always greener until you're standing on it. "No" is still the highest ROI word in my vocabulary.

The internet is very, very big:

Make something work for one person (could also be yourself), then work on distribution.

Scale is seductive but you can't get it if you don't have something people want.

You can't please everyone:

If you could, there would be no point anyway - it's tough when someone doesn't love your work but it's how markets function.

The blows hit harder in the early rounds, just keep getting up.

Why promoting yourself/your business/your ideas feels uncomfortable:

You must repeat things that are obvious to you until they become obvious to others.

This is why most people hire marketers or outsource the amplification of their message.

The problem with that is no one is an invested as you are, and no one knows your message like you do.

And why those who break through their discomfort reach an escape velocity that eludes most.

This is a difficult and unnatural process, hence the upside on the other side.

Another way to think about it is the famous shelf analogy:

No one wants a drill they want a hole, no one wants a hole they want a shelf, no one wants a shelf they want to a place to put books to look smart, etc.

People care about the 2nd, 3rd, 4th order effects of your work.

Circle of Competence 101:

@SahilBloom x @jackbutcher

↓

1/

A Circle of Competence is the set of topic areas that align with a person's expertise.

If the entire world of information were to be expressed in a circle, an individual's Circle of Competence is the small sub-circle that represents their expertise.

2/

The idea surfaced in the 1996 BH annual letter.

"You don’t have to be an expert on every company...you only have to be able to evaluate companies within your circle of competence. The size of that circle is not very important; knowing its boundaries, however, is vital."

3/

A Circle of Competence is built over time.

It is built through experience, reading, dedicated study, and effort.

It is dynamic, not static.

It can expand as you deepen your knowledge in new areas. It can contract if you fail to nurture your existing areas of expertise.

4/

To engage this mental model in your life, there are two key processes to go through:

(1) Identify what falls within your circle
(2) Identify the boundaries of your circle

(1) is all about figuring out what you know, while (2) is about humbly admitting what you don’t.

10 reasons your product will fail.

Words: @BrianNorgard

↓

1. Too complex

2. Can't be easily described

10 ideas that changed my life: (thread)

Illustrations by @visualizevalue

1/ Get more done by doing less.

2/ You can't get better unless you get started.

3/ Zoom out. It's getting better. (IP via @behaviorgap)

4/ 'Normal is an illusion. What is normal for the spider is chaos for the fly.' — Charles Addams

1/ In early 2004 we were heads down executing on Edit and Continue across a large contingent of teams. There had been several iterations of scoping, redesigns, and customer feedback.

2/ We had a weekly meeting every Thursday morning when representatives from each of the teams would get together and review progress. It was fairly heavy weight, but there were so many teams involved that it was necessary to have a regular sync.

3/ Regardless, E&C was coalescing, but teams were stretched thin working diligently to enable scenarios, improve performance, fix bugs, etc. It had been a month or so since we decided to add support for C# to the matrix as well, so folks were a bit stressed.

4/ That set the stage for the meeting that we had on the first Thursday in April. A debugger PM named Habib Heydarian ran the meeting and after a brief intro he gave me a ring to come in and present.

5/ I walked in and handed out a document that I had written up, titled DCR: C# Edit and Continue for Venus. DCR meant design change request, and Venus was the design-time code name for ASP .NET support.

@mattblaze AFAIK the only group to discover Ken’s hack was us in PWB/UNIX. One of the other guys noticed C prepreprocessor had gotten bigger, looked at binary namelist, found symbol not in source code. I got onto Ken’s system, found the code, very clever.

A bit latet, I was in Lab 127’s terminal room, talking to dmr or bwk, and overheard amusing conversation between ken and Robert Morris Sr, who sometimes consulted for NSA.
(RM Jr of worm fame was just a kid then.)

They were chortling away over cleverness of exploit. Then one (must have been ken) said “think we could put this over on NSA?” (which already had UNIX systems... we did favors now and then).
More chortling, then (must have been Bob): uhh, NSA really doesn’t have sense of humor.

PWB crew ran 1st real UNIX computer center & we were hyper-sensitive, partly because someone had called at night, told operator he was Ken Thompson & needed root password ... and got it. Turned out to be high schooler ... proving that social engineering tactics have been eternal.

Years later, as many BTL Directors were buying PDP11-70s for labs as general service systems, some PWB crew were asked to do security audits, given experience running biggest UNIX site. One lab was very proud of enhanced password software.
We did audit, agreed with that, BUT:

One of the big promises of software is composability. You can build rich, powerful experiences out of basic building blocks.

APIs add new things to the toolbox. For example: Treasury, which lets an app/platform store, move, and track a business’

I've been a small business owner and can talk at length about SMB banking, and will later, but let's put on the software developer hat right now.

Lots of software talks about money, keeps records about money, does calculations about money, but can't *touch* money.

This is extremely frustrating when you're building SaaS apps for businesses, because you have total control over your UX right until your app needs to touch money... at which point all data about it lives in a silo you can't access.

So you generally push work to the operator.

For example, suppose you’re writing a business-in-a-box system for electricians, including an invoicing feature.

You need to be able to read bank transactions to reconcile. You probably can't. The owner can. So you ask the owner to do mind-numbing work a computer does better.

It sure would be great if your business customers had bank accounts you could actually introspect and operate on their behalves! You could just get the list of incoming payments and match against the invoices.

There is some software to write but it is not rocket science.