When to avoid Snowflake solutions from …Snowflake employees

Look, I am still in touch with decent and even brilliant former or current Snowflake employees. But once in a while you simply get a slap in the face from what people throw nowadays on the net. And I am not talking here about honest mistakes. But huge silly blunders that show a basic misunderstanding of fundamental things.

We have someone at Snowflake who left a post on Medium two months ago. Except that his solution could simply never work. And it’s just simple basic stuff for anyone who understands the 101 on how Streamlit works.

Copy and paste his code in a new Streamlit app, and add “cryptography” to Packages. Then generate new keys and try to save them BOTH locally. You cannot! :) At least one value will always be re-generated on the page-rerun.

The guy generates a private and a public key, and displays them on screen, in separate text areas. And adds a download button below each key, to save the keys locally (see my post featured image).

Except that each click on a button will simply trigger a page refresh, and you cannot save the other related key. All is useless! ;)

Some other Snowflake employee posted a better solution a while ago, saving the data through the st.session_state dictionary. And myself I posted a solution two years ago…