Since when am I a blockchain developer? This is the question that’s gone through my head for a little over a month now.
I’m primarily a frontend developer, and I’m reasonably happy with that. Angular and ngrx are well-documented. I’m passionate about clean code and quality software engineering. I’m comfortable with the tools and technologies I use. Go to work, write some tests, write some code to pass those tests, go home – things have been pretty simple.
But recently I’ve had to add Ethereum into the mix, and I’ve become more of a web3.js code monkey than an engineer. I don’t like being a code monkey.
Blockchain is in a very alpha phase, so trying to elegantly integrate it into an existing frontend is a major challenge. I’m hoping the Web3 Chronicles will change that. I have high hopes for this blog series; things I’d like to do include:
- document my learning process (the “how” as well as the “what”)
- share my discoveries
- vent my frustrations
- celebrate my successes
- learn from my failures
- make life easier for other developers working on this
If you were looking for a more philosophical motivation, I guess it’s this: if blockchain and cryptocurrencies are going to scale, we need rock-solid engineering around them. We as developers have a professional obligation to build maintainable software, and users deserve to have confidence in what we’re doing. To be honest, I’d rather not be working with such a young technology. But if I’m along for the ride, then dammit, I’m going to do it right.