Warning: ksort() expects parameter 1 to be array, object given in /homepages/35/d125357260/htdocs/blog/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php on line 214
Hunter Walk and Mark Suster and Deleting History and Editing Like #cs183e
Subscribe NOW

Enter your email address:

Text Message our CEO:


or on twitter

Free Resources

Click Here to learn more

In The Media

Hunter Walk and Mark Suster and Deleting History and Editing Like #cs183e

by Larry Chiang on April 19, 2017

By Larry Chiang
I rely on searching inside twitter for specific topics. Thus, deleting histories runs counter in my effort to use twitter like it’s a “repository of signature business protocols”. 
David Silva Smith asked “Mark Suster, you stopped tweeting?”

Mark Suster 👊🏼 (@msuster)
Nope. Just deleted history. Following in the footsteps of the great @hunterwalk twitter.com/davidsilvasmit…


So, I will be more diligent in 
– screenshotting
– hashtagging
– embedding. 

Tweets that will help founders who search inside twitter 
Larry Chiang (@LarryChiang)
@msuster @hunterwalk Histories (on twitter) can evaporate, but screenshotting-hashtagging-embedding your tweet on WP was real. #cs183e = editing #postmortem pic.twitter.com/GUrPPZ7fqa

Histories (on twitter) can evaporate, but screenshottibg-hashtagging-embedding your tweet on WP was real. #cs183e = editing #postmortem 

Searching inside twitter for distribution hacks and editing their startup to improve their startup = best use of twitter for a newbie with few followers. 


Hunter Walk (@hunterwalk)
Postmortems are important, but consider a premortem too



Hunter’s tweet applies to #cs183e

☆ Sean Lindsay (@rseanlindsay)
@hunterwalk I really liked this post from @lpolovets that seems relevant to your point: 


#cs183e is postmortems and premortem. CS 183e is inspired by YC and Stanford engineering. 

Leo Polovets (@lpolovets)
“How to Use Thought Experiments to De-Risk Your Startup” codingvc.com/how-to-use-tho… [new blog post] pic.twitter.com/GnoWw1ru7Z

Leave a Comment

Previous post:

Next post: