1.1.1 of Tweed is now available in the App Catalog.
- User profile can scroll
- increased photo upload timeout
- font size setting should apply to direct message timeline
- Tweet text is image caption on photo uploads
Features and Changes
- changed photo upload default to yFrog
- forward gesture composes new tweet
- use j.mp for url shortening (instead of tinyurl.com)
- show original tweet on replies
- Pixi support
- landscape mode (& preference to disable)
The question came up in the course of using RabbitMQ of how to ensure that if something catastrophic happens that the system wouldn’t lose any data due to either side of the queue coming down unexpectedly.
We had the exchange and the queues both set as ‘durable’, which we thought should cover everything. Right?
In addition to the exchange and queues needing to be durable, the messages themselves must be flagged as ‘persistent’.
Carl Smith, founding member of nGen Works, breaks down the steps to understanding, building and keeping trust with your users. Trust is becoming vulnerable based on a positive expectation. It’s about the promises you make in subtle and obvious ways.
In a special evening event, Scott Chacon from GitHub gives an excellent overview of Git for developers, with a lively back and forth from the audience.
I’ve been a member of an online Star Wars club for…wow…almost 10 years now. At the time that I joined I was just learning about databases and web-programming and was rather impressed with the functionality that existed (and still exists) in the club’s website.
The site is coded in old-school ASP, with SQL Server on the backend.
I cringe just thinking about it.
I’ve been trying to convince The Powers That Be for a while now to look at recoding the site to some other environment. For a long time I tried to push them towards PHP, but they just dug in their heels and refused to look at that option really.
Then I discover Ruby on Rails, and I see how much better RoR would be for this site. It would provide structure to the codebase, organization, and seriously increase readability. And since the club is a volunteer organization, with a pretty regular rate of people transitioning in/out of positions, having a strong test suite would be HUGE towards helping new developers ramp up on how the system is supposed to work and quickly identifying when a change in the code has broken something else in an unforeseen manner.
Of course as I’m making those discoveries, The Powers That Be decide to move ahead with PHP…
So, on to the question at hand: What do you do, what information do you use, in an attempt to convince someone to switch from an older technology (ASP, PHP) to Ruby on Rails?
This week we moved our gems over to GemCutter. It’s very easy to claim the gems that were automatically synced over from RubyForge, but if you have gems on GitHub it takes a little more work. We had several gems to move over, some of which had quite a few versions we wanted to preserve. You can’t just push the .gem files over because GitHub built the gem namespaced with your username (e.g. “pivotal-apdex”). So Sam and I built a little script to pull down the gems from gems.github.com, fix the name in the spec, repack, and push up to GemCutter.
You can get the hubcut script at http://gist.github.com/220908
I was introduced to the world of Ruby in general (and Ruby on Rails specifically) almost 2 years ago. Prior to that my professional programming experience consisted mostly of PHP, with a little bit of Java and ASP thrown in for good measure.
Then came that almost magical day when I was hired to a new job and instructed that I needed to learn Ruby on Rails.
“Ok, I can do that.”
I absolutely fell in love with the language and the framework, and that experience put me on the path that led here to Pivotal Labs. But I know that I still have a lot to learn, so am still picking up things that in some ways I feel stupid for not having picked up earlier.
One such thing is RailsConf. I had heard of it before, but not in any kind of context that I really appreciated it or understood what that was (I’m getting a better idea now after some research).
Now I really want to get involved and submit a proposal for a talk/presentation at RailsConf. I just have no idea what to do it on or where to start….
If you are using AutoTagger, you may want to upgrade to the latest version. The following bug fixes were applied:
First, you can now define your stages as strings or symbols and auto-tagger will not fail (thanks to Chad Wooley for the bug report).
Next, when deploying from a branch auto_tagger uses real_revision, not the previous tag, to create the new tag thanks to Brian Takita.
I recently released a new version of ActiveHash which adds a number of features that make it even easier to use Hash or Yaml data stores for ActiveRecord-esque models. The recent updates include:
- belongs_to and has_many associations
- save, create and destroy methods that add or remove the objects from the in-memory collection (great for object mother libraries like Fixjour)
- support for string ids
- support for hash-style yaml data (think Rails fixtures)
- auto-incrementing ids by default (again, for Rails fixtures)
If you have earlier versions of ActiveHash I highly recommend that you upgrade. It makes testing and common uses much nicer. If you are on gemcutter, it’s as simple as:
gem install active_hash