nickh

Switzerland has NOT decided to "end secret bank accounts".

From a BBC News article:

"while it will now abide by international rules on bank data sharing, it said it would only respond to "concrete and justified" requests." http://news.bbc.co.uk/2/hi/business/7941717.stm

I'm skeptical about the audio quality, because even small amounts of packet loss and latency can wreck havoc on VoIP calls.

However, even if Zer01's service doesn't live up to its claims, it's a step in the right direction. North America needs more companies striving towards this type of service.

In my experience, there's a "sweet spot" for how much functionality a method "should" have.

If a method is "too short", it: * may result in methodA calling methodB calling etc., increasing complexity; * may not be readily apparent how it fits in to the problem that's being solved.

If a method is "too long", its: * complexity increases; * ease of testing decreases; * frequency of reuse decreases.

Obviously, some methods have little functionality, and thus require very few lines. For the majority of the other methods, though, I tend to keep them below 25 lines. If a method grows past 15 lines, I examine it to see if there's any functionality that feels like it should be broken out into a separate method.

> Do a Good Thing today: convince a friend never to pay for recorded music again.

If you do that, how do you plan on showing support for artists whose works you enjoy?

I suggest you start by improving the marketing of Rainbow Ninja on its own website. As alaskamiller said, an explanation of what the game is/does is a good starting point. Throw some screenshots up there, too. Maybe even a video. Users shouldn't have to search around to find out what the game's premise is, and what the gameplay is like.

Also, I may be a stickler for grammar, but I'm sure there are others who notice that "To celebrate the launch of our RainbowNinja iPhone Video Game." isn't a proper sentence, and has incorrect capitalisation. Get a few trusted people to proofread your copy before publishing it.

Great idea, mate. Enabling people to embed the upload form into their site is awesome.

I have one suggestion. I watched the "How It Works" video, which was informative, though a bit slow-paced. However, the soundtrack could really be improved. That looping Windows chime forced me to mute the video =P

There's also parkour: http://en.wikipedia.org/wiki/Parkour

It's a hell of a lot of fun, keeps you in shape, gets you outside and away from the computer, etc.

Pretty much every major city, and many smaller cities, have local parkour communities. Just search Google for "parkour MY_CITY".

And if you live in Toronto, Canada, come join us at pkto.ca

I use gandi.net for my .com, .org and .net domains. Their interface is great, but I can't comment on their support because I've never had a problem =P

For .ca domains, I use easydns.com .

--- Short Version:

Stop actively thinking about names. Let your subconscious chug away on the topic for a while; at least for a couple of weeks, if not for a couple of months. Eventually, something will bubble up that you like.

--- Long Version:

Just two days ago, I decided on a name for my startup company and app/website. It took me about 6 months, though. For the first 4 months, I was actively thinking about names, writing BASH, Ruby and Perl scripts to generate names, using websites like makewords.com and others, etc. Every name that I made either sucked, or was taken. That was pretty disheartening.

Eventually, I let the task of finding a name slip into the background. Every now and then, a name would bubble up from my subconscious, I'd ponder it for a few minutes, then write it down.

Then two nights ago, after a long coding session, I went to bed. I was tossing and turning, with my mind wandering all over the app that I'm creating. During that time, I started thinking about dinosaurs.

Say what?..I like dinos. They're pretty awesome!

After lying in bed for about 2 hours, thinking about how to integrate dinosaurs into my app, I got up and did a few whois searches. Lo and behold, most of the dino-related names that I'd just thought of were available!

What I'm trying to say is that naming is a very ephemeral process. You can spend 10 full days on the task, and still come out with nothing [that you like]. So if you're having trouble choosing a name, forget about it for a while. It'll still be in your mind, just at the back.

On the home page, it says "lighter is more popular, darker is less." That's the inverse of what people expect. I recommend switching it around.

If the programmer has "carte blanche", why are you restricting them to PHP?

Good on you, mate. I just watched the Dabbleboard video, and was really impressed with what you've created!

Great feedback guys. Thanks.

I'm going to go the route of virtual machines, and give Multipe IE a shot so that I only need one Windows VM. After that, I think I'll start writing up some scripts (text, not code) to follow, step-by-step, to check various functionality.

Also, webrat (http://github.com/brynary/webrat) has received a lot of commendations on the rspec-users mailing list, so I'm definitely going to give that a whirl.

In the past, I've used stunnel for encrypting server-to-server communications. It's very easy to setup.

Check to see if the site that you're considering scraping has any sort of "terms and conditions", "terms of use", "legals", etc page. If it does, read that page in detail. If it doesn't, ask the site for permission to scrape.

If the site doesn't have one of those pages and you don't ask for permission, you're not only putting yourself in danger of legal action, but you're also depending on a data source that isn't reliable.

Remember, it'd only be a matter of time before they notice you scraping, and take measures to stop it.