A shorty today.
- A massive group of developers is revisiting and debating the current state of our shared-code architecture. appable_plugins might not be a perfect match, and we might develop our own or plugin-sharing system.
A shorty today.
<code> $> svn propset svn:executable ON somescript.sh $> svn propset svn:eol-style native somescript.sh </code>
ruby -r profile, and our own custom ruby test benchmarker, amongst others.
ActiveRecord.connection.execute("some sql")to build some reporting statistics, but it seems too early to blame that. Coincidental, though.
:persistent => false:
<code> AWS::S3::Base.establish_connection!( :access_key_id => access_key, :secret_access_key => access_key, :persistent => false ) </code>
Not much of interest today beyond project updates.
GC.startafter heavy RMagick use. We’ll also check the version and insure that it’s 1.13.
Follow-up: Actually it looks like we were hanging connecting to Amazon’s S3 service.. Once we figure out the details we’ll let you know what the problem was.
Brief project reports, and that’s it!
Image::change_geometry(geometry_string). In a nutshell, you can perform complex image transformations my passing
change_geometrya string; for example,
my_imageto a 50×50 pixel image, but only if it’s larger than 50×50. For us, this exact line turned our 600×600 image into a 50x38 image. Weird. Only on Linux.
Interesting/Ask for Help for 02/07/2007
require RMagick, but neither the PC or Mac complained, only Linux.
Our standups (as many standups) had devolved. They were taking too long, and people were just giving status reports. So we put up a list on the wall to remind us of the main points of standups:
– in that order. In other words, previously we were focusing on the least important step just because it was chronologically first.
Now, since we’re focusing on the present and future, we often don’t even talk about yesterday — unless something interesting happened then.
This also helps the standups scale to multiple teams all meeting together in the morning — we reserve 5 minutes at the beginning for each team lead to give an update, then go around and ask if anyone needs help or has something interesting to share. We also have an “Interesting” list on the whiteboard that people add to throughout the day. That makes each standup serve as a mini-retrospective… which, in turn, allows our monthly retrospectives to focus on big issues rather than the daily minutae.