Knowledgebase

Writing Publicly About Technical Work Print

  • 0

Building a record of thinking.

WHY IT HELPS A CAREER

It demonstrates communication, which is hard to assess otherwise.

WHAT TO WRITE ABOUT

A problem you solved Something that confused you until it did not A comparison you actually made An account of something that went wrong

WHY THAT LAST ONE IS VALUABLE

Accounts of failure are rare and useful.

WHAT MAKES A USEFUL PIECE

A specific problem What you tried What worked and why What you would do differently

WHAT TO AVOID

Introductory material that exists everywhere Opinions with no experience behind them Writing to a schedule with nothing to say

WHY THAT LAST ONE

Volume without substance damages more than silence.

HOW OFTEN TO PUBLISH

When you have something worth saying.

WHAT LENGTH

As long as the substance requires.

WHERE TO PUBLISH

Anywhere durable that you control.

WHY YOU CONTROL

Platforms close, and the work should survive.

WHAT TO BE CAREFUL WITH

Employer confidentiality Naming people unfavourably Publishing internal detail

WHAT TO CHECK

Your contract, and with your employer where uncertain.

WHAT TO EXPECT

Little response, mostly.

WHY WRITE ANYWAY

The compounding is slow and real, and the clarification is immediate.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot