This week I started digging deeper into what exactly is going on with the Blockchain. I’ve always been interested in it but never felt like actually going further than the wikipedia page and a couple of whitepages. Sure, I’ve monitored Bitcoin prices for years, wishing I had invested when I first heard about them, but the subject has never been more than a curiosity. Now, with the way Bitcoin and Ethereum are growing, the potential of blockchain systems is impossible to ignore. There are two sources I’ve used to get started learning about the space:
The Quiet Master of Cryptocurrency - Nick Szabo - This is a podcast where Nick Szabo, Naval Ravikant, and Tim Ferriss discuss what cryptocurrency is and how it is going to take over the banking industry. The podcast is a perfect place to start. It’ll at the very least get you excited about the subject.
Blockchain Fundamentals - Blockchain Fundamentals is a course that was added to Pluralsight this week that is led by Jan-Erik Sandberg. The course offers a background on what the blockchain is, how it can be used, how to use it in development, and how to use it moving forward.
I finished Cory House’s new course on Creating Reuseable React Components. The course gives a survey of the options developers have when building a React component library. House’s courses are some of the finest on Pluralsight and this course is no exception. It’s clear that he is passionate about the subject matter and is constantly searching for and sharing the best ways to approach React projects. One note about the content, this course is more centered around setting up and releasing a React component library than it is about writing code. The techniques here can be used to make you better at the craft of software development but not necessarily the act of writing code.
Book(s): Man’s Search for Meaning
PluralSight Course(s): Implementing and Securing an API with ASP.NET Core, Domain-Driven Design Fundamentals
Book(s): Smalltalk Best Practice Patterns
On the Next…
I’ve moved the idealistz source to VSTS rather than storing it on GitHub. The major reason I chose to move it to a closed source environment is because I don’t know what it can be yet. I’ve never really felt the urge to monetize any of my projects so far. It’s possible this one could be bigger than my past projects. I want to see how much I can grow the solution and see what it can become. I could move it all back to GitHub eventually, but for now I’m going to close the source and see what kind of solution I can create.