Working With Rails

Actualizar JDK 1.6 en Mac OS X

/System/Library/Frameworks/JavaVM.framework/Versions

it affects the system globally, it changes the system from how Apple shipped it (things under /System are Apple managed), and it can cause updates to fail and/or have unintended side effects.

weemac:Versions jenaiz$ ls -la
total 56
drwxr-xr-x 14 root wheel 476 15 jul 08:59 .
drwxr-xr-x 11 root wheel 374 4 jul 08:08 ..
lrwxr-xr-x 1 root wheel 5 7 may 20:39 1.3 -> 1.3.1
drwxr-xr-x 3 root wheel 102 29 sep 2007 1.3.1
lrwxr-xr-x 1 root wheel 5 21 oct 2007 1.4 -> 1.4.2
lrwxr-xr-x 1 root wheel 3 7 may 20:39 1.4.1 -> 1.4
drwxr-xr-x 8 root wheel 272 21 oct 2007 1.4.2
lrwxr-xr-x 1 root wheel 5 21 oct 2007 1.5 -> 1.5.0
drwxr-xr-x 8 root wheel 272 21 oct 2007 1.5.0
lrwxr-xr-x 1 root wheel 5 7 may 20:39 1.6 -> 1.6.0
drwxr-xr-x 8 root wheel 272 7 may 20:39 1.6.0
drwxr-xr-x 8 root wheel 272 7 may 20:40 A
lrwxr-xr-x 1 root wheel 1 15 jul 08:57 Current -> A
lrwxr-xr-x 1 root wheel 3 15 jul 08:59 CurrentJDK -> 1.5

ln -hfs 1.6 Current
y
ln -hfs 1.6 CurrentJDK

- Sólo soporta 64 bits: adios a los applets en Safari.
- No hay soporte para Cocoa: aplicaciones como Cyberdurk dejarán de funcionar. Esto no sólo significa que no podamos tener look&feel de Mac OS sino que también perderemos algunas de las utilidades tales, como poder usar Growl como sistema de notificación, por ejemplo.

iPhone on Rails

Day six and still going strong …

8:36pm just ate brocolli with a strange sauce on it that caused me to make a face

Make that broccoli. Damn you, obscurely-spelled vegetables!

Links for 2008-07-15 [del.icio.us]

• Doctor Horrible’s Sing-Along Blog
• Unsuspicious Chain Shaw Decapitation!?
• 10 MORE Must-try exotic fruits
• Rock n Roll McDonalds
• Daruma-otoshi skyscraper demolition

Links for 2008-07-15 [del.icio.us]

• Will Google use Jaiku to kill Twitter?
  An interesting set of maybe's involving Google's purchase of Jaiku last year
• bit.ly, a simple url shortener
  Seems very neat, with it's own API and some interesting tracking and caching features.
• Twitter Search
  See what the world is doing — right now.

Links for 2008-07-15 [del.icio.us]

• .htaccess password generator
• RailsConf: Stefan Kaes - Rails Performance
  Stefan starts by citing a factor of 4-5 improvement in performance in Rails over the last year.
• DISQUS | Turn Blog Comments into a Webwide Discussion with a Powerful Comment System
  comments for weblogs (tumblr)
• 10 Examples of Beautiful CSS Typography and how they did it…
• 39 dicas de perfomance PHP
• Aintablog: Open Source Tumblogging/Feed Aggregation with Ruby on Rails
• ZigZig Software - ZigVersion
  ZigVersion : Subversion Made Easy
• Demos | CSS Decorative Gallery
• Create a Slick iPhone/Mobile Interface from any RSS Feed

Links for 2008-07-15 [del.icio.us]

• 再論《Milk》與《Tea》的日式中文句法 - 知日部屋 - 哈日反日不如知日

rush 0.4

rush 0.4 released. Some changes:

• Rush::Box#processes returns a ProcessSet, for syntax like this:

processes.filter(:cmdline => /mongrel_rails/).kill

• Daemonize shell commands: bash 'some_daemon', :background => true

• Pass args to rush on the command line to execute a one-off, like this:

$ rush 'processes.filter(:command => "ruby")'

Details and rdocs.

Asterisks are shady. Any time I see “*” in an ad, I...

Transparência

Lick My Love Pump (via TSOTLOTU)

Factory Girl!

Last month, factory_girl was featured in the RailsEnvy podcast. factory_girl is one of the best things that happened to my Rails TDD/BDD life. It's the only other thing I use with rspec and rspec-rails, though I'm pretty open, so suggestions to make making tests easier are very much welcome. The one con is that factory_girl is tied to ActiveRecord, but it's not really an issue for me because all my non-personal projects use AR. If you are still using fixtures, take a look at factory_girl. It's really nice. Anyway...

