# My journey I started in C# at an IT services firm. After a year, I joined a big bank as a **business rules specialist (credit)**: more abstraction, lots of upfront prep/understanding and documentation, less coding. It mainly confirmed one thing: I love building software. Through school and friends, I got into crypto. We tried small projects, then started our own thing. I took my first steps in Web3 as a **Solidity smart contract dev**. As a beginner, I quickly moved toward setting up test environments and writing docs. At first, I saw these as “the tasks no one wants.” Over time, I realised: this work lays the foundation and prevents big problems later. I was also lucky to work with demanding devs and CTOs who taught me to aim for quality and think a few moves ahead. ​## Mindset I learned that: - good work isn’t just fast, “clean” code; - foundational (often invisible) work is crucial; - preparation matters more than rush-to-implementation; - making a system understandable is as valuable as building it. I remind myself not to code too fast. **80% of the real work happens before the first line of code.** Practically, that means: - deeply understanding requirements; - studying what already exists; - writing clear specs; - mastering environments and their interactions. Even under pressure, this preparation is **priceless**. With AI, it’s even more true: “pure coding” matters less, but you still need to guide the tool and keep an architect’s view. ​## What I’ve built I set up a quiet-but-essential automation framework: - automatic transaction processing, - report generation, - operational maintenance routines. In short: automation is a silent force. I like these high-impact, often invisible contributions that make everything else more reliable and simpler.