Se tem algo que tem me deixado cansado ultimamente são as discussões sobre linguagens de programação. Mas as discussões que me deixam cansado não são aquelas discussões construtivas onde linguagens de programação são comparadas para percebermos quais são os pontos fortes e fracos de cada uma. O que tem me incomodado e muito são aquelas discussões juvenis que começam com frases do tipo "a minha linguagem é melhor do que a sua", "a linguagem que você usa vai morrer" e seguem com argumentos fracos e geralmente baseados em suposições infundadas, ou seja, a discussão pelo simples prazer de discutir e não de melhorar algo ou alguém.
Eu trabalho numa grande empresa do país. Apesar de não ser uma empresa de software, a área de TI é enorme e devemos ter pelo menos umas 6 mil aplicações desenvolvidas (sem exagero!) ao longo do tempo para atender às demandas da empresa, não estou contando aqui as aplicações que foram compradas, apenas as desenvolvidas mesmo. A fila de espera de aplicações a serem desenvolvidas é enorme, e depois de conviver nesse ambiente por quase 5 anos, eu posso afirmar categoricamente: estamos fazendo a coisa errada, estamos desenvolvendo software de um jeito completamente equivocado.
Anyone who knows me knows that I'm a fan of video games. Indeed, choosing a programming career has a lot to do with my passion for games because in my childhood I was curious to know how these games were produced and it made me went deep down into the world of computers and software development.
Today I work with programming, but not games programming, and I'm still trying to understand the game development world. So this post is to tell you my little history as an inveterate gamer.
This post is a translation of a blog post from Scott Berkun for Brazilian Portuguese.
Original post: http://scottberkun.com/2009/letter-to-micromanagers/
Translation to Brazilian Portuguese: http://ricardoduarte.net/posts/carta-aberta-aos-microgerentes.html
What freedom means? Montesquieu has his own definition: "Liberty is the right of doing whatever the laws permit." The Internet has brought freedom for an enormous amount of people in the world, as some used to say: "there is no freedom without knowledge", and the web makes available the maximum amount of knowledge to the greatest amount of people around the world.
But it seems that some governments and large companies still do not get it and want to forbid downloads, searches, or in some cases they appeal to misplaced censorship. However, in the midst of this sea of ignorance, a story that made me still believe in free speech, it is something that can make people think about how we treat other people's freedom.
It began when Joel Spolsky wrote an article on his blog entitled The Duct Tape Programmer. And then it began to spread, some liked it, others not so much. But the curious thing was to see the amount of blogs that immediately raised the finger to say how Joel was wrong, how the comparison was exaggerated, how the concept was flawed.
Heaven's sake! Let's stop this thing of always wanting to label everything as right or wrong, few things in life are right or wrong, black or white, light or dark, or whatever you prefer to compare. The secret is to seek balance. And when we talk about software development, programming, this becomes even more true. Very few things are on the ground of right and wrong, in most cases, you need to use common sense (rare thing nowadays) to choose the most appropriate form of work, the most appropriate technology or most appropriate working tool.
Therefore, instead of wasting energy criticizing the article, we get the main idea and see how it can improve our lives, the way we work, to see if we can do our best in developing software.
We were very excited about the methodology, however, the physical space where we work does not allow the main tools Scrum suggests (whiteboard, pen, paper and post-it). As a disclaimer, our team has not fully adopted Scrum, our idea is to incrementally adopt some practices so we can improve the way we develop software. This post is a result of researching I did to find to support our team work. Let's take a look at the tools.