factory_girl has a nice feature that ...

Mingus: Charles Mingus Cat Toilet Training Program

[Music] coldplay - viva la vida

Will a Space Startup Be the Future Google? (via Google Reader)

Jabber Filaments Blog: Presence During Times of Crisis (via Google Reader)

Double Shot #249

Trying out mongrel instead of thin

Building a proof of concept landmark app for communication with Second Life in Sinatra.

Should I accept or not?

My follow through. . .

Links do dia 15/07/2008

Servoy 4.0 goes final

(posted by cardioid) zoom

Unavailable Domain Names and Their Alternatives

Noisy Fan on the ThinkPad X300

One thing that got annoying with my new ThinkPad X300 was the fan seemed to run at full speed almost all the time. I’m running Ubuntu 8.04 Hardy.

Once again, ThinkWiki came to the rescue in their article on How to control the fan speed.

Using my new found knowledge, I wrote a little script that made it easy to control the fan speed:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

#!/bin/sh                           
#
# Control fan on a ThinkPad.
#
# Be sure to add the following to /etc/modprobe.d/options:
#
#    options thinkpad_acpi fan_control=1
#
# and reboot, before using this script.

usage() {
  echo "$0 <level> (<level> is 0-7, auto, disengaged, full-speed)"
  exit
}

if [ -z "$1" ]; then
  usage
  exit
fi

sudo sh -c "echo level $1 > /proc/acpi/ibm/fan"

Be sure to modify your /etc/modprobe.d/options as specified in the comments.

Then just run:

$ ./fan.sh 2

for a much quieter fan (low speed) that doesn’t seem to sacrifice cooling when coding (vi, Firefox, mutt, and Gnome is what I run mainly).

You’ll want to switch it back to ‘auto’ if you’re gonna do anything processor intensive.

Enjoy!

Fix for Noisy Fan on the ThinkPad X300

One thing that got annoying with my new ThinkPad X300 was the fan seemed to run at full speed almost all the time. I’m running Ubuntu 8.04 Hardy.

Once again, ThinkWiki came to the rescue in their article on How to control the fan speed.

Using my new found knowledge, I wrote a little script that made it easy to control the fan speed:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

#!/bin/sh                           
#
# Control fan on a ThinkPad.
#
# Be sure to add the following to /etc/modprobe.d/options:
#
#    options thinkpad_acpi fan_control=1
#
# and reboot, before using this script.

usage() {
  echo "$0 <level> (<level> is 0-7, auto, disengaged, full-speed)"
  exit
}

if [ -z "$1" ]; then
  usage
  exit
fi

sudo sh -c "echo level $1 > /proc/acpi/ibm/fan"

Be sure to modify your /etc/modprobe.d/options as specified in the comments.

Then just run:

$ ./fan.sh 2

for a much quieter fan (low speed) that doesn’t seem to sacrifice cooling when coding (vi, Firefox, mutt, and Gnome is what I run mainly).

You’ll want to switch it back to ‘auto’ if you’re gonna do anything processor intensive.

Enjoy!

Rarities, B-Sides & Other Stuff, Vol. 2 by Multiple Artists (Music)

Rarities, B-Sides & Other Stuff, Vol. 2 by Multiple Artists (Music)

Rarities, B-Sides & Other Stuff, Vol. 2 by Multiple Artists (Music)

Rarities, B-Sides & Other Stuff, Vol. 2 by Multiple Artists (Music)

Protegendo projetos com o .htaccess

SSH Config Aliases

Do websites need to look exactly the same in every browser?

About OneAgileTeam - We heart "Getting Real", as one native form of Agile Development

Agile Software Development is a style of software development which has been gaining popularity. According to a former colleague, upwards of 10% of corporate software development projects in North America are now conducted this style. Agile Development (hereafter Agile) is to beat the long lasting development style called Water Fall Model (hereafter WF).

Suppose you want to build a dream house. With WF, you hire an architect who designs all the elements of the house . You then move onto the actual building stage (i.e. foundation -> framing -> plumbing/wiring -> walling -> flooring etc). Once you start, you are relatively locked in to the plans. You cannot abruptly change things and decide that a faucet should be installed in a completely different location. Well, you could, but it would be very costly. In this model, the longer things continue to be built, the more unexpectedly things may turn out. And it may not be at all like you imagined. Within the WF model, once a project is in motion, and the "water is flowing," you cannot really go back "upstream" (i.e. the design stage). Instead you must wait for the design to run it's course, and then pay for it. Once the project is in motion you don't have much control.

