Skip to main content

Art of the Start: Causation

I recently started reading Art of the Start by Guy Kawasaki. Guy was probably one of the first "recognized" technology evangelists and has written lots of books on the topic. Each of his books always seem to be slightly different variations on the same theme - on how to create something that completely changes lives (loosely: Selling the Dream was on how to sell it, How to Drive Your Competition Crazy was on how to compete with it, Rules for Revolutionaries was on creating it) - so I wasn't too sure how his new Art of the Start would read, especially since his new focus is on helping startups get venture capital. But once again, he's really done a good job.
 
The first chapter, Causation identifies what you really need to work on: Meaning, Mantra and MAT (Milestones, Assumptions and Timetables).
 
Instead of all those books that say study this and plan for that, come up with a mission statement and the like, Guy promotes the easier to remember style of a Mantra. Who wants to remember a huge mission statement when a five or six word mantra will do? In fact, one of his first exercises was to write your mantra in the following space: __________________ .  Not a lot of space - but what a GREAT guideline! Now you can actually remember what you do (for all those unclear moments)
 
 

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP