Wow, I've been thinking along similar lines.

However, instead of "learn to code" I would like to have a token for sharing code.

Sharing code is slightly different concept and a completely different market from learning code.

There are thousands of books and web sites that feature basic learn to code posts. It is a crowded space. Most learning code sites are highly structured they have sections that focus on a single language at a time and present code in a standard structure.

It would be hard for HIVE to compete in that space.

Sharing code is a different thing. This market is open for free form discussions.

Sharing Code Web Sites

Github is the best example of sharing code. The site often serves as the repository for working projects.

HIVE could never compete with GitHub.

One could create a social media project that supplements GitHub. Users could discuss the working code projects on GitHub. This would encourage github projects to link back to HIVE.

Sharing Code Token to Support HIVE Engine Development

Anyway, the goal of a share code project would be to help people develop code for projects. It could be used to help people develop programs that interface with HIVE and HIVE-Engine. It could be used for discussions about development issues.

STEM Is Not Sufficient For Sharing Gode

The #STEM token is sufficient for "learn to code" projects since learning code falls under the blanket of STEM education.

Sharing development code does not fall under the STEM blanket as developing code is not about learning it is about doing.

I would love to see a token for sharing code. We already have STEM for learning code; So, I wouldn't bother wasting any BEE on a learn to code project.

!WINE