Amazing conversation I had with my family on Facebook.
Musings of a twenty-something web guy.
This article in the New York Times is fascinating. A review of a study concluding the effects and influence we can have on our friends and social connections. Next time you’re in a bad mood, want to light up a cigarette or you want to skip the gym, think of the effect you could be having on those around you, and more importantly, the effect on people you’ve never even met.
Are your friends making you fat?
Posted via web from Jared McFarland | Comment »
@2 months agoIn order to keep myself on task with all my little programming projects (The LPP?), I joined the SPUC (Secret Project Update Club). I’ll post updates once a week. This week, introductions:
Hopefully the accountability of posting here will keep me making progress on all these projects. School just started, so we’ll see how that goes.
Posted via email from Jared McFarland | Comment »
@2 months agoHere at Bookmans, our development flow works in stages. We code locally, push to a staging server, and move from the staging server to the live server. To manage issues we have a ticket management system setup in ActiveCollab, where tickets are assigned a number by project. A few days ago I pushed about five tickets to the staging server for review. @tilopa checked ‘em out, and told me that three of them were good to go live, but the last two had a few more quirks to work out. This actually turned into an issue for me, I had been working in a Git branch called “jared”, and merging into “master” to push to staging, then merging master with a branch called “stable” to go live. But I didn’t have a way to just push three tickets like, they were all jumbled into “master” together.
Now, when working on a new ticket, I branch out a ticket with the project name and the ticket number in it, for example “classifieds_8”. Then, when I want to push to staging, I merge that branch into “master”. When that piece of code is ready to go live, I don’t merge “master” and “stable”, I actually merge the branch containing the fix (ie, “classifieds_8”) with “stable”. This way I can push one ticket at a time to the production server.
Posted via web from Jared McFarland | Comment »
@3 months agoThis article goes over getting Ruby development on Snow Leopard in great detail. Worth the read if you’re having trouble, or if you have a less than perfect setup on your machine currently. http://www.metaskills.net/2009/9/5/the-ultimate-os-x-snow-leopard-stack-for-rails-development-x86_64-macports-ruby-1-8-1-9-sql-server-more
Posted via email from Jared McFarland | Comment »
@2 months ago