Working Backwards
From APIDesign
(Difference between revisions)
| Line 6: | Line 6: | ||
* My last press release was [[GraalPolyglotStudio]] and it failed miserably - e.g it is still pending. Probably [[OracleLabs]] isn't the right place for future press releases. | * My last press release was [[GraalPolyglotStudio]] and it failed miserably - e.g it is still pending. Probably [[OracleLabs]] isn't the right place for future press releases. | ||
| - | Later [[I]] found out that [https://twitter.com/werner Werner become CTO of Amazon]. Today [[I]] learned that these days the methodology is called "future news". I have to admit I miss writing future press | + | Later [[I]] found out that [https://twitter.com/werner Werner become CTO of Amazon]. Today [[I]] learned that these days the methodology is called "future news". I have to admit I miss writing [[future press release]]s. If you need someone to write a [[future press release]] (and then make it happen), let [[talkback|me know]]! |
Revision as of 16:59, 3 May 2019
Working Backwards is a methodology I learned about from a Werner's blog post many years ago. I had immediately felt in love with that methodology and started to practice it. Every time I was about to start new project, I started with a future press release:
- Window System 7.1 press release - needed just a little tweaks and three months delay
- We created many future press releases while working on the NetBeans performance team
- JerseyFaces was radical, but we almost made it
- My last press release was GraalPolyglotStudio and it failed miserably - e.g it is still pending. Probably OracleLabs isn't the right place for future press releases.
Later I found out that Werner become CTO of Amazon. Today I learned that these days the methodology is called "future news". I have to admit I miss writing future press releases. If you need someone to write a future press release (and then make it happen), let me know!
Follow
