Skip to content

Create SCP_cohort_recap.md #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open

Create SCP_cohort_recap.md #137

wants to merge 14 commits into from

Conversation

michelleellen
Copy link
Contributor

@michelleellen michelleellen commented Aug 12, 2025

Blog post

@michelleellen michelleellen requested review from moul and a team as code owners August 12, 2025 17:50
Copy link
Collaborator

@leohhhn leohhhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm just some minor styling issues


### **Student advice to getting started**

- Always use gnodev – Develop with the same interface end-users will see to catch issues early and save both gas and time.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Always use gnodev – Develop with the same interface end-users will see to catch issues early and save both gas and time.
- Always use `gnodev` – Develop with the same interface end-users will see to catch issues early and save both gas and time.


- Always use gnodev – Develop with the same interface end-users will see to catch issues early and save both gas and time.
- Start small – Build a simple blog, game, or voting app. Shipping something functional teaches more than passive reading.
- Keep a HackerSpace diary – Write short daily notes about what you build, learn, or fix. It makes progress tracking easy and helps mentors guide you.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

link it

- Always use gnodev – Develop with the same interface end-users will see to catch issues early and save both gas and time.
- Start small – Build a simple blog, game, or voting app. Shipping something functional teaches more than passive reading.
- Keep a HackerSpace diary – Write short daily notes about what you build, learn, or fix. It makes progress tracking easy and helps mentors guide you.
- Read other realms’ code – The monorepo is full of solid, real-world examples that can accelerate your learning.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Read other realms’ code – The monorepo is full of solid, real-world examples that can accelerate your learning.
- Read Gno code by other gnomes – The monorepo is full of solid, real-world examples that can accelerate your learning.

Comment on lines 24 to 26
- Ask questions early and often – Use Office Hours, PR comments, or Signal. Small clarifications now prevent big roadblocks later.
- Expect rough edges – Gno is still evolving, so some issues may be language-level limitations, not your mistake.
- Stick to determinism – Avoid relying on time, randomness, or anything non-deterministic; these won’t work on-chain.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to rewrite a bit


The cohort tackled a wide range of technical and creative projects, including applications, tools, and ecosystem enhancements. Here's a highlight of what they accomplished:

Applications & Demos
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make it a h3, h4?

- Change.org-style petition realm
- Friendly Organizer app using the CommonDAO implementation

Core Enhancements & Utilities
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as comment abovce


[@mounia](https://github.com/moonia) ‘During this cohort, I had the opportunity to get hands-on with the Gno.land ecosystem by working on two technical projects. I explored the idea of a Gno-based EVM interpreter, allowing Solidity bytecode to run in a Gno-native environment. I also led the profiling project for GnoVM, enabling source-level insights via pprof and flamegraph tools. It was a great opportunity to contribute meaningful tools while learning the internals of Gno and I really appreciated how close Gno feels to Go. Overall, it was a great experience that deepened my interest in the blockchain space and made me eager to keep contributing.’

[@Tchips46](https://github.com/Tchips46) (Leo)‘During this cohort, I focused on exploring the EVM on Gno.land, which helped me understand complex blockchain concepts and the inner workings of virtual machines. I learned how to build more advanced dApps and got introduced to Solidity. This allowed me to write documentation about well-known Solidity design patterns, using examples to make them easier to understand. Overall, it was a valuable experience that grew my technical skills and deepened my understanding of blockchain development.’
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consistency? you added (Leo) here but not for others

@leohhhn
Copy link
Collaborator

leohhhn commented Aug 13, 2025

also, you need to make sure that the file you're adding is in the posts/POST_FORMAT/README.md ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants