For most blockchain developers, a day starts with a “stand up”. But for the Historia development team, the day begins with a strong coffee.
Phone calls
We value team autonomy a lot here at Historia, so individuals have a lot of flexibility in how they choose to work. Shortly after coffee, team members converge for an update concerning the progress of the project. This is typically run by our Lead Developer and involves discussing project development and what needs to be done that day. These discussions are meant to be kept at fairly high-level diving into details such as problems being faced, breakthroughs and what steps to take going forward. Additionally, every team member is assigned a task to work on.
At the end of the meeting, we all have a good sense of what the team is doing and the direction the project is going.
Code
After the morning calls meetings, it’s time to delve into what matters most—coding.
Most of the day is spent writing and debugging code to follow the specification laid out by our lead developer. Not all our developers write in the same language—individual coders are at liberty to write in their own language and styles (e.g HTML5, JavaScript, CSS, Python, Solidity, and Angular JS).
Blockchain development is an ongoing process of research, testing, trial, and error. As a result, we dedicate part of the day researching next iterations including ways to implement protocol-level changes and how to implement voting via the web application. Once researched, we try to implement these items in an effort to enhance the functionality of the Historia blockchain solution.
Attention to detail is critical to ensuring the quality of the code. So we conduct a peer review of the previously implemented items. Next, we test the previously implemented items on the DevNet to evaluate the behavior of the code. If the code does not behave as expected, we conduct testing to identify and fix bugs. This is followed by a peer review of the bug fixes and further testing of the bug fixes.
Like any other blockchain development team, we check our GitHub dev branch to discuss the existing code and communicate with developers on other projects too.
Now, as the day comes to a close, we move the code to testnet branch (currently v0.16.3.X) for deployment. And with that, we’ve deployed our code we wrote this morning. Next, we update testnet nodes and perform long term testing.
A good day in the office for Historia development team ends when the code we have written works efficiently and can be re-used at later stages. The way we work at Historia has largely been shaped by our desire to develop the most functional and scalable blockchain application for history recording.
Help us in our efforts to preserve original history. Join Historia blockchain today.
Please do not forget to visit, join, follow, and like us on:
[url=http://historia.network/]Historia Website[/url]
[url=https://twitter.com/historiasys]Historia Twitter[/url]
[url=https://discord.gg/b3FJPpn]Historia Discord[/url]
[url=https://www.reddit.com/r/historiasys/]Historia Reddit[/url]
[url=https://github.com/HistoriaOffical/historia]Historia on Github[/url]
Historia is a community project. The influence of any one superpower does not endure in Historia. The project is for the greater good of the global community with allegiance to no one except the everlasting truth of how it actually happened. If you would like to be a part Historia discussion, join us on Discord and let us know your thoughts. All spectrum of opinions and facts wanted, come all.
Originally published at blog.historia.network on May 14, 2019.
