Posts by Marcelo Park

Hello friends!

We are excited to present our new visual identity and website.

We felt that it was time to give a step further into the way people see us. Our previous visual identity was very dense and the logo had a very strong appeal to “engineering”. It felt very solid and we liked it. But since we’ve founded Plataformatec we have learnt lots of new things, launched dozens of apps and we’ve met new great clients. Because of this, we brought new people onboard to complement us, with skills we didn’t have before.

Today, our team has engineers, designers, agile project managers and some business guys too. It would be more accurate if our visual identity incorporated them too. We still like to be seen as software engineers, but now, our team and services scope has grown.

We hope you like our new look.

Don’t be shy! Take a look into our new website and our page on Facebook and tell us what you think.

By the way, we’ll keep using @plataformatec twitter account for announcements, so keep following us. ;)



Startup Weekend is a global network of passionate leaders and entrepreneurs on a mission to inspire, educate, and empower individuals, teams and communities. And when they say global, they really mean it! There are Startup Weekends in Germany, France, Poland, Malasya, China, Uruguay, USA and many other countries, incluing Brazil.

It is the time and place where developers, designers, product managers and startup enthusiasts gather to build products and launch startups. And now, it is São Paulo’s turn! ;)

The ‘paulista’ edition will be hosted at ESPM in the next weekend (November 18th, 19th and 20th) and we will be there too. Don’t miss this opportunity. Bring your ideas and coding skills. Let’s share experiences and meet other entrepreneurs.

Watch the video below or take a look into for more information.

No dia 13 de agosto, a PlataformaTec estará no evento RS on Rails com a palestra “Código Saudável => Programador Feliz” que será apresentada pelo Rodrigo Flores.

A palestra abordará importantes conceitos intrínsecos ao framework Ruby on Rails e algumas dicas de como melhorar a qualidade e a manutenabilidade de suas aplicações web. O Rodrigo Flores também compartilhará algumas práticas que se tornaram indispensáveis no dia-a-dia dos nossos projetos.

Então, se você estiver interessado em saber como tornar o seu “dia-a-dia de desenvolvedor” mais feliz, vale a pena assistir a palestra. ;)

Ah sim! Não deixem de procurar pelo @cantoniodasilva, @georgeguimaraes e o próprio @rlmflores durante o evento. Conversar e trocar experiências é sempre muito interessante!


E que todos tenham um excelente RS on Rails!

"You" by Hugo Barauna

Ei você! Que gosta de codar em Ruby e Rails e não fica sujando o código com remendos... (by @hugobarauna)


Estamos procurando por desenvolvedores Ruby/Rails que:

  • … querem trabalhar com um time ao invés de colegas;
  • … gostam de trabalhar com pessoas que praticam a melhoria contínua ao invés de pessoas conformadas com o status quo;
  • … são pragmáticos ao invés de xiitas cegos e teimosos;
  • … entendem que fazer código bem feito e testado gera impacto positivo para os clientes;
  • … têm os skills necessários para contribuir com o crescimento da PlataformaTec.

Além das características listadas acima, nós valorizamos muito os profissionais que tem prazer em realizar o seu trabalho. E para ajudar os candidatos a entenderem um pouco mais sobre o que fazemos aqui, vou listar algumas coisas que o nosso time de devs fez durante os últimos meses. O nosso time de devs…

  • … desenvolveu uma API com protocolo de segurança utlizando o conceito de chave pública;
  • … aperfeiçoou o algoritmo do Readability em Ruby para parsing de páginas web;
  • … trabalhou na integração do Git como repositório de templates utilizando Rails 3;
  • … aplicou coaching em Ruby e Rails;
  • … estudou sobre arquitetura RESTFul;
  • … discutiu implementações de código e testes com o José Valim;
  • … executou uma série de stress testings utilizando httperf e JMeter;
  • … participou de reuniões com clientes para entendimento de escopo;
  • … fez programação pareada durante o desenvolvimento de um aplicativo para Facebook com Rails 3;
  • … desenvolveu projetos open source (Devise, SimpleFormCapybara Zombie e Outpost);
  • … participou de reuniões com os gerentes de projetos e desenvolvedores de negócios para decidir os rumos dos projetos;
  • … escreveu no blog da PlataformaTec e recebeu mais de 1.000 pageviews num único dia;
  • … revisou, colaborou e leu o Crafting Rails Applications antes que todo mundo;
  • … participou do churrasco e reunião de “Kick-start 2011 PlataformaTec”;
  • … e por fim, jogou duas mesas de poker e perdeu uma para o @vinibaggio e outra para @hugobarauna ;)

Requisitos da vaga:

  1. Inglês intermediário
  2. Sólido background em programação orientada a objetos
  3. Experiência com desenvolvimento de aplicativos web em qualquer linguagem (pelo menos 1 ano)
  4. Experiência com Ruby e Rails (pelo menos 6 meses)
  5. OS Linux ou Mac
  6. Disponibilidade integral
  7. Local: São Paulo (nosso escritório)


Update (abr/2011):  este processo seletivo foi concluído. Obrigado a todos que participaram.

[as some of you might have noticed, I accidentally clicked on "Publish" on my draft version, here is the full version of the post. Sorry about that]

*Though this blog post was written for any audience, there is a chance that you’ll be more interested if  you are a startuper or running a knowledge workers based company.

A year ago I was writing about a few uncertainties that we faced while starting up Plataforma Tec and how we dealt with them. We know that we still have a lot to learn, but now that another 12 months have passed by we are feeling much more solid and confident about what we’re building.

