Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I had something similar happen to me earlier in the week. The conversation went something like this:

Boss: Hey, we've got an urgent production issue that needs to be looked at. I'm getting some heat on this one and I need someone to diagnose it to see if it's a blocker for our release.

Me: Would you be able to ask X and Y to investigate? It seems they are on the support rotation for production issues. It'll take me at least an hour to clean up what I'm doing and switch over to run the old production instance locally.

Boss: It's urgent, I think you need to drop whatever you're doing and look at this.

Me: OK, sure.

(50 minutes later, as I'm almost done building the old production instance)

...

X and Y come back from a meeting.

Boss: I'll have X and Y look at this, you can go back to working on your stories for this sprint.

Me: !@#?$



One of the advantages of doing eXtreme Programming with lots of pair programming is that we eventually setup machines to be assigned to certain branches. Costs more computers, but is more productive. The best thing ofcourse is to reduce that buildtime, but not a whole lot you can do there.


Use a VM


Not enough CPU and Memory to do so. Our app is huge.


How many lost hours make up for the necessary CPU and RAM?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: