Refresh of the dependencies in Vigilant Crypto Snatch
The dependencies in the Vigilant Crypto Snatch project ended up being the dependency hell. Now I finally got it fixed.
Einträge über Vigilant Crypto Snatch
Abhängigkeitshölle mit Python
Im Vigilant Crypto Snatch Projekt nutze ich Python als Programmiersprache und Poetry zum Verwalten der Abhängigkeiten. Dabei hat sich mit der Zeit einiges angesammelt:
Perspectives for Vigilant Crypto Snatch
I have been working on the Vigilant Crypto Snatch program for a while now. It has started as a command line utility and eventually got extended with a Streamlit web interface for simulation. Recently I added a GUI with the Qt framework. The user experience is now scattered over three different interfaces. After talking to product managers at my company about our company's product, I learned to view programs in a new angle. So far I would see it from a programming perspective, and with technical boundary conditions. But they view it completely differently. One of their view angles are jobs to be done. And this made me reflect over my hobby project.
Trigger GUI for Vigilant Crypto Snatch
At the beginning, the status screen of the Vigilant Crypto Snatch program looks rather bleak. It somehow has information on it, but it isn't really nice to look at. There is no real hierarchy of information, lots of empty space. I just don't like it.
Qt GUI for Vigilant Crypto Snatch
The Vigilant Crypto Snatch software started as a two-user project, where Chris and I just had it running on our respective machines. Over time a few other users came along, and now we have a Telegram group with around 50 members and likely even more users of the software. Initially the software was just a command line utility and ran only on Linux. Then I've used Streamlit to create a little web user interface to simulate triggers. People have asked for Windows support, which was not hard to do with Python. The user basis grew even more, and eventually somebody asked for a GUI. Command line programs are very uncommon on Windows, and the reach of the software seems to be large enough to be of interest to non-tech-savy users.
Notifications from Python to Android
For the Vigilant Crypto Snatch we currently use Telegram to send notifications from the Python program to the phones (mostly Android, I guess). Each user has independently set up a bot with Telegram. This bot token is registered in the configuration file and the Python script can then use the bot to send messages. The users have to write to their bot using Telegram such that the bot knows about their personal account. Then the bot can send messages to that particular end user.
Adding CCXT to Vigilant Crypto Snatch
The Vigilant Crypto Snatch software had been refactored into the Clean Architecture a while ago. This process started when we wanted to also support the Kraken marketplace next to the Bitstamp marketplace. Then I switched over from the clikraken package to krakenex to improve the support with Kraken.
Better Exceptions for Vigilant Crypto Snatch
When running the Vigilant Crypto Snatch software, I often get these error messages sent via Telegram:
Adding Fear & Greed to Vigilant Crypto Snatch
In my Vigilant Crypto Snatch project I have spent quite some time in improving the architecture of the software such that further changes would be much simpler. At the time I did not have a backlog of new features, so I just tried to add more tests. This then forced me to separate a few things, improving the overal design.
Making Adapter Code More Testable
Part of my Vigilant Crypto Snatch project are the marketplaces. The most popular is the Kraken one. I use the krakenex Python library to interface with that. In the UML diagram you can see how the KrakenexMarketplace directly uses the krakenex library: