Lateral Development @lateraldevelopment - Tumblr Blog

An overview of why full-stack JavaScript might be right for you and how it works its magic.

This entry is part 1 of 4 in the series A Guide to Ruby CollectionsA Guide to Ruby CollectionsA Guide to Ruby Collections, Part I: ArraysA Guide to Ruby Collections, II: Hashes, Sets, and RangesA Guide to Ruby Collections III: Enumerable and EnumeratorA Guide to Ruby Collections IV: Tips and Tricks Programming consists largely of [&]

Awesome Post on Ruby Collections

Good rules for implementing Test Driven Development as if you meant it

http://evan.tiggerpalace.com/articles/2012/10/06/the-dcamp-manifesto/

At the end of September 2013, I'll be attending Ruby Camp 2013. I missed last year's so I'm really pumped up about it!

The idea is in essence pretty simple: Get a 78 group of Ruby developers into a camp site where people have sessions to discuss different subjects.

If you notice the keyword above is: Sessions. This is different to the typical Developers Conference that follows the classroom model: Someones gets in front of every one for say 45 mins and talks about some topic with almost little to no back and forward interaction with the audience (only during the QA time)

Don't get me wrong I like conferences too (Just went a couple of months ago to Ruby Nation and I'm going to Ruby Conf 2013 in Miami Yeahh you know... Welcome to Miami Bienvenido a MIami!) However this is a "conference" from a different point of view, no one is really in front, we are all the front. This reminds me to the analogy of the book: "The Spider and the Starfish" (read it, it's really good) Basically the idea is that if you cut the head of a spider it dies, but if you cut a piece of a starfish, that piece will regenerate. In Other words, no one really is the director of the Ruby DCamp orchestra, all people are in charge of make this a success and great experience for everyone.

Long life to Ruby Dcamp, long life to the King Ruby.

Typography Basics for Developers by Rachel Shillcock. Typography is a fundamental element in any design that you work on. The main reason we have websites in the first place is to display information, and for that information to be consumed by users who come across it. While there may be many other elements to a website, at the core is content. That content needs to be easily read, digested, understood and having a solid typographic base will only help with that.

This is a great article from Kalzumeus Blog on what are your options if you decide not to upgrade your Rails 2.3.x apps. Check it out it worth a read and it has some really good tips.

But the best tip of course is: Upgrade your Rails Apps!

CSS3Generator is a great tool that allows you to get CSS3 cross browser code for different common tasks: Rounded Corners, Box & Text Shadow and more. It's really simple to use and really useful, check it out.

Last Monday April 15th I went to the first Rails meetup from the Northern Virginia Web Development User Group, which happened at Booz Allen Hamilton near Tysons Corner in VA. The presenter was John Athayde from LivingSocial and the talk was about Rails views.

It was a really interesting talk with many do's, dont's and best practices for keeping Rails view clean and elegant. It was not about: "Ohh.. let's use HAML to clean up our erb's" It was more about the 7 sins (e.g., Don't user model logic inside .erb files) and 10 commandments to clean up your views (e.g., Use presenters when necessary)

Really cool talk, check the slides here: https://speakerdeck.com/boboroshi/the-rails-view-the-junk-drawer-grows-up-triangle-dot-rb-version

Uninstall MySQL on Mac OSX Mountain Lion

If you need to get rid of MySQL (issues/nightmares while trying to install the mysql gem anyone?) you need to do the following:

Make a backup of your database data

Stop MySQL if it's runinng

Run this commands in your terminal:

sudo rm /usr/local/mysql

sudo rm -rf /usr/local/mysql*

sudo rm -rf /Library/StartupItems/MySQLCOM

sudo rm -rf /Library/PreferencePanes/My*

rm -rf ~/Library/PreferencePanes/My*

sudo rm -rf /Library/Receipts/mysql*

sudo rm -rf /Library/Receipts/MySQL*

Finally edit the /etc/hostconfig file and remove the line MYSQLCOM=-YES-

Done.

P.S. I don't know why there isn't a clean way to uninstall it, didn't find one.

If you ever get a weird mysql error when installing the mysql gem on Rails

If you try to install the mysql gem and you get stuck with an error saying something like:

library not found for -lmysqlclient

You need to install the gem telling it to use your mysql_config file:

sudo env ARCHFLAGS="-arch x86_64" gem install mysql -- --with-mysql-config=/usr/local/mysql_folder/bin/mysql_config

(Update your mysql_folder as appropriate)

The ARCHFLAGS value it's needed if you are running Mac OS X in 64 bits (which is more likely the case if you are running snow Leopard or newer)

That will save your bacon while installing mysql gem.

Note: If you are still having strange errors && you are on Mac OS X, make sure you update your XCode Version and then install the developer tools

A pretty good tutorial (both written and video available) on how to use multiple tools that interact with github to empower your software collaboration experience.

Really cool and clear presentation on the differences and similitudes of Python and Ruby.

Agile Product Ownership in a Nusthell: Any person involved in Software development cycly need to watch and embrace this video

Suggested Recipe for TDD/BDD in Rails 3.x

The following is an opinionated process for setting up a Rails app for TDD/BDD testing using: RSpec, Capybara & Guard

Create new rails app with the -T flag (this will skip Test Unit)

Add the following gems to your gemfile group :development, :test do gem "rspec-rails" gem "capybara" gem "guard-rspec" end

Run: bundle install

Run: rails g rspec:install

Run: guard init rspec

Optional:

Install the rb-fsevent gem (if you are on a Mac and want Growl style notifications) with: gem install rb-fsevent

Install Spork gem to speed up your tests

Install guard-livereload to view changes on the fly

3 Laws of TDD (Test Driven Development)

You may not write production code until you have written a failing unit test.

You may not write more of a unit test than is sufficient to fail, and not compiling is failing

You may not write more production code than is sufficient to pass the current failing test

Source: http://www.slideshare.net/tyler4long/rails-automatic-test-driven-development

Git Tips from the Pros

Here is a set of cool git tips that will help you tons on your current git workflow. I really like the alias section since I added a couple of aliases to my .gitconfig file, that I'm sure will save a lot of time in the long run.

http://net.tutsplus.com/tutorials/tools-and-tips/git-tips-from-the-pros

A great summary of the most important principles to keep in mind while developing in OOP.

Trending Blogs

Recently Viewed Blogs

Lateral Development