As last year’s post, this will also be about sharing our thoughts and a few practices that have been helping us a lot in creating a company culture and leveraging our team into its best. I hope you enjoy and find them useful!

what a team! =D

what a team! =D

We believe that (…)

1)… mastering our work IS our work

better and better and better - steve jobs keynote

"better and better and better"

We constantly tell people and customers “hire us only if you need a well developed application” (for example: a web application that will provide a revenue stream or will constantly have new features). This is one of our main assets and our main differentiation in this price competitive industry. Frankly, this strategy has been working fine for us but in order to keep it running this way, we are constantly looking for mastering our work all the time. Otherwise, if we don’t, there will be a great chance of losing our competitive edge.

2)… responsibility comes along with autonomy

"with great power, comes great responsability" - uncle ben

"with great power, comes great responsibility"

In last year’s post we mentioned that we only hire professionals that we feel comfortable giving autonomy, but it’s important to remember that it must be used very carefully. So, although autonomy makes a great pair with the constant search for mastery, don’t forget to be very cautious when dealing with decisions that might have a great impact in your company. We usually handle this kind of situation with two simple practices:

  • we show our team, in a very explicitly way, the goals and guidelines that should de followed;
  • and we constantly gather the team to discuss important issues (see the item below).

3)… gathering  the team to discuss problems is a great way to find solutions

gather your team and discuss problems and solutions

gather your team and discuss problems and solutions

Once in a while we face situations that are a bit more risky or complicated to be solved by our selves alone. They can be technical or design problems, a project management issue or even a simple warm-up for a business meeting. For all this we usually gather two or three team mates to ask for their opinion and discuss about the options that we might have.

4)… projects managers shouldn’t delegate work or establish random deadlines. They should serve and protect the team from undesired noise.

to protect and serve

"to protect and serve"

In our company, projects managers, salesmen and organization leaders work together with developers and designers. We see it as a system that must work synchronized. Also, the actions of planning, estimating and taking decisions in a project  should be made by the whole team (and not only by the manager). We found out that serious problems might arise when this system is desynchronized or made only by one person.

In our opinion, the manager role is to assure that developers and designers have the proper atmosphere to do their best. And by ‘proper atmosphere’ we mean that they have to provide the right tools (hw and sw), proper workplace, avoid useless interruptions and support the team when they get stuck with something.

5)… establishing roles is good and we avoid hierarchy levels

do not create communications layers between team and managers and leaders

Some managers try to list and predict 100% of the problems that might happen in a project. Here at Plataforma Tec, we assume that it’s impossible to do so. Therefore the big deal is NOT about trying to predict and avoid 100% of the problems. The deal is to BE PREPARED TO REACT when a problem happens and trying to avoid the most obvious problems that could happen.

Ok, but what does it all have to do with Roles vs. Hierarchy?
Check this: if we are prepared to react to a problem, first we must DETECT the problem. Right?

So, that’s where hierarchy kicks in… there is a great chance that creating hierarchy levels will degrade the communication quality in you company. This is one of the reasons we avoid creating different levels here at Plataforma Tec. Instead, we prefer defining roles. Developers should develop, Managers should support, Salesmen should sell (but synced with the whole “system” mentioned in item “4″).

If you’re having trouble understanding the difference between Roles and Hierarchy, take a look at Scrum’s roles (as an example of definition of roles).

6)… business leaders must create the right policies to enable all the items above

new policy

policies should be discussed, not imposed

All these practices won’t be effective if the organizational leaders don’t believe and provide the right policies to really enable them. Important notice: be careful not to confuse policies from impositions.

Well, this is a list of a few things that we’ve been doing and they have worked fine for us. Also, these six practices will work a lot better if implemented together, since they leverage each other.

I guess that’s it and I hope they’ll be useful or inspiring to others. Also, don’t forget to comment what you think about this small list of practices… Do you think they’ll work in your company?

Oxente Rails 2010

Pois é pessoal, estamos há somente dois dias do Oxente Rails 2010 e nós da Plataforma Tecnologia já estamos na expectativa para embarcar para Natal!

@cantoniodasilva, @fabioyamate, @hugobarauna, @josevalim e @vinibaggio já estão com as malas prontas para aproveitar os dois dias de palestras sobre Ruby, Rails, agilidade e empreendorismo. Certamente será uma grande oportunidade para re-encontrarmos todo o pessoal da comunidade Rails e não poderíamos perder essa!

Aliás, gostaria de parabenizar o Paulo Fagiani pela excelente organização do Oxente Rails. Parabéns!

Mas falando em palestras… quero convidá-los a assitir as apresentações do José Valim e do Hugo Baraúna que ocorrerão lá no Oxente Rails. Serão dois assuntos:

DRY – Don’t Repeat Yourself (José Valim)
As nossas ferramentas open source desempenham um papel importante no ganho de produtividade do nosso dia-a-dia. Nesta palestra, José Valim apresentará os nossos principais plugins e como cada um deles se integra ao Rails 3.

Project Rescue – Salvando projetos à beira do precipício (Hugo Baraúna)
Hugo Baraúna contará uma história de horror (real) e explicará como o nosso processo de Project Rescue pode mudar o rumo de um projeto quase perdido para um final feliz.

Pessoal, aproveitem o evento ao máximo e nos procurem para conversar e discutir sobre Ruby, Rails e desenvolvimento de software. Mas não se esqueçam que a praia e água de coco também fazem parte da programação, hein?! ;)