Welcome to my page as a writer. This place is where I keep documentation about my career as a non-fiction writer. It's an under development career, and because of that, I consider this a sacred place in the sense of maintaining the level of compassion that is necessary for one to build a writing journey.
Here you will find references for works where I helped public corporations. For these works, have I received feedback and participated in a collaborative process. On the other hand, I have also included other not-so-precise works, generally unknown. These are anyway content that I consider as important since there is always a strange work before a known and popular work is made.
This section embodies my intention to cover entrepreneurship, especially the field of early-stage startup development. The themes developed in the following articles are generally derived from real challenges or situations that I have observed, lived, or when interacting and learning with other entrepreneurs and companies.
The following technotes are in-progress annotations related to learning activities. You can think of them as by-products derived from the learning activities related to my role as a software engineer. Although not reviewed, they are posted in Github because they may contain substantial content or samples that can help developers explore modern technologies and frameworks such as ReactJS, JavaScript, Node.JS, and more.
TelaSocial was an open-source project that I founded in Brazil in 2009. The project consisted of using parts of the Firefox engine, specifically the Gecko/XULRunner engine, to bring a presentation experience delivered through TV appliances. The project gained momentum in Brazil, especially at universities and science parks. It became a solution that helped communication departments create a social-aware content experience used in indoor communications. Tela Social was the antithesis from the traditional advertising TVs used at airports, fundamentally different from the market concept known as digital signage. In the context of universities, this project brought the voice of locals to their spaces. It replaced paper-based indoor panels in walls and created a more connected community-friendly medium.
My contribution to Mozilla dated from 2000 when I started contributing to the original Mozilla developer site. My goal was to help developers to enjoy demonstrations related to modern web standards. At the time, the effort of writing about standards was a bit like navigating against the status quo. Today, however, we use all these standards as building blocks for all sites. The developer-writer role is, therefore, a strategic role. Our channels are sacred places because they usually serve as a space that pulls honest conversations with developers and open-minded people.
I should also acknowledge that writing for APIs and SDKs is not a one-person job. Therefore, these works are usually published by the complex workflow, or ecosystem, of publishing involving technologies and many participants such as editors and peer reviewers. As a technology evangelist, my job was to be in the center, between browser engineers, customers (in this case, developers), and quality assurance.
After the first browser wars, and Netscape had released their open source (Mozilla) project, a team of evangelists was assembled to inspired and help developers to write standards-compliant code. I was part of this new team, in the days that Netscape browser had 2% of marketshare. We helped thousands of developers that joined us in the fight against the dark forces of the web (non-standards web pages). We designed a movement and supported the direction that aligned with a much better future, a future where Firefox emerged bringing back a balance, and competition, to the browser's world.
As a technote producer and content writer my daily activities involved producing sample code, demonstrations, presentations, and articles. Other activities included peer-reviewing other articles and organizing the strategy and documentation schedule for a variety of documentation categories. In this context I was a technical writer, software engineer, and category editor to categories such as DOM, JavaScript, XML, and more.
Back in the golden days of the web, before Google, in the days of early Yahoo!, Lycos and Altavista; I joined pioneers in the evangelism field, to show the world how to make dynamic web pages. That was the beginning of my career as a technology evangelist and writer — it was also my first contact with English writing and the idea of collaborative writing.
My involvement as a technote writer emerged from the need to explain to developers how to accomplish particular web effects. In this regard, it is common to use a variety of communication elements — sample codes, diagrams, and more. For example, check how a 3d visualization helped to explain how to achieve the results.
This work was only possible due to the support from early evangelists part of the Nestscape team.
I am a developer, writer, and entrepreneur. I consider myself a specialist and a generalist. My interest in innovation is the essential part of this story. After that it comes a strong need to present, to document, to make available the bits and pieces that can enable developers to act. I love communication.