CNXS

A small lesson from Zen Brain reflections

2010-04-21T21:45:59Z

There are plenty of lessons to be taken from this book. Lessons about zen, learning, education, brain science, and what it means to be aware of yourself.

It is, however, not very readable, in the sense that it is very abstract and terse sometimes. But it does pass the torpor test[1]. That means that it is a hard quest, but one with a great reward.

A small fragment from the book summarizes its quality:

One of these Kyoto-trained Zen teachers taught me a basic lesson about myself. A simple, dramatic demonstration showed me how strong was my own I-Me-Mine. It happened during an informal private interview before our retreat began.

We had conversed for a while. Then, he took a short, dark, wooden stick from his lap and placed it down on the low table in front of us. It caught my eye immediately. No ordinary wood was this, but a wonderfully aged, irregularly shaped stick, obviously an antique object. This work of art, about a foot long and perhaps an inch and a half in diameter, exemplified wabi-sabi. Its mellow patina conveyed associations with long use and advanced age. No word was spoken, yet the roshi's nod obviously invited me to pick it up.

I did. Turning it over and around in both hands, I then held it horizontally with my right hand at one end, slowly admiring it as I had the other antique objects during that earlier ceremony in Kyoto.

Surprise! In one swift act, the Roshi reached across and suddenly grabbed the free end, eyes twinkling as he did so. And almost as fast, without thinking, as my grasp reflex tightened, I found myself locked into a semi-mock tussle with the rightful owner of this antique treasure!

It was an impromptu tug of war, neither of us moving that stick very far in either direction. The strength of his pull just sufficed to neutralize mine. So there we were, like two boys at play, tugging on his beautiful stick!

Soon enough, it dawned on me: How could I possibly dispute his owner- ship!? Yielding, and relinquishing my grasp, I found we were both smiling when our brief mock play session ended.

A simple unexpected demonstration: Yes, I had longed to go on admiring his beautiful stick. He had (playfully) thwarted Me from doing so. I had behaved like it was Mine, and had grasped the stick reflexly. The greedy grasp of the I-Me- Mine was nakedly on display.

Words were unnecessary. I had been educated. I had done more than observe the full extent of my own instinctual tendency to grasp things. I had felt the strength of my attachment in my muscles, joints, and sinews.

[1] Basically, after exposure to the work, do people care less about the subject than they did before? Taken from this terrific book.

Good writing is equal to good programming

2010-01-20T15:36:23Z

I just read Zinsser (2010), and I though that his approach has a lot in common with good programming, and indeed with some good universal design principles.

Zinsser basically resumes his thoughts with these sentences:

Short is better than long.
Simple is good. (Louder)
Long Latin nouns are the enemy.
Anglo-Saxon active verbs are your best friend.
One thought per sentence.

I think all of that are equivalent to a combination of these universal principles of design: William Lidwell (2003):

Accessibility - the principle that asserts that the design should be usable by people of diverse backgrounds.
Chunking - accommodates short term memory limits by formatting information into small number of units.
Interference effects - when outputs of different mental system are incongruent, interference occurs and additional processing is required.
Ockham's razor - Oldie but goodie. As Einstein puts it Everything should be made as simple as possible, but not simpler.

To close, this little exercise was a great evidence on how writing is simply to program in a different media for a different audience (or vice versa) but the same principles apply to both of them.

Bibliography

Jill Butler William Lidwell, Kritina Holden.: Universal Principles of Design.
october 2003.
William Zinsser.: Writing english as a second language.
2010.
URL http://www.theamericanscholar.org/writing-english-as-a-second-language/.

Código com liberdade ou morte(): Porque Hackers geralmente são libertários

2009-09-08T16:27:17Z

por Daniel Franke,(traduzido por Eduardo Bellani)

Para qualquer um que tenha habitado a internet por tempo suficiente para diferenciar ICANN de 4chan ou um netcat de um LOLcat, não vai ser novidade que hackers são com freqüência libertários. A razão é normalmente entendiada como algo assim: hackers, por definição, gostam de coisas esquisitas, como desmontar o tocador de DVD ou pesquisar como uma bomba nuclear funciona. Legisladores, que falham cronicamente em entender o porque alguém iria gostar dessas coisas ou porque que elas teriam valor pra alguém, passam leis que interferem com essas atividades. Justificadamente irados, hackers adotam visões políticas que se opõem a estas intrusões.

A mais clara exposição deste modelo talvez seja o artigo de 2004 do Paul Graham chamado "A palavra `hacker'". A idéia geral entretanto já está tacitamente entendida a muito mais tempo. Ela é a base para o tom de várias histórias do site Slashdot. Observações da correlação hacker-libertário é ainda mais antiga; não da pra ler USENET antiga por 10 minutos sem perceber-la.

A rescrição de Gordon ao corolário de Newman sobre a lei de Godwin observa "Libertarismo (pro, contra, e lutas entre as facções) é o tópico primordial de discussões do net.news. Qualquer hora que o debate muda para outro lugar, ele precisa eventualmente voltar a esta fonte de combustível" (Não sei quando isto foi escrito. Não foi entes de 1990 que a lei de Godwin foi criada, e não depois de 1994 que Godwin a citou).

Hackers tem uma longa história de conflitos com governo. Uma lista incompleta:

