Other than pairing with SWAP.HIVE as the first or second diesel pool for a new H-E token having become rather cliché?😁 I believe that @yintercept made a good point in [a reply to one of the previous posts](https://peakd.com/hive-163521/@holovision/learn-to-code-tribe-and-byte-token-will-launch-march-31): 

> My hope is that a "Learn to Code" tribe would discuss developing #hive-engine programs. In that case, a BEE:BYTE pair might be in order.

I am hoping to be sufficient in creating first layer Hive smart contracts within a year or so (and posting about what I learn here on @learn2code) and then move on to second layer smart contracts. BEE is the token of hive-engine (the token name is "Hive Engine Token"), for example, the [airdrop contract](https://tribaldex.com/airdrop) requires BEE as payment for it to use a CSV or TXT file. 

Therefore, as an aspiring hive-engine smart contract creator I want to abide by Ferengi Rule of Acquisition #33, “It never hurts to suck up to the boss.”😁