Agile however addresses the above problems. Agile developers always work with the client step-by-step from the design stage to the flooring. Agile developers in fact welcome changes to the plans so they can ultimately build a better home. Agile developers always try to show what the actual finished product will be like along the way while working, or in the form of a mock-up made to scale at least. This way the client can confirm what the finished product will look like before it is completed. In a nutshell, Agile's strength is that it permits change derived from mutual conversation with clients throughout the development process.

One very specific and opinionated approach of applying Agile Software Development to create web products efficiently is called Getting Real. Created by Chicago-based company 37signals, Getting Real utilizes Agile Development to build the best web product possible. One of the greatest challenges to developing a successful web product is the fact that you have not met your potential users in person. Also, potential users are quite diverse in their needs and internet savvy. So, you need to explore what would be the best features and interface for millions of different users, which is pretty challenging to do at the beginning of a project. WF doesn't work here because it requires a plan for the product to be set before the construction can begin. But what is needed is exploration.

Getting Real is quite agile, in the sense that you can create a product step by step, and in each step you take into account client feedback and observes customer behavior. From there you can adjust the product to implement the most recent feedback. If it doesn't work, you can easily go back to the previous step. This rewinding in a product can be confusing to clients at times, but this can be avoided if the changes (or "tweaks" as we call it) is small enough.

37signals' project management product, Basecamp, which I recently started using for coordinating this blogging project with my proof reader Emily (whom I utilize as I am not a native English speaker), was developed with Getting Real. 37signals created Basecamp five years ago. Currently, they have more than 2 million users, and they still continue to change and tweak the product little by little fairly frequently (sometimes weekly, or even daily). It seems that Emily understood how to use Basecamp almost instantaneously. In fact, she did not even ask me any questions about how to use it, and she figured out very quickly what can and cannot be done with the built-in wiki called Writeboard. For several reasons, we are drafting actual blog posts on Google Docs and doing the rest (like To-Do management and messaging) on Basecamp. The point I am making is not that that there is anything wrong with Writeboard, but that she had to spend only a few minutes exploring Basecamp to grasp what it could and couldn't do. From there it was easy to make a decision—that we should just use Google Docs for editing my blog drafts. It is very easy to understand and therefore made it very quick to reach a decision. We did not have to spend hours figuring out how to do this and that. 37signals has spent five Getting Real years slowly crafting Basecamp in to the outstanding work of art that it is, and as a result it is easy to use, intuitive, and requires no manuals or training.

While Agile development may seem like a logical model, it is actually rare to see it implemented in the real world. I'm sure you have experienced this already. For example, when you call customer service at a company to complain about something, the customer service reps seem like they are listening to your concerns, but they are probably just being polite. If the service reps were working in an agile manner on a web product, they would need to report your complaint to their boss, who would then compile a list of all complaints and once a month report to the VP of Engineering. The VP of Engineering would then prioritize the complaints and pass the highest priority items on to the developers. In this case there are several steps or filters that your complaint must pass through to go from your lips to the ears of the guys actually developing the project. Although the developers try to be agile, there are too many steps in the process. This is what happens in most businesses. Getting Real, however recognizes this problem and recommends doing everything as a very small team. For example a team consisting of myself acting both as a core developer customer support staff at the same time so as to avoid unnecessary steps in between input and action.

So my company OneAgileTeam remains small, and applies the Getting Real approach wherever applicable. We strive to fully understand both identified and unidentified business needs and fulfill them in the most agile, simple and timely manner possible. And by timely, I mean a few of hours to a few weeks at the most. This is the main goal at OneAgileTeam.

Live for Fame

Live for Fame

Alienware Micro-site e 3D

E o motivo deste post ?? exatamente esse, marketing. A um certo tempo a empresa v??em criando curiosidade com uma campanha interessante onde s??o lan??adas algumas pistas sobre alguma nova inven????o que ser?? lan??ada. Hoje eles lan??aram um micro-site feito em Flash, mas o que chama aten????o n??o ?? o micro-site ou o trabalho em Flash mas sim o trabalho em 3D, magn??fico que chega a confundir o digital com realidade.

Para quem gosta de 3D vale apena conferir: Site

Colocando mais Ruby na minha vida

I love the way this code looks, part of whatsgayer.com

Rails layouts

URL helpers

The Mapping of URLs to Controller Actions

links for 2008-07-16

Slayers Revolution (season 4) …