I don't trust apps with my crypto. Every wallet, exchange, and dapp is a black box. You hand over your private key, click "send", and hope the code does what it claims. So I built my own scripts instead: small, auditable Python programs that I can read and understand completely.
The differences between Stellar and Ethereum force you to confront each blockchain's design philosophy. Here's what I learned building scripts for both.
In this article, I will explain why Python Virtual Environments are so cool when you know how to use them properly. I will also show you how to use them the right way.
If you have been using [pylint][pylint-website] tool to check the format of your Python code you may have encounterd the rule W1203: logging-fstring-interpolation but you didn't really understand why it's important.
The warning looks like :
path/to/my/file.py:37:4: W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation)
It appears when you are using the [Python logging library][python-logging-doc]. On the [pylint][pylint-website] documentation about this rule it is said that you shouldn't use f-string formated strings.
First of all I'm not a web engineer and I hate web development. There are too many framework to work with ([ReactJS][reactjs-website], [Angular][angular-website], [jquery][jquery-website], ...). [Javascript][javascript-website] asynchronous system is a pain to manage at large scale. And dependencies maintainability is too much for me (yes, I'm talking about you npm). I'm not a web designer either so [HTML][html-rfc]/[CSS][css-rfc] are the enemy (mostly because I don't know how to use them at their full potentials).
This is pretty much why I quit web development in the first place and became a SysOps engineer.