Skip to main content

A focus on making DevOps more open and connected

After serving the RESAAS vision and its team of high performance salespeople, visionaries, and software engineers for the past year -- I've made the decision to take on a different challenge that involves helping DevOps be more open and connected to their tools, teams, and solutions using social and big data as vehicles to achieve our grand vision. It's official -- I have left RESAAS and I'm determined to make things easier for DevOps as it continues to grow as an integral role in software engineering teams.

By reading Software Will Eat The World -- one can agree that software has the ability to disrupt a wide array of industries and markets. The great thing about this is with cloud computing, costs to ship an MVP have been reduced drastically. Furthermore, having production systems serving millions of customers have caused the "DevOps" role to emerge in Internet-based software companies.

DevOps can be defined as a hybrid of operations, quality assurance, as well as, development. With over 3+ billion users on the internet and different SaaS initiatives across the globe, it's becoming an increasingly hot role to play on a field where your online services must have an exceptional uptime record. But let's face it, anyone who has been in the role of a DevOp knows this -- it can be extremely stressful with the velocity of most software engineering teams shipping code to production over 20 times a day utilizing continuous deployment processes.

The faster a DevOp can react and resolve a situation with the right tools and right environment in place, the safer the business can feel about the user experience (do our customers trust our brand and reliability of our services if we're down?) and the health of their sales pipeline (can we as a business keep the foot on the gas pedal for customer acquisition?).
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!