Someone had to to it… and someone did! The FPS gender finaly comes to the Nintendo DS. And what’s great about it? Nothing… What’s bad about it? Well… most of it…

The graphics are just horrible ( you can’t ask much… ) and the gameplay is just like like Quake or Doom! Oh well, they did something so… good for them…

I think you can fully trust this comparion. I admit that I hate Microsoft and Mr. Bill Gates ( and Windows ) but Xbox360 is an exellent and awsome console. GO GET IT! :) But, honelsty, in this game, the difference is not much so… go, go Sony PS3…

Choose your poison!

So, this “game” has been surrounding the Internet for a wile, so I decided to give it a try!

After I registered, under the name of Don Kozlov ( original right? ), and installed it’s client I logged in. Then… it crashed, URRAY, I tried to restart the game, download it again, reboot my MAC but nothing seamed to work. After many tries it decided to work ( don’t ask me why ) and I finally got into the universe of SL.

I checked the interface, which is very good and I liked it a lot, and the Inventory thing, which was even more awesome, and the thing that called me attention in the 1st place was the Script category! Why? Because I like programming  of course! I created a sample script but I didn’t know what to do with it or how to code it ( I tought it was C++ but, nah… ).

After I saw all those things I went to a sample house. And that sample house gave me a object ( I think it’s called “object” ) that gave me the ability to create a house of my own. To do so I had to get and island, which coasted money. No way I was going to buy it, money for a game? You kidding me?

So, I zoomed out to see the full starting area ( which is an island ) and it is pretty nice! Then, I saw some doors all over the island that said: “Enter Second Life”, so I concluded that that was the actual “really world” ( if you can call it that way ).

And, finally, comes the best part. The thing that all the gamers like! LAGGGGGGGGGG, and lots of it! The thing they call the World is full of lagg ( I wouldn’t want to live in a word full of lagg! ). So, the 1st thing that came to my head was to go up in the sky ( yes, you can fly ), up in the clouds like Superman! You can’t have lagg in the sky right? Of course you can’t, but crashes you can!

When I was really close to hit the cloud the game just crashed with a error that reminded me of M$’s Windows ( the Send and Don’t Send error report thing ).

Oh, it was fantastic, so fantastic that I just removed the game after that!

And this was my awesome experience with Second Life for MAC.

Coming today for crapalollics, crashaollics and laggaollics!

Windows Mobile 6.5

19 de Fevereiro de 2009

Microsoft a few days ago anounced that Windows Mobile 7 is still a year away, but unstill then they’ll launch Win. Mob. 6.5 ( not a very original name ).

While Steve Ballmer was to busy talking about burning, smacking and crushing Google’s Android ( good luck with that Microsoft… ) he confirmed that Windows Mobile 6.5 that Motorola was talking about was real!

He didn’t say much but he did say that it will have a new and better GUI and that it will have an implementation of Zune just like the iPhone as of the iPod! ( Windows Media Player sucked anyway… )

Let’s hope that this time Microsoft gets it right. Probably not, they always manage to screw things up…

Google Friend Connect

15 de Fevereiro de 2009

Have you eared of Google Friend Connect? I’ve seen a video of it yesterday and I didn’t taught it was a big deal. Today I’ve been in several websites that now have Google Friend Connect and didn’t have before!

What is it? Well, it’s a way that peaple can reach each other by the websites they visit. So you see that it’s not a regular social app like Twitter and such.

It still doesn’t sound big deal but by what they’ve put on their website I might try it! What do you think of it? Should everyone start using it? It just sucks and it’s a waste of space? Send me an e-mail with your reasons to like or dislike it.

Website:

“Google Friend Connect means more people engaging more deeply with your website — and with each other.

Enrich your site
Choose engaging social features from a catalog of gadgets by Google and the OpenSocial developer community.

Attract more visitors
Your users can easily invite friends from social networks and contact lists to visit and join your site.

No programming whatsoever
Just copy and paste a few snippets of code into your site, and Friend Connect does the rest.”

YouTube – Not that bad after all!

12 de Fevereiro de 2009

So after I had that anoying problem with YouTube ( check my previous post ) I finally got it!

I was using the standart uploader but I saw a button telling me to use the Beta Uploader in the end of the page.

It was fantastic, it’s much faster and it gives you a progress bar so that you can get an idea of how many time is remaning to finish the upload.

It’s awsome, try it!

YouTube – The Revolution Has Began

11 de Fevereiro de 2009

So, I finally started to upload videos to my YouTube channel.

I sent one ( Yey! ) and it didn’t took to long but the next ones… don’t tell me about it!

YouTube just started to take “hours” to send videos!

I don’t know what to do! :)

If you know how to make it faster please tell me at pwnedpt@gmail.com.

Anyway, check out My Channel.

TextMate Post

7 de Fevereiro de 2009

So, what’s the point of this post?

Well, I’m posting it from TextMate!

I found out this feature in the TextMate website under “Videos”

Pretty cool, and it’s almost all automated!

Check it out: http://macromates.com/screencast/blogging_take_two.mov

Mac Developer

7 de Fevereiro de 2009

So, I just found a beta testing website!

It’s called MacDeveloper and in there there are some known projects such has Path Finder and Fetch!

If your informations turn out to be useful for the developers they may get you some money and a free licence for the program you are testing!

Sign Up! You won’t regret it!

Beta Testing

7 de Fevereiro de 2009

Here are a few tips for running a beta test of a software product intended for large audiences — what I call “shrinkwrap“. These apply for commercial or open source projects; I don’t care whether you get paid in cash, eyeballs, or peer recognition, but I’m focused on products for lots of users, not internal IT projects.

  1. Open betas don’t work. You either get too many testers (think Netscape) in which case you can’t get good data from the testers, or too few reports from the existing testers.
  2. The best way to get a beta tester to send you feedback is to appeal to their psychological need to be consistent. You need to get them to say that they will send you feedback, or, even better, apply to be in the beta testing program. Once they have taken some positive action such as filling out an application and checking the box that says “I agree to send feedback and bug reports promptly,” many more people will do so in order to be consistent.
  3. Don’t think you can get through a full beta cycle in less than eight to ten weeks. I’ve tried; lord help me, it just can’t be done.
  4. Don’t expect to release new builds to beta testers more than once every two weeks. I’ve tried; lord help me, it just can’t be done.
  5. Don’t plan a beta with fewer than four releases. I haven’t tried that because it was so obviously not going to work!
  6. If you add a feature, even a small one, during the beta process, the clock goes back to the beginning of the eight weeks and you need another 3-4 releases. One of the biggest mistakes I ever made was adding some whitespace-preserving code to CityDesk 2.0 towards the end of the beta cycle which had some, shall we say, unexpected side effects that a longer beta would have fleshed out.
  7. Even if you have an application process, only about one in five people will send you feedback anyway.
  8. We have a policy of giving a free copy of the software to anyone who sends any feedback, positive, negative, whatever. But people who don’t send us anything don’t get a free copy at the end of the beta.
  9. The minimum number of serious testers you need (i.e., people who send you three page summaries of their experience) is probably about 100. If you’re a one-person shop, that’s all the feedback you can handle. If you have a team of testers or beta managers, try to get 100 serious testers for every employee that is available to handle feedback.
  10. Even if you have an application process, only one out of five testers is really going to try the product and send you feedback. So, for example, if you have a QA department with 3 testers, you should approve 1500 beta applications to get 300 serious testers. Fewer than this and you won’t hear everything. More than this and you’ll be deluged with repeated feedback.
  11. Most beta testers will try out the program when they first get it, and then lose interest. They are not going to be interested in retesting it every time you drop them another build unless they really start using the program every day, which is unlikely for most people. Therefore, stagger the releases. Split your beta population into four groups and each new release, add another group that gets the software, so there are new beta testers for each milestone.
  12. Don’t confuse a technical beta with a marketing beta. I’ve been talking about technical betas, here, in which the goal is to find bugs and get last-minute feedback. Marketing betas are prerelease versions of the software given to the press, to big customers, and to the guy who is going to write the Dummies book that has to appear on the same day as the product. With marketing betas you don’t expect to get feedback (although the people who write the books are likely to give you copious feedback no matter what you do, and if you ignore it, it will be cut and pasted into their book).

By Joel Spolsky

Seguir

Get every new post delivered to your Inbox.