Skip to main content

Momentum



We've all been through that phase in product development where you're extremely excited to keep building out specific features and you're hustling so hard that you want to get it into the hands of your users and get feedback (The MVP, minimum viable product). Incidentally, I've come to the conclusion that what really makes or breaks startups is momentum.

If the team stagnates on product development and continuous improvement, your team's overall confidence, dedication, and motivation will dissipate slowly. Taking this advice on, it becomes ever so clear on how to determine whether a team is going to be successful; also, it provides you that level of insight when to cut your losses short.

They say, "never give up when all hope seems lost". I'm a big believer in this; only if I'm the only person in the equation. For example, if I'm on the treadmill with no breath and needing to hit a specific benchmark (time or distance) -- I'll muster up an immense amount of motivation to hit that mark because I know in the long run it'll have a return on investment. 

When you're in a professional, collaborative environment where you have to rely on founder (majority stakeholder) to pull their own weight as part of a business venture -- the situation gets increasingly more complex. 

Ultimately, everyone has to make tough decisions and I'm passing this advice to anyone wanting to do any risky business venture, you should always be surrounded by people with the same level of passion and dedication. This will allow your team to gain momentum and sustain development velocity to really nurture a great product, grow your user base, and make a positive impact on your customers.
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.

Cheers,
Jaime

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!