Most people don’t know that installing software packages takes more time than programming.
This is why using containers is so revolutionary – they are like little preinstalled computers.
This is what I learned day 2 of solidity programming
My computer ground to a halt.
I ran the three functions in scaffolding eth. I started them stopped them restarted them. And then my computer stopped.
I had like 10 million node processes running. Maybe I should run this in a container!
While waiting for everything install I thought about port 3000.
Is it related to @mst3k mystery science theater 3000?
Probably not but I went down a rabbit hole.
Here are all mst3k episodes ranked.
I have a favorite – but I don’t know its name 🙁
I started programming a python app.
The python app turns mantras into sounds. I am going to use #scipy and matrices. http://zulko.github.io/blog/2014/03/29/soundstretching-and-pitch-shifting-in-python/
Maybe I will work on it more doing this 30for30 when solidity is slow – like saving things to the blockchain.
At one point my terminal stopped working!
The error: Clear error in Linux: Terminals Database Is Inaccessible Solution https://programmersought.com/article/78227910950/
I reset the terminal emulation:
export TERM=vt100. Something I have not done in like 20 years. And it worked!
I researched tricking out my tmux config – as one does.
Can different panes in #tmux have different color schemes?
Day 2 and it does not feel like much solidity was learned, but sometimes the hardest part is getting your environment set up
If you liked this :
1. Toss me a follow for more threads → @hackerm0m
2. Join me in learning solidity this month