A little rant:
I am seeing much too much copy and paste solutionism in this and other Cardano forums!
In this great community, you will often, nearly always find someone to hold your hand through any and all problems you encounter. But, please, if you want to operate financial infrastructure – a stake pool, an exchange, a marketplace – you should have a quite good knowledge of what runs on your system and how it works.
In my opinion, it would be good if you had seen a Linux system, a command line, a .bashrc
, and an editor, before you even start, but if you want to learn all that also on the way, in parallel to all the Cardano-specific stuff, that’s also okay with me.
All these copy and paste guides are nice to have a quick reference, to not forget a step in a process, to remember something you seldomly do. They are even a necessity, since the more or less official documentation is scattered among all those systems IOG and other players experimented with in Cardano’s almost five-year journey. But, please, don’t follow them blindly! Try to understand what is in there!
After some time you should really know, what most of cardano-cli
’s options mean and why they have to be there and have exactly that value or why not. You should have at least a basic understanding of what the non-Cardano technologies you maybe use – from systemd
to Docker – do and how. You should know, which parts of the “create a transaction” walkthrough are the necessary steps and which are just some shell shenanigans to keep the guide at a reasonable size. (Looking at you, awfully complicated while read
loop aggregating the UTxOs!)
It really is a lot more fun to help people out, where they learn something on the way (and often me also), have a better understanding, have a better mental model of their system and its place in the Cardano network in the end, instead of just: “Ah, yeah, now GLiveView says it’s running. We left a lot of unused files in all corners of the filesystem in the process and have no idea, what exactly was the problem, but it’s running. Kthxbye!”
Even seasoned developers or operators have some places in their projects and systems with a label: “I don’t know why it works this way, but I’ve tried everything else. Just don’t touch!” But they should be rare!
Please, try to learn, not just get something to work somehow! Thank you!