Joao Felipe C.

⚗️🚀 The maker and the scaler. I'm 13+ years System Architect and Developer with focus on scalable Agile products. My most successful projects were a combination of two mindsets: a client, the maker, and me, the scaler, working in tandem. A maker is a talented user that develops his ideas in an artisanal way end-to-end. It can be a mockup, a spreadsheet, a NoCode tool or AI. He can leverage instantaneous feedback, validate features, solve problems at end-user level, and make demonstrations to clients and investors. A scaler takes care of the amplification effect, the bad decisions that multiply the costs when scale. In the Agile methodology, there is not enough time to plan long term, so he must rely on his experience to spot a bad idea and avoid it. It is not much different from cinema where the director deals with the creative side and the producer deals with the analytical side of it. === TOGETHER is better than ALONE. If you're a maker, send me a message for 30% off on my technical hour (from U$ 50 to U$ 35) for milestone-based projects, or U$ 25 for hourly-based projects. === In my experience, scale is not only necessary to support a certain number of users and make the business plan's ends meet. When it doesn't scale well, you need to add components to your infrastructure that can introduce complexity and bugs, increasing the unplanned work, often called technical debt. OpenSource scales very well in throughput and is so simple to be maintained. That's why I like to own the scale end-to-end instead of having a product manager, a frontend developer, a backend developer, a devops and a QA separated as commodities. Understanding the whole process let me decide the best solution for the overall scale without a lot of meetings, documentations, and conflicts. Conversely, I empower the maker to also own what doesn't require scale by providing data export and import mechanisms, so he can do end-user development (EUD) and continue the experiments of new features. Plus, because I know the feature in detail in advance, I can provide estimates of how long it will take to productize, so he can decide when to scale or not each feature. What technologies do I work with? I'm happy to solve most of the Small and Medium Business challenges using OpenSource technologies. PostgreSQL is for sure what I know more in depth, and combining it with Apache HTTP, KeyCloak, Linux and Apache Camel I can scale your digital transformation. I have solid knowledge about SQL, PL/pgSQL, mod_lua and Bash. I also can decently program in C, Java, PHP, Python, JavaScript, HTML, CSS and XML/XSLT.