Development

Our IT books club has started reading new book - about Software Engineering at Google - processes, culture, and tools that help Google create and maintain high-quality software. First chapter is about Software Engineering in general: What is Software Engineering vs Software Development/Programming? Three principles Google consider: Time and Change Scale and Growth Trade-offs and Costs How these three principles are applied to Software Engineering and how it is different from Software Development/Programming Interesting opening chapter of the book:

This is a continuation of my previous post Real Projects with Ethereum) - about how to setup a development infrastructure around real-life smart contract.

How to build a complex blockchain smart contract? What standard issues will you face with arrays, gas, different types of variables, deployment of contracts, etc? And how to solve them?

What is the right architecture for the app that should work with blockchain (and how it differs from traditional web architecture)? What libraries to use? How to configure environment?

Useful advanced info and techniques of writing and testing Smart Contracts: basic data types, reference data types, global variables, gotchas with dynamic arrays, validations and modifiers, debugging, generating random numbers, sending ether.

What is the right toolset for Blockchain development? Here are some keywords: nodejs, npm, web3, solc, ganache, mocha, metamask, rinkeby, infura, remix…

There is quite a high demand for blockchain development these days. We do some experience with it as a company (one complex multi-year project), but personally I only had high-level knowledge and I wanted to improve it…

So me and few of my colleagues have started the course “Ethereum and Solidity: The Complete Developer’s Guide” (https://www.udemy.com/course/ethereum-and-solidity-the-complete-developers-guide/)

The book club of our company has chosen a new wonderful book for reading: Robert Martin - Clean Architecture - a Craftsman’s Guide to Software Structure and Design 👍 Fifth part of the book contains A LOT of useful information: What is software architecture? What type of interdependencies can exist? How to draw borderlines between components? What type of borders exist? How to distribute policies by the levels? What are business rules, entities and use cases?