Continuous Deployment of Ghost from Github

As part of my fellowship at Code For America, my team had to set up a blog in order to keep everyone updated about what we’re doing and how everything is going. Most teams just set up a tumblr blog. However I had some ethical qualms about doing that and successfully was able to convince my team to agree to running Ghost.

Read more »

Why I'm Coding For America

I am not a natural born United States citizen. I spent the first ten years of my life in a country much different than this one, with a much different culture. After arriving in the United States, I witnessed and participated in my family’s struggle to understand and work with the complex bureaucracies wrapped around immigration, food stamps, social security and public services. I waited with my family in seemingly endless lines, only to be told I needed to go to a different building and wait in another endless line. I learned that the system is flawed and wondered how to fix it.

I have always been curious in understanding how cities develop, sustain and function, and I have been fortunate enough to explore these topics in many cities and countries across the globe. Just like every human being, every city–while maintaining similarity in the most obvious and general features–is an extremely unique and complicated living organism.

And just like when doctors treat human beings, often unsure that the decision or action they’re taking will help rather than harm the patient, oftentimes the people making decisions for a city simply do not have the information to be confident in the outcome of their actions.

I have always been the observer. I always wondered, read, asked, but never acted. I saw, but never dove deep enough to understand. I often wondered how my skills could be of help, but was never really able to answer the question on my own.

Today we have the technology and the knowledge to help governments make better decisions, provide better services to their residents, and to improve the quality of numerous people’s lives.

That’s why I’m coding for America. As a Code For America fellow, I have an opportunity to no longer be the observer, but the doer. I have a chance to dive in deep and use my skills to help fix and improve the systems that each of us interacts with on a daily basis.

Read more »

ITA Spotlight -- ME!

I guess it’s weird to be writing a blog post about myself.

I’m not that great at shameless self promotion. But it was pretty cool that the Illinois Technology Association chose to do a spot light on me as the Solutions Architect for Promet Source.

I personally don’t think I’m THAT awesome, but hey, I’ll take the props. So, thanks ITA and Promet!!

Read more »

Rails 4 Strong Parameters

So I’ve been going through the awesome JumpStart Labs Tutorials lately to learn some rails and found a small bug in the tutorial.

It’s not really a bug though. The tutorial was made with Rails 3.x in mind and I’ve been using Rails 4. So I found a small discrepancy and submitted an issue

I was strongly encouraged to blog about my journeys into Rails and Ruby so this is one of those posts. Really hoping someone finds this useful.

Read more »

Firm Grip on Menus in Drupal

For many that have worked with Drupal in teams before, I’m sure you have run into problems with managing menus. There are many ways to create a menu item in Drupal, one of them being from the menu editor, and others when creating content or views, or panels pages.

The menu items created when you’re creating content, views or panels override any configurations you may have set in the menu editor, hence the source of the problem.

In addition, the way that menu items are stored in features, they get explicitly linked to node id. So if you have a page on dev that’s node/5 and the same page that lives on staging that’s at node/6 and prod is node/7, it’s extremely different to move menu configurations across environments.

This was causing a ton of wasted time and even more frustration.

Read more »