Skip to main content

On Execution

Systemic problem in the startup culture is that people have plenty of ideas but no execution. I'm incredibly lucky to be passionate about software engineering and that I have the ability to build products (on my own).

We all can't be great at everything and I'm a firm believer that people should focus on their strengths while on a day-to-day basis keep improving their weaknesses. For me,  I kept following my love for software engineering (I've become both technical and design focused); therefore, my weakness is really the sales and marketing side. After hanging around plenty of software salespeople -- I've come to realize that their primary strengths boil down to inside connections, confidence, and presentation.

Thomas Watson (IBM) once said, in order to sell software, you have to look like the person you're selling to. IBM at the time was selling "punch carded tabulating machines" which were used in many law and financial offices.  This was when an IBM salesman was distinguished with their navy blue suits and wing-tipped shoes. Thomas Watson and his son were amazing salesmen. They were so dominant in their field of expertise that they could close only a few deals and have their quotas filled for the year. Many salesmen at the time were all about a large volume number of small deals here and there (less risk) but the Watsons closed the big deals.

Based on the couple of projects that I've tried tackling, I've come to learn that the only way to really push your product into the hands of people who can provide constructive criticism is to be disruptive, aggressive, and 'in your face'. Never be shy about sharing what you've built and don't worry because embarrassment is key to improving. Push forward, be bold, take risks, and most of all, learn to sell the vision of your MVP in order to encourage constructive criticism.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.


World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:

Now, whenever you make a commit, it should show up like this in the log:

Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this

Want more emojis? check out the Emoji Mardown Cheatsheet!