Skip to main content


Words by Lieutenant General Hal Moore:

There are four principles in leaders conduct in battle. First is three strikes and you're not out. There's 2 things a leader can do, either contaminate his environment the unit with his attitude and actions or he can inspire confidence. He must be visible on the battlefield. He must be in the battle. Self-confident, positive attitude, must exhibit his determination to prevail no matter what the odds or how desperate the situation. Must have and display the will to win by his actions, his words, tone of his voice on the radio and face-to-face, his appearance, his demeanour, his countenance, The look in his eyes, he must remain calm and cool--no fear. He must ignore the noise, the dust, smoke, explosions, screams of the wounded, the yells--the dead laying around him, that is all normal. Must never give off any hint or evidence that he is uncertain of a positive outcome even in the most desperate situations. Again, the principle that must be driven into your head and your head's of your men is 3 strikes and you're not out.

And the corollary principle which is interactive with one is there is always one more thing that you can do to influence any situation in your favour, and after that one more thing, and after that one more thing, etc.

In battle, I periodically detach myself mentally for a few seconds from the noise, the screams of the wounded, the explosions, the yelling, the smoke and the dust and the intensity of it all and ask myself: what am I doing that I should not be doing and what I am not doing what I should be doing to influence the situation in my favour?

The third principle is when there's nothing wrong, there's nothing wrong except there's nothing wrong. That's exactly when a leader must be most deliberant.

Finally number four, trust your instincts. In critical, fast moving battlefield situations, instincts and intuition amount to an instant estimate of the situation. Your instincts are the product of your education, your reading, your personality, and your experience--trust your instincts. When seconds count, instincts and decisiveness come into play. In quick developing situations the leader must act fast impart confidence around him. He must not second-guess the decision--make it happen. In the process, he cannot stand slack-job when he is hit with the unexpected. He must face up to the facts, deal with it, and move on.

Inspirational words for team leaders on any project.

Good luck and have fun,
Jaime Bueza

Jaime Bueza is a software developer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Starbucks, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications and Microsoft. When he's not developing useful software that constantly evolves with business requirements, he's creating tutorial videos for aspiring front-end developers.
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.


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!

NodeJS Hack Session: MMO Pokemon with NodeJS/WebSockets

The primary focus of this proof of concept is to determine how easy it is to build real-time web applications for all iPad, iPhone, droids, Safari, Chrome users on top of NodeJS (non-blocking event driven server side Javascript platform). The proof of concept was built within 6-8 hours including the following:

Uses Express framework for server side Javascript development (inspired by Rails / Sinatra / Django)Uses EJS for templating language (much like Django templates and symfony) -- allows partials and passing parameters into partials like symfony PHPReal-time chat using WebSocketsArena Queueing System for real-time competitive matchplay using WebSocketsHTML5 AudioCSS3 transitions for all hand cards, tappable cards, transparent panels, rounded corners, drop shadowsFallbacks for Firefox, IEFirefox/IE will fall back to Flash socketIE will fall back to XHR long poll if the user doesn't have Flash installedNoSQL CouchDB for fetching users and soon cards, achievements, friend associat…