1986: O ``Computer Fraud and Abuse Act" passa no congresso americano, tornando pela primeira vez cracking um crime. Enquanto ele é direcionado principalmente a crimes não controversos, abuso legal por autoridades ignorantes por atos perfeitamente legais como port-scanning se torna rotina na década de 90.
1993: Philip Zimmerman é o alvo de uma investigação criminal depois que o PGP é sai dos Estados Unidos, em violação de restrições de exportação para criptografia (que era classificada como munição na época).
1996: O ``Communications Decency Act" restringe severamente material "obsceno ou indecente" na internet. Esta lei é negada pela Suprema Corte dos Estados Unidos no ano seguinte
1998: O ``Digital Millennium Copyright Act" passa, tornando crime qualquer tentativa de passar pelas medidas de segurança que tem como objetivo proteger material com copyright, independentemente da intenção do tentativa.
1999: Jon Johansen et. al. libera o DeCSS, decodificando a `encriptação' ridícula usado praticamente em todos os DVDs e tornando possível assistir DVDs usando software open-source. No ano seguinte, a casa de Johansen é invadida pela polícia Norueguesa.
1999: Amazon recebe a notória patente do 1-click.
2000: 72 pessoas na Califórnia recebem uma intimação proibindo-as de usar uma camiseta contendo o código de uma parte do DeCSS.
2001: Dimitry Sklyrov, um programador russo visitando os Estados Unidos, é preso pela lei DMCA e detido por vários meses por ter escrito um leitor de e-book capaz de ler vários formatos com DRM.
2002: Sarbanes-Oxley torna quase impossível para pequenas startups web fazerem abertura de ações
2003: A saga legal da SCO começa. SCO exige que todos os usuários Linux a paguem $700 dólares de licença.
2003: O FBI invoca abusivamente o USA PATRIOT ACT para recuperar notas de repórteres que entrevistaram Adrian Lamo.
2004: No que Brad Templeton descreve como `spamlitigação', o RIAA começa a processar seus clientes em massa, distribuindo mais de 20000 processos legais, incluindo crianças, avós e falecidos entre os acusados.
2005: FEC Commissioner Bradley Smith afirma que `a exceção da imprensa' do McCain-Feingold Campaign Finance Reform Act não inclui bloggers.

Entretanto, estes casos são insuficientes para explicar as atitudes dos hackers. A cultura hacker existe desde que as universidades tiveram acesso aos computadores - desde os anos 60 - e mesmo antes era reconhecida pela sua incarnação anterior dos operadores de rádio amador. Foi uma cultura libertária desde sua concepção. Mesmo assim, a lista começa em 1986. Antes do CFAA, era difícil apontar para qualquer intrusão que incomodasse os hackers em particular. Uso civil dos computadores não estava no radar do congresso e da polícia até então.

Para não fazer injustiça a tese de Graham, ela é muito mais abrangente que qualquer lista de reclamações. Graham observa corretamente que hackers tem suspeita de toda a autoridade, mesmo onde a teoria libertária diz que esta autoridade é legítima. Hackers ficam tão nervosos com o chefe que controla seu departamento fala para eles que "Eu acabo de ler numa revista sobre algo chamado virtualização. Nós deveríamos usar isso." quanto vão ficar com algum agente do governo. Por isso os hackers já se incomodavam bastante antes de 1986. O governo chegou tarde para essa festa.

Mas a obvervação que hackers são um grupo de espertinhos reclamações não explica o porque disto. Se as reclamações não se limitam a intersecção entre governo e tecnologia, porque esta atitude tem relação com escrever código?

A resposta de Graham a isto é a seguinte:

Deixe-me colocar isto em termos que um oficial do governo iria apreciar. As liberdades civis não são apenas um ornamento, ou uma velha tradição americana. Liberdades civis fazem os países enriquecerem. Se você fizer um gráfico de PIB per capita vs liberdades civis, você verá uma forte relação. Poderia tais liberdades serem a causa, ao invés da conseqüência da riqueza? Eu penso que sim. Eu penso que uma sociedade em que as pessoas podem dizer e fazer o que quiserem irá ser uma onde as soluções mais eficientes venceriam, ao invés daquelas que fossem patrocinadas pelas pessoas mais poderosas. Países autoritários se tornam corruptos, países corruptos se tornam pobres, e países pobres se tornam fracos. Parece que existe uma curva Laffer para o poder do governo, assim como para impostos. No mínimo, é provável o suficiente para não se tentar um experimento para testar a hipótese. Ao contrário de impostos, você não pode repelir o totalitarismo se ele não funcionar direito.

É por isso que os hackers se preocupam. O governo espionando as pessoas não faz com que o código que eles escrevem se torne pior. Ele apenas leva a um mundo onde as idéias ruins vencem. E por causa que isto é tão importante para os hackers, eles são especialmente sensíveis a isto. Eles podem sentir o autoritarismo se aproximando a distância, como animais podem sentir uma tempestade.

Eu acho que isto é uma falácia petitio principii. É uma visão libertária sobre o porque os hackers deveriam ser libertários. Se alguém concorda com a premissa que as liberdades civis fazem as pessoas enriquecerem, então tudo seque tranqüilamente. Mas se o governo autoritário "não faz com que o código que eles escrevem se torne pior", então porque hackers tem uma chance maior de fazer esta conexão?

Uma resposta tentadoramente lisonjeira para esta pergunta vêm do post de 1992 de Stuart Reges. Resumidamente, Reges afirma que existem uma certa habilidade mental - "QI libertário" - que nos faz melhores em formar modelos mentais de como programas funcionam assim como formular como a sociedade funciona. A primeira habilidade nos faz bons hackers. A segunda nos da um entendimento intuitivo de como o libertarismo funciona.

Apesar de cortês, eu acho que este argumento erra o ponto da discussão. Toda a teoria econômica que vem junto com o libertarismo é um efeito secundário. Libertarismo não é sobre o que nos faz ricos; é sobre o que é certo. ``We hold these truths to be self-evident'' e tudo mais. Libertários não se opões ao governo porque é atrapalhado e ineficiente, se opõe porque é maligno.

Além disso, acho que Reges nos dá muito crédito. O conhecimento médio dos hackers sobre a escola Austríaca ou a de Chicago é mais medíocre do que eles se permitiriam em qualquer assunto técnico. Comece a falar de externalidades ou o problema do parasita e nós mudaremos de assunto. Claro, os mais sofisticados irão citar o Teorema de Coase, mas a maioria nem ouviu falar dele.

Eu acho que nós estivemos olhando para o problema do ângulo errado. Não é que hackers adotam políticas libertárias, nem que existe um terceiro fator que influencia libertários e hackers. Ao invés disso, pessoas com uma atitude anti autoritária tendem a serem atraídos para programação.

A frase "conhecimento é poder" é um clichê, mas é também verdadeira num sentido bem literal. Aquilo que você não entende tem poder sobre você. As pessoas que não tem interesse em entender os computadores estão totalmente acostumadas a serem mandadas por eles; é mais um fato da vida. Se você não sabe que você pode mudar o bit de apenas-leitura ao clicar com o botão direito e editar o atributo na janela de propriedades, então não ter a permissão de editar o arquivo não é fundamentalmente diferente de não ser capaz de tocar um arquivo .wma cifrado porque a Microsoft fechou seu servidor de licença. Tentar fazer com que pessoas leigas se importem com DRM é inútil. Eles são sujeitos as tiranias de seus computadores todo o tempo. Porque esta seria pior?

Mas para aqueles de temperamento libertário, isso é um estado inaceitável. Ser mandado pelo governo já é ruim o suficiente. Mas ser mandado por um objeto inanimado? Intolerável. Como eu posso controlar essa coisa?

Este modelo da psiquê humana explica bastante nossas idiossincrasias de personalidade. Quando você não tolera ser ignorante sobre uma tecnologia, aprender sobre ela é a única saída. A outra é se tornar um ludita. Hackers se tornam luditas com freqüência.

Para exemplificar, eu tenho o mais barato celular do mercado. Ele não pode nem fazer o download de tons. Mas é ótimo para fazer chamadas. Porque é isso que eles tem que fazer. Eles não são feitos para mandar email. Nem para jogar tetris. Nem para tirar fotos. São feitos para fazer chamadas. É bastante chato ter que descobrir como tirar meu telefone do modo de câmera. Eu não quero descobrir como tirar meu telefone do modo de câmera, porque telefones não são feitos para tirar fotos. São feitos para fazer chamadas.

Algumas pessoas riem dessa atitude, mas é o mesmo sentimento que hackers tem quando reclamam de inchaço de software. Todos já escutamos, se já não tivermos participado, de conversas como:

``Eu não quero que meu editor de texto leia email! Eu quero um editor de texto!''

``Então use-o como um editor de texto.''

``Mas ai vou ficar com todo esse lixo espalhado no meu computador.''

``Por quê você não ignora isso? Não está nem exposto na interface gráfica. Você tem que saber o comando correto para ativá-lo. São menos de 80MB de espaço, e você tem 1TB no seu disco, e a maior parte não chega na RAM até que você a invoca.''

``Mas é nojento!''

Pode parecer forçado chamar a atitude dos odiadores do emacs de ludismo, e mais forçado ainda chamá-lo de libertária. Mas a psicologia é a mesma. Ninguém quer tirar o tempo para entender alguma coisa que eles consideram supérflua. Racionalmente ou não, hackers irão encontrar qualquer tecnologia que eles não entendem com suspeita - não de seus mérito, mas de sua segurança. "I eu quero isso ai ferrando com meu sistema", nós iremos dizer para você, mesmo sabendo perfeitamente bem que ele irá apenas sentar em um canto do disco rígido. Já recompilou seu kernel apenas para desabilitar um módulo que você não necessita? A maior pare de nós já o fez, mas isso desafia qualquer base racional.

Mas essa irracionalidade é comum. As atitudes libertárias geralmente ultrapassam os princípios libertários. Essencialmente todos os libertários defendem o direito de portar armas, mas consideram o direito a propriedade privada mais fundamental. Então, nós compreendemos o direito do de proprietários de proibir armas em sua propriedade. Mas isso não impede libertários de ficarem perturbados cada vez que um proprietário exerce esse direito.

Ficamos perturbados com os hoplofóbicos (medo de armas de fogo) pela mesma razão que arrancamos aquele módulo do kernel: odiamos e tememos sermos controlados.

My .vimrc

2009-09-02T22:08:50Z

For those of you who are not familiar with vim (shame on you), it is a marvelously powerful text editor, which I use for coding and text editing in general (Latex, html, rails, ruby, etc). The only exception is scheme, for which I use DrScheme, but that is another story.

Anyway, .vimrc is the file that sits on your home directory and configures the state your vim will be. Here is mine for the curious.

  1 " An example for a gvimrc/vimrc file.
  2 " The commands in this are executed when the GUI or vim is started.
  3 "
  4 " Maintainer:   Bram Moolenaar <Bram@vim.org>
  5 " Last change:  2001 Sep 02
  6 "
  7 " To use it, copy it to
  8 "     for Unix and OS/2:  ~/.gvimrc
  9 "             for Amiga:  s:.gvimrc
10 "  for MS-DOS and Win32:  $VIM\_gvimrc
11 "           for OpenVMS:  sys$login:.gvimrc
12
13 " Make external commands work through a pipe instead of a pseudo-tty
14 "set noguipty
15
16 " set the X11 font to use
17 " set guifont=-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso8859-1
18
19 " Switch on syntax highlighting if it wasn't on yet.
20 if !exists("syntax_on")
21     syntax on
22 endif
23
24 "SETTINGS
25 "
26 set ch=2                " Make command line two lines high
27 set mousehide           " Hide the mouse when typing text
28
29 "sets the default grepping engine to be ack-grep with the -a flag
30 "change this to --ruby or some other stuff for searching only ruby
31 "use it like this
32 ":grep Dumper perllib
33
34 set grepprg=ack-grep\ -a
35
36
37 " Switch on search pattern highlighting.
38 set hlsearch
39
40 "display current info all the time
41 set ruler
42
43 colorscheme twilight
44
45 "prettier font...
46 set guifont=Liberation\ Mono\ 12
47
48 " those next 2 commands are taken from a tip in http://vim.sourceforge.net/tips/tip.php?tip_id=259
49 " They basically map to keys F1 -> toogle menu; F2 -> toggle toolbar
50
51 " get rid of toolbar
52 set guioptions-=T
53 :let g:toggleTool = 0
54 map <silent> <S-F2> :if g:toggleTool == 1<CR>:set guioptions-=T<CR>:set lines+=3<CR>:let g:toggleTool = 0<CR>:else<CR>:set lines-=3<CR>:set guioptions+=T<CR>:let g:toggleTool = 1<CR>:endif<CR>
55
56 " get rid of menu
57 set guioptions-=m
58 :let g:toggleMenu = 0
59 map <silent> <S-F1> :if g:toggleMenu == 1<CR>:set guioptions-=m<CR>:set lines+=1<CR>:let g:toggleMenu = 0<CR>:else<CR>:set guioptions+=m<CR>:let g:toggleMenu = 1<CR>:endif<CR>
60
61 "line numbers please...
62 set number
63
64 "set the incremental search
65 set incsearch
66
67 "remember more history
68 set history=500
69
70 "Generally the :substitute command changes only the first occurrence of the word
71 "unless you use the 'g' option.To make the 'g' option the default use this:
72 set gdefault
73
74 "this is for vim omni completion of ruby code. Check out :help new-omni-completion or :help ft-ruby-omni
75 let g:rubycomplete_buffer_loading = 1
76 let g:rubycomplete_classes_in_global = 1
77 let g:rubycomplete_rails = 1
78
79
80 "*****************************************************************************************************
81 "*****************************************************************************************************
82 "*****************************************************************************************************
83 "
84 "MAPPINGS
85 "
86 "
87 " Make shift-insert work like in Xterm
88 map  <S-Insert> <MiddleMouse>
89 map! <S-Insert> <MiddleMouse>
90 "this pastes what's copied, not what is selected
91 map  <leader>v <ESC>"+gp
92 map  <leader>c "+y
93
94 map  <leader>n :vnew<CR>
95
96 "reload vim configuration automatically whenever I edit it
97 "found here http://dailyvim.blogspot.com/2008/11/reload-vimrc.html?showComment=1228044660000#c2642014041159858949
98 au! BufWritePost $MYVIMRC source %
99
100 "this maps to James Buick's FuzzyFinder: TextMate plugin
101 "Found here http://weblog.jamisbuck.org/2008/10/10/coming-home-to-vim
102 map <leader>t :FuzzyFinderTextMate<CR>
103
104 "minibufexpl plugin http://www.vim.org/scripts/script.php?script_id=159
105 let g:miniBufExplMapWindowNavVim=1
106 let g:miniBufExplMapWindowNavArrows=1
107 let g:miniBufExplMapCTabSwitchBufs=1
108 set hid "Hide abandoned buffers in order to not loose undo history (taken from http://heykevinle.blogspot.com/2007/06/vim-minibufexpl.html)
109
110 " this is a shortcut to the minibufexplorer
111 map <Leader>b :MiniBufExplorer<cr>
112
113 " SPELLING OPTIONS
114 "
115 "set the spell checker for txt, html, README and tex files
116 autocmd BufNewFile,BufRead *.txt,*.html,README,*.tex,*.story setlocal spell spelllang=en_us
117 "autocmd BufNewFile,BufRead *.txt,*.html,README,*.tex setlocal spell spelllang=pt
118
119 map <F2> :setlocal spell spelllang=en_us<CR>
120 map <F3> :setlocal spell spelllang=pt<CR>
121
122 "popup the a menu on mispelled words with the mouse
123 set mousemodel=popup
124
125 set textwidth=80
126
127 "found those on http://wiki.rubyonrails.org/rails/pages/HowtoUseVimWithRails
128 filetype plugin indent on " Enable filetype-specific indenting and plugins
129 augroup myfiletypes
130     " Clear old autocmds in group
131     autocmd!
132     " autoindent with two spaces, always expand tabs. For other types of
133     " identation, add new file types.
134     autocmd FileType ruby,eruby,yaml set ai sw=2 sts=2 bs=2 et
135     " if not any of those files, fall to the default
136     set ai sw=2 sts=2 bs=2 et
137 augroup END
138
139 "Autoidenting ruby code using the kode gem. Found on http://antono.info/en/50
140 nmap <leader>rci :%!ruby-code-indenter<cr>
141
142 "map the leader c key to the buffer delete
143 nmap <leader>d :bd<cr>
144
145 "write the buffer
146 nmap <leader>w :w<cr>
147
148 "write all the  buffers
149 nmap <leader>wa :wa<cr>

A review of The i of the vortex, from neurons to self

2009-08-27T13:40:45Z

A little review of the book, The i of the vortex, from neurons to self.

This is a stimulating book, from one of the modern fathers of neuroscience, Rodolfo Liinas (if anyone is interested in a video of him discussing the book, there is a great one online here) where he attempts to build a coherent theory of consciousness as an emergent property of neurons. He does not only stay within the confinement of describing the current modern discoveries. He actually attempts to find a framework.

That framework stems from motricity, the capacity to move. Llinas argues that moving and being conscious are profoundly linked, in such that for one to move, one needs:

The capacity to move
A perception of how one is moving and where
The desire to move

From there it follows that the brain is essentially a prediction, or dreaming, machine, but the dream is always being modulated by the information coming from the senses.

All that does not, of course, spring from nothing. There is a evolutionary progress in the development of this three items, that according to my interpretation of Llinas' book, is what consciousness is all about.

There is a lot of technical information there, so my advice is, give this book a couple of readings, because Llinas is at the forefront of neuro research, and his compilation of recent finding is a worth reading in itself.

An emergent participatory design framework for higher education

2009-06-17T15:53:49Z

Here is an improved version of an article about education I have wrote some time ago. If anyone is curious, this is the abstract:
Abstract
This paper proposes a model of higher education that uses emergence and constructionism as the guiding design principles and takes the current computational technologies and networks as the technological base to distribute and generate information and knowledge.

Thoughts on Deschooling Society

2009-05-31T21:59:51Z

This is a small review about Ivan Illich's book, Deschooling Society. One of the best books I've ever heard about the negative effects of the current educational system.

The author explains exactly what the book is about:

School groups people according to age. This grouping rests on three unquestioned premises. Children belong in school. Children learn in school. Children can be taught only in school.

I think these unexamined premises deserve serious questioning.

Most of the text is dedicated to question, very skillfully in my opinion those premises. The author anarchist/libertarian tendencies show in the book, in the sense that most emphasis is directed to the free choice of the individual in detriment of institutions. But I think one would be wrong to say that Illich has an agenda other than point out the evils of a systematic enforcement of teaching:

To understand what it means to deschool society, and not just to reform the educational establishment, we must now focus on the hidden curriculum of schooling. We are not concerned here, directly, with the hidden curriculum of the ghetto streets which brands the poor or with the hidden curriculum of the drawing room which benefits the rich. We are rather concerned to call attention to the fact that the ceremonial or ritual of schooling itself constitutes such a hidden curriculum.

We cannot begin a reform of education unless we first understand that neither individual learning nor social equality can be enhanced by the ritual of schooling. We cannot go beyond the consumer society unless we first understand that obligatory public schools inevitably reproduce such a society, no matter what is taught in them.

Illich goes very keenly to the core of the damages that the paternalistic system of education do to a person.

The man addicted to being taught seeks his security in compulsive teaching. The woman who experiences her knowledge as the result of a process wants to reproduce it in others.

In fact, healthy students often redouble their resistance to teaching as they find themselves more comprehensively manipulated. This resistance is due not to the authoritarian style of a public school or the seductive style of some free schools, but to the fundamental approach common to all schools-the idea that one person's judgment should determine what and when another person must learn.

From every single source about pedagogy I have ever heard, this book is the one to learn about why the current situation is fundamentally broken, why it is harmful to society and to the individual.

But school enslaves more profoundly and more systematically, since only school is credited with the principal function of forming critical judgment, and, paradoxically, tries to do so by making learning about oneself, about others, and about nature depend on a prepackaged process.

It is a very profound responsibility of the individual, to take charge of his own education, and you could say the same about freedom. It is hard work to be a free person, and you cannot be a free person if others control what, how and when you should learn something.

Only liberating oneself from school will dispel such illusions. The discovery that most learning requires no teaching can be neither manipulated nor planned. Each of us is personally responsible for his or her own deschooling, and only we have the power to do it. No one can be excused if he fails to liberate himself from schooling. People could not free themselves from the Crown until at least some of them had freed themselves from the established Church. They cannot free themselves from progressive consumption until they free themselves from obligatory school.

This is a life changing book, and I guess Illich's works will only increase in importance the deeper we go into the knowledge age.

Difference between constructivism and constructionism

2009-05-13T21:12:07Z

Hello there.

Just giving a heads up on a good article I've read recently called Emergent Design and learning environments: Building on indigenous knowledge by David Cavallo.

It tells the story of a constructivist project in Thailand, and it is a great read if you want to get a better grip on education as Seymour Papert dreamed it could be. One small quote from the article, about the difference between constructivism (Jean Piaget) and constructivism (Papert):

Constructionism builds upon principles in constructivism. While constructivism holds that the learner constructs new knowledge based on the existing knowledge he or she has, constructionism builds on this idea by maintaining that this process happens particularly well when the learner is in the process of constructing something.

Thoughts on Alan Kay's teaching style from Xerox

2009-05-11T16:13:56Z

Just finished reading one more article in my quest for understanding Alan Kay's Xerox park advances (I should in the future write a post about the quest itself).

I'll summarize here a part of the article, particularly the part regarding education, a little enticement for the whole deal. Sincerely, just go ahead and read the article if you are the least curious about the words here.

So, Alan's words about the principles they used for education in the Xerox park:

These ideas are found in many places and many cultures. We came to them from our own experiences, the Suzuki violin method, O. K. Moore, Piaget, Furth, Bruner, Minsky, Papert, and others.

Here are them, enumerated:

Listen to the student.

Since we believe that teaching involves helping a student adapt his knowledge structures to a new situation, we can guarantee ourselves (not to mention the student) an unpleasant journey if we don't try to understand these gossamer schema at the outset.

Many of the current ways that things are done in Smalltalk come directly from listening to the kids. Smalltalk, as an "extensible" system, can easily "be" any kind of tool that we wish. We ourselves have remolded it several times.

Never teach anything which has to be unlearned later.

In our experience, humans are very poor at unlearning any kind of skill, whether it be muscular or mental. This principle is well understood by every teacher of music. "Tempting analogies" which later come back to haunt are especially to be avoided.

We teach "straight" Smalltalk, the very same system which adults learn. The very first examples and methods to which the kids are exposed resemble strongly the most sophisticated adult systems.

Never pace a student in a way that will require future remediation.

Principle 2. basically says: don't simplify to the point of a lie; Principle 3. is a corollary of this which states: don't put the student into a situation where he will feel dumb and inept because a good enough foundation has not yet been laid. Most kids do not understand the distinctions between skill, structure, and intelligence any better than adults do and are apt to feel stupid rather than unskilled in new situations.

Hook on to existing fruitful structures when possible; if unfruitful concepts exist, don't unteach them, rather supply completely fresh orthogonal concepts.

Most kids know about dictionaries and looking up the meaning of a word. The meaning can be an explanation of a passive relationship or a dynamic act. In fact, every idea in mathematics and in programming can be easily explained in dictionary oriented terms alone; this is a fruitful, useful concept, and it makes sense to use it with kids.

Many other "natural language" linguistic structures are ultimately deadly and we avoid them.

Examples are: "nouns", "verbs", "pronouns", inflections, and their counterparts in most programming languages: data structures, functions and control structures, variables, tagging type to names, etc. Instead, we immediately give children a running example which directly exhibits the more fruitful notions of states-in-process communicating-with-messages found in Smalltalk.

Do not look over the student's shoulder.

Aside from the obvious reason of avoiding "putting the student under the gun", there is also a great difference between performing and creating. In music, this is known as the difference between improvising and composing (and a greater difference could hardly be found, as any musician will attest). We are much more interested in the design-oriented and planning processes associated with unhurried goal-directed reflection than in the more shallow though flashy effects obtained by virtuoso "thinking on one's feet".

Teach and Show Multiple Perspectives of Situations.

A typical problem with fledgling designers of all ages is a strong tendency to commit all of their short term memory to a given perspective of a Situation. If it happens to be an unfruitful view it might be very difficult for them to "bail out" or even tell that it is unproductive. We feel that the Piagetian example of the tilted glass is much more the result of lack of practice in multiple viewing than the result of physiological immaturity.

One of the striking things about design methodology is that "simultaneous" use of a perspective and its dual is remarkably more rewarding than using either separately.

A very global example is the duality of wholes-as-collections-of-parts found in Western science and wholes-as-wholes found in Eastern philosophic thought.

The former has an important dualistic aspect itself: analytic (or top-down) vs. synthetic (or bottom-up); both of these emphasize differences and boundaries: a corpuscular theory. The Eastern philosophy emphasizes samenesses and connection: a field theory. As more complex systems are studied, the apparent differences between the two schools of thought blur in the underlying sameness that characterizes duals

The content of the computer is descriptions of processes; the ability of computers to simulate the details of any descriptive model means that the computer, viewed as cc medium itself, can be all other media if the embedding and viewing methods are sufficiently well provided.

Those principles show a very pragmatic way to teach any skill, not the least programming, mathematics, epistemology and so forth. They are imbued with respect for both the student and the concepts needed for a citizen in the knowledge age to make informed decisions.

You can also see the notion of the computer as a form of media (think speech, printing press, dance, etc) and how that concept is a very powerful idea, that can give rise to a new age of human perception and civilization. Again, read the article to gain a bit of insight on how a group of 25 people 30 years ago created tools and concepts that kept entire fields busy ever since.

Review of Marvin Minsky's Society of Mind

2009-05-02T02:40:12Z

Introduction

This is a small review of Society of Mind(SoM). I urge anyone who is looking for a more in depth analysis to check Push Singh (R.I.P) review or just to read the book itself. It is the magnum opus of Marvin Minsky, and it is more a philosophical and psychological venture into the nature of the mind than a technical AI work.

There are very few works around like this one. It basically sets a very abstract framework of how he thinks the mind works. The ground that is covered in the book is staggering, and I think it is one of the reasons why this book is not as famous and cited as it should. It is the culmination of the ideas of two genius, Minsky and Papert, on how the mind structure itself, the world, time and beyond.

The structure of the book is also something very uncommon. It is organized in several mini ideas, one per page, and those ideas are themselves organized in larger modules or chapters. So Minsky used his society idea for the structure of the book itself. What that results is there are technical aspects that are not immediately clear, but run through the book, much like a though.

So, it is a difficult book to understand, but one that is easy to read I guess. I'm going to try and give some insights from several quotes I have gathered in my path in the book. It is very disconnected and floating around, but the book is in this format, and I for sure lack the competence to formulate a coherent string of though were Minsky himself failed to. Like he says:

My explanations rarely go in neat, straight lines from start to end. I wish I could have lined them up so that you could climb straight to the top, by mental stair-steps, one by one. Instead they're tied in tangled webs.

Well, I'll use his justification also:

I'm inclined to lay the blame upon the nature of the mind: much of its power seems to stem from just the messy ways its agents cross-connect. If so, that complication can't be helped; it's only what we must expect from evolution's countless tricks.

The book

The book provides several kind of falsifiable (perhaps some are too abstract) theories and hypothesis floating around the book, but don't worry, Minsky is well aware of how science marches

The only course left for us is to study the mind the way scientists do when something is too large or too small to see - by building theories based on evidence.

That is not what the book is about of course, like I said before, it provides a framework, or several frameworks and hypothesis, to begin building experiments and improving the hypothesis and frameworks(or destroying them).

There is a lot of talk about what things mean, and how meaning is merely the connections that one does between scarcely existing things.

The secret of what anything means to us depends on how we've connected it to all the other things we know. That's why it's almost always wrong to seek the ''real meaning'' of anything. A thing with just one meaning has scarcely any meaning at all.

This connectionism is keenly related to Papert's principle and to how people learn (the ideas that grew into this book originated from Papert and Minsky dialogues, but they went into separated directions, Papert went into pedagogy and the applications of these ideas into constructionism, Minsky remained interested in the construction of an intelligent machine).

I disagree with what Minsky's concept of intelligence.

Our minds contain processes that enable us to solve problems that we consider difficult. ''Intelligence'' is the name for whichever of those processes we don't yet understand.

Then he goes and adds

Like the concept of ''the unexplored regions of Africa'', it disappears as soon as we discover it.

I think that our concept of intelligence is flexible and mutable, but it is not bound to disappear, it will just change with our perception of the world.

There is also several Buddhist quotes, mostly about the nature of suffering (attachment). Since I identify a lot with those though, I'll cite one of them:

Do not become attached to the things you like, do not maintain aversion to the things you dislike. Sorrow, fear and bondage come from one's likes and dislikes.

The most interesting part for in was the description of what is called Papert's principle:

Some of the most crucial steps in mental growth are based not simply on acquiring new skills, but on acquiring new administrative was to use what one already knows.

I think the development of this principle is one of the aspects of the book who is most valuable in a profound personal way. It is, as Papert would say, a powerful idea

This idea, in my opinion, is the embryo that gave birth to constructionism. There is several ideas that resonate with those found in other works by Papert, specially Mindstorms. Like for instance

Our best ideas are often those that bridge between two different worlds!

The book goes on through a lot of ground. Sincerely there is quite a lot to learn, even from casual reading, like this little pearl from Buddha:

If the mind were an ego-personality, it could do this and that as it would determine, but the mind often flies from what it knows is right and chases after evil reluctantly. Still, nothing seems to happen exactly as its ego desires. It is simply the mind clouded over by impure desires, and impervious to wisdom, which stubbornly persists in thinking of ''me'' and ''mine''.

Well, I'll say it one more time, Minsky is a genius, one of the greatest minds to work on AI and psychology. This is a great work, so go ahead and fetch it! My bet is that this book and its successor will still be studied for decades, and will be looked back as reference for a lot of subjects.

The present and the future

There is a successor for the book, and I have it in hands, so there will be a review of it in the future. Not that I have digested the SoM, but perhaps a little peek on the development of the ideas will make me understand them better.

This book is a point of view from an AI father about intelligence, and it is a must read. But there is a lot of finer tools for analysing the brain these days. My hope on cracking the intelligence and consciousness enigma is to look at the brain with those tools and frameworks like those shown in this work.

One last quote:

One can acquire certainty only by amputating inquiry.

Go ahead, read the book with a lot of inquiry, and enjoy!

Jeff Hawkins's On intelligence review

2009-04-20T15:12:40Z

This book is a very interesting reading for everyone who wants to get a hold of a emerging framework for understanding intelligence, specially as a it emerges from a common algorithm in the neurocortex.

The neuro and cognitive sciences are, by the experts own admission, lacking a common and powerful framework where to try out the large corpus of data that exists and continue to be collected. This book presents a very compelling hypothesis for one. Basically Jeff argues that

The neocortex areas act as one single mechanism.

and that its main function is to recognize patterns and elaborate predictions based on them. Roughly there is a upward flow of information in the neocortex from the diverse senses and a downward flow that fills information and elaborates predictions (this is overly simplified, you should really grab a copy of the book and read the whole argument). Here is a small quote that tries to clarify this point:

Think about information flowing from your eyes, ears, and skin into the neocortex. Each region of the neocortex tries to understand what this information means. Each region tries to understand the input in terms of the sequences it knows. If it does understand the input, it says, "I understand this, it is just part of the object I am already seeing. I won't pass on the details." If a region doesn't understand the current input, it passes it up the hierarchy until some higher region does. However, a pattern that is truly novel will escalate further and further up the hierarchy. Each successively higher region says, "I don't know what this is, I didn't anticipate it, why don't you higher-ups look at it?" The net effect is that when you get to the top of the cortical pyramid, what you have left is information that can't be understood by previous experience. You are left with the part of the input that is truly new and unexpected.

One thing that the reader should be aware is that the book is a new framework proposal, so there is a lot of assumptions going on. That is not to say that Jeff is wrong, but simply that there is not enough compelling evidence for the framework yet. He honestly admits that on chapter 6 (where he presents the kernel of the framework) of the book:

To find and establish a new scientific framework, it is necessary to look for the simplest concepts capable of uniting and explaining what were large quantities of disparate facts. It is an unavoidable consequence of this process that the pendulum swings too far toward simplification. Important details are likely to be ignored, and facts will be misinterpreted. If the framework takes hold, refinements and fixes will inevitably be found showing where the initial proposal went too far, didn't go far enough, or was in error. In this chapter, I have introduced many speculative ideas on how the neocortex works.

Jeff also makes a very interesting analysis of creativity and why it is so mystified:

Isn't creativity some extraordinary quality that requires high intelligence and giftedness? Not really. Creativity can be defined simply as making predictions by analogy, something that occurs everywhere in cortex and something you do continually while awake. Prediction by analogy— creativity— is so pervasive we normally don't notice it.

That lead to some insight on how to improve one's creativity

First, you need to assume up front that there is an answer to what you are trying to solve. Second, you need to let your mind wander. You need to give your brain the time and space to discover the solution.

what mind is and some warnings about the failings of the brain/mind:

I hope I have convinced you that mind is just a label of what the brain does. Our brains are always looking at patterns and making analogies. If correct correlations cannot be found, the brain is more than happy to accept false ones. Pseudoscience, bigotry, faith, and intolerance are often rooted in false analogy.

I did had a problem with his Einstein example:

It had more support cells, called glia, per neuron than average. It showed an unusual pattern of grooves, or sulci, in the parietal lobes— a region thought to be important for mathematical abilities and spatial reasoning. It was also 15 percent wider than most other brains. We may never know why Einstein was as creative and smart as he was, but it is a safe bet that part of his talent derived from genetic factors.

Given the brains plasticity, we cannot be sure that Einstein's brain differences are genetic in nature or the result of his efforts and focus on creative process.

His framework is sound and very promising, and this book is probably a landmark in neuroscience study. I did have a couple of problems with the book though.

He is careful to make a distiction between intelligence and intelligent behavior. That is paramount and of course there is a difference. But his failing in this case is to use The Chinese Room argument to illustrate his point. I think that argument is a fallacy, and I use Jeff's own words to illustrate why it is a fallacy:

There is a single powerful algorithm implemented by every region of cortex. If you connect regions of cortex together in a suitable hierarchy and provide a stream of input, it will learn about its environment.

Here he makes a case where intelligence is rested on a given algorithm. Well, the same could be said about the chinese room, invalidating it's supposed conclusion that computers cannot be intelligent.

The second point I would critisize is his suggestion to read Hubert Dreyfus in the end of the book. For anyone interested in a thoughful analysis on Dreyfus ideas and why they are filled with fallacies I suggest and old work by Seymour Papert.

To summarize, it is a great reading, his framework sounds very promising and a new encompassing algorithm was really needed in the field. Go ahead, it is more than worth the money and time. And if you feel curious, fetch his article explaining in more depth his theories.

Review of Seymour Papert's Children's Machine

2009-04-13T18:34:58Z

Recently I've bought the translation of Children's Machine by Seymour Papert in Portuguese for my girlfriend. Having a justifiable belief on Papert's ideas obviously I've read it the fastest as I could also ;)

This is a classic from the point of view of pedagogy. But let me first give some context. Papert (www.papert.org) is the father of constructionism, LOGO and a lot of powerful ideas. His beliefs on the power of technology, if used to enhance human capabilities as a support for creativity, to produce mega change in School (with a capital S to mean our current educational system) are developing since the 60's. In my opinion his works are paramount if one wants to understand the technology world as it is, because they influenced directly Alan Kay at his time at Xerox, and lead to the personal computing revolution.

The children's machine was written in 1993, before the web and when the PC revolution was in full motion. In it we encounter a very friendly and close dialog with one of the greatest genius of the computer age. We encounter several insights about epistemology, some of them dating from the time Papert spent with Piaget in the 60's, but updated to the current times.

Papert also makes explicit something that was more hidden in his other book Mindstorms, the concept of demanding permissiveness. Basically that means that a more libertarian and open education does not mean less work and responsibility. Much to the opposite, even though the results are more fun and efficient. One analogy that I found useful is that even though a system can have many successful outcomes, that does not mean that it has no unsuccessful ones.

His concept of mathetic is also La borated more profoundly. He argues that there is a word for the art and science of teaching (pedagogy) but not one for learning. He then proposes Mathetic (http://en.wikipedia.org/wiki/Mathetics) as a good candidate. The purpose is not to establish mathetic in itself, but to get some term to mean it, to make thinking and having a point of view about it more easy and feasible. (As Alan Kay says, a point of view is worth 80 IQ points)

I'll follow the translator in his recommendation of the book for teachers, parents, educators and professionals of TI. I'll add that it is crucial for anyone who want to know how to better learn anything. That audience I believe includes anyone who wishes to live a better life.

Buffer size on send_data

2009-04-13T18:00:22Z

The send_data method haves just 4096 bytes of buffer used to stream the file.

A trick to expand the limit is change the 'content-length' on the HTTP Headers.

Example:

def index
  @posts = Post.all

  respond_to do |format|
    format.html # index.html.erb
    format.csv {
      list = Post.csv_list(@posts)
      send_data(list, { :type => "text/plain", :filename => "posts.csv", :disposition => "attachment" })
      headers["Content-Length"] = list.to_s.length
    }
  end
end

The Ruby On Rails ActionController::Request headers method provides access to the request‘s HTTP headers. So you can use it to change the content length of the request.

If you have the path of the file you can use "File.size(path)", but if the file is generated on the fly, you need to convert to string and use the length to know the file size in bytes.

See you.

Acts as Conference 2009

2009-02-18T02:40:47Z

I was @Orlando last weekend for Acts As Conference 2009. As a hole the event was good, but somehow I was expecting more from this event (not from the weather, it was freaking cold!). I will brief the talks that IMHO were the best.

Greg Pollack and Jason Seifer on Innovation in Rails:

In this talk they brought attention to what was new since the last year, and I got some plugins and stuff that I didn't know it. The resume of the things presented: http://www.railsenvy.com/aac

Brian Liles on TAFT

Brian in the first day asked if DHH Test all the fucking time and DHH said no! Well this talk was the funniest of the event. He talked about tools to test and tips to improve your way of testing. And also Test All The Fucking Time.

Yehuda Katz on Merb Rails Merge

Yehuda Katz did a nice presentation over the new features of the merge of Rails and Merb codes, for the future version of Rails. Also at the end of the talk he did a good Q&A with the attendees.

Those talks was my highlights of the conference, the rest it's a little bit of the same bullshit from here, repeated things from there.

Sistema de cotas, mentiras e covardia

2008-11-23T19:28:07Z

Olá, gostaria de discutir uma questão que é muito relevante para os brasileiros em geral. O sistema de cotas que acaba de ser aprovado na câmara. Aqui tem um bom texto para saber mais sobre o assunto.

A questão real é de eficiência da solução. Cotas, ao meu ver, serviriam mais para prejudicar o mercado alvo (índios, negros, excluídos sociais, etc), pois retiraria pressão do governo em providenciar aquilo que é responsável, um ensino médio de qualidade, compromissado com o aprendizado técnico, social e crítico da população, sem distinções.

Cotas em suma, não contribuiriam em nada para o alívio da dívida moral (que existe e realmente precisa ser paga), econômica e política que a sociedade brasileira e mundial tem com suas parcelas mais fracas e historicamente exploradas, e sim contribuiriam para os políticos terem desculpas, ao apontar para a "realização" da "justiça" com as cotas, sendo que nada realmente justo foi realizado, e a solução verdadeira que só viria com sacrifício e mudança real é empurrada para as próximas gerações realizarem.

Ou seja, é a solução de covardes que se escondem atrás de um escudo de mentiras politicamente corretas.

How to get better error messages for an associated model.

2008-11-13T15:07:43Z

Hey there. Let's assume you have some set like this

class User < ActiveRecord::Base
  has_one :profile , :dependent => :destroy
end


class Profile < ActiveRecord::Base
  belongs_to :user
  validates_presence_of :first_name, :last_name
end

And you create the profile in the same view as your user. How do you validate those first_name and last_name fields with a friendly message for your user?
Well, you could use validates_associated, but you would end up with a message like "Profile is invalid". Now, how friendly is that?

To obtain a more precise message, use this on you user.rb

def validate
  if self.profile
    self.profile.errors.each do |error|
      self.errors.add_to_base error.join(' ')
    end
  end
end

Security idea for banking cards

2008-11-12T20:34:06Z

I'm a brazilian, and on our big cities we have a type of crime known as flash kidnap ("sequestro relâmpago" in portuguese), which is a crime that consists in one kidnapper taking a hostage and cruising around with him (probably on the hostage's own car) and forcing the victim to release his banking account numbers so money can be drawn from his banking account.

This type of crime is basically a problem that was induced by the introduction of a technology (bank credit cards). But this technology could be made safer by the introduction of an emergency number. This number would work just as the normal one, so there is plausible deniability for the victim, so money could be drawn and all, but if ever used it would raise alarms on the credit central, and the authorities could be immediately called. Since close to 100% of the ATM machines have cameras around them, and there is the location of the drawn, it would be easy to check where criminals are.

For example:

Bob uses a banking card and has 2 passwords (pass A and pass B). Bob uses pass A on his day-to-day, without a hassle. Some day Eve kidnaps Bob, and forces him do release his card and a password. Bob releases pass B. Eve uses Bob's card with pass B without a problem, but doing so warns Alice that there is an emergency happening with Bob (possibly a kidnap). Alice warns the authorities.

I'm not interested in making money at all with this idea, but I would like to see it implemented, so it perhaps could save some property and lifes, so I'm asking for some directions as to what the heck I should do with it, and also some criticism.

This idea is registered under CC Attribution-Noncommercial 2.5 Brazil

Startup school 2008

2008-11-03T22:10:35Z

Quick link to some valuable resource...

Startup school 2008!

Ahhh, we here at cnxs are busy learning some new exciting technology, so keep you heads up for some fresh new content soon....

Difference between is_a? and instance_of?

2008-10-28T03:55:15Z

Hi Sirs.

There is a difference between a bunch of methods that appear that they to the same job, but they won't.

The methods instance_of?, is_a? and kind_of? do related jobs, but not the same job.

For example is_a? and kind_of? do the same job, they return true if the caller is an instance of the method argument, if the caller is an instance of every superclass in his inheritance tree or if the argument method is a module included in the caller.

The instance_of? is more specific, it returns true just if the caller is an instance of the method argument.

Let me show some examples:

module Hand
end

class Animal
end

class Mamal < Animal
  include Hand
end

class Dog < Mamal
end

dog = Dog.new

puts dog.instance_of?(Dog)    # true
puts dog.instance_of?(Mamal)  # false
puts dog.instance_of?(Animal) # false
puts dog.instance_of?(Hand)   # false

puts dog.is_a?(Dog)    # true
puts dog.is_a?(Mamal)  # true
puts dog.is_a?(Animal) # true
puts dog.is_a?(Hand)   # true

Remember that is_a? and kind_of? do the same job.

See you.

Rails Summit Latin America 2008 - Review Day 2

2008-10-24T02:21:52Z

Second Day of Rails Summit, started hot. Phusion guys talked about Scaling Applications, what are the problems, bottlenecks, solutions, how's the possibilities to face it. Was very good and entertaining, specially when Darth Vader come into it. Slides were good with funny animations.

After that comes Charles Nutter e Thomas Enebo talkin on JRuby and because the technical problems during the virtual presentation, left an impression that could be better. They gave an overview of the status of JRuby, how it runs on hotspot, and also presented some (strange) numbers of memory usage in JRuby comparing to MRI.

Jay Fields talking was about testing and some testing frameworks. Well in general was a good presentation but for him almost all solutions are imature, which I disagree and when he was questioned on what makes a framework mature, he said time, years...

David Chelimsky did 2 great talkings one about RSpec and the other about Cucumber, much more for newbies (with all respect to newbies it's just a stage). I liked a lot because he seem to be very confident on his arguments, this is a thing that I appreciate on speakers.

The others between Chelimsky's and Obie I didn't payed too much attention so I'll skip my review on them.

Obie Fernandez closed the event with a great keynote, telling about how his software consultancy deals with the agile manifesto. It's great to hear that you apply the techniques that he says that's a key of success of his company. He presented a full stack of the way his company develop software, since the first contact to the client.

Rails Summit for me was a great event, that I've met good mates from the brazilian and latin america Rails community. I will be waiting for the next one on 2009!

Diff entre respond_to? e respond_to

2008-10-21T13:18:30Z

Um pequeno tutorial em português pra diferenciar melhor respond_to? e respond_to. Não parece ter muita não? Mas o tio Chuck Norris vai me ajudar a esclarecer melhor isso aqui.

respond_to? é um método do Ruby Core como você pode ver, e não do Ruby On Rails, ele basicamente verifica se determinado objeto responde a um método, como o nome sugere mesmo.

Por exemplo:

class Chuck < Object
  def norris
    puts "the man"
  end
end
chuck_norris = Chuck.new
p chuck_norris.respond_to?("norris") # true
p chuck_norris.respond_to?("mr_t") # false

Já o respond_to, sem o ponto de interrogação (eles fazem parte do nome do método) faz parte do ActionController do Ruby On Rails. Ele coloca suporte a Web Service na sua aplicação, isso quer dizer que ele consegue resolver o tipo do recurso que você deseja.

respond_to do |format|
  format.html # render por default nome_da_acao.html.erb
  format.js # render o nome_da_acao.rjs
  format.xml { render :xml => @chuck.to_xml } # coloca o chuck pra xml e envia
end

Com esse código na action você poderia usar, por exemplo:

http://localhost:3000/nome_da_acao.html

http://localhost:3000/nome_da_acao.xml

Ou realizar uma chamada JS unobstrusive usando AJAX.

Isso ai, espero ter ajudado.

Rails Summit Latin America 2008 - Review Day 1

2008-10-21T03:10:18Z

Rails Summit Latin America 2008 was a great event at all. Nice speakers, nice people all around, good food. Only the weather wasn't so fine (above 30 C).

The event started with DHH talking on new features of Ruby On Rails 2.2 answering questions of the crowd. I didn't liked it too much, mostly common questions with common answers by him, nothing special.

Then Chad Fowler comes and well really debut the event, he made an awesome presentation about be remarkable, talking about his book "My Job Went to India", his life as a musician and Doom player :-)

After lunch, George Malamidis talked about REST. I didn't liked too much, was hard to me after lunch pay attention, after 9 hours driving in day before and an early wake up for the event.

Dr Nic Williams talked on Open Source and encouraged people to contribuite more to Open Source Projects. Dr Nic Williams presented a very funny talk and I think if he could take a shot on a Saturday Night Live, if he don't want to be a developer anymore. He's the Jerry Seinfield of Ruby On Rails community.

Chris Wanstrath, his keynote was very similar to Ruby Hoedown keynote (good IMO, but I expected a little different).

The summit ends the first day with a Birds of Feather were some participants presented random thoughts, Eduardo Bellani also gave his presentation at this time. This whole BoF was one of the funniest moments at Rails Summit Latin America 2008.

Eduardo Bellani on Rails Summit Latin America 2008

2008-10-20T06:26:42Z

Apresentação de Eduardo Bellani sobre voto eletrônico no Rails Summit Latin America 2008, em São Paulo.

Votação caixa preta (Black box voting)

2008-10-10T19:36:50Z

For the english readers (if any) => sorry, this one will be in portuguese (except the article with a ++ in front)

Aqui embaixo vai uma coletânea de artigos sobre esse assunto (revisitei de novo o esquema de votação digital depois de assitir este documentário, o qual recomendo fortemente). Pretendo escrever algum artigo a respeito futuramente, mas não pude deixar de compartilhar estas fontes, dada a gravidade deste assunto:

entrevista com um especialista brasileiro
++Analysis of an Electronic Voting System, artigo que é citado no documentário sobre a fragilidade do sistema eleitoral americano
versão tupiniquim inpirada no artigo acima
neste aqui, o nome diz tudo
livro disponível sobre fraudes na urna eleitoral brasileira

Não esqueçam, ser um líder nada mais é do que agir pensando no coletivo, e por incrível que pareça nós (uso essa palavra pra descrever todo mundo que esteja lendo um blog sobre tecnologia como este) somos a elite de nossa sociedade, e isso implica em agirmos como líderes, sob pena de ruir a mesma com nossa apatia.

New article on pedagogical development

2008-09-29T17:49:28Z

Hey there readers.

I've written a new small article, and I'm not even sure on what do to with it (if someone has a clue, drop me a line).

It's based on the works of Seymour Papert and constructionism.

Anyway, here it is.

Rails Summit Latin America by Locaweb

2008-09-24T13:24:53Z

Here we go!

My thesis short article

2008-07-28T23:43:52Z

Hey there. I've closed college (finally) and for the last project we had to built an extensive conclusion work and an article on this work.

The full length work is in portuguese, so it's a bit inaccessible to most readers, but I've tried to write the article in english, since it was permitted and it increased the potential reader base.

So here it is. It's about using the Getting Real philosophy as a way to be competitive in an ever increasingly competitive and integrated world. Hope you guys enjoy it, and any grammar mistakes, please point them out, english is not my first language, and mistakes do happen :P

Hugs

Export the database models to YML fixtures

2008-07-08T17:12:49Z

Hi Sirs,

Many tutorials over the web shows how to load data from fixtures. But, if you want to migrate your mysql data to a postgresql database?

We can export our data to fixtures, and after that we can load the fixtures to every database management system we wish.

Let's go to the rake task:

desc "export the database models to YML fixtures" 
task(:models_to_fixtures => :environment) do 
  ActiveRecord::Base.establish_connection(
    :adapter => 'postgresql', # mysql, sqlite3
    :encoding => 'utf8',
    :database => 'cnxs_development',
    :username => 'username',
    :password => 'secret'
  )
  ActiveRecord::Base.connection

  if ENV['MODELS'].nil? || ENV['MODELS'].blank?
    raise "Please enter valid models names separated by coma. Ex: MODELS=User,Account"
  end

  models = ENV['MODELS'].split(',').collect { |arg| arg.camelize.constantize }

  models.each do |model|
    output = {}
    collection = model.find(:all)
    collection.each do |object|
      output.store(object.to_param, object.attributes)
    end
    file_path = "#{RAILS_ROOT}/tmp/#{model.table_name}.yml" # /tmp/
    File.open(file_path, "w+") { |file| file.write(output.to_yaml) }
  end
end

Here you need to fill your database attributes like you do in the /config/database.yml.

You will call the command line:

$ rake models_to_fixtures MODELS=<your model names separated by coma>

For example:

$ rake models_to_fixtures MODELS=User,Post

All your model data will be stored on /tmp/ directory.

Download this rake task here.

See you.

Better than grep? You bet!

2008-06-26T13:58:57Z

Well, long time no post here.

I'm going to talk about a tool that changed the way I do search on the programming front.

Since I really don't like grep for common searches (it's a great tool but it's interface is a bit clunky) I used to use the Regexxer for those kind of project searches (it's a great GUI tool, I recommend it to anyone).

But since I'm more of a minimalist command line kind of guy, I was happy as a bonobo when I found ack, a grep like program hat has a interface for human beings (yeah, ubuntu reference, sue me). To give a little example on how simple is to search in a ruby project for example:

cd ~/project/path

ack-grep --ruby string_to_be_searched

And that's it, if you want any more details, the ack home page has a great little tutorial.

Hugs everyone.

Windows in Ubuntu 8.04 with VirtualBox

2008-06-24T16:01:13Z

I have a Windows on my machine, cause for some stuff I still need it, (MS Visio, MindMaps and couple of others application that doesn't run fine with Wine). It's a pain in the ass to always boot machine to access 2 or 3 files and stay 15 minutes on Windows.

A couple of years ago I was a big fan of VMware (old times that I virtualize ubuntu on windows), and I felt a lack of OSS on this area. So the solution it's virtualization, with VirtualBox it all comes easy!

VirtualBox, was recently bought by Sun, has 2 licenses: one commercial and one open source. I use OSE and to install it you have to follow these steps:

$ sudo apt-get install virtualbox-ose virtualbox-ose-modules-generic

Then add your current user on 'vboxusers' group

$ sudo adduser someuser vboxusers

Go to applications > system tools > VirtualBox

Now create your Windows VM with the almost NNF (next, next,finish) wizard. It's a piece of cake!

RSpec view test for render :partial with :locals?

2008-06-18T13:38:37Z

I was working on some rspec views tests and I've noticed that partial renderization can be tricky.

For example, if we have an index page that renders the objects list in a partial template.

In my case I was testing using a 'GivingClub' list:

describe "giving_clubs" do
  before do
    @giving_clubs = [mock_model(GivingClub)]
    assigns[:giving_clubs] = @giving_clubs
  end

  it "expect render giving clubs list" do
    template.expect_render(:partial => "/giving_clubs/list", :locals => { :giving_clubs => @giving_clubs })
    render "/giving_clubs/index"
  end
end

Do not forget the assigns before call template.expect_render. Locals works fine in this way.

HP Acquired EDS

2008-05-13T12:12:26Z

Well another big player buying other big player. Big acquisitions in the last couple of months! For around $13 billion ($25 per share). HP said that they could double their service revenue. Well seems that market doesn't believe too much in HP since their shares are down on 6% now...

Source: market watch

Clean Objects with find method

2008-03-02T12:51:19Z

Hi Sirs.

An important trick on the famous ActiveRecord::Base find method.

When you are in development time of your application, and you do some query on your database query editor, is a good practice to use the limit clauses and selects just the columns you want.

In the find method we can do it with the :limit and :select arguments.

For example in our code when we try to authenticate some user we got it like:

find(:first, :conditions => [query, hash], :select => "id, email, login")

The returned object contains just the id, email and login attributes. Clean object.

Password and other attributes do not appears in the returned object =]

Simple development practice, but very important too.

See you.

Rspec quickref

2008-02-21T20:05:53Z

Hey wanderers

Sorry for all this time frozen, the crew and I have a lot to post about, but our current assignments has kept everyone pretty busy(but that's not an excuse, so let me blow the dust off this blog).

So, just stumbled on Dave Astels (for those of you who don't know the guy, he's one of the responsible for the creation of the rspec behavior driven development framework, I'll post more specifically about it later, but you can find tons of info on the web about it) rspec QuickRef. For those of us who are using rspec a lot, this might come in handy. I know it did for me.

Just a tip this time folks, but I'll try and get some cooler tutorial next time.

Hugs to you all

Installing RMagick on Ubuntu

2008-02-05T09:18:31Z

Last week I was installing again rmagick on a Ubuntu server, then I discovered an very easy way to do it.

$ sudo aptitude install librmagick-ruby

Edit 10/20/08: Avoid this tutorial it doesn't work, if you wanna install rmagick use the old fashion way:

$ sudo apt-get install imagemagick

$ sudo apt-get install libmagick9-dev

$ sudo gem install rmagick

SQL Lite for Ruby On Rails

2008-01-28T13:19:07Z

Hi all.

If your Operacional System is Ubuntu and you are using Ruby on Rails 2.0.2 you can easily use it:

$ sudo apt-get install sqlite3

$ sudo gem install sqlite3-ruby

SQLite3 does not use authentication and needs only a pointer to the database file on database yml.

development:
  adapter: sqlite3
  database: db/development.sqlite3
  timeout: 5000
test:
  adapter: sqlite3
  database: db/test.sqlite3
  timeout: 5000
production:
  adapter: sqlite3
  database: db/production.sqlite3
  timeout: 5000

When you run "rake db:create:all" on your RAILS_ROOT it creates all 3 databases.

More information about other plataforms?

Here: http://wiki.rubyonrails.org/rails/pages/HowtoUseSQLite

See you.

Atom Feed Helper Example

2008-01-23T18:21:26Z

Hi all,
Rails 2 makes the Atom RSS Feed much more sophisticated and elegant. If you are using the Ruby on Rails by RubyGems installer, maybe you have an old version of the Atom Feed Helper. To fix it you can check out the atom_feed_helper version inside the Ruby on Rails repository and after that, copy and paste it to /vendor/plugins/ directory.
The repository is: http://svn.rubyonrails.org/rails/plugins/atom_feed_helper.
In there you will find plugins that are more up to date.
In the README you will find a simple example to build your feed. Like when you click in our Cnxs feed at the navigation bar, if you are browsing with Firefox.
Here comes our example:

# rss.builder
atom_feed(:schema_date => @posts.last.created_at.year) do |feed|
  feed.title("CNXS")
  feed.updated(@posts.first ? @posts.first.created_at : Time.now.utc)
  @posts.each do |post|
    feed.entry(post) do |entry|
      entry.title(post.title)
      entry.content(post.body, :type => 'html')
      entry.author do |author|
        author.name(post.user.name)
        author.email(post.user.email)
      end
    end
  end
end

You can note the the atom_feed method has 4 arguments, but just one of them is required, that is the :schema_date. You can read at http://feedvalidator.org/docs/error/InvalidTAG.html, you see that the URI tag needs a year to be fix in the validators, month and day parts are optional. The others arguments are :language, that defaults to "en-US", :root_url, that defaults to the root path on the current host and :url that defaults to the current URL.
Another thing that you can look is that the ".builder" extension has higher precedence. So, if you code it in your rss action in the PostsController:

respond_to do |format|
  format.atom { render :layout => false }
end

the atom format respond int the same way to rss.builder and rss.atom.builder.
See you.

Some Thoughts on Some Thoughts on Security

2008-01-18T09:33:27Z

I've been reading a great paper by Daniel J. Bernstein, the creator of a qmail, and wow, what a pearl of wisdom. One of the most clarifying and straight to the point works on code security I have ever read. He (quite correctly) makes a parallel between the code security and the amount on exploitable bugs (EB), stating that it is the major problem on the code, regarding security. And then gives some answers to that problem, along with a couple of common distractions of the programmer while coding that helps those EB creep on our code base (CB). Let's review then, starting with the distractions, and I'll try to make some links with my favorite unambiguous tool of choice, Ruby.

Chasing attackers. The point here is give some thought to respond to tomorrow's attacks, and not being trapped by the anti-virus mentality of being only responsive to aggressors. Perhaps the dynamic nature of Ruby would help with that, but I think it is more a personal posture problem than anything else.
Minimizing privilege. Here, what is being said is that the old principle of least privilege is fundamentally wrong. How so? Well, it might (!) reduce the damage done by security holes, but never fixes these. Plus, IMO, it might even give users a false sense of security. Again, it is more of a way of a personal way of thinking (but what isn't? :P ).
Speed, speed, speed. Here I think rubists have some advantage. Since we work on a language that is 'slow', usually we tend to not place emphasis on premature optimization. I think this quote summarizes the thinking here:
Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efﬁciencies, say about 97% of the time; premature optimization is the root of all evil. —Knuth in [13, page 268]

Now, to the answers. These are also 3, and they are codependent connected to each other:

Eliminating bugs. I think everyone saw that one coming. But even so, Daniel's down to earth advices on it are a very worthwhile reading. I think I can summarize him on this section by saying (and that is a plus to rubists too), simplify stuff. Simplify interfaces, UI, parsing. Elegance is not a luxury, it is a way to obtain security. Following that logic we come to.
Eliminating code. Heck, here I'll quote his quote, and be done with it.
To this very day, idiot software managers measure 'programmer productivity' in terms of 'lines of code produced,' whereas the notion of 'lines of code spent' is much more appropriate. —Dijkstra in [9, page EWD962–4]
But as our systems grow, and our time and budgets remain the same or are diminished, and as programmers get more dumb, something has to give right? Wrong (don't know about the last part though).
Eliminating trusted code. That is somewhat more difficult I think, but it says that a program should do what it is meant to do, nothing more, and trust as few sources of data as possible. KISS and all that stuff.

I would love to hear any input on that. Until next time people.

Oracle Acquired BEA

2008-01-16T20:07:26Z

What a day huh? Oracle bought BEA for around U$ 8.5 billions. I don't like this kind of acquisition, cause means less competitors in some market that they used to compete.

MySQL Acquired by SUN

2008-01-16T18:52:28Z

Huh? Sun acquired MySQL as announced today. I was very surprised by this notice, I guess soon we gonna have a much better DBMS. How does it sound for you?

Work Environment

2008-01-14T23:29:16Z

What's your work environment? Which IDE or whatever you use for code? I will describe mine:
I use Eclipse as my IDE for Rails Java or ColdFusion (I use a separate version/dist of Eclipse for each). I don't have too much to complain about memory usage, cause everytime I prefer spend a hundred bucks more on my pc's to get much more memory that I would use. By the way here's a tip for those who want to reduce the memory usage of Eclipse, or just want to not have some tools that they will not use (that's me!). Download only the Eclipse Plataform Binary (around 40MB) that comes without the JDT and without other unnecessary plugins.
Ok that will save some MB on your memory. Now build your own environment, with only plugins that you want!
Here is mine for Ruby on Rails: Aptana, RadRails, Subclipse.
ColdFusion: CFEclipse, Aptana, Subclipse
Java: WTP, Subclipse.

Ext JS

2008-01-14T21:35:07Z

Hey people, here is my first post and I expect you enjoy it.
Have you ever heard about the javascript library Ext JS? If your answer is no, you should visit their website. It's an amazing javascript library, build in the top of Yahoo UI library (another amazing), with a impressive variety of pretty beautiful and fully featured components. It's also extensible, customizable and very well documented. This last point I want to give a special focus, cause the documentation of the api is very good (part are inherit of YUI).
So if you want to deliver web 2.0 applications, don't forget to take a look closely on this library.

HTML Filtering with sanitize helper

2008-01-14T13:08:17Z

Hi sirs,
another important feature that we need to use is the 'sanitize' helper. This Ruby on Rails helper filters HTML nodes and attributes and strips invalid protocols. Here in our case the use it on the simpler way:
<%= sanitize(post.body) %>
Other time you can choose the options ':tags' and ':attributes' to do a custom use where just the HTML tags and attributes pointed here are allowed to be interpreted.
It is another little tip that helps in malicious posts or comments containing javascripts codes or comments with different enconding. Here comes the Rails API link to more information about this: SanitizeHelper.
See you.

Ruby on Rails pagination

2007-12-27T22:09:33Z

Hi sirs.

I really recommend the official Ruby on Rails paginator. Very easy to use. Like 95% of the plugins =).

I just checkout the project on SVN, change one line of code on my controller, appends a line of code on the ".html.erb" template index file, and paste a piece of CSS code on the stylesheet, and it works. The piece of CSS code is defined on the README file inside the plugin's root directory.

In my case, I just insert on my controller:

@posts = Post.paginate(:page => params[:page], :per_page => 10, :order => "created_at DESC")

and just insert on the view's bottom:

<%= will_paginate @posts %>

The CSS code I just change the color =).

The SVN repository is svn://errtheblog.com/svn/plugins/will_paginate.

The page that contains most of instructions is the err.the_blog, but if you just read the README in the will_paginate plugin you will be prepared to do all the work.

See you.

New file extensions on Ruby on Rails

2007-12-27T08:17:28Z

The very best point to participate of a developers group like CNXS is when you found a problem, everyone tries to help faster they can.
Rafael Souza shows me this post on another blog and it helps a lot. Just change the extension ".rhtml" to ".html.erb" and ".rxml" to ".builder" on you Ruby on Rails application in version 2.0.2. Your problems is gone.
See you.

Problems on Ruby on Rails 2.0.2

2007-12-27T07:37:51Z

Hi all,
Ruby on Rails 2.0.2 is released... and I do not like this version, because of 2 modifications.
1. Database default: Postgresql is my favorite database management system, but I know that Mysql is very easy to use on Windows and Linux. I respect the preference about Mysql. But I do not like what I read on "Riding Rails" that says "This is especially so under OS X 10.5 Leopard, which ships with SQLite3 and the driver gems preinstalled as part of the development kit". Sincerelly, for me, it is not a good point to change the default database :P
2. ".rxml" files was fired. Our feed on the site just blow up... because we use the .rxml files to render the xml version of the site.

Our host is using just Rails 2.0.2, living on the edge has problems too.
=)
See you.

CV with Curve and LaTeX in Ubuntu 7.10

2007-12-19T14:52:22Z

Hey there. In our little how-to I'll explain something that was very useful to me, this great tutorial by Didier Verna, on using the Latex curve class to build Cvs (pretty nice and standardized ones). That will be a superb reading for a more detailed tutorial. If you want to take a peek before reading on, here is my CV sample(a little past upgrade time :P), using a modified version of the sample used on the aforementioned tutorial, plus the source files here.

Anyway, I'll use the Ubuntu 7.10 distro, and all the wonderful free tool that are at our disposal in there. First, lets download the, IMO, best latex docs editor, kile. Then let's proceed to fetch the LaTeX packages so our Kile can compile smoothly our docs.

$ sudo apt-get install kile tetex-extra

Now bake a cake and go play soccer (looong download). Then download the Curve (or take the compiled one with my source files) class and place it on the docs root tree. So, now build a new project, add all the necessary files on that, including the curve class. If click on the pdflatex button (the big gear with a little pdf symbol) it should generate the cv.pdf nicely (don't forget to only use PDF, JPG, JBIG2, and PNG graphics formats, kile use pdflatex on this command, do yourself a favor and read the manual).

On some future post I'll go step by step on my modifications and the meanings of the commands. But if you just change the text and go hacking stuff you'll eventually find out what things mean. Oh, and please write on open office or something else that has a grammar correction, a CV with grammar mistakes don't look so good :)

First page on google.com.br

2007-12-18T18:26:23Z

Hi all,
I am very happy to type 'cnxs' on google.com.br, and found our name in the first page.
Thanks to meta tags =)
See you.

Installing Postgresql on Ubuntu 7.10

2007-12-16T21:19:54Z

Hi Sirs.

Now I am using Ubuntu 7.10 and my favorite Database Management System is Postgresql.

The best tutorial that I found is the Ubuntu tutorial about Postgresql and pgAdmin installation.

Very easy to learn by every developer. This tutorial shows how to install both the Database Management System and the Administration and Development Platform.

https://help.ubuntu.com/community/PostgreSQL

Easy to install and configure.

Just one line to install the 'Sophisticated open-source Object-Relational DBMS' and the 'graphical Open Source management, development and administration tool'.

$ sudo apt-get install postgresql pgadmin3

Other two commands to configure your new account:

$ sudo -u postgres psql template1
$ template1=# ALTER USER postgres WITH ENCRYPTED PASSWORD '<***password***>';

I recommend this tutorial =]

See you.

Filter sensitive information on logs

2007-12-13T21:44:39Z

Hi Sirs,

a very important thing that I can remember about security on web environment is 'logs'.

Ruby on Rails provide a very simple way to protect us of store sensitive information on the logs. Every information that goes through the parameters is writed on the log. In websystem development phasis logging information is important, but in the production phasis, is dangerous. Hackers in general can take information through many ways. Our tip to protect sensitive information in the logs is the method 'filter_parameter_logging' of the Class ActionController::Base.

ActionController is the mother class of every controller in your applications, so the best place to call it is in the app/controllers/application.rb.

Just insert this example line of code:

filter_parameter_logging :password, :password_confirmation

and than it replaces the values of all keys that matches the arguments name with "[FILTERED]", and you are protecting your informations in the logs.

Is a simple tip, but very important. Do not forgot to use it.

See you.

Rails 2

2007-12-10T00:12:04Z

Hi all,

I am very happy to give you the notice that our website here, is installed in Ruby on Rails 2.0.1 just 3 days after the release is finished. Installed and tested in the weekend =].

That's the way that the CNXS team likes to work. Ever living on the edge.

Congratulations to Ruby on Rails Development Staff and to CNXS Team.

See you sirs.

A good testing idea

2007-12-10T00:05:34Z

The approach of Douglas Sellers about testing their AJAX heavy system really sounded to me as an excellent idea. I can imagine in the future this being adopted by more and more web systems, as they embrace javascript for building RIAs more and more.

Essentially they have built a DSL on top of selenium using ruby (yay), for testing the AJAX stuff on their page, aiming at easiness to write the tests, trading the complexity of writing the tests for the complexity of the DSL itself, trying even for the non technical people on the company to write their own tests.

Really recommended for a fresh and no nonsense view on testing.

Freedom of our thoughts and works

2007-12-10T00:04:34Z

If you have not yet seen or read Lawrence Lessig, I urge you to. I'll try to make a small analysis on his work, just as a appetizer for for those still ignorant about it :).

His point is that we are moving away from a read-only culture, where the content is controlled and governed by producers and broadcasters, and consumers have little saying on the content, to a read-write culture.

What is a read-write culture? One that is governed by the freedom to modify. Where distribution costs are next to zero, and each individual now has a shot at producing her own content, and to mix and remix work of a third party, without being worry of a lawsuit. A new (we could argue that for most of the human history it has been that way, just in the 20 century the paradigm has changed) way of looking at our own freedoms, and how we can not only consume work of others, but create ours, based or not on all the free content available.

Introduction to cnxs

2007-12-10T00:03:34Z

Hey Folks. This is the first post, so I'll manage to keep myself away from technological ramblings and just say some words about us and our purpose here.

This is not exactly a company, it is more a group of friends with some mutual interests who got together because they thought it would be fun to do it and each could learn and teach the others a lot.

What bought us together here is a passion for developing good software, with tools that help us not only accomplish this, but to have some fun while we are doing it. We like what we do, and I can say that we don't view this as a job, but as a pleasant thing, which fortunately happens to be payed sometimes (yay). I think that's that for now, but we'll be back tomorrow.

Hugs everyone, and welcome to the joy of connected thoughts :D