From Token Watcher to Program Builder: 100 Days of Solana
I came into this program as a Web2 developer who moderates Web3 communities. I knew Solana as "the blockchain people build products and solutions on, and launch tokens on." That's it. I'd watched projects build on it, seen the ecosystem from the outside as a community moderator and ambassador. But I'd never written a line of Solana code. Ninety-nine days later, I have a program deployed to devnet…
For 100 days, a Web2 developer transitioned from being a token watcher to a Solana program builder. Initially, the developer believed blockchain development would feel like backend development with a crypto coating. However, this was not the case. Solana's blockchain does not have servers or databases that can be quietly edited; everything is a transaction, and every transaction is permanent.
The developer's understanding of authority ownership also changed - while programs can be upgraded, they cannot alter past code execution.
The developer's understanding clicked when building a "vault" program that held SOL, allowing deposits, withdrawals, and control over withdrawals. The pieces learned in isolation (accounts, PDAs, constraints, error codes, tests) began to form a cohesive system. The developer recognized the importance of the toolchain in making Solana manageable.
The protocol itself is only accounts, transactions, and programs, but the toolchain — Anchor, PDAs, and IDLs — is what makes the protocol usable. The capstone project, a program called "ship" that records on-chain proof of completing a capstone, demonstrated the integration of these concepts. It features PDAs, custom errors, runtime constraints, tests, a TypeScript script, and a read-only agent tool for fetching ship records.
The developer encourages others to dive deeper into agent tooling, contribute to open source, and help other developers, bridging the gap between learning Solana primitives and building real products on the network.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
