Understand first, build second
I don't build until I know what problem is being solved and for whom. One hour of conversation upfront saves weeks of rework later.
From sales to technology
I worked 8 years in finance, commerce, and sales — before getting into development. I sold products, negotiated with clients, and understood how money flows in a business. That experience taught me something no programming course teaches: before building a solution, you need to understand the business problem you're solving.
Automation came as a real need. I watched hours being lost to manual tasks that an application could resolve in seconds. I started learning to automate processes, and discovered that what I enjoyed wasn't just technology — it was solving business problems.
Today I combine both: I understand how businesses work and I know how to build the tools that make them work better. WhatsApp catalogs, online stores, landing pages — every project starts with the same question: how do I help this business sell more and work less?