Sign Up | Login Standout Jobs

Atlantic Dominion Solutions

Blog

  • The first half of 2008 has seen a great number of happenings in the Ruby and Rails worlds. Here are the top ten for the first half of 2008.

    • June 23, 2008 - Rails scales - LinkedIn serves 1 billion pages using Rails
    • June 1, 2008 - Rails 2.1 is released
    • May 31, 2008 - Ruby 1.8.7 is released
    • May 30, 2008 - Joel Spolsky keynotes RailsConf 2008
    • May 30, 2008 - FiveRuns released TuneUp to help with Rails performance optimization
    • May 27, 2008 - JRuby 1.1.2 is released, and runs Rails 2.1 like a champ
    • April 13, 2008 - Phusion Passenger (mod_rails) is released
    • April 11, 2008 - Rails core moves to Github, prompting many to move with them
    • April 2, 2008 - Morph Labs makes Rails deployments to EC2 a cinch
    • January 1, 2008 - Thin comes on the scene as an alternative to Mongrel

    See something I missed? Drop us a comment below.

    Other posts you may enjoy

    Share this post
    July 3rd, 2008 · No comments No comments
  • The last BarCampOrlando was a brilliant success, and at the same time, spurred a lot of conversation about what is/is not BarCamp. Now is the time to start planning the next one, and the folks over at Create Chaos are presenting us with an opportunity to hold BarCampOrlando at Create Chaos. They would provide the room and the AV equipment; we’d bring the people. And that’s all you really need for a BarCamp. We are looking to gauge interest so we can say yay/nay to these kind folks.

    I had a great time at the last BarCampOrlando. If I remember correctly, around 400 people signed up and more than 200 people came out for the two days. There were a ton of great talks on a variety of subjects, so there was definitely something for everyone. I got the chance to meet a lot of new folks that I don’t normally see in the local tech scene, which was perhaps the best part of the entire event.

    So, if you attended the last BarCampOrlando and want to voice your opinion on the next, please join the discussion on the BarCampOrlando Google group. Thanks for adding to the conversation.

    Other posts you may enjoy

    Share this post
    July 1st, 2008 · No comments No comments
  • We purchase all of our domain names on GoDaddy.com and host our DNS there as well. Our main domain, techcfl.com, had been hosted along with our corporate site on FatCow, when our site was written in PHP. We converted it to Rails some time ago along with giving it a major facelift. We also use Google Apps for email, team calendar, and team docs.

    At RailsConf 2008 we partnered with Morph Labs (announcement coming soon), a “complete and fully managed hosting environment for Web applications.” Mor.ph’s hosting platform uses Amazon EC2, and your application can be easily scaled with a click of a button. Since partnering, we have moved our main site, the acts_as_conference site, and the Rails For All sites there. In doing so, we had to update our DNS, and during that process, we managed to take our email down for an entire week. So, after much troubleshooting, here’s the skinny on setting it all up.

    Google Apps

    If you are hosting email on Google Apps (for your domain) already, there is nothing more you need to do.

    Mor.ph

    When you sign up with Mor.ph and create a paid AppSpace Subscription, you have access to a domain redirection feature. To use it, you add each domain you want the site to answer to. Here’s how ours is set up:

    • *.techcfl.com
    • techcfl.com

    This ensures that our site responds whether or not you use the “www” in the address. Personally I hate it when web sites crap out if you don’t add the “www,” so make sure yours doesn’t do that. Once you have that ready to go, stop and start your subscription.

    GoDaddy

    The GoDaddy configuration was the one that took the longest to figure out. After much ado (and perhaps a good dose of ignorance and refusal to call for support), I figured out that when setting the name servers to use, if you are going to use the GoDaddy DNS servers, but host your site elsewhere, you need to select the default parked nameservers. Next, create an ‘A’ record for your root domain, ‘techcfl.com’ in our case, and give it an IP of a Morph load balancer: 72.26.105.226. After that, create a CNAME record as follows:

    Alias: www
    Host name: yourapp.morphexchange.com
    TTL: 1 hour
    

    Substitute ‘yourapp’ with the Morph domain you selected when setting up your AppSpace. You can find it on the subscription settings page of your Morph subscription. In our case, we named ours ‘techcfl,’ so the host name we use is: ‘techcfl.morphexchange.com’.

    Once you have those records set up, you want to configure you MX (mail server) records to use Google Apps if you haven’t already. Google has the skinny on that.

    Ready to Roll

    Once DNS propogates you should be ready to go.

    Random Posts

    Share this post
    June 30th, 2008 · No comments No comments
  • I came across a great article on LinkedIn’s use of Ruby on Rails to serve 1 billion (yes with a ‘b’) page views per month for a Facebook application. The solution is simple: application architecture and appropriate hardware. My favorite line in the article is this: “Jim Meyer, manager of LED says that Rails scales like any other web application: ‘That is to say you need to take into account all the components from the moment the request is received at the load balancer all the way down and all the way back again.’”

    Other posts you may enjoy

    Share this post
    June 25th, 2008 · No comments No comments
  • I’m a member of the Scrum Development group on Yahoo!, and after lurking for more than a month, have joined the conversations going on there. A recent thread that I responded to was started by a gentleman in a semi-government organization dealing with some major issues while implementing Scrum. His manager is unsupportive, his team does not see him as a leader (he was previously a peer), and due to a lack of responsibility being put on the team the entire process has gone down the tubes. He’s been dealing with this for a more than a year and his frustration comes through in his writing.

    This leads to the question: is Scrum for everyone?

    When I spoke at RailsConf about Agile Development with Scrum one question I was asked was whether or not Scrum is a good fit for all teams. In short my answer is it could be, but you might run into challenges. Some of the biggies that stand out are:

    • No top-down buy-in from management
    • Project managers are unwilling or unable to use a new method
    • Micro-management abounds and there is seemingly no way of changing that
    • General ignorance of how Scrum works and its’ benefits

    The last point is the easiest to deal with - education. The other three are tougher nuts to crack. With Scrum leadership is stressed over management. My advice: lead by example, start small, and prove its worth. Scrum isn’t an all-or-nothing proposition; the larger the organization the longer it may take. Stay positive and keep moving forward with it. The results will speak for themselves.

    Other posts you may enjoy

    Share this post
    June 25th, 2008 · No comments No comments
  • If you live here in Central Florida, are in a tech or tech-related industry, and you haven’t heard about doterati yet, let me introduce you. doterati is a not-for-profit organization whose mission is, “to advance the Central Florida interactive marketing, media and technology community by serving as an association for professional development, education, community networking and overall inspiration for our digital society.” We are well down the road to doing just that. There are a lot of people involved including myself, Dan Kinchen, Mark Krupinski, Greg Rollett, and Tara Lamberson. There are also many advisors on board including Alex Rudloff. There was a lot of talk at first about Ted Murphy’s involvement and whether or not doterati was one of his ploys or a way to take advantage of local tech people. Thus far I haven’t seen that happening.

    The doterati focus group last night was great. We had a room packed with people from tech, marketing, and a student from Valencia, providing feedback on proposed plans for the web site, educational activities, and membership structure and benefits.

    As with anything local I urge you to get involved. We are in the formative stages and moving ahead at a rapid pace. Here’s some stats to show you how far we are after just six weeks:

    • 233 members
    • 14 groups with 188 members
    • 19 forum threads
    • 1400 “unique” visitors
    • 45+ events posted
    • 175 followers on Twitter

    If you aren’t yet a member join today and get involved. At the very least it will be a great way to meet other tech folks here in Central Florida as well as business people. If you have any questions post them here. Otherwise, I’ll see you there.


    View my page on doterati

    Random Posts

    Share this post
    June 19th, 2008 · No comments No comments
  • I was having lunch today with a new client that is interested in implementing scrum in their organization. They are a very large company where a single project can have five or more departments involved as stakeholders. They are not interested in turning on a switch and being 100% agile overnight. For a company such as this, they need to be more prudent in bringing scrum online. In addition, the move to scrum should be transparent to everyone outside of IT and software development. Thankfully the planets are in alignment for us and they have the perfect opportunity to use scrum: a project that needs to be completed, and a staff and higher-ups wanting to use scrum.

    Often times we look at a project as an all or nothing proposition. We do this with many other things including improving development practices and business processes. Introducing scrum does not have to be done in one large, sweeping move. I recommend against doing that. It is those instances where scrum is introduced too quickly, on too large of a scale, or in areas where scrum is not useful, that cause projects to fail and everyone blames scrum. That is akin to blaming a framework for scalability issues where the framework isn’t to blame, but rather the implementation.

    If you have a project or a small set of tasks where you can apply scrum use that as the test bed. You can even start using it without telling anyone. “Geez, how is Jim able to crank out so much stuff in such a short amount of time? I love seeing new stuff every couple of weeks.” Scrum. It’s great stuff; however, it is a paradigm shift for many. Don’t dive in too quickly lest you end up in shallow waters and bonk your head. Use it on a project, achieve a great success, and use that as proof that it can work. Then build on it.

    Other posts you may enjoy

    Share this post
    June 17th, 2008 · No comments No comments
  • I’m proud to be talking about Leveraging the Cloud with Ruby at the Ruby Hoedown this coming August. Ruby Hoedown is a regional Ruby conference held this year in Huntsville, Alabama. There is a great lineup of speakers and it should be a great time.

    I’ll be discussing cloud computing and showing rich code examples of how Ruby developers can use services such as Amazon Web Services to build highly scalable applications. Do you want to see something specific? If you’re attending Ruby Hoedown and would like to see something in particular leave a comment here. Register for the Ruby Hoedown today and I’ll see you in August!

    Random Posts

    Share this post
    June 16th, 2008 · No comments No comments
  • During my Agile talk at RailsConf 2008 I was asked if we turn down jobs. My answer was yes. Some clients can work within a scrum process, others cannot, and yet others you just want to stay away from. A follow-up question to that was how I know if we should turn down a project, what are the indicators that someone might be a bad fit for scrum or the company. My responses included:

    • The person has not invested any time up front to create any documentation listing what they want their site to do.
    • The person is asking for an estimate on a laundry list of features that they cannot explain the goals of (i.e they heard the stuff is cool and want a site to do all of it).
    • They are trying to rush into a project without much forethought (similar to #1 but with added urgency and increased danger of failure).
    • The client is non-technical and attempting to dictate application architecture.
    • No budget. While a budget isn’t always a necessity, it usually means that the person on the other end is fishing and doesn’t have funds yet available. This is more of a warning sign than a “turn down this project” sign since people sometimes go for funding once they know how much their project will cost.

    Note that I said “might” before, as some of the above can be handled through education. Chris pointed out a list of Software’s Classic Mistakes, some of which apply to turning down projects as well. The main ones that jump out at me are:

    • Overly optimistic schedules
    • Unrealistic expectations
    • Lack of project sponsorship
    • Lack of user involvement

    What are the “stay away from this one” signs that you look for?

    Other posts you may enjoy

    Share this post
    June 5th, 2008 · No comments No comments
  • We’re looking for an experienced Rails developer to join the ADS CREW here in Orlando, Florida or in Stillwater, Oklahoma. Check out the job description for all the details and to apply. If you’re here in Orlando give me a call at 321-274-4684. We look forward to you joining us at ADS.

    Other posts you may enjoy

    Share this post
    June 4th, 2008 · No comments No comments