Meme – finito

Meme #016 – Diversidade faz Bem

pv — Tue, 29 May 2007 18:35:00 +0000

When solving problems, diversity may matter as much as, or even more than, individual ability.

– Scott Page (professor na Universidade de Michigan e autor de “The Difference: How the Power of Diversity Creates Better Groups, Firms, Schools and Society“).

.:.

Meme achado-forçado, que ajuda no debate sobre ‘Especialistas Generalistas’.

.:.

Meme #015 – TI Centrada na Informação

pv — Mon, 14 May 2007 17:18:00 +0000

In the existing IT environments, I believe we moved from being Server-centric to OS-centric to Application-centric. In the next generation, we become more network-centric but fundamentally (for the first time I might note) start building Information Technology actually around the Information. This is powerful. It means that Information is no longer captive to a single application but can be leveraged across any number of applications.

– Mark S. Lewis, VP da EMC

Vale a pena ler toda a sua série chamada “Flat IT”.

.:.

Meme #014 – Tecnologia é só 1% da Solução

pv — Thu, 22 Mar 2007 15:20:00 +0000

Qualquer combinação de software e hardware pode ser vista como um sistema de informação que pode ser dividido, literalmente, no sistema propriamente dito e a informação, suas propriedades e contexto que trata (incluindo aí regras de negócio, gente, problemas, oportunidades…).

O sistema, por sua vez, é uma composição das tecnologias usadas para sua construção e a capacidade de aplicação das mesmas em um dado ambiente de informação. O que normalmente significa que um grande especialista em sistemas financeiros, por exemplo, vai estar perdido se o problema à sua frente for desenvolver um sistema de e-mail. Depois de quase 30 anos fazendo software, acho que descobri as porcentagens que regem as divisões acima: um sistema de informação é 10% sistema e 90% informação. E o sistema é 10% tecnologia e 90% aplicação, o que faz com que a tecnologia, de fato, seja apenas 1% da solução.

– Sílvio Meira (em “Mudando o Mundo. Como?“)

Meme #013 – O Ócio Lubrifica

pv — Wed, 21 Feb 2007 13:24:00 +0000

Slack at all levels is necessary to make the organization work effectively and to grow. It is the lubricant of change. Good companies excel in the creative use of slack. And bad ones can only obsses about removing it.

– Tom DeMarco (em “Slack”)

Surrupiei a citação deste excelente artigo do Maurício Linhares. Cheguei até ele via Fragmental.

Meme #012 – O Cliente está sempre Conectado

pv — Mon, 15 Jan 2007 15:59:00 +0000

“I think that right now we’re at a stage where the tools and accepted architectures do not fit the job that programmers have to do. We have three factors that are not going to change in the near future, and they all live on the client: HTML, the browser, and Javascript. Everything else is negotiable. It’s up to programmers to figure out how to deliver the best application they can using any back-end they want, as long as it works with those three front-end technologies. Programmers have done some really cool stuff on top of those three technologies, but things are still pretty awkward.”

…

“The big problem, I think, is that the front-end is still very disconnected from the back-end. Because of SOA, people are still thinking very much in terms of sending and receiving messages rather than thinking about how to create a smooth and seamless application that exists both on the client and the server. I don’t know if it’s because of the fact that the Web was very disconnected in the early days, but most programmers still don’t think of the Web browser as a connected client.”

…

“However, there is no longer any good reason to keep the client disconnected from the server in terms of software architecture. Broadband penetration is now 75% of active Internet users in the U.S., and much higher in countries that are not as backwards as we are. For some reason, programming techniques have not yet adapted to this fact. And what’s more, everyone is on their way to becoming an always-on node on the Internet network. One third of Blackberry owners are not using their phones for business. The iPhone from Apple (if it gets to keep its name) is a tiny OS X computer with Internet connectivity. In places where Wi-fi hotspots aren’t present, Wi-Max will be soon. In other words, we can no longer get around the fact that the client is once again part of the architecture equation, and our programming practices need to support that fact.”

– Jason Kolb (em “Network-Oriented Architecture“)

Meme #010 – SOA não é Futuro

pv — Thu, 28 Dec 2006 12:56:00 +0000

A impressão que tive é que com a quantidade de dinheiro que se está investindo em SOA hoje não dá mais pra chamar de futuro, mas de presente. Claro que há um problema muito grande aí: Este foi o mesmo cenário, por exemplo, com EJBs.

Eu espero sinceramente que tenhamos aprendido a lição e que estudemos os conceitos por trás das coisas antes de sair por aí implementando sistemas que não funcionam utilizando ferramentas caríssimas.

– Philip Calçado (em seu blog Fragmental)

===

Acabei de conhecer o trabalho do Philip. Coisa muito boa, escrita d’uma forma muito legal. Tanto que já tá devidamente assinado e referenciado ali embaixo.

E assim retomo os posts “meme” aqui no finito.

Meme #009

pv — Tue, 26 Jul 2005 20:06:00 +0000

ManagementSpeak: This company is ISO 9000 certified.
Translation: We have documents to prove who screwed up.

Hehe.. Sou fã do Bob Lewis desde que li “IS Survival Guide”. No livro ele já tinha essa série, com “falas da gerência” e suas “traduções”. Hoje ele mantém o site “IS Survivor” e o mesmo bom humor.

Meme #008 – "You Get what You Pay For"

pv — Mon, 09 May 2005 20:15:00 +0000

Trechos de um excelente artigo de Bob Lewis, autor de “IS Survival Guide”:

…

What motivates most employees is achievement, approval, or a sense of belonging to an exclusive group that’s doing something important. The money is nice, but not their primary driver.

Not that they ignore what they’re paid. Quite the opposite — they give it their closest attention. That’s because a company’s compensation system is the loudest, clearest, and most emphatic communications channel it has for explaining to employees what it considers important.

The classic example, used in every introductory seminar on Total Quality Management ever given, is the company that decided it wanted quality. It preached quality, taught quality techniques, and measured quality improvement. The result, month after month, was a total lack of improvement in its defect rate. Why? The factory manager’s bonus depended on how many widgets rolled off the production line every month.

Pay for quantity, beg for quality, and quantity will win every time. What you pay for explains your priorities far better than your company newsletter.

Bring it home to IT. Many CIOs want to establish a more process-oriented perspective in their organizations, to get (all together now!) Repeatable, Predictable Results. Whether it’s an ITIL initiative or an attempt to rise to higher levels in the Software Engineering Institute’s Capability Maturity Model, they want the IT staff to “plan the work and work the plan” instead of coming to work every day as if the world had just been created fresh and new.

Good for them. These are important goals for many IT organizations. So if you’re one of them, go ahead and want process, teach process techniques, and measure process results. And then …

A project team finds itself under time pressure. The project manager rallies the troops, who work a succession of twenty-four hour days and seven-day weeks. Gasping for breath, exhausted but exhilarated, they meet their deadline with minutes to spare.

Impressed, you give them all bonuses for going the extra mile.

Outstanding. Except …

Another project team doesn’t find itself under time pressure. Every week, every team member meets every milestone. The project manager spots risks and issues early and deals with them. If one team member gets into trouble, the rest help out immediately so the schedule is never in jeopardy. The deadline rolls around, they put the software into production, and go home to spend the weekend with their families.

Boring. Why would you give them a bonus? They didn’t go an extra block, let alone an extra mile. All they did was the work in front of them.

Making process happen in IT is hard. If you pay extra for heroics while ignoring those who do their work by the numbers, you’re preaching process in a whisper while shouting, in the loudest voice you can, that you really don’t care for it all that much.

As with any good process, the results are predictable, and have been repeated so many times you’d think we’d have caught on by now.

You get what you pay for. If you want process, start paying for it, instead of its opposite.

Meme #007 – "What needs 2 b done?"

pv — Sat, 23 Apr 2005 17:06:00 +0000

Se vc surrupiar uma frase de alguém para usar como ‘slogan’ corre o risco de ir parar na cadeia? Espero que não. A frase aí é do Drucker. Já tinha pintado por aqui no post “Ask a great question“. Fala tudo que o FINITO pretende falar.

É mais “SLOGAN”, né? Pq uma frase tão boa quanto é uma do Fernando Sabino, que pintou como um graffiare no GrAFfiTi: “No fim tudo dá certo, se não deu certo é porque ainda não chegou ao fim.”

Dúvida: um Meme pode ser uma pergunta?

ps: graffiare no graffiti? SIC2x – a turma vai dizer que é tão ruim (no pior sentido mesmo) quanto “colocar o google no blog”, uma das frases ‘contumbantes’ de 2004.

Meme #006 – "Reality Shock – The Chaos Report"

pv — Mon, 18 Apr 2005 19:26:00 +0000

Pesquisa do Standish Group em 2004:

.53% dos projetos em ‘alerta’ (atrasados, acima do orçamento etc etc)
.29% de projetos bem sucedidos
.18% de projetos cancelados

O ‘Chaos Report’ está completando 10 anos. Em 1994, tínhamos os seguintes números:

.52.7% de projetos em ‘alerta’
.16.2% de projetos bem sucedidos
.31.1% de projetos cancelados

Praticamente dobramos o número de projetos bem sucedidos (ou reduzimos pela metade os cancelados). Mas mais da metade ainda é reportada como ‘em alerta’. Apesar… deixa pra lá.