Archive by Author

Top Commits of May 2013

4 Jun

It’s that time again folks. All of the commits from May have been collected, tallied, analyzed, and sometimes giggled at.

And away we go!

Looks like some people are putting in extra effort to make the list. Kudos for this one:

This class is a stub. You can help Bruce by expanding it and adding citations.

Can’t pass up a chance to highlight the elevated language choice:

Removing misbegotten commit of duplicated classes

Someone gave this developer TOO much power:

no more time zonez.

Speaking of time:

build fix.. stupid…

Thanks for keeping source control PG:

*&%$&^: Broke a JSLint Test – fixing

Got this check-in 3 times in a row. I’m guessing the answer was ‘no’:

Does this fix the EF mapping?

And our top commit of the month is a timeless adage:

Compiles fine on my machine.

Alright that wraps up this month’s edition. I can’t wait to see what wacky commits our dev team can come up with for next month.

Can You CrowdSource a Program?

30 May


Fortigent Engineering is always looking to innovate, not only in what we create, but in how we create it. It maybe a bit cliche, but I really believe that ‘thinking inside the box’ constrains a team to produce box-shaped results.

FoodOn Wednesday, the ever-growing Engineering team was locked in a room together for a no holds barred development experiment to stretch the walls of that metaphorical box. Luckily, brain food was on the menu.

In teams of 6 we were challenged to invent a novel presentation of user data given an expansive set of variables. Basically, the teams were tasked with creating a formula that would distill the most pertinent pieces of information into one aggregate product.

Without further adieu, the formula we came up with is:


OK, so that’s NOT the formula. In fact, we didn’t come up with a very definitive answer at all. As it turns out, 25 engineers can’t always agree with one another. We did however, carve out a few victories. We were able to identify what variables we believed were essential to solving the problem. We were also able to obtain feedback from almost every individual and evaluate their approach. To that end, my views on the problem were swayed half a dozen times in the span of an  hour because of all the unique ways the team was going at it.


So maybe we didn’t come to a solution once and for all, but we sure are closer. We’ve also proven that exercises like this can peel away at an amorphous set of requirements by harnessing the enormous brain power of our entire team at once. I believe that we have pioneered a new means to problem solve in our group. Sure, it will require some refinement, but I think that large group development can evolve into a powerful tool for solving the increasingly difficult problems we face as a team.

Not to mention it was a pretty sweet way to spend my birthday if it had to be on a work day.

Favorite Check-Ins of April

24 Apr

Following in Brett’s footsteps, I have thumbed through some of our repository commits over the past month and found a few bits of a wisdom, and a few bits of not-so-much wisdom:

Jimmy – 4/18:


Dobri – 4/18:

Wierd namespace got in there somehow….and kept compiling until now? >.>

Brett – 4/15 (Channeling his inner Fiddler on the Roof):

daily positions – oy vey.

Jimmy – 4/10 (To the point):

bad test.

Dean – 4/10:

Killing This branch

And the day before:

Just swearing — cause I’m an idiot

Contrasted with Geoff, who chooses to rid the world of frustrations, one popup at a time:

Removed an annoying alert 🙂

And my favorite commit message of the month is brought to us by Pushpak:

Checking in change

Whoever runs into Pushpak  first should let him know that he’s this month’s grand prize winner.

Well that’s it this for this month folks. Leave a comment with your favorite recent commit message and keep the one liners coming.

Fortigent Engineering is Growing

15 Apr


After nine months on the team, I am safely able to say that I’m no longer the F.N.G. (that’s Fortigent New Guy for those of you snickering in the corner).

In the span of less than a year, the pool of engineers on our team has almost doubled. We’re analyzing, developing, and testing more every single day. We’re stretching ourselves into new areas with enthusiasm and vigor. Needless to say, it’s an exciting time to be here because the more we prove to the world that we’re a great team, the more our team is able to grow. To that end, we have already been able to hire four new developers in 2013!

Our two newest senior developers, Dobri and Alex, come from very different areas of expertise, but have already begun sizable contribution to our systems, especially with concerns to scalability and user experience.

We have also brought on board two new associate developers, Leah and Nick. Both are beginning a new career in software, and have shown amazing progress as they begin to assimilate with their teams and tackle features in our core applications and even our newest creations.

To learn a little bit more about our 4 newest developers as well as our seasoned veterans, take a look at our updated brochure courtesy of Jimmy.


The contributions of our newest developers is really no surprise. We have always made it a team responsibility to teach, listen to, and foster colleagues to success. It’s a reflection on the experienced team members’ efforts as well as the new members’ skills that they can be plugged in to the most fundamental of our business’s applications and begin producing immediately. This spirit of camaraderie and  mutually shared success isn’t an order from up above, or a meaningless slogan. Rather, what we’ve learned is, when you’re a part of a team that works together organically, you root for one another (I think I’ve made one too many plant-based puns this post).

I hope we can continue this spirit and attitude as we expand our team in the coming months. We have already announced that we’re looking for summer interns, so check out the recent post on that. Alternatively, we are always looking to hear from interested developers, testers, and business analysts who would be excited to work at a place like Fortigent. If you’d like to learn more about us, connect with us on Twitter.

We’re Looking for Summer Interns

3 Apr

The Development team at Fortigent is seeking four Software Development Interns for the Summer of 2013. We have paired with the University of Maryland to offer an unpaid, 3 month internship to Computer Science students who are interested in cultivating their skills and exposure in the software development world. Successful completion of the internship can be leveraged for credit at the University of Maryland if the applicant makes proper arrangements with their academic adviser.

We are looking for candidates who have experience in Object Oriented Programming as well as knowledge of relational databases. Students who participate in this internship can expect to become familiar with enterprise development concepts such as Continuous Integration, Agile, Scrum, Unit Testing, and Source Control.

If you are interested in applying, search for job ID 75365 on UMD’s Careers4Terps service or send your resume to

FYI: We have a decent coffee machine, so your internship probably won’t look a whole lot like this.