_tldr_

• at ethglobal hackathon i rebuilt a scheduler from the ground-up with 2 frens, with many features, but not fully working

• now i'm gradually adding thos features to qcast by debugging carefully as i go

• i recorded a new video for a new launch

• see update #7 (#8 was buggy, i contacted paragraph to get it back)

_technical_

• last week at ethglobal we built a database with postgresql and prisma for several features. i'm implementing this into qcast, but i want to understand things well as i go along, so i've been studying several concepts (e.g. connection pools, db hosting, cloud providers like supabase and neon).

• here i explain some design choices i was able to make with the knowledge from already having done it last weekend.

_farza notes_

go through itertive loop 10 times, with 10 different cohorts (your ppl who like what you're doing). remember update #7 ? ...create, launch, measure, learn... repeat with new cohorts over time.

to find a cohort, first find a good channel and content type that's right for you rn.

• find your channel: e.g. a specific subreddit, discord groups of cs departments of unis, public square in front of public library at specific time...

• and find your content type: e.g. videos of showing behind the scenes of your software with commentary, learn a song in 30 seconds and perform on the spot, skits about gen z vs boomers, videos of going in pubic and asking ppl for feedback...

it's ok to try several channels and content types at first but find you niche and stick to it. plan it out...

however, focus on developing your product as a main concern - nobody wants a shit sandwich on a silver plate with cherry on top.

_tldr_

• at ethglobal hackathon i rebuilt a scheduler from the ground-up with 2 frens, with many features, but not fully working

• now i'm gradually adding thos features to qcast by debugging carefully as i go

• i recorded a new video for a new launch

• see update #7 (#8 was buggy, i contacted paragraph to get it back)

_technical_

• last week at ethglobal we built a database with postgresql and prisma for several features. i'm implementing this into qcast, but i want to understand things well as i go along, so i've been studying several concepts (e.g. connection pools, db hosting, cloud providers like supabase and neon).

• here i explain some design choices i was able to make with the knowledge from already having done it last weekend.

_farza notes_

go through itertive loop 10 times, with 10 different cohorts (your ppl who like what you're doing). remember update #7 ? ...create, launch, measure, learn... repeat with new cohorts over time.

to find a cohort, first find a good channel and content type that's right for you rn.

• find your channel: e.g. a specific subreddit, discord groups of cs departments of unis, public square in front of public library at specific time...

• and find your content type: e.g. videos of showing behind the scenes of your software with commentary, learn a song in 30 seconds and perform on the spot, skits about gen z vs boomers, videos of going in pubic and asking ppl for feedback...

it's ok to try several channels and content types at first but find you niche and stick to it. plan it out...

however, focus on developing your product as a main concern - nobody wants a shit sandwich on a silver plate with cherry on top.