As part of my journey to learn more about blockchain, I discovered I had a growing desire to visualize what was happening on the blockchain. I’m quite comfortable in the terminal; however, it’s not always the most visually efficient way to interpret something. Not to mention it can be quite exciting to see things happening on a fancy UI!
Here are the steps:
- Setup
- Download and Install Tools
- Configure the Node Monitoring App
- Start the Node App
- Start the Frontend
- Explore the Dashboard
Preface
This post will go over 2 tools that work together to visualize various stats and information about the…
Private Network with Ethereum
I’ve recently discovered the wonderful world of the Ethereum blockchain. Rather than continue to stand on the side lines watching blockchain tech evolve, I thought I would venture into this new ambiguous world. There’s a lot of material to cover when exploring blockchain technology so I decided to focus on the blockchain itself.
My goal is simple…create a private multi-node blockchain using the Ethereum blockchain.
Here are my steps. Steps 1–6 focus on getting the private network up and running. Steps 7 & 8 are used to test the private network.
- Install go-ethereum aka
geth - Build the node directories locally
- Create…
I recently stared playing with Git hooks and thought it might be useful to customize my Git commit messages. The default commit message that appears in the editor was not terribly helpful. It also doesn’t do much in the way of enforcing some sort of commit message convention.
Commit Message Convention
There are many ideologies on what a good commit message should look like. Based on my own experience and some advice found here and here, this is what I believe a good commit message should include:
- Subject line should be a summary of changes in 50 characters or less
- The body of the commit message should focus on why the changes are being made as well as how the changes address the issue and any implications or side effects caused by the…
I recently moved onto a new project that had already completed several of the first key milestones. I joined the team as a third developer and had the opportunity to spend a few days getting my environment setup and exploring the code base. Given the high turnover of developers in the consulting world, I thought it might benefit me and possibly others to try and define some concrete checkpoints when on-boarding a developer onto existing projects.
Step 0
Depending on the project, there are a couple key tasks that must be completed before anything else can be accomplished:
- Account setup (GitHub, GitLab, Jira, company specific…
About
