Today was my first day at a new job. I knew much of the people who works there, so culture wasn’t a real breakthrough for me.

So, I arrived in the office by 11:00 am, said ‘Hi’ to my friends (it’s really good to be back, guys), and by 1 pm (one lunch hour included) I was ready to work. I had it all installed, permissions given on the projects I would be working and a thin documentation ready to be read.

I spent another hour or two reading and talking to people who were on my project and started delivering real code. That means I had barely 3 hours of environment setup, organization setup, chair adjusting, etc and was GETTING THINGS DONE. When I began thinking about it, I was totally amazed.

This is the kind of organization mindset I think brings this kind of result:

  • Leave development stuff to development people: permissions, servers, environment, documentation, everything; If they’re smart, they will know what to do. If they’re not, don’t hire them :).
  • Plan! Plan to have everything needed when people arrive. Map your risks, act accordingly when needed. Don’t overplan, though: there is stuff that is unpredictable;
  • Don’t assume risks you don’t have to: If you don’t have to micromanage something, don’t do it. Why would a company want to run an e-mail server? Google Apps delivers it all! Calendar, Docs, Sites, Groups, Mail! With GMail user interface and functionalities!

That being, I couldn’t have had a more productive first day at any new job. It was a marvelous experience, and I am looking forward to improving it even further.

What about you? Any good/bad situations on a new company set up you would like to share? Comment!


Google has just launched Jarlsberg – A Web application that generates web applications full of vulnerabilities. Jarlsberg is a great idea for people who work with web development/security. Just access to learn more about ir. For the impatient: access and try to find some exploits!!

I’ll give it a try and will write more about it later.

I’m directly from brhackday, SP! The event is amazing so far, I’m sure I’ll have plenty of stuff to blog on the next days (YQL is amazing, Yahoo! is getting more social, everything is very exciting around here).

But I want to talk about the project we chose to implement here for the competition (Thanks Leonardo and Gustavo, you’re being great so far! Hope we can make a great project out of this):

We’ll cross routes (from and to anywhere anywhere) with traffic and weather information (from the official traffic agencies) in São Paulo, to help users choose what route to take when using google maps.

So, what do you think? Will it be useful for you guys? Have already seen anything like this?? Any extra feature you would like to have in this system?

Any feedback will be greatly appreciated!

EDIT: There is a traffic layer on google maps, and it works pretty well. Don’t know why we haven’t seen it before, but it showed up here just before we begin the work. Actually, I think they used the exactly same structure we intended to use. Anyway, we dropped this project to work on a more useful one.

I just received my registration confirmation to Yahoo! Open Hack Day Brazil 2010! I have a lot to study now, so you should expect to hear a lot about Yahoo! services (YQL, YAP, YUI3, Meme, etc) around here in the next weeks!

If you haven’t registered yourself yet, there’s still time! Go to and sign up!

Anyone else going? Any Yahoo! APIs you have experience and would like to share? Do so in the comments!

Last week, I gave a lecture on Basic .NET Development (focusing on C# and ASP.NET). To say the truth, I can’t count myself as an expert on these technologies (actually, I’m not an expert in any particular technology).

At the end of the course, I asked the students to fill a fairly simple form, which asked them what were the three worst problems and the three best things they experienced during the class. I decided to post it here because it can be useful for people preparing lectures who happen to stumble with this page. Helps to say: the form was anonymous.  The results (only for the three worst problems) are categorized below:

.NET Basic Development Course Feedback

.NET Basic Development Course Feedback (Bad Stuff)

Click here for the full responses (portuguese only). This link also includes the positive feedback.

Some interesting comments:

  • Short Timespan: That’s 100% my fault. Maybe I tried to squeeze as much content as I could in the fixed timespan we got. Doing this, you will always give people the feeling that you are out of time, and so are they.
  • Physical Infrastructure: If you are to prepare a course, don’t underestimate this. People don’t like to stay in an uncomfortable chair with wires all around. And this WILL affect the quality of the attention they will be able to pay on you.
  • The Technology Sucks: We encoutered some bugs when dealing with some examples/exercises and had to get workarounds for them. Truth is every technology/programming language/software have bugs.
  • Software Infrastructue: Some (few) machines were not ready for some steps of the course.

I suppose there aren’t any comments regarding the instructor because the instructor asked for the feedback :).

The interesting stuff to notice here is : If I had spent more time(4 hours would be more than enough) preparing everything to improve the quality of the environment we spent together, I could get 70% of this stuff solved. They were simple, easy-to-notice, easy-to-solve issues.

So, the lesson I learned was: Get yourself involved in every step of the course. Prepare the environment yourself (or at least check it early). Check the software. Get yourself prepared. It’s not so different from developing software, is it? If you let any aspect get out of control, it will hunt you and make you regret disregarding it.

Also, always get feedback. I spent 3 minutes to set up the google form to enable the students to answer the survey. Actually, it’s so simple it makes you feel bad about thinking of using anything else. And remember: The only thing worse than bad stuff you do is bad stuff you do and don’t know is bad, because you’ll do it again.

So, want to talk about situations you got feedback (class-related or not) that was useful later? Comment below.

killer gama

July 10, 2009

Today I received a visit in this blog for someone who was looking for ‘killer gama’ on a search engine.

Please, don’t kill gama. 🙂

Press FAIL

July 10, 2009

Can the press stop Google (and other news aggregators) from copying/indexing their news? They probably can. Sometime ago, major press companies begun to complaint about Google showing some of their texts (mainly headlines and a summary), at both google search AND google news.

But this will drive them crazy: People are making ‘press releases’ on their own. Brazilian soccer is beginning to move towards this. Vanderlei Luxemburgo,  former Real Madrid manager, announced he was fired before anyone could announce it. On twitter. Now Belluzo, Palmeiras president, announced he couldn’t get to an agreement with Muricy Ramalho, also on twitter(pt/BR).

As I already told some friends, the press as we know will have to reinvent itself in order to remain profitable. Become less pure-factual, more analyzer (eg.: After Luxemburgo being fired, some articles could be written about the possibilities for his future). People are begginning to know how to tell their own stories (or their own version), and this is one step further in the direction of  a less dumb and manipulating press.