Alumni blogs

I’ve written before about using the cypher CREATE statement to add inferred information to a neo4j graph and sometimes we want to do that but have to deal with optional properties while creating our new relationships.

For example let’s say we have the following people in our graph with the ‘started’ and ‘left’ properties representing their tenure at a company:

CREATE (person1 { personId: 1, started: 1361708546 })
CREATE (person2 { personId: 2, started: 1361708546, left: 1371708646 })
CREATE (company { companyId: 1 })

We want to create a ‘TENURE’ link from them to the…

Just released a new Agile In a Nutshell Planning video. You can see it and the other Agile In a Nutshell videos (like user stories and estimation) here.

Here are some slides from the deck.

Agile Planning

An important part of deploying a database-backed application is keeping the database schema up-to-date. For Rails applications, you typically do that by running:

$ rake db:migrate

For Rails applications running on Heroku, you typically run the migrations immediately after deploying a new version of your app, e.g.

$ git push heroku master
$ heroku run rake db:migrate

Since Cloud Foundry takes after Heroku in so many ways, I expected to use a similar workflow when deploying my Rails application on Cloud Foundry. I was suprised to discover that CF does not…

Agile Software Community of India is happy to announce 4 new exciting conferences.

• July 19th and 20th 2013 – Agile Coach Camp Bangalore 2013
• September 21st and 22nd 2013 – Agile Goa 2013
• November 29th and 30th 2013 – Agile Kerala 2013
• February 26th – March 1st 2014 – Agile India 2014

————————-

* Agile Coach Camp is an unconference for Agile Coaches, Scrum Masters, Agile Trainers, Leaders, Change Agents and Mentors. (Last coach camp in June was completely sold out 2 weeks in advance. Since we had a waiting list of 43 coaches,…

Everyone loves a project that comes in ahead of schedule and under budget. But if you consistently too under budget, people will accuse you of sandbagging your estimates and accuse you of being a little too cautious.

This caught me once. We sized a project using the estimates as a range technique, and convinced management to use the upper numbers.

We then estimated our team velocity and again, used a conservative number around how fast we thought we could go.

Turns out we the project was simpler than we thought, and we ended up going…