hey,
this week was all about visibility and validation, making sure what i built actually gets seen.
the main focus was driving traffic to saasheaven. the goal was 10 pull requests, which i didn’t hit, but something even cooler happened: the repo hit 67 stars. that’s a personal high I’ve never reached before. posting on reddit and sharing the project made me realise that if people think your project is genuinely cool, they’ll engage, even if they don’t contribute immediately.
i also joined the hackclub event flavourtown, which rewards hours spent coding open-source projects with grants for things like domain credits. i started with saasheaven, and the plan is to use the credits to fund future domains so i don’t have to spend extra money. it’s a neat way to make the building process more sustainable.
i’m also putting together a github repo of stem-related simulations. it includes the simulation code itself plus a flask app api to run them. so far, i’ve added random walks, page rank, and coin toss simulations. it’s a small project, but it feels great to have something reusable and educational that other people can interact with.
on the personal challenge side, i’ve committed to taking part in the swift student challenge, and i’ve already come up with a strong idea for the app. once my current projects are finished, this will be a major focus.
mathhacks, my maths + cs leetcode-style platform, is also on my mind. i’ve decided that validation is key: i’ll only start building if the waitlist hits 25+ signups by the start of march. it feels good to set clear thresholds before jumping in.
next week will be the final push on the b2b product. with exams over, i’ll have time to grind, ship, and then move fully into swift student challenge, cold emailing for the b2b, and getting people signed up for mathhacks.
having a clear timeline and knowing exactly what i need to do makes everything feel manageable. it’s all about momentum, focus, and finishing what i start.
thanks for following along,
vulcan