( ESNUG 593 Item 03 ) --------------------------------------------- [04/13/23]
Subject: Cooley's two new policies of Radical Laziness and Radical Honesty
COOLEY'S PRIVATE HELL: I made a simple flow chart to explain the personal
hell that I go through from running DeepChip.com
|
Step #1
|
Cooley sends out an email blast to the 62,000 DeepChip subscribers telling them a new article is on the site.
|
|
Step #2
|
Over the next 7 days, Cooley receives 25 to 100 replies about his new DeepChip article. 30% are replies about the article itself. 70% are terse "good article" type replies.
In addition, Cooley gets typically 5 to 8 really interesting replies that Cooley can possibly use for a killer future article. (I call those really interesting replies "tips" then.)
|
|
Step #3
|
Cooley then obsesses over those 5 to 8 "tips" to see if he can develope them into a Hot New Sexy EDA story. "The next big thing."
Problem is chasing each "tip" can easily take 3 to 6 man-weeks each -- and most them (90% or more) are dead ends that aren't significant -- or there's not enough to confirm them.
Either way, Cooley is in this researcher's/writer's HELL until a "tip" actually works out -- or a sudden unexpected "breaking news" story pops up.
|
|
Step #4
|
Weeks or months later Cooley finally gets a break and gets to publish a new worthwhile EDA story.
|
|
Step #5
|
Return to Step #1 above.
|
BREAKING THE CYCLE: The HELL part is Step #3 (above) makes it so even though
I'm busting my ass to chase down tips for that glorious Next Big Story -- I'm
not publishing anything on DeepChip for weeks at a time.
I stepped back.
Then I slowly realized I had take my ego out of this process.
Instead of being that guy who publishes these amazing, pentrating EDA stories
that wows the chip design world -- why not just go back to what I did in the
early 1991 ESNUG 1999 DeepChip years?
That is, practice Radical Laziness where I just cut & paste and then publish
all the reader replies that come in on a particular story. (It's a LOT less
work that way, I can tell you!)
Then also practice Radical Honesty where I just let the DeepChip reader
comments go out "as is" anonymously -- and when it's important it's clearly
marked when it's an EDA user talking vs. an EDA vendor talking.
- John Cooley
DeepChip.com Holliston, MA
P.S. And if, from time to time, I can slip in one of those occassional
well researched Next Big Killer EDA Stories with my name on it, great!
P.P.S. TL;DR -- you're going to start seeing a lot of raw reader replies
to the articles you see on DeepChip.
Join
Index
Next->Item
|
|
