<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vinícius Pereira de Oliveira on Medium]]></title>
        <description><![CDATA[Stories by Vinícius Pereira de Oliveira on Medium]]></description>
        <link>https://medium.com/@vinitech?source=rss-1d7604386893------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SDCTJFR7gqrCa9Q8x1cCDQ.jpeg</url>
            <title>Stories by Vinícius Pereira de Oliveira on Medium</title>
            <link>https://medium.com/@vinitech?source=rss-1d7604386893------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:41:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinitech/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Java — Technology resistant to economic cycles]]></title>
            <link>https://vinitech.medium.com/java-technology-resistant-to-economic-cycles-2df0dac0e1ed?source=rss-1d7604386893------2</link>
            <guid isPermaLink="false">https://medium.com/p/2df0dac0e1ed</guid>
            <category><![CDATA[quarkus]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[it-market]]></category>
            <category><![CDATA[market]]></category>
            <category><![CDATA[economy]]></category>
            <dc:creator><![CDATA[Vinícius Pereira de Oliveira]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 17:13:55 GMT</pubDate>
            <atom:updated>2023-04-24T17:13:55.876Z</atom:updated>
            <content:encoded><![CDATA[<h3>Java — Technology resistant to economic cycles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*ZBzEEGn_lcdzya85NHLRKw.png" /></figure><p><em>Would the Java platform be a technology resistant to the different economic cycles that have occurred since its release in 1995?</em></p><p>Firstly, in order to understand the reasoning behind this article, we must define what economic cycles are and what it means to be resistant to them.</p><p><em>Note: This article may be especially important for those planning to focus their studies on a programming language and considering Java. The goal is to show how relevant the platform is in the current and future technology market.</em></p><p><strong>Economic Cycles: </strong>In a very simple way, since this is not the focus of this article, economic cycles are the set of different phases of economic activity that can be specific to a particular country or even related to global economic activity. They are moments of expansion, slowdown, stagnation, recession, and recovery. There may be some variation in the definition/nomenclature of these phases, but the essential idea is that cycles are distinct phases of the economy within a period of time.</p><p>Depending on specific actions of each government, central banks, or other variables, the phases of these cycles may not follow exactly this order; a country may, for example, go through a period of stagnation and then move to a period of recovery without necessarily going through a recession. However, cycles tend to occur one way or another. Generally, the economy expands when individuals, families, and businesses consume more, leading to more demand for products and services and thus a “heated” economy. After a while, there is a slowdown and possible stagnation (which can also be considered in many cases as “financial crises”) and eventually a recession, and finally recovery, when the cycle is ready to start again.</p><p><strong>Resistance to economic cycles: </strong>Products, services, companies, families, and individuals go through the phases of economic cycles in different ways. Some are more fragile and exposed while others are more resistant. A classic example that can serve as an analogy to the reasoning of this article is the automotive industry.</p><p>In the phase of economic expansion and high consumption, automobile brands tend to make good sales of all or almost all the models launched, and some bring good profits for short periods of time. In the phase of economic slowdown, some vehicle models maintain stronger sales, while others have a decrease in sales. Finally, in economic crises, models of vehicles that are already consolidated in the market and approved by a portion of consumers, with upgrades and evolution in the latest versions, end up maintaining sales while many others do not. We can say that the vehicle models that sell (even if less) even in financial crises are resistant to economic cycles.</p><h3>About Technology</h3><p>How do the paragraphs above relate to Java as a platform?</p><p>Programming languages are technological tools created with the goal of developing software. There is a wide range of programming languages, and usually they are created to meet specific needs. In the case of Java, the main motivation behind its creation in the 90s was the need to run the same source code on different platforms and/or operating systems (OS) such as Windows, Linux, Unix, MacOS, etc. All the OS needs is the JVM (Java Virtual Machine), and the “magic” happens.</p><p><em>“Write once, run anywhere.”</em></p><p>This was the launch slogan of the Java platform.</p><p>But this was in the 90s when we did not yet have advanced computer virtualization technologies or the concept of containers such as Docker.</p><p>If today (March/2023) we have already advanced significantly in tools that allow executing isolated code in containers, why did Java continue and still continues to be a widely used platform for maintaining projects and also for creating new software projects?</p><p>Java as a programming language and platform performed very well in its main objective in the 90s and therefore gained a very large share in the market of applications of all kinds that needed to run on different platforms.</p><p>It can be considered that this advantage (<em>running on the JVM</em>) allowed the Java platform to be inserted into small, medium, and large projects of large companies worldwide very quickly. However, Java went further because it consolidated itself as a well-architected object-oriented language and despite the fact that the JVM consumed too many hardware resources from servers, the final result when the application architecture was well designed and the code was well written, were high-performance and reliable corporate applications.</p><h3>Obstacles in the way</h3><p>The 90s were an interesting time for the Java platform, but it grew even more in the 2000s. However, it’s worth noting that in the years 2000/2001, the internet bubble burst, which became known as the “internet bubble” or the “.com bubble”.</p><p>The Java platform, along with others such as PHP, sought to keep up with the growth of the then-recent internet. The novelty and potential of the internet caused investors to inject high financial volumes into all kinds of “innovative” projects for the new era of the web.</p><p>As in any financial bubble, the fact is that many of the companies did not have truly solid businesses, and when the investor market of Nasdaq (the US technology exchange) realized that many of the supposed technology companies were not viable, projects were canceled and companies were closed. The Java platform and others implemented support for web development in their structure. Around 1997, Java Servlet Specification version 1.0 was implemented, which allowed the creation of dynamic web applications with support for the HTTP protocol. Certainly, many of the companies whose projects were terminated due to the internet companies’ crisis in 2000 and 2001 used Java among other technologies to develop their products.</p><p>The fact that a huge financial crisis shook projects did not stop the evolution of technological platforms thinking about the future and growth of the web, including, of course, the Java platform. Companies that remained solid in the market (whether or not in the technology industry) continued to need more and more applications that ran on servers connected in different geographical regions, Java already had a large market and ended up being the natural choice for new projects and challenges in many cases. Since 1998, the Java developer community has had the JCP (Java Community Process), which is a community-led collaboration process to develop technical standards for the Java platform.</p><p>JCP members include companies, organizations, and individuals who want to contribute to the development of the Java platform. Anyone can become a JCP member, and there are different levels of membership available. It’s important to note that different companies have always had a significant contribution to this process, and among them, we can mention IBM, Nokia, Oracle, Microsoft, SAP, Fujitsu, among many others. The giants who have always contributed to the world of software development hold the Java platform in high esteem.</p><h3>Year 2008, new global financial crisis followed by changes in the technology industry</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*dxNPwjLHp7tBCzFEtqJU1w.jpeg" /></figure><p>The technological evolution did not stop after the 2000/2001 financial crisis; on the contrary, it continued to advance. In 2006, Amazon Web Services (AWS) emerged, bringing with it a new concept of Cloud Computing, a milestone in the way companies and users utilized the internet. On the web application development side, the adoption of various technologies beyond Java, such as PHP and Javascript (which greatly facilitated the development of dynamic web pages), was rapidly growing.</p><p>In 2008, a new financial crisis erupted (<em>the subprime crisis in the USA</em>), which initially involved large investment banks. This time, the crisis was more severe because the markets were already more interconnected, and the effects were felt globally. One of the ways found by government authorities and central banks worldwide was to save the banks from bankruptcy by injecting money into them. In the decades that followed, <em>Quantitative Easing(QE) </em>was implemented, which was the act of flooding the economy with money while reducing the reference interest rate to avoid a general recession in the economy. Yes, it was an attempt to try to control the economic cycle or at least avoid the most painful part, which in this case would be truly painful globally.</p><p>Through QE initiated by several central banks in response to the 2008 financial crisis, especially the US Federal Reserve and the European Central Bank, credit became increasingly accessible, encouraging more and more risky projects and ventures. Investors had access to low-interest credit and returned to investing heavily in the new era of startups. The rule was no longer exactly to create a proven profitable business, but rather a business that would scale, grow rapidly, and dominate as much of the market as possible. Talented and not so talented entrepreneurs entered the race to “prove” that their company was the next one to be valued at $1 billion and thus attract heavy rounds of investment. <em>Uber, Netflix, WeWork, and Spotify</em> are some of the fruits of this era, but the market was flooded with many supposedly innovative new companies with different cultures from the old technology companies.</p><p>On the technological side, the Java platform remained strong but saw its space rapidly decrease. In the new world of innovation race, the area of software development and engineering saw the emergence of new types of architectures, evolution of some existing ones, and spectacular tools that allowed projects to scale quickly and efficiently.</p><p>One thing that cannot be denied is that cheap credit and the frenzied culture of fast-growing startups without profitability guarantees brought various technical challenges to software engineering teams worldwide. Java no longer reigned supreme in the new world; on the contrary, it now had new competitors (<em>NodeJS, Golang</em>) and some old ones (<em>.Net framework, Python</em>), while others like PHP, although still active, lost ground.</p><p>Innovative projects required identity, and showing the visual identity of a product goes through websites and web applications with a bold, modern, and fluid look. It wouldn’t be very productive to bet on JSP’s or JSF. Java was taken out of the scene, and Javascript dominated the frontend scene with a meteoric rise.</p><p>New Javascript frameworks emerged every week, one promising more productivity than the other. Java was still a frequent choice on the backend, and frameworks like Spring Boot helped keep the Java stack alive even in many startups, but it wouldn’t be wrong to say that Java was still even more firm within the same traditional big companies, now bringing platform evolutions. The tools used to build the next $1 billion company varied widely, and usually the hype of the latest fashionable technology became the code base of new and <em>“promising”</em> businesses.</p><p>All new aspiring software developers had “tons” of content about the latest <em>Javascript framework</em> in the market, bootcamps that taught how to become a senior developer in 1 year and master frontend and backend technologies, what we know as Full-Stack Developers because the market was immensely lacking these professionals. Yes, indeed it was and to some extent still is, but the hype directed novice developers to overly focus on newer technologies and programming languages while others, though also had many opportunities, did not receive as much attention from learners.</p><p>All new aspiring software developers had “tons” of content about the latest Javascript framework in the market, bootcamps that taught how to become a senior developer in 1 year and master frontend and backend technologies, what we know as Full-Stack Developers because the market was immensely lacking these professionals. Yes, indeed it was and to some extent still is, but the hype directed novice developers to overly focus on newer technologies and programming languages while others, though also had many opportunities, did not receive as much attention from learners.</p><h3>Year 2022 and 2023 — Inflation and credit crisis</h3><p>Some economists and people who had been following the financial market since before 2008 had continuously warned that the injection of money into the economy from central banks and the low interest rate maintained for so long would probably culminate in inflation that would be difficult to control. To make things more dramatic, the world experienced a global pandemic in 2020 and the beginning of a war involving a nuclear power nation (Russia) and Ukraine in 2022. <strong><em>Boom!</em></strong></p><p>To contain the inflation that took hold of the globe from 2021, the same central banks that allowed cheap credit and money injection into the economy began to “turn off the tap” and gradually and continuously raise interest rates.</p><p>The mass of startups that only thought about growing fast seeking new rounds of investments and never discovered how the business would give solid profit, began to see their investors abandon the risk of investing in “super innovative projects”. Without the money from investors, even consolidated companies like Google, Amazon, Microsoft, and others began to reduce expenses, cancel projects, and … lay off employees. What about startups that did not have cash flow as powerful as the Big Techs? Layoffs and more layoffs everywhere.</p><h4><strong>Legacy of an era</strong></h4><p>Again, I would like to point out that the period of cheap credit and the trend of startups seeking scalability and performance in their applications brought a world of new technical challenges and this was incredibly beneficial for the software industry. Older programming languages like Java, Python, and Javascript (in frontend layers) had new horizons to explore through developer communities and emerging challenges, newer languages like Nodejs and Golang showed their full potential for problem-solving.</p><p>The Java platform saw Spring Boot dominate development with this stack and recently has seen Quarkus grow and gain a lot of market share, all in response to technical challenges related to business challenges. The software industry as a whole gained a lot, but what now? What to expect from 2023 onwards?</p><h4>The legacy can be the seed of a future</h4><p>I believe that the hype of new languages and frameworks in the visualization layer of applications (frontend), whether web or mobile, created the expectation that the future of software development passed by quickly learning and mastering such technologies since there were indeed many vacancies, especially in startups.</p><p>Now, with the market correction in a scenario where all companies go through some financial difficulty, it is realized that solid companies with business models already consolidated for a long time need to continue evolving and investing in technology and guess what, many of them never abandoned the Java platform. The community knows the legacy of what was done in the project that started led by James Gosling in the 90s. Some companies did adopt the new programming languages of the moment in some projects, and many of them heavily invested in hype technologies, but the corporate applications that are essential to keep the operations of large businesses worldwide tend to be maintained and updated with Java, C#, and technologies that for many of the new generation were considered <em>“extinct languages.”</em></p><p>Obviously, many new projects will not use Java and new technologies have emerged, proven to be efficient and will also have a chance to consolidate themselves.</p><p>Startups that had a solid business with real potential for profitability should remain, and many of them also bet on the Java platform. The economy itself, at some point, should enter the recovery phase and new projects that will emerge when the economy heats up again will certainly consider the maturity and evolution of the technological platforms available.</p><p>The Java platform, considering the core of the programming language, has received great attention from both Oracle and the Eclipse Foundation. The platform has been constantly updated with new features that demonstrate a concern for keeping Java language modern, reliable, productive, and flexible without losing its robust architecture and already attested for over 20 years of use in the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*yQQM1_sK2Io5nlPa4vYYBQ.png" /></figure><p>RedHat has been doing a spectacular job with the <strong><em>Quarkus Framework</em></strong>, making Java a friendly, flexible, and economical alternative for cloud environments. VMware maintains the excellent quality of the <strong><em>Spring Boot Framework</em></strong>.</p><p>While software engineering is still mostly a field where people (and not AIs) define the best tools to maintain or start new projects, the Java platform will certainly remain strong in the software industry. If you already have a certain level of mastery of the Java platform, it is more than important to learn new technologies and evolve professionally. However, if you are thinking of starting to study or even deepen your knowledge in a programming language considering the job market, I believe this article can be useful in demonstrating that a well-built legacy based on solid foundations is generally resilient and long-lasting, and in this case, Java can be an interesting choice, although later on, career evolution may bring challenges of learning new and different technologies.</p><p>I hope the article has been useful, and thank you for reading.</p><p><strong><em>References:</em></strong></p><ul><li><a href="https://exame.com/negocios/carros-populares-voltam-a-liderar-o-mercado-confira-os-mais-vendidos/">Automotive industry — variation in model sales in times of crisis.</a></li><li><a href="https://jcp.org/en/participation/committee">JCP (Java Community Process) Committee.</a></li><li><a href="https://startups.com.br/noticias/veja-quais-startups-enxugaram-operacoes-e-demitiram-no-ultimo-ano/">Layoffs in startups.</a></li><li><a href="https://www.federalreserve.gov/monetarypolicy/bst_recenttrends.htm">Federal Reserve’s credit and liquidity program since 2008</a>.</li><li><a href="https://www.tiobe.com/tiobe-index/">Programming Languages Ranking.</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2df0dac0e1ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Java — Uma tecnologia resistente aos ciclos econômicos]]></title>
            <link>https://vinitech.medium.com/java-uma-tecnologia-resistente-aos-ciclos-econ%C3%B4micos-82dcf5111da0?source=rss-1d7604386893------2</link>
            <guid isPermaLink="false">https://medium.com/p/82dcf5111da0</guid>
            <category><![CDATA[aprender-programação]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[engenharia-de-software]]></category>
            <category><![CDATA[mercado-de-trabalho]]></category>
            <dc:creator><![CDATA[Vinícius Pereira de Oliveira]]></dc:creator>
            <pubDate>Fri, 31 Mar 2023 17:16:03 GMT</pubDate>
            <atom:updated>2023-05-04T16:54:04.945Z</atom:updated>
            <content:encoded><![CDATA[<h3>Java — Uma tecnologia resistente aos ciclos econômicos</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*ZBzEEGn_lcdzya85NHLRKw.png" /></figure><p><em>Seria a plataforma Java uma tecnologia resistente aos diferentes ciclos econômicos que ocorreram desde o seu lançamento no ano de 1995 ?</em></p><p>Primeiramente, para o correto entendimento do raciocínio deste artigo temos que definir o que seriam ciclos econômicos e o que significa ser resistente a eles.</p><p><strong><em>Observação:</em></strong><em> este artigo pode ser especialmente importante para quem planeja focar estudos em uma linguagem de programação e está considerando a linguagem </em><strong><em>Java. </em></strong><em>O objetivo é mostrar o quão relevante é a plataforma no atual e futuro mercado de tecnologia.</em></p><h4><strong>Ciclos Econômicos:</strong></h4><p>De forma muito simples, visto que este não é o foco deste artigo, ciclos econômicos são o conjunto de diferentes fases da atividade econômica que pode ser de um país específico ou mesmo relativo a atividade econômica global. São momentos de <em>expansão, abrandamento, estagnação, recessão e recuperação</em>. É possível encontrar alguma variação quanto a definição/nomeclatura destas fases, mas a ideia essêncial é esta, os ciclos são fases distintas da economia dentro de um período de tempo.</p><p>A depender de ações específicas de cada governo, bancos centrais ou de outras variáveis as fases destes ciclos podem ainda não seguir exatamente esta ordem, um país pode por exemplo passar por um momento de estagnação e logo passar a um momento de recuperação sem passar necessariamente por uma recessão, entretanto, os ciclos tendem a ocorrer de uma ou outra maneira. De uma maneira geral a economia se expande quando indivíduos, famílias e empresas consomem mais e isto leva a mais demanda por produtos e serviços e desta forma temos uma economia “aquecida”, depois de um tempo ocorre o abrandamento e possível estagnação (<em>o que também pode ser considerado em muitos casos como “crises financeiras”</em>) e eventualmente uma recessão e por fim a recuperação, quando o ciclo está pronto a ser iniciado novamente.</p><h4><strong>Resistência aos ciclos econômicos:</strong></h4><p>Produtos, serviços, empresas, famílias e indivíduos atravessam as fases dos ciclos econômicos de maneiras diferentes. Alguns estão mais fragilizados e expostos enquanto outros resistem mais. Um exemplo clássico e que pode servir de analogia ao raciocínio deste artigo, é a indústria automotiva.</p><p>Na fase de expansão econômica e de alto consumo, as marcas de automóveis tendem a fazer boas vendas de todos ou quase todos os modelos lançados e alguns trazem bons lucros por curtos períodos de tempo. Já na fase de abrandamento da economia alguns modelos de veículos mantem as vendas mais fortes, enquanto outros modelos tem queda nas vendas. Por fim, em crises econômicas geralmente modelos de veículos já consolidados no mercado e aprovados por uma parcela de consumidores, com upgrades e evolução nas versões mais recentes, estes acabam por manter vendas enquanto tantos outros não. Podemos dizer que os modelos de veículos que vendem (ainda que menos) mesmo em crises financeiras são resistentes aos ciclos econômicos.</p><h4><strong>Sobre a tecnologia</strong></h4><p>Como exatamente os parágrafos acima se relacionam ao <em>Java</em> enquanto plataforma ?</p><p>Linguagens de programação são ferramentas tecnológicas criadas com o objetivo de desenvolver software. Existe uma gama abrangente de linguagens de programação e geralmente as mesmas são criadas para satisfazer necessidades específicas, no caso do Java, a <em>motivação principal</em> por trás do projeto de criação nos anos 90 foi a necessidade de executar um mesmo código-fonte em diferentes plataformas e/ou Sistemas Operacionais (SO) como <em>Windows, Linux, Unix, MacOS, etc</em>. Basta que o SO tenha a JVM (<em>Java Virtual Machine</em>) e a “mágica” acontece.</p><p><em>“Escreva o código uma vez, execute em qualquer lugar.”</em></p><p>Esse foi o slogan de lançamento da plataforma Java.</p><p>Mas isto foi nos anos 90 quando ainda não tínhamos tecnologias avançadas de virtualização de computadores ou o conceito de containers como por exemplo o Docker.</p><p>Se hoje (<em>março/2023</em>) já avançamos bastante em ferramentas que permitem executar código isolado em containers, <strong><em>por qual motivo o Java continuou e ainda continua sendo uma plataforma muito utilizada para manter projetos e também para criar novos projetos de software ?</em></strong></p><p>O Java enquanto linguagem de programação e plataforma se saiu muito bem quanto ao seu objetivo principal nos anos 90 e portanto <strong><em>ganhou uma fatia muito grande no mercado de aplicações de todo tipo</em></strong>, que precisavam executar em diferentes plataformas.</p><p>Pode-se considerar que esta vantagem (<em>executar sobre a JVM</em>) permitiu a plataforma Java estar inserida em projetos de pequeno, médio e grande porte de grandes empresas no mundo inteiro muito rapidamente. No entanto, o Java foi além pois se consolidou como uma linguagem orientada a objetos bem arquitetada e a despeito de a JVM consumir demasiados recursos de hardware dos servidores, o resultado final quando a arquitetura das aplicações era bem desenhada e o código bem escrito, eram aplicações corporativas de alta performance e confiáveis.</p><h4>Os obstáculos no caminho</h4><p>A década de 90 foi interessantes para a plataforma Java, mas a partir dos anos 2000 ela cresceu ainda mais, porém é interessante pontuar que nos anos de 2000/2001 estourou a bolha financeira das empresas de internet, o que ficou conhecido como a “<em>bolha da interne</em>t” ou a “<em>bolha .com</em>”. A plataforma Java, assim como outras como PHP buscavam acompanhar o crescimento da então recente Internet. A novidade e potencial da internet fizeram com que investidores injetassem altos volumes financeiros em todo tipo de projetos <em>“inovadores” </em>para a nova era da web<em>. </em>Como em toda bolha financeira o fato é que muitas das empresas não tinham negócios realmente sólidos e quando o mercado de investidores da Nasdaq<em> (bolsa de tecnologia dos EUA) </em>compreendeu que grande parte das supostas empresas de tecnologia não eram viáveis, projetos foram cancelados e empresas foram encerradas. A plataforma Java e outras implementaram em sua estrutura suporte para desenvolvimento web. Por volta do ano 1997 foi implementada a <em>Java Servlet Specification version 1.0</em> que permitia a criação de aplicações web dinâmicas com suporte ao protocolo <em>http</em>. Certamente muitas das empresas cujos projetos foram encerrados devido a crise das empresas da internet em 2000 e 2001, usavam entre outras tecnologias, a linguagem Java para desenvolver seus produtos.</p><p>O fato de uma enorme crise financeira ter abalado projetos não parou a evolução das plataformas tecnológicas pensando no futuro e crescimento da web, dentre elas obviamente a plataforma Java. Empresas que se mantiveram sólidas no mercado (<em>sendo ou não do ramo de tecnologia</em>) continuavam necessitando cada vez mais de aplicações que executassem em servidores conectados em diferentes regiões geográficas, Java já tinha grande mercado e acabou sendo em muitos casos a escolha natural para novos projetos e desafios. Desde 1998 a comunidade de desenvolvedores Java já contava com o JCP (<em>Java Community Process</em>) que é um processo de colaboração liderado pela comunidade para desenvolver padrões técnicos para a plataforma Java. Os membros do JCP incluem empresas, organizações e indivíduos que desejam contribuir para o desenvolvimento da plataforma Java. Qualquer pessoa pode se tornar um membro do JCP, e existem diferentes níveis de associação disponíveis. Importante ressaltar que empresas distintas sempre tiveram grande contribuição nesse processo e dentre algumas podemos citar <em>IBM, Nokia, Oracle, Microsoft, SAP, Fujitsu entre tantas outras</em>. As gigantes que sempre contribuíram com o mundo do desenvolvimento de software tem alta estima pela plataforma Java.</p><h4>Ano de 2008, nova crise financeira global seguida de mudanças na indústria de tecnologia</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*dxNPwjLHp7tBCzFEtqJU1w.jpeg" /></figure><p>A evolução tecnológica não parou após a crise financeira de 2000/2001, ao contrário a evolução avançou. Em 2006 emergia a Amazon Web Services (AWS) que trazia consigo um novo conceito de Computação em Nuvem, um marco na forma como empresas e usuários utilizavam a internet. Do lado do desenvolvimento de aplicações web, crescia rapidamente a adoção de diversas tecnologias além do Java, como PHP e Javascript (<em>que facilitava muito o desenvolvimento de páginas web dinâmicas</em>).</p><p>Em 2008 estourou uma nova crise financeira (<em>crise do subprime nos EUA</em>) que envolvia inicialmente grandes bancos de investimento, desta vez uma crise mais grave pois os mercados já estavam mais interconectados e os efeitos foram sentidos globalmente. Uma das formas encontradas por autoridades governamentais e bancos centrais no mundo inteiro foi primeiramente salvar os bancos da falência injetando dinheiro nos mesmos e nas décadas que se seguiram foi a <em>Flexibilização Quantitativa </em>que na prática era o ato de inundar a economia com dinheiro ao passo que se reduzia a taxa de juros de referência para evitar uma recessão generalizada da economia<em>. Sim, foi uma tentativa de tentar controlar o ciclo econômico ou ao menos evitar a parte mais dolorosa que neste caso seria realmente dolorosa a nível global.</em></p><p>Através da <em>Flexibilização Quantitativa</em> iniciada por vários bancos centrais para dar resposta a crise financeira de 2008, em especial o Banco Central dos EUA<em> (Federal Reserve) e</em> o Banco Central da Europa, o crédito ficou cada vez mais acessível e isto encorajou cada vez mais projetos e empreendimentos de risco. Investidores tinham acesso a crédito com juros baixos e voltaram a investir pesado na nova era das <em>startups. </em>A regra já não era exatamente criar um negócio comprovadamente lucrativo mas sim um negócio que viesse a escalar, crescer rapidamente dominando o máximo de mercado possível<em>. </em>Empreendedores talentosos e outros nem tanto entravam na corrida para “provar” que sua empresa era a próxima a ser estimada em 1 bilhão de dólares e assim angariar pesadas rodadas de investimentos. <em>Uber, Netflix, WeWork, Spotify</em> são alguns dos frutos dessa era, mas o mercado foi inundado de muitas novas empresas supostamente inovadoras com culturas diferentes das antigas empresas de tecnologia.</p><p>No lado tecnológico, a plataforma Java continuava firme, mas viu seu espaço diminuir rapidamente. No novo mundo da corrida por inovação, a área do desenvolvimento e engenharia de software viu surgir novos tipos de arquiteturas, evolução de alguns já existentes e ferramentas espetaculares que permitiam escalar projetos de forma rápida e eficiente. Se tem algo que não se pode negar é que o crédito barato e a cultura alucinada das startups de crescimento rápido sem garantias de lucratividade, trouxe desafios técnicos dos mais diversos para as equipes de engenharia de software no mundo inteiro. O Java já não reinava soberano no novo mundo, ao contrário, agora tinha concorrentes novos (<em>NodeJS, Golang</em>) e alguns já antigos (<em>.Net framework, Python</em>) ao passo que outros como PHP embora ainda ativos perderam espaço. Projetos inovadores exigiam identidade e mostrar a identidade visual de um produto passa por websites e aplicações web com visual arrojado, moderno, fluído. Não seria muito produtivo apostar as fichas em JSP’s ou JSF. O Java foi retirado de cena e o <strong><em>Javascript</em></strong> dominou o cenário <em>frontend </em>com ascensão meteórica. Novos frameworks Javascript surgiam a cada semana, um prometendo mais produtividade do que o outro. Java ainda era uma escolha frequente no backend, frameworks como o<em> Spring Boot </em>ajudaram a manter a stack Java viva mesmo em muitas startups, mas não seria errado dizer que Java continuava ainda mais firme dentro das mesmas tradicionais grandes empresas, só que agora trazendo as evoluções da plataforma. As ferramentas usadas para contruir a próxima empresa de 1 bilhão de dólares variavam muito e geralmente o hype da nova tecnologia da moda se transformava na base de código de novos e “promissores” negócios.</p><p>Todos os novos aspirantes a se tornar um Desenvolvedor de Software tinham “<em>toneladas</em>” de conteúdo sobre o mais recente framework Javascript de mercado, bootcamps que ensinavam a se tornar um <em>sênior developer</em> em 1 ano e dominar tecnologias de frontend e backend, o que conhecemos por <em>Full-Stack Developers </em>porque o mercado estava imensamente carente destes profissionais. Sim de fato estava e em algum nível ainda está, mas o hype direcionava novos desenvolvedores iniciantes a dar foco demasiado a tecnologias e linguagens de programação mais recentes enquanto outras, ainda que tivessem também muitas oportunidades, não receberam tanta atenção dos aprendizes.</p><h4>Ano de 2022 e 2023 — Inflação e crise de crédito</h4><p>Alguns economistas e pessoas que acompanhavam o mercado financeiro desde antes de 2008 continuamente alertavam que a injeção de dinheiro na economia vinda dos bancos centrais e taxa de juros mantida baixa por tanto tempo, provavelmente iria culminar em inflação difícil de ser controlada. Para deixar as coisas mais dramáticas, o mundo viveu uma pandemia global em 2020 e o início de uma guerra envolvendo uma potência nuclear (Rússia) e a Ucrância em 2022. <strong><em>Booom!</em></strong></p><p>Para conter a inflação que tomou conta do globo a partir de 2021 os mesmos Bancos Centrais que permitiram o crédito barato e injeção de dinheiro na economia começaram a “<em>fechar a torneira</em>” e subir juros gradativa e continuamente.</p><p>A massa de startups que só pensava em crescer rápido buscando novas rodadas de investimentos e nunca descobria como o negócio daria lucro sólido, começou a ver seus investidores abandorarem o risco de investir em <em>“projetos super inovadores”. </em>Sem o dinheiro dos investidores mesmo empresas já consolidadas como Google, Amazon, Microsoft e outras começaram a reduzir despesas, cancelar projetos e… demitir funcionários.<br><strong><em>O que dizer de startups que não tinham fluxo de caixa tão poderoso quanto as Big Techs ? Demissões e mais demissões em todos os lados.</em></strong></p><h4>Legado de uma era</h4><p>Novamente eu gostaria de pontuar que o período de crédito barato e a moda de startups que buscavam escabalidade e performance em suas aplicações trouxe um mundo de novos desafios técnicos e isso foi incrivelmente benéfico para a indústria de software. Linguagens de programação mais atigas como Java, Python e Javascript (<em>nas camadas de frontend</em>) tiveram novos horizontes para explorar através das comunidades de desenvolvedores e desafios que surgiam, linguagens mais recentes como Nodejs e Golang mostraram todo o seu potencial para resolução de problemas.</p><p>A plataforma Java viu o Spring Boot dominar o desenvolvimento com esta stack e recentemente tem visto o Quarkus crescer a ganhar bastante mercado, tudo em resposta a desafios técnicos ligados a desafios de negócios. A indústria de software de maneira geral ganhou muito, mas e agora ? O que esperar de 2023 para frente ?</p><h4>O legado pode ser a semente de um futuro</h4><p>Acredito que o hype de novas linguagens e frameworks da camada de visualização das aplicações (<em>frontend</em>), sejam elas web ou mobile, criou a expectativa de que o futuro do desenvolvimento de software passava por aprender rapidamente e dominar tais tecnologias visto que de fato haviam muitas vagas principalmente em Startups. Agora, com a correção do mercado em um cenário em que todas as empresas passam por alguma dificuldade financeira, percebe-se que empresas sólidas com modelos de negócios já consolidados por bastante tempo precisam continuar evoluindo e investindo em tecnologia e adivinha, muitas delas nunca abandonaram a plataforma Java. A comunidade conhece o legado do que foi feito no projeto que começou liderado por <em>James Gosling</em> nos anos 90. Algumas empresas adotaram sim as novas linguagens de programação do momento em alguns projetos e muitas delas investiram pesado em tecnologias do <em>hype</em>, mas as aplicações corporativas e que são essenciais para manter a operações de grandes negócios no mundo inteiro ainda tendem a ser mantidas e atualizadas com Java, C# e tecnologias que para muitos da nova geração eram consideradas “<em>linguagens em extinção</em>”.</p><p>Obviamente que muitos novos projetos não vão utilizar Java e novas tecnologias surgiram, se mostraram eficientes e também terão a chance de se consolidar.</p><p>Startups que realmente tinham um negócio sólido e com real potencial de lucratividade devem permanecer, e muitas delas também apostaram na plataforma Java. A economia em si, em algum momento deverá entrar na fase recuperação os novos projetos que devem surgir quando a economia aquecer novamente certamente vão considerar a maturidade e evolução das plataformas tecnológicas disponíveis.</p><p>A plataforma Java, levando em consideração o core da linguagem de programação tem recebido grande atenção tanto da <em>Oracle</em> quanto da <em>Eclipse Foundation</em>, a plataforma tem recebido atualizações constantes com novas features que evidenciam a preocupação em manter a linguagem Java moderna, confiável, produtiva e flexível sem perder sua arquitetura robusta e já atestada por mais de 20 anos de uso no mercado.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*yQQM1_sK2Io5nlPa4vYYBQ.png" /></figure><p>A <em>RedHat</em> tem feito um trabalho espetacular com o <strong><em>Quarkus Framework</em></strong><em> </em><strong><em>tornando o Java uma alternativa amigável, flexível e economica para ambientes de Nuvem.</em></strong><em> </em>A <em>VMWare</em> mantém a ótima qualidade do <em>Spring Boot Framework</em>.</p><p>Enquanto a engenharia de software ainda é majoritariamente um campo onde pessoas (e não IA’s) definem as melhores ferramentas para manter ou iniciar novos projetos, a plataforma Java certamente vai se manter forte na indústria de software de modo que se você já tem um certo domínio da plataforma Java, é mais do que importante aprender novas tecnologias e evoluir profissionalmente, entretanto se você está pensando em iniciar os estudos ou mesmo aprofundar conhecimentos em uma linguagem de programação considerando o mercado de trabalho, penso que este artigo possa ser útil em demonstrar que um legado bem construído sob fundamentos sólidos geralmente é resiliente e duradouro e neste caso Java pode ser uma escolha interessante, ainda que depois a evolução de carreira possa trazer desafios de aprender novas e diferentes tecnologias.</p><p><strong><em>Referências:</em></strong></p><ul><li><a href="https://exame.com/negocios/carros-populares-voltam-a-liderar-o-mercado-confira-os-mais-vendidos/">Indústria automotiva — variação de venda de modelos em tempos de crise.</a></li><li><a href="https://jcp.org/en/participation/committee">Comitê JCP (Java Community Process)</a>.</li><li><a href="https://startups.com.br/noticias/veja-quais-startups-enxugaram-operacoes-e-demitiram-no-ultimo-ano/">Demissões em Startups.</a></li><li><a href="https://www.federalreserve.gov/monetarypolicy/bst_recenttrends.htm">Programa de crédito e liquidez do Federal Reserve desde 2008</a>.</li><li><a href="https://www.tiobe.com/tiobe-index/">Ranking Linguagens de Programação.</a></li></ul><p>Espero que o artigo possa ter sido útil e obrigado pela leitura.</p><p>Se quiser conhecer mais sobre os meus <strong>cursos</strong> voltados ao desenvolvimento com <strong>Java</strong>, basta acessar o link abaixo:</p><p><a href="https://linktr.ee/vinilearncodeclub"><strong>Cursos de Java com Spring Boot e Quarkus Framework</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82dcf5111da0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t just be a good Code Developer]]></title>
            <link>https://vinitech.medium.com/dont-just-be-a-good-code-developer-1f10256b2e00?source=rss-1d7604386893------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f10256b2e00</guid>
            <category><![CDATA[think-different]]></category>
            <category><![CDATA[change-mindset]]></category>
            <category><![CDATA[multitasking]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[thinking]]></category>
            <dc:creator><![CDATA[Vinícius Pereira de Oliveira]]></dc:creator>
            <pubDate>Wed, 06 Nov 2019 16:45:53 GMT</pubDate>
            <atom:updated>2023-03-27T12:53:42.189Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*CUNBs6_9b3CC9eX-88feew.jpeg" /></figure><p>The world is crazy my friend. Everything changes so fast!<br>Ok, our parents and our grandparents also thought so with great innovations of their time.</p><p>But, they were not in a globally linked society as we are.<br>We live with the many advantages and benefits of the internet when it is free, but the global connection goes far beyond the ability to socially interact globally.</p><p><strong>Have you ever wondered what the complete context of the software you are developing at this time? The context of this exactly moment ?</strong></p><p><em>Do you develop logistics software? A disruptive product for a startup? A critical health care system? A government software?<br>Maybe event-oriented microservices for online cryptocurrency, stock exchange or gold trading?</em></p><p>Have you sought information about geopolitical movement and how it affects imports and exports? Do you understand where exactly the new disruptive product fits into the inflated economic situation of nations? Will the startup be alive in 3 years?</p><p>It would be interesting if developers were more aware of how and where their art of coding (or responsibility for new bugs) can be important in healthcare and how citizen information should be secure as the state still holds our information.</p><p>I could be writing this just to tell you how much you would be improving your skills if you learn from each work context and how it would make you more desired by the job market. While this is true, my goal is another. Think about how productive this can be for you personally.</p><p>I’ve had conversations that were worth more than college classes with people from other areas in the same project. A non-technical person.<br>Before simply ignoring a Product Owner because he or she never wrote code, try to understand why <em>he/she</em> really needs software to be accurate.<br>You may learn much more about trading from power suppliers and have broader notions of the stock market than in specific formations/courses. <strong><em>It depends on how willing you are.</em></strong></p><p>Now think a little more…<br>You have decided to save money or invest in assets that your bank manager has guided. Most in own bank bonds.<br>However, you develop software for real estate market analysis, which measures variables such as inflation, population income growth, and interest rate. Your P.O. asks if your application architecture can deliver faster results for decision analysis. You can and should get as much technical information as possible to make the application fit the needs of the business, but if you seek to understand the business in detail, you may find that your bank income is ridiculous and perhaps it would be better to seek market income. Real estate… Or another.</p><p>Perhaps you understand the thinking logic behind the search for better investments and it is the beginning of something good that you don’t expect.<br>One thing that is evident today is that things are increasingly dependent on technology, software, and talented people to code. Your main skill will still be very valuable. But the world also needs people who are trying to be learning new things all the time, multidisciplinary thinking.</p><p>Believe me, even your technical decisions can be more assertive in seeking richer details within the context of your codes.</p><p>Thank’s for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f10256b2e00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Skin in the Game and Software Engineering]]></title>
            <link>https://vinitech.medium.com/skin-in-the-game-and-software-engineering-72dee2798258?source=rss-1d7604386893------2</link>
            <guid isPermaLink="false">https://medium.com/p/72dee2798258</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Vinícius Pereira de Oliveira]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 18:10:19 GMT</pubDate>
            <atom:updated>2023-03-27T12:27:01.450Z</atom:updated>
            <content:encoded><![CDATA[<p>I plan to write a few articles on this platform about the concepts of the <em>Black Swan, Antifragility</em>, and putting its own <em>Skin in the Game</em> from a software engineering standpoint. All of these concepts originated in the work of Nassim Taleb (a non-specialist and a non-intellectual), after all, over the last decades we have seen a number of highly educated media experts or intellectuals making decisions or even influencing people without take the risk for decisions or even worry about the consequences of their statements.</p><p>Perhaps that is why Nassim Taleb (<em>the author of Skin in the Game</em>) is not comfortable when given the label of intellectual or expert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/183/1*aYL9o5Iog7lWMxsgGpJUXg.jpeg" /></figure><p>But I said the point here is to raise reflections on the concepts mentioned above and their relationship to software engineering.</p><p>See this image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*8x-6wD6ukkoCcQvhyXL1bA.jpeg" /><figcaption>Source: Reuters</figcaption></figure><h3><strong>This is a Boeing 737 MAX 8 after a </strong>MCAS <strong>software crash</strong></h3><p><a href="https://www.boeing.com/commercial/737max/737-max-update.page"><em>Boeing takes responsibility and has worked to support the families of the victims.</em></a></p><p>I have been trying to meditate on the fact that software was never just code. This image should make any developer explicit what code matters. Software means bringing the real world, the physical world, into the virtual world and then merging them.</p><p>You may have codes that run on a console (<em>XBOX or PS</em>) on which you may be flying an airplane or a car. The software provides entertainment, works your emotions, and perhaps arouses a talent for skills.</p><p>But you also have code running on critical products like … commercial aircraft.</p><p>Code and software are never written to be appreciated as art in a museum, they usually interact with <strong>people</strong>.</p><p>In the book Skin in the Game, Nassim Taleb gives an example of the motivation we have in trusting our lives in the hands and professional competence of an airplane pilot while traveling on vacation or work and can usually only think of vacation or work during the flights.</p><p>The pilot is on the same plane as the passengers. He literally has his <em>Skin in the Game</em>.<br>If you have read or heard about <em>Antifragility</em>, you can imagine that it is not easy to write an article criticizing the civil aviation industry.<br>This industry is rigid, serious, efficient and is an example of how to learn from mistakes and become better.<br>But in this case, not even pilots who were on the same flight and lost their lives could have avoided it (evidence points to this and models are prohibited from flying), the central problem of these aircraft was software.</p><p>This is hard. Obviously, of course, who made the software, who tested the software, who worked hard to do the best in a critical software industry did not think that lives would be lost because of <strong>software</strong>. It’s just only code!</p><p>I believe the simple fact of working on critical software projects like this one evidence the extreme abiliity of the people involved, but…</p><p>Investigations into accidents with the model<br>737 MAX 8 are still ongoing and so, considering that investigations can actually get the concrete reality of events, new facts can be revealed.</p><p>However, based on journalistic investigations of the incident, some things should be cited:</p><blockquote>The spokesman said F.A.A. employees were following agency rules when they didn’t review the change. “The change to MCAS didn’t trigger an additional safety assessment because it did not affect the most critical phase of flight, considered to be higher cruise speeds,” an agency spokesman said.</blockquote><blockquote>Source: <a href="https://www.nytimes.com/2019/04/11/business/boeing-faa-mcas.html?module=inline">The New York Times</a></blockquote><ul><li>The design of the aircraft obviously involves not just software, but software is a critical part of the design;</li><li>The software has undergone unforeseen changes (<em>sorry the extremist fanatics who misrepresented the concepts of Agile, sometimes unforeseen changes are bad for everyone involved and they don’t deliver value</em>) and for some involved they weren’t major enough changes, not should influence “<em>important</em>” things;</li><li>They did not give due importance to the need for further revisions and testing after the software change;</li><li>Aircraft pilots (<em>Skin in the Game</em>) had not been informed of the changes;</li><li>One of the premises of the MCAS software was to ensure more flight safety in more extreme situations, in practice they took control of the pilots.</li></ul><p><a href="https://www.nytimes.com/2019/04/11/business/boeing-faa-mcas.html?module=inline">The article also cites other serious errors related to how the software change worked.</a></p><p>The conclusion we can make, assuming this <a href="https://www.nytimes.com/2019/04/11/business/boeing-faa-mcas.html?module=inline">NYT</a> article is reliable, is that people with greater decision-making power, perhaps experts, have ignored that software can cause real problems. Big problems.</p><blockquote>“In creating MCAS, they violated a longstanding principle at Boeing to always have pilots ultimately in control of the aircraft,” said <strong>Chesley B. Sullenberger III</strong>, the retired pilot who landed a jet in the Hudson River. “In mitigating one risk, they created another, greater risk.”</blockquote><p>The civil aviation industry (<em>in this case</em>) did the opposite of what was expected, allowing a single point of failure in the project to literally bring down the system, with human lives aboard.<br>Technology through software engineering is increasingly abstracting the real world from the virtual world, and the goal of this should be to assist with reliable tools so that the final decision could, where possible, be in the hands of those who have the “<em>Skin in the Game</em>”.</p><p>Software development is already important, and the more the infrastructure around us returns through code and software, the more our responsibility towards society increases.<br>Our responsibility, not only technical (developers, software engineers, software architects …), but also the bureaucrats involved in the whole process of developing technology, those who often replace technical reason with the “art” of politics.</p><p><em>Other reference article:</em><br><a href="https://www.nytimes.com/2019/06/01/business/boeing-737-max-crash.html">https://www.nytimes.com/2019/06/01/business/boeing-737-max-crash.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72dee2798258" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Black Swans in Software Engineering]]></title>
            <link>https://vinitech.medium.com/black-swans-in-software-engineering-3b9bda2628d?source=rss-1d7604386893------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b9bda2628d</guid>
            <category><![CDATA[black-swan]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[nassim-taleb]]></category>
            <dc:creator><![CDATA[Vinícius Pereira de Oliveira]]></dc:creator>
            <pubDate>Mon, 17 Jun 2019 15:12:23 GMT</pubDate>
            <atom:updated>2023-03-27T12:28:03.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*88MRbAEVnHmZrSQcOWkh0Q.png" /></figure><p>What is the relationship between the Black Swan logic proposed by Nassim Taleb and Software Engineering ?</p><p>Books and technical content are good, they help us keep our knowledge up to date, but also I like to reflect on standards and concepts proposed by authors who do not are directly linked to the technology and study whether these concepts can be applied to specific areas of knowledge.</p><p>The Logic of the Black Swan, whose author is Nassim Taleb, seems to be in harmony with many events that we can observe in our reality, in the economy, in politics or even in how we develop software. If the subject is interesting and you want to find more information about the Black Swan Logic, the best source is The Black Swan book (<em>in Amazon books or others stores</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*ao8VTdsZDe3e9skAyJwPUQ.jpeg" /></figure><p>Basically, the Black Swan Logic consists of a research related to highly improbable events, difficult, but occur and bring consequences together. Positive or negative.</p><p><em>Does anyone else see resemblance to critical bugs that only reveal themselves in production environments?</em></p><p>Although such events are highly improbable and difficult to predict, it is common and routine that people making such predictions and conveying the message that they have all the knowledge determine the future.</p><p>We have some basic examples only for the context of this article.</p><p>The financial crisis that began in the US in 2008 (Negative)</p><p>Big Wall Street investors, economics experts, real estate experts, big investment banks and even the US government itself sailed in calm waters with an accelerated economy and lots of dollars circling, everything seemed good to everyone until … Boommm !!!</p><p>Maybe a few months earlier, some people were already aware of details to wait for the crisis, but a crisis like 2008 does not occur in a few months, is the sum of many related variables for some years. At the beginning of the process, it is impossible to predict. After unlikely events occur all possible explanations.</p><p>The popularity of personal computers (Positive)</p><p>The technological giants of the 1970s and early 1980s ridiculed the idea that computers could be accessible to many people like television or radio. However, due to several unexpected events by the renowned experts of the time, in the spontaneous action of the market and consumers, today computers are in the hands of people everywhere.</p><p>The Black Swan Logic reveals our arrogance</p><p>How often when writing software with bad code, developers along with project managers consider that the most important thing is to deliver the code (big and complex) ready for production and make a profit? After all, everything was documented and combined with the customer and with the business areas and the entire team was very knowledgeable, nothing could go wrong.</p><p>Even worse, how often developers blame analysts because a complex and packed implementation of different possibilities has not been sufficiently documented, although the analyst has to make a large and complete document.</p><p>It seems clear that the problem was not specifically the developers, nor the analysts, nor the managers and even less the client. The problem was that in designing a comprehensive, complex, multi-variable system to build this system within a short and absurd time frame, an enabling environment for an event of Black Swan. The critical bug that can cost a lot of dollars/euros, the code that turns an indomitable monster and that generates more cost for maintenance than for optimization of new functionalities, illegible code which makes the team lose productivity.</p><p>The Black Swan Logic states that events of this nature are unpredictable because they are complex and have many related variables. An event that departs from this characteristic is the one that has simple nature or at least as simple as possible. If there is a large and complex smaller and simpler deliveries, we gradually learn to eliminate the chances of Black Swans.</p><p>However, this is not just about using agile methodologies and their various ways of delivering value quickly, <em>more important than this is to code with the thought of eliminating large complexities</em>.</p><ul><li><em>It is not helpful if the Scrum Master has full dedication to the most efficient agile method ifof the code do 7 things and are impossible to test.</em></li><li><em>It is not helpful if code methods are simple and do specific things if the developerexpects completion of 12 methods, 5 classes and 2 configuration files to send all this complexityto the repository and receive conflicts that will require more time.</em></li><li><em>Application architectures distributed in microservices are not advantageous just because they give resilience to a project, but also because they separate in smaller problems and with less complexity the parts of the application.</em></li></ul><p>Developing software is about solving problems, we can not and do not want to get away from it. But if problems exist to be solved, it is best that we can do without creating new and more complex ones.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b9bda2628d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>