Forem: Samina Rahman Purba

Building Disco Week 2: Making Event Networking Less Random 🪩

Samina Rahman Purba — Tue, 21 Oct 2025 00:07:41 +0000

Last week, I started a new series documenting the journey of building Disco, a more effective networking app for in-person events.

We also formed our first pilot partnership with York University, which helped validate the idea early on and gave us real-world feedback to shape our next steps.

Finding the right people to build with ✨

For the past two weeks, I've been building Disco with two friends. A small, scrappy team that believes in the idea as much as I do.

As I started sharing about Disco more, demoing it at friends' parties, at the Startup Open House event that recently took place in Toronto, and even to incubators such as the DMZ, new ideas kept coming in and the feedback was amazing.

Every conversation helped me refine what matters most for our MVP and where we should focus next.

I used to be terrified of talking about my ideas in public and sharing the work in progress. However, I soon realized that creating an app is just the beginning. There's so much more than just the coding part.

Finding the right team members, setting a clear vision, getting partnerships, and staying disciplined to do the work day in and day out without going insane all matter in the building process.

What Disco is hoping to solve 🪩

As an introvert, I've always found networking events overwhelming. The awkward small talk, the frantic search for someone new to speak to, and the pile of business cards that I collect but never look back at.

As a product studio founder, I love meeting potential collaborators or clients, but there's no good way to meet the right people at the right time during events. Most of the meaningful connections I've made at events happened completely by chance. That always made me wonder:

What if meeting the right person at an event didn't depend on luck? What if I knew who was coming to the event and what their goals were?

That's exactly what Disco aims to solve. An app that connects people at in-person events based on their goals for attending. Users create profiles sharing what they're looking for, whether that's finding co-founders, landing clients, or learning from experts, so you can meet the right people at the right time.

I'll be sharing weekly updates on building Disco, lessons learned, and behind-the-scenes progress. If you're interested in trying Disco at your next event or have feedback to share, drop a comment. If you are interested in becoming a beta tester, I'd love to hear from you!

The Disco Build 🪩 Week 1: MVP Sprint

Samina Rahman Purba — Sat, 11 Oct 2025 14:14:47 +0000

We overthink, over-research, and over-plan until the idea dies in our notes app.

Last week, we did the opposite. We built a networking app called Disco in 3 days, pitched it at York University with a barebones demo, and walked out with a pilot partnership in under an hour.

If You Have an Idea, Build It

As an introvert, I find networking events overwhelming. The awkward small talk, the frantic search for the next person to speak to, the business cards that end up in the trash. All of it feels draining. Yet I understand its importance and the role it plays in opening doors to opportunities. In fact, most of my work opportunities came through people I met at events.

Last week, we showed up at York University with an idea: Disco, an app that makes networking at events actually work. I’ll discuss more about its features as we get closer to the launch date.

We built a barebones demo in just three days and had one shot to pitch it to decision-makers.

We presented the demo to the heads of engineering student clubs and the manager of the entrepreneurship program at the Lassonde School of Engineering. Their eyes lit up as they watched the app in action, and within an hour, we walked out with an agreement to pilot Disco at their upcoming events.

If You Don’t Try, You’ll Never Know

For years, I’ve struggled with self-doubt, imposter syndrome, and a persistent sense of confusion about what I truly want to pursue in life.

I get new ideas. I start a project. I find competition. Then self-doubt creeps in, and I stop.

But every time that shroud of negativity begins to take over, I remind myself: If I don’t try, I’ll never know.

A lot of great products that exist today almost didn’t. Slack started as an internal tool for a failing gaming company. They were about to shut down when they realized the chat tool was actually the product. Discord was built by a team whose previous gaming company had just crashed. They made it for themselves and almost gave up on it. Notion’s founders were down to their last $10K, and it took them two years to get 1,000 users.

There are countless stories like these: teams pivoting, products evolving, and ideas rising from the ashes. The lesson is simple — try, because you’ll never know otherwise.

Early Signs of Validation

A few months ago, I joined several WhatsApp groups where tech founders discuss AI, share ideas, and help each other out.

I shared my idea for Disco, and to my surprise, many of them were interested in signing up. That early signal gave me confidence, but more importantly, clarity. I started to see who our users really were and what features actually mattered.

I also have an incredible team of four working on this project, people who believe in it every single day and keep our Discord project server alive.

AI is making it ridiculously easy to build quick prototypes for feedback and validation. It’s helping us automate repetitive tasks and move faster than ever. There’s never been a better time to just start and figure out the details as you go.

Cultivating a Culture of Building

My partner and I have built a strong culture of collaboration and problem-solving at home.

We set up a cozy double workstation even before we purchased a couch, a TV, or a dining table.

Being in the zone and completely locked in was critical for us. It got us through college, multiple hackathon wins, our engineering jobs, and now building our product studio, Foam On Latte Inc.

Here’s what I want you to take away from this:

If you have an idea sitting in your notes app, your Notion workspace, or just rattling around in your head — build it. Build a rough version. Show it to people. Get feedback. Iterate.

You don’t need perfect timing. You don’t need to wait until you feel “ready” because the stars will never align.

You just need to start. Because if you don’t try, you’ll never know.

This is Week 1 of The Disco Build. Follow along as we build Disco in public.

From 10-Week Project to Long-Term Partnership

Samina Rahman Purba — Mon, 22 Sep 2025 20:53:40 +0000

Thank you, from the bottom of my heart 💌

Huge thanks to everyone who read my last post, From Dev.to Posts to Running a Startup, and gave me a follow here on DEV. I never expected that sharing my entrepreneurial journey — the ups, downs, and struggles — would resonate with so many people.

In my previous post, I briefly mentioned the early days of my studio Foam On Latte and how difficult it was to land clients consistently and get them to pay us what we deserved. After months of underpricing ourselves and battling constant self-doubt, fear of failure, and rejection, we finally found some stability.

So, I'm going to make it a habit to post weekly about what I'm learning and building in my digital product studio. In these weekly blogs, I'll document product building, forming partnerships, and the projects we're building on our own.

I'll be sharing real case studies, real struggles, and the lessons learned through each project. Many of these short-term projects have turned into long-term engagements, and we're super grateful for that.

If you want to see more behind the scenes of my studio, follow me on Instagram.

Recent Project Highlight

We recently partnered with a mission-driven company based in Ontario that provides learning solutions for younger generations. They approached us to build an AI-powered gamified learning app designed to change how young people develop soft skills.

They needed Version 1 built in just 10 weeks. As a nonprofit, they had strict reporting requirements from donors and funding organizations.

In our initial call, I quickly found common ground. When I learned they were a nonprofit, I shared my background as a grant writer for Thai organizations before pivoting to tech, and my contributions to various nonprofits through open-source during Hacktoberfest. This connection immediately created trust and set us apart from others.

I understood the unique pressures of building tech in the nonprofit space: how the right metrics can make or break funding continuity, and how every feature needs to tie back to measurable impact for their stakeholders.

Together we designed the app to include:

Gamified soft skills development
Real-time experience tracking
Built-in community features for peer support
AI-powered growth recommendations
Dynamic resumes that showcase true potential
Workforce connections

How We Went From 10 Weeks to a Partnership

Obsessive Communication
This client came in with serious skepticism. They'd previously worked with a dev team that failed to deliver for an entire year. Knowing this, I provided daily updates, no matter how small the progress. Showing proof of work being completed and breaking down each piece weekly assured them we'd deliver on time.

Fast Bug Fixes
We didn't let bugs sit for days. If something was simple, we fixed it while the client was still on the call. With today's AI tools, it's easier than ever to quickly identify and ship fixes.

Valuable Strategic Advice
Since the client was non-technical, I provided extensive guidance on technology choices for cost savings, future-proofing the system, and optimizing product experience. This consultative approach showed we cared about their long-term success, not just completing the project. This also helped the client see us as true partners and not just a one-time vendor.

Kindness Goes a Long Way
Being genuinely kind and maintaining a sense of humour during client interactions creates lasting relationships. It sounds simple, but it's often overlooked.

This 10-week project evolved into a true partnership. We're now responsible for building Version 2 with more robust features.

The transformation happened because we treated the client as a partner from day one, not just as another project to complete.

I get it — it's not always possible to go from a one-time project to a long-term engagement due to budget constraints or other issues from the client side. However, if you show this level of care, you will also end up being recommended within their circle. This is another great outcome that happened to us, and it's been incredibly valuable for growing our business.

Question for you: What aspect of client relationships do you struggle with most? Communication? Pricing? Scope creep? Let me know in the comments.

Until next week — keep building, keep learning!

From Dev.to Posts to Running a Startup

Samina Rahman Purba — Fri, 08 Aug 2025 15:43:45 +0000

In 2022, I was learning how to make my first pull request on GitHub. Today, my development studio hit a $56K month milestone, with just three people on the team.

It's surreal to see just how much has changed. Looking back at my posts from 2022, I was just getting into open source, experimenting with new programming languages, doing Hacktoberfest, and exploring GitHub for the first time. A lot has changed since then. I worked as a software developer for about 1.5 years, then started my own web and app development studio with my partner.

Coming from learning how to squash and merge on GitHub to now managing client projects serving thousands of people around the world is a big jump, and it all happened in under 3 years.

A big thank you to the dev.to community. It is the first platform that welcomed me to share my coding journey, no matter how beginner my questions were or how small my wins seemed.

The Brutal Start

Diving into entrepreneurship was always part of the plan. I always had this deep desire and need to be involved in creative work where I'm in control—a place where I can get my hands dirty, live in the startup chaos, and even dream in pixels. No, really, I actually dream about my work nowadays. Is that normal?

I've always wanted to create and build applications for others that are as solid in the backend as they are scroll-stoppingly beautiful in the frontend. Most importantly, my definition of success in this world is the freedom to choose what projects I want to work on while creating value for others, especially other business owners.

So, I founded Foam On Latte Inc.

Foam On Latte is a full-stack product studio building web and mobile apps for startups worldwide. Here, I can not just work with amazing clients but also have creative control over my work.

Baby Steps, But We're Getting Somewhere

The first few months of starting Foam On Latte were brutal. We were SO scared to charge our clients because we were afraid of losing them!

Honestly, it was a totally valid fear.

We had zero projects in our portfolio at this point, $0 in revenue, and among thousands of mature development agencies out there, it seemed impossible to convince clients that we would be a valuable addition to their team. So, we underpriced ourselves to get our foot in the door.

We started working with very early-stage startups who also had no revenue or budget for their MVP development.

Did we burn out? Yeah, a lot. But was it finally worth it? Absolutely.

Outside the Comfort Zone

Everything changed when we decided to stop competing on price and start competing on value.

Our big break came when we landed a client who was already in business for 6+ years and had 8 figures in revenue.

Now, the scary part—we were, for the first time ever, going to charge higher than we had before.

We fired off the proposal and sat in silence for a few hours, thinking and overthinking that maybe the quote we sent was too high.

Did we just ruin everything? We were constantly battling these crippling thoughts, and my co-founder and I started arguing over the number.

I even called my mom asking if the quote I sent was too high.

Maybe the number should have been lower. Maybe... just maybe.

And THEN, a few hours later, our proposal got signed and approved! It all happened too fast for us to process. We started working on it the very next day.

This was suddenly the most money we had made from a single project deal—a $17,000 client.

Our confidence was restored, and it all felt like a fresh start.

A 17K Win and Then Silence

But things weren't all rosy and beautiful after that. There were many months of downtime after that initial win. We did not have a proper customer acquisition system in place.

We were just relying on luck.

After all, can you blame us? We were just a two-person team at this point.

The winter months, coupled with no projects on the map, were severely affecting my mental health. I started falling into depressive episodes, and my co-founder and I were questioning if we were cut out for being founders.

The Tipping Point

The whole notion of entrepreneurship was starting to feel like a house of cards. The dream that people sell of a digital nomad's life on the beach felt like a scam. But just as we were again taking some small projects that underpaid us, we got another massive break.

What happened next was unfathomable.

We landed a client in HealthTech, and then in the same month another client in FinTech, and then again in EdTech.

Three back-to-back huge clients who already had thousands of customers, established products, and good budgets.

And that became our biggest month — with $56,000 in contracts signed.

Our clients came in expecting to work with just another dev shop but found a deeply caring tech partner who became part of their team.

They became our biggest advocates, brought in other clients, and extended our contracts to become multi-phase projects.

Scrappy and Happy

Suddenly, I was also doing a whole lot more accounting, keeping track of invoices and learning how to set up payroll accounts. With that money flowing in, we finally had breathing room and space to experiment with a lot of side project ideas that had been sitting and rotting in our Notion folders.

Honestly, it all happened too fast. We are a small and scrappy team, deeply passionate about our work and in creating value.

Our unfair advantage is our team size and, dare I say, youth. Being twenty-something and full of energy really keeps us delusional enough to say yes to big projects and deliver, then overdeliver.

With nothing but work to think about all day, we work incredibly efficiently. We live in our Discord servers, pair program effectively, and plug in AI tools where necessary to speed things up.

What's Next

Working with clients has been great, but now we have a few more projects of our own. With AI prototyping now making it easier than ever to validate an idea, I understand there are no excuses not to build.

The journey from GitHub newbie to running a profitable dev studio taught me that the biggest barriers are often in our own minds. Sometimes you just need to be delusional enough to believe you can do it, even when you don’t feel ready, then put in the work to make it happen.

Our goal is to continue increasing monthly revenue through a mix of client work and our own suite of SaaS products. Honestly, we have a LONG way to go, but I am very happy with how far we have come.

If you're thinking about starting your own business or have questions about our journey, feel free to reach out. Always happy to help fellow builders.

2022 Highlights: Open Source Development! ✨

Samina Rahman Purba — Wed, 14 Dec 2022 08:53:06 +0000

Looking back at 2022, I can certainly say that this year has been one of the best years of my life in terms of self-growth, learning, and productivity.

Tech Skills Gained ✅

Cool projects I worked on

rwar - My static site generator
Exploit - A browser-based cybersecurity game built with three.js
Fragments - A cloud computing course project built with AWS tools
A Seneca College research project for automating the customer onboarding process using Optical Character Recognition (OCR).
Built multiple iOS and Android applications for my portfolio.

Open-Source Development 💻

I made some awesome contributions to these repos in the last 14 weeks.

intel/cve-bin-tool - 2 pull requests
ifmeorg/ifme- 2 pull requests
glific/glific-frontend - 1 pull request
flutter/flutter- 1 pull request
humphd/my-photohub - 2 pull requests
rahat agency - 1 pull request
fig/autocomplete - 1 pull request

Two most recent open-source contributions 2️⃣

1. My favorite repository: My-Photohub 📸

I began working on this repository a few weeks ago as an internal project of Seneca College. As someone who loves photography, I knew I had to contribute to this.

The issue: GitHub Action to Generate Website and Commit to Repo

GitHub Action to Generate Website and Commit to Repo #5

humphd posted on Oct 19, 2022

Similar to #3, we need a way to generate an HTML page that uses all of the optimized images. Once it has been created, we need to re-commit everything in the Actions filesystem back to the repo's gh-pages branch (i.e., we want the built web site to be put into the gh-pages branch).

View on GitHub

The solution 💡

This issue required me to work with GitHub Actions and what I had to do was use the images uploaded by the users and generate a website for them using GitHub pages.

GitHub Action to Generate Website and Commit to Repository #34

saminarp posted on Dec 08, 2022

Fixes https://github.com/humphd/my-photohub/issues/5

This GitHub Action workflow takes the images uploaded from optimized directory and generates a website using GitHub pages. See the example of generated website from this link

Preview of the website

Note: The branch is currently named as issue#5-gen-web. Every test image that is currently in the optimized folder is in this branch. It copies over to gh-pages branch to generate the website.

Once this gets approved, we need to replace the branch name (issue#5-gen-web) in publish.yml to main

To test

You can change your branch to issue#5-gen-web and upload your desired pictures to optimized directory. After a successful commit and a push, this branch will result in a gh-pages website.

View on GitHub

2. Risky contribution: Flutter 🔵

Flutter is an open-source UI software development kit created by Google and is used to develop cross-platform applications for Android, iOS, Linux, macOS, Windows, Google Fuchsia, and the web from a single codebase.

I took a huge risk making this contribution to Flutter, but I knew it was a very useful one and the biggest I have done. I wanted to step way out of my comfort zone to do something, unlike anything I had done before. At first, I did not think I would end up contributing to Flutter as I was just simply experimenting with the issue I was thinking about. After about four days of work, I figured it out. But of course, the pull request was not so smooth, and tonight I discovered I still have some failing tests which I need to address promptly.

A little bit of backstory... 📽️

This summer, I was working as a research assistant at Seneca College for their industry partner which is an exciting startup in the vehicle renting industry - similar to Turo.

I had to do a lot of research for an efficient and automated customer onboarding process for them as it was their number one priority.
Their mobile application was built using Flutter and I found myself looking at a lot of Flutter code. Even though I was not directly involved in building the mobile application, I was required to quickly learn Flutter and therefore, Dart which is the language used by Flutter.

The Issue 📝

I took a big risk and filed the issue myself before working on it! So, how did the idea come about?
As I was browsing through the 5000+ issues currently filed on Flutter, it felt intimidating. I was not being able to find the right issue to work on. I tried working on one and it was going nowhere. Then, I had this sudden aha moment after reading many issues and thought, why don't I just file the issue myself that I was thinking about and work on it? I had seen many others do the same.
The issue was filed by me as a new feature request.

Add a way to flip/mirror an widget #116702

saminarp posted on Dec 08, 2022

Use case

We need a named option to flip widgets horizontally or vertically. It's been mentioned in certain discussions that flutter does not provide a way to flip/mirror widgets. Though we can mirror a child by applying negative scaling, but it would be more appealing to have a dedicated option to flip/mirror widgets.

Proposal

Add a named constructor in the Transform widget to flip/mirror it's child

View on GitHub

The Solution ✅

Add transform flip #116705

saminarp posted on Dec 08, 2022

Adds Transform.flip to allow flipping/mirroring child widgets

Fixes https://github.com/flutter/flutter/issues/116702

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

</div>
<div class="gh-btn-container"><a class="gh-btn" href="https://github.com/flutter/flutter/pull/116705">View on GitHub</a></div>

Flutter uses a 4-dimensional matrix to transform the image a widget is producing just like OpenGL. To mirror that image we have to rotate it around an axis.

To mirror it horizontally we have to rotate it around the y axis by 180 degrees, and to rotate it vertically we have to rotate it around the x-axis by 180 degrees.
With that theory in mind, we can apply matrix rotation to get the expected results. And by applying the transformation we get the scary math results as in the photo.
I love maths!

Flutter already has transform widgets and it has named constructors to facilitate different transformations like translate and scale, but it did not have one to flip/mirror. So inspecting their way of implementing those transformations, I simply plugged in the values for the final matrix for the arguments flipX and flipY. :)
I know it sounds simple, but it took me a lot of figuring out and studying the codebase to come up with this. I did not honestly think it would work out as I was just experimenting with it and ...ta-da... it did work out!

The hardest part about the PR was writing the tests. It took a lot of research, trial, and error. It took me around 4-5 days to complete the entire pull request and I still am fixing some failing CI/CD workflow tests.

Going forward... 🚀

I need to improve on code reviews and it is a big part of my 2023 goals.

✨Day in the life of a college student during finals week - self reflection blog

Samina Rahman Purba — Sat, 10 Dec 2022 08:01:48 +0000

Dear college students,

I am sure we all can relate to this.

Finals week is here, and everything is about to go to..... bleep

Why are all the assignments due on the same day?

I sleep and wake up at unusual times.

Maybe I can implement a few more features before sleep for my cloud computing assignment. Maybe just one more cup of coffee will keep me awake for a few more hours. Well no, the extra cup of coffee just made me jittery and now I am left with a racing heart.

There is no sleeping schedule anymore. There are just random hours of sleep in a 24-hour period.

Upon waking up, I check my email and Slack and Teams messages.
My messages are somewhat like this:

"CI/CD failed from the flutter pull request I had done." Great!

"Your assignment 4 is due tonight." Awesome.

"Your promo code that is set to expire in 24 hours for Ugg boots."

I panic. Because the decision is tough. I have just 24 hours to decide that if I fit in another pair of Ugg boots in my meticulously planned Christmas shopping list already containing 993732 items, will I suffer financially?

Back to reality.... 💭

I panic. I realize I have no time for Christmas shopping. It needs to happen after the finals. Well, will the stuff I like be out of stock before the finals?

I think of this, and I stress even more.

The Uber Eats bill is piling up fast.

My bank app is displaying a warning message stating there might be a possibility of duplicate charges from the same merchant. No mistakes there. It's all me.

I pour my Starbucks coffee beans into my french press. The first sip of the morning coffee feels like an elixir. I eat my daily dose of morning eggs and protein wraps and promptly sit to study.

7 hours later ⏰

I finally debugged the flutter issue I was working on. Debugged. It all looks good. All the checks pass now. ...

I take a small break, stretch out my legs, and eat a meal...

I catch a glimpse of myself in the mirror and I notice new stress pimples.

Time to study again 🥹📖

Another 6 hours later ⏰

I think to myself, "wow that was a productive 6 hours".
At this point though I feel my cognitive functions declining.
Maybe I should nap or maybe I should get more coffee.

I look at my TODO list and I get a momentary sense of deep satisfaction every time I mark something as done; but then I realize I have a lot more in blues and pinks than greens.

This is what a typical day for me looks like leading up to finals. But this is neither healthy nor sustainable. So, don't be like me during finals week. This semester I took five difficult courses, but I am glad this is my last semester.

In my previous blog - I set myself some really big goals for December..So far, I am really satisfied with how much I have accomplished. I also realize that if I focus, really focus on my work without distraction for hours, I can get so much done.

What's going good? 😃 ✨

1) The open-source contributions are going well!
- I was able to successfully make pull requests to flutter and to my-photohub
- I am currently working on responding to the issues I worked on.

2) I have also been keeping up with the advent of cyber but fell behind on the advent of code. But not to worry. I am going to catch up right after the finals.

3) I have also responded to some changes requested for a pull request I did last month for fig/autocomplete and had it successfully merged yesterday.

4) Most of my assignments are complete. Thanks to careful planning, Uber Eats and the Thai food store 5 mins away from me.

What's not going good 🥲

1) I am behind on code reviews and I realize I should put more effort into it.
2) I missed out on writing two blogs for my static site generator.
3) I had no time to workout for the last two weeks

Thank you all for reading! Next blog will be filled with technical details about my pull requests made for flutter and my-photohub.

Also, I just started a brand new desk setup and studygram on instagram... Please do give me a follow on Foam On Latte!

☃️ My December Goals🎄: ending the year right by learning new things ✨

Samina Rahman Purba — Sun, 04 Dec 2022 06:12:42 +0000

About 12 weeks ago, I set on a mission to get comfortable with the uncomfortable. I decided to try out open-source development and contribute to interesting projects on GitHub. It was an amazing process in terms of learning new technologies, communicating with others, getting active in the open-source community, and building my resume. Over the next 10 days, I will be contributing to more open-source projects and working on some small issues or bugs. Not just that, I also came across some amazing challenges to take part in to learn new things and end the year on the right note. I will be blogging about my progress along the way!

1) More Open Source Project Contributions 🚀

For the next two weeks, I will be focusing on making contributions to a few open-source projects. Although I have not settled on which issue I will tackle yet, below I have curated a list of potential repositories I will contribute:

1) My-Photohub: This is a Seneca College student-run project. Previously, I already contributed to this project where I wrote code for the functionality of uploading resources to GitHub.

2) Glific-frontend: This was a project I had the opportunity to work on during Hacktoberfest. I loved the idea behind the project and how it was helping to solve a crucial challenge for community-led organizations regarding data collection at a grassroots level. I am planning on working on one front-end issue from Glific. They are also a very welcoming community of people and ready to answer questions whenever I have any.

3) Intel/cve-bin-tool: There are some issues I found here that seemed interesting to me to work on, especially related to refactoring the code or creating new checkers.

4) Some other cool repositories I found containing beginner-friendly issues:
- pandas
- freeCodeCamp
- pytest
- bokeh
- flutter

I am not entirely sure I will end up successfully contributing to any of these repositories yet. We will find out in my next blog!

2) Advent of Cyber 🤖

Stumbling upon this amazing challenge was one of the best things for my December learning goals. If you like me and want to learn the basics of cybersecurity, while solving fun challenges and then getting a certificate in the end, this is perfect!
For my project management and implementation course at Seneca College this semester, my teammates and I are building a browser-based cybersecurity quiz game with three.js. This was one of the most difficult projects I have been working on over the last 3 months. Advent of Cyber is great for learning those basics and then applying them to building content for the gaming project I am building.

3) Advent of Code 💻

Advent of Code is great for putting our problem-solving skills to work! We can solve the puzzles in any language we like and do not require knowledge of any fancy tools or frameworks. When I attempted doing Advent of Code last year with just a few months' worth of coding experience under my belt, I felt miserable. This year, I want to challenge myself to go through all the questions and attempt to solve them with a mix of using JavaScript and Python.

4) Advent of JavaScript 📺

This is another cool challenge to try if you are into JavaScript or want to improve on it. I found this somewhat accidentally when I was just randomly googling "advent of stuff".... Although, the first three are my priority I would love to give this a go and complete it if I can manage the time.

Some Non-Code Stuff 📝

Apart from coding, I also do a lot of writing for Asia-based community-led organizations and non-governmental organizations. I am ending the year writing and designing a 25-page report for a Bangkok-based organization summarizing the impact of COVID-19 on marginalized populations over the last two years based on research materials they provided me.

So...let's make the most of the last month of the year and have fun doing some amazing projects and challenges!

✨Today I learned: Using Octokit! 🐙✨

Samina Rahman Purba — Fri, 25 Nov 2022 07:24:38 +0000

A little reflection...

As important as it is to set goals, it is also important to measure progress along the way. I wanted to take a moment and see how far I have come in my first couple of months of open-source development journey and what more I want to achieve.

Part of the goal I set for my open-source development journey is to aim for continuous progression and development. Hacktoberfest was a great way for me to navigate the mysterious world of open-source projects. Well, a little less mysterious than before. I am more comfortable now with the process of forking, cloning, experimenting with a project, and following the contribution guideline rules to make a proper pull request. I also learned to be more professional in my communication with maintainers and make changes according to their requests. I am also better at reading contribution guidelines now and following them.

The Project

Along with a small team of incredible developers, I decided to work on the My Photohub project.

As stated in the README.md

My Photohub is a web app that makes it easy to share your photos on the web. My Photohub takes your images and optimizes them for the web, creates a beautiful HTML page to show them, and hosts everything in a new GitHub Repository owned by you! Your photo web page is made available to the world via GitHub Pages. Best of all, everything is free, and you are in control of the end product.

As someone who loves photography and working with images, the moment I saw this project, I knew I had to contribute to it. I also liked the idea of using GitHub to upload images, it felt original and innovative.

Teamwork

Having a great team all sharing a common vision and being equally motivated and active is so important to making a project work. I was truly lucky to have worked on the My PhotoHub project with some brilliant developers who were ready to review my code, provide feedback and actively communicate on our team chat. Since the project was new, it took a lot of coordination and communication to figure out the conflicting parts of the code could be resolved and turned into one properly functioning whole.

My Contribution

Issue: "Figure out how to 'upload' resources to GitHub"

Most of the time, in order to make code contributions, we need to have some idea of what the entire codebase is doing or what the project is about. Unless, of course, the issue is very minor and won't affect the entire project. I had to look through the pull requests of two other members of the team to have an idea of how to approach 'uploading' resources to GitHub.

What is Octokit? 🐙

To contribute to this project, I first had to learn about Octokit. I never used it before for any of my projects so I had to read some articles about it first and go through the documentation.

Octokit is a lineup of GitHub-maintained client libraries for the GitHub API.
The Octokit client can be used to send requests to GitHub's REST API and make queries to GitHub's GraphQL API.

Example taken from the documentation: Get the username for the authenticated user.

// Create a personal access token at https://github.com/settings/tokens/new?scopes=repo
const octokit = new Octokit({ auth: `personal-access-token123` });

// Compare: https://docs.github.com/en/rest/reference/users#get-the-authenticated-user
const {
  data: { login },
} = await octokit.rest.users.getAuthenticated();
console.log("Hello, %s", login);

I came up with the code below to upload the resources following the pull requests for other issues for the project. To form the logic, the documentation was my main source of guidance. It had a lot of code examples for me to follow and work with.

import { Octokit } from "https://cdn.skypack.dev/octokit?dts";

const UPLOAD_DIRECTORY = 'raw'

function getBase64(file) {
    return new Promise((resolve, reject) => {
        const reader = new FileReader();
        reader.readAsDataURL(file);
        reader.onload = () => resolve(reader.result.substring(reader.result.indexOf(",") + 1));
        reader.onerror = error => reject(error);
    });
}

export async function githubUpload(token, repository, file) {
    const octokit = new Octokit({ auth: token })
    const [owner, repo] = repository.split('/')
    return await octokit.request('PUT /repos/{owner}/{repo}/contents/{path}', {
        owner,
        repo,
        path: `${UPLOAD_DIRECTORY}/${file.name}`,
        message: `Upload File - ${file.name}`,
        content: await getBase64(file)
    })
}

Going forward... 🚀

For the next few weeks, I want to actively work on turning the My Photohub project into a functioning application. There are important bits and pieces of it still missing and I want to actively contribute to making it whole.

What's so cool about Fig Autocomplete? 💭

Samina Rahman Purba — Tue, 22 Nov 2022 21:25:44 +0000

The Perfect Trio ³

It was around 2:00 am when two of my classmates (Batu, TD) and I were online sharing our screens and helping each other out with an open-source project. We were scanning the documentation as we kept working, cautiously coding away to maintain proper style and clean code. We each picked an issue to work on and reviewed each other's codes at the end to squash any bugs ahead of time before making the pull requests.

The three of us decided to work on Fig - a tool that provides IDE-style autocomplete but for the terminal. As developers, we all know how important the terminal is. We thought this would be a cool project to contribute to since we use this tool daily.

What's So Cool About `Fig Autocomplete` ❓📺

As written in their README:

Fig makes the command line easier for individuals and more collaborative for teams.
Our most popular product is Autocomplete. As you type, Fig pops up subcommands, options,
and contextually relevant arguments in your existing terminal.

Look how beautifully it gives suggestions

To install Fig:

brew install fig

I use Fig every day. The Fig autocomplete repo had clear documentation and a lot of activity going on. Plus, it was written in Typescript, a language I have experience with. The development environment setup took only a few minutes, again, thanks to the clear documentation. I scanned the list of issues and found an interesting one.

Issue: hyperfine missing spec

What's `Hyperfine`❓ 🤖

Hyperfine is a command line benchmarking tool with the following features as written in their README.md

Features

Statistical analysis across multiple runs.

Support for arbitrary shell commands.

Constant feedback about the benchmark progress and current estimates.

Warmup runs can be executed before the actual benchmark.

Cache-clearing commands can be set up before each timing run.

Statistical outlier detection to detect interference from other programs and caching effects.

Export results to various formats: CSV, JSON, Markdown, AsciiDoc.

Parameterized benchmarks (e.g. vary the number of threads).

Cross-platform

To install hyperfine I did:

brew install hyperfine

So let's say I type hyperfine ls. This shows how much time it takes the ls command to run on my computer. Below, you see the screenshot of the command run on a 2020 Intel MacBook 13-inch 2020 model with 16 GB RAM.

And this one was done on my 16GB 2021 M1 iMac.

Honestly, this was fun for me to watch the performance metrics. I then followed the documentation and played around with a few other commands across all my machines.

What Are `Completion Specs`❓ 📝

For this issue, I had to write a completion spec for hyperfine. Completion specs are:

A completion spec is a declarative schema that specifies the subcommands, options, and args for a CLI tool. Fig uses these schemas to generate suggestions.

As mentioned in the issue above, the hyperfine completion spec was missing. I had to read through the documentation very carefully and study the manual of hyperfine to figure out how to get this working.

After typing in man hyperfine on my terminal to pull up the hyperfine manual, I studied the long list of options and commands for the type of arguments I had to pass in. Then, I started coding.
The file ended up being almost 300 lines long, but here is a small snippet of the code structure.

As I was doing the autocompletion spec, I was testing the commands as well to make sure they were working as intended. I also had two more pairs of eyes checking and testing my work before I made the pull request.

Measuring My Progress 📏

This was a much bigger pull request in an open-source project compared to the ones I had done before. I realized that previously I spent way too much time just setting up the development environment and it took time away from the actual coding part itself. I was also working with unfamiliar languages so the scope and size of my contribution were small. This time I decided to work on a bigger repo and write more lines of code.

So, what are some of the things I did right this time, compared to Hacktoberfest which was my very first plunge into the world of open-source development?

1) I read the CONTRIBUTING.md file and followed it.
2) I used proper commit messages as they specified as their guideline.
3) I used proper naming conventions.
4) I looked through their examples of completion specs to make them consistent with others.
5) I squashed and rebased my commits.
6) I was more professional in my communication while making the pull request.
7) I collaborated with others working on this repo so that we can speed up the process and help each other out.
8) I did a lot more research on the topics - in this case, hyperfine and completion specs, before writing code.

Note: I received some feedback from the maintainers to make some minor changes and I am currently working on fixing them.

Well, it is quite evident that as a beginner I learned a LOT of things contributing to open-source projects and I continue to learn something new each day.

✨Today I Learned: The Subtle Art of Code Reviews 💡✨

Samina Rahman Purba — Sun, 20 Nov 2022 08:14:07 +0000

Code reviewing is hard. The pull requests I reviewed were for the My Photohub project.

Code reviewing for the first time in my life made me realize how difficult the task is. As a first-time code reviewer, I found myself staring at the code, pondering about what could be done to make it better. Feeling rather lost. I came up with some mediocre suggestions. Nothing too great. Nothing that I felt truly satisfied with suggesting. Then came professor Dave to do his code review on the same pull request I was reviewing. I just sat there astounded at the details he looked at and all that I missed. He suggested major things such as better programming logic, and minor things such as updating the project description. I could have suggested those minor issues too; a better project description, a better logo that goes with the project instead of the default React logo, and creating follow-up issues for certain things. Why did I overlook the obvious, which professor Dave so elegantly and effortlessly pointed out?
Well, I was so fixated and overloaded with trying to find something big to suggest that my senses had completely shut down on the easy stuff. This made me realize just how much I need to practice reading other people's codes and thinking critically about them. Like attaining mastery in any skill, being a good code reviewer is a skill that takes time, patience, and practice.

Some code review best practices 🌱

This is a great article I came across while researching for the code review best practices.
It beautifully elaborates on how design, functionality, complexity, testing, naming, commenting, style, consistency, documentation, and context are all important components of a code review.

Time. Attention. Communication ⏳‼️

A good review takes time and attention. It requires us to think critically about the programming logic. For beginners, it can feel overwhelming to stare at the code someone else wrote to suggest something meaningful. There is a fear of being wrong. A fear of offending the person writing the code. I know, because I felt all those. However, in open-source development, it is always important to remain polite and respectful in communication while giving constructive feedback. We can sometimes disagree with the review but if we do so, we should communicate that politely.

It is also important to keep an open mind while giving and receiving feedback. It is through this exchange of ideas, and feedback that we can improve over time.

If you have some coding experience and spend enough time and give undivided attention to the code, it is almost always possible to come up with suggestions for improvement.

Start small 🐌 🌱

If you are a beginner, start small and learn from others. I learned a lot of important things by reading professor Dave's reviews. Then I realized that it is by seeing how more experienced people review code, that I can get better. I made some notes of the things I learned by reading a lot of his code reviews on GitHub. I turned those things into some sort of a checklist:

Ask specific questions regarding certain lines of code, if unclear.
Look for unused dependencies and ways to optimize package.json.
Look at the code from the context of the entire codebase.
Leave some words of encouragement to point out what the developer is doing right!
Focus on functionality and compatibility.
Look for clear names and proper naming conventions.
When reviewing README or CONTRIBUTING.md files, look for consistency in style, formatting, spelling, and grammar.
Make sure that the design and UI look good.
Ensure that the unit tests are appropriately designed for the code.
Make sure that the code conforms to a certain style guide provided.

My code reviews

Here are the code reviews I did over the last few days. Click on the links to view the entire review :)

While suggesting changes, I also provided the rationale behind suggesting the changes and asked for the developer's opinion. This kept communication professional and polite.

Review 1

Review 2

In `linters` we trust 🚀

Automated code checkers and static tool analyzers can help a reviewer save a lot of time looking for silly typos or stylistic errors. Linters and scanners act like spell and grammar checks for a code. With the headache of formatting and other stylistic issues out of the way, the reviewer can focus on the actual logic of the code. As code reviewers, it is essential to make use of the automated code checkers available to save time and sanity.

Closing thoughts on productivity 💭

If you are someone like me who loves reading about psychology and productivity, this is a great article!

🧪🐍✨Unit Testing Python Code With The unittest Framework

Samina Rahman Purba — Mon, 14 Nov 2022 01:26:59 +0000

Unit testing is an important part of software development as it isolates different components of a software program or system and checks if it operates the right way. It ensures that the code meets quality standards and that flaws or bugs in a system can be properly traced back to the isolated unit of code that is failing, and remedy the failure promptly.

My static site generator - rwar is evolving and getting better over time, which means I need to ensure that the code is professional and of high quality! Also, being able to work with testing frameworks and learning them well can help you stand out during interviews. 😃

The learning curve 📚🧠

I was not used to writing tests much for the personal projects and small group projects I have worked on so far, which is why thinking of code from a test-driven perspective was challenging for me. I could feel my neurons firing as I was trying hard to think how to put all the unit testing pieces together. Until now, I only had a little bit of experience working with the Jest testing framework for JavaScript, and Junit for Java, so I had to go through a big learning curve to understand the unittest framework. This explanation was really useful for me to get an overview of what unittest is and how to get started with it. I used to underestimate the importance of reading documentation, but I know now how crucial that skill is.

Why `unittest` framework❓

Upon doing some research on some of the most popular testing frameworks for Python I came across pytest, nose, and unittest. They are all great tools, however, I decided to give unittest a try for this project because unittest was inspired by JUnit which I had some prior experience with. It is always good to experiment and learn different frameworks to eventually find out what we like most. I am going to give pytest a try for my next Python project. Each testing framework has its conventions for naming files and structuring code, which is another important reason to look at examples and go through the documentation for the framework of your choice.

Having a good test plan 📝

It is really important to have a good test plan before starting.

1) Understanding what your code does

What kind of inputs the function takes
What are the program's functions
What are the expected outputs

2) Good and bad test scenarios

Think of the success cases and cases that are anomalies. For example, if you are building a school management system - adding the same student twice should result in some sort of warning.

3) What does not need testing

A good example of what does not need testing would be functions from external packages. Another example would be a program invoking functions where the code was already tested.

4) Writing the tests

Then, comes the test writing part!
For example, if you are building a school management system - then you can test for functions such as adding students, loading an existing student, adding the same student twice, and so on.

The process 🔨

For my project I have created two test files - test_parser.py and test_ssg.py - under the test folder.

As stated in this documentation:

unittest requires that:

You put your tests into classes as methods

You use a series of special assertion methods in the unittest.TestCase class instead of the built-in assert statement

1) To get started with unittest I first had to:

import unittest

2) Then, I created a class SSGTest that inherits from the TestCase class and it is meant to test my class SSG

class SSGTest(unittest.TestCase):

Similarly, I have done this for my other test_parser.py file.

class CLIParser(unittest.TestCase):

An example:

It is hard to go over all the test I have written for my project because there are many! However,
here is an example from test_parser.py. Notice, how I have used descriptive names for my test. Here I am checking if the test has any input files or not.

class CLIParser(unittest.TestCase):

def test_without_input(self):

with self.assertRaises(SystemExit) as err:

get_parser_args([])

self.assertEqual(err.exception.code, 2, "No input directory provided")

assertRaises() verifies that a specific exception gets raised.

with self.assertRaises(SomeException):
    do_something()

assertEqual() checks for an expected result.

with self.assertRaises(SomeException) as cm:
    do_something()

the_exception = cm.exception
self.assertEqual(the_exception.error_code, 3)

When to use setUp() and tearDown() ❓👀

If you go through my code on test_ssg.py, you will see that I have used the setUp() and tearDown() methods. For every test in test_ssg.py, a temporary file was created which needed to be deleted after the test, which is what I could accomplish with setUp() and tearDown(). These were repetitive processes that I could simplify using these methods. Imagine you have a suite with 10 tests and 7 of them require the same setup/teardown code, while the 3 don't, setup and teardown gives you a nice way to refactor the code. It is often used when we need to create a fake database for testing purposes or for mocking purposes.

Here is an example of how I have used it in my code:

class SSGTest(unittest.TestCase):

def setUp(self):

self.tempdir = tempfile.TemporaryDirectory()


self.output = self.tempdir.name

self.input = os.path.join(self.output, "input")

os.mkdir(self.input)

self.stylesheet = "test-stylesheet-link"


def tearDown(self):

self.tempdir.cleanup()

Test discovery 💡

Test discovery is the process of locating where the tests are in your codebase. This means that you don't have to explicitly state where the tests are located as the testing framework can automatically locate them based on the matching patterns of the naming convention. In this case, it will look for test*.py `files.

As stated in the documentation:

Unittest supports simple test discovery. To be compatible with test discovery, all of the test files must be modules or packages importable from the top-level directory of the project (this means that their filenames must be valid identifiers).
Test discovery is implemented in TestLoader.discover(), but can also be used from the command line. The basic command-line usage is:

cd project_directory python -m unittest discover

Upon running that command, it shows the number of passing and failing tests. I had two tests that were failing, so I went back and fixed those before pushing my changes to GitHub.

Documentation ✏️

A good software or system is properly documented. I used to underestimate the value of documentation until I participated in Hacktoberfest and had to work on large open-source projects. Some interesting projects I wanted to contribute to had unclear documentation and even though I wanted to work on them, I just couldn't. The projects I ended up contributing to were all properly structured and had clear documentation.

The same goes for rwar. I am trying to write clear documentation so that anyone interested in using it or contributing to it will find it easy to do so. I have added the instructions for testing on the CONTRIBUTING.md file!

For the full codebase, please feel free to check it out on GitHub :)

Part 2: Building a Cybersecurity Game with Three.js - Inspired by Google’s Interland

Samina Rahman Purba — Wed, 09 Nov 2022 03:26:11 +0000

Preview 👾

In part 1 of this series, I talked about how we were inspired by Google Interland's Reality River and decided to build a cybersecurity game similar to it with three.js called Exploit. We wanted to create a lightweight browser-based game that would be fun, engaging, and educational. As complete beginners who are learning three.js for the first time and also our first game-building experience, we are happy with our progress.

Each week we are working hard coding as a team, to meet our deadline of having a basic version of the game ready by mid-December 2022. We also wanted to publish weekly blogs as we believe it might help out others who are interested in game development to see what the process is like for beginners. We did not find many game development processes being blogged out so we believe documenting this will be of massive value to those interested in three.js, game development, open-source development, and collaborative coding!

After our initial release in mid-December, we invite all developers interested in open-source to contribute to this project!

What's new ❓🤖

Our little game character that we call threat hunter is now able to jump from one building to another as it answers questions. Last time, we did not have any buildings or environments at all. However, this time our threat hunter and its question-answering ability is fully functional.

This logic of our character jumping through buildings is very similar to Google Interland's game where the little character crosses a river successfully upon answering questions.

Disclaimer: However, the game is still buggy at the moment and we are working hard to debug them. The question display sometimes fails and sometimes the character keeps walking endlessly without stopping. But hey, it is okay, this is a work in progress and we are going through a huge learning curve working on this project.

To check out our progress so far you can always visit our GitHub repo for the game environments. Please see the GitHub issues as our project documentation.

The code for our awesome character resides here.

We have also created some user stats such as modules completed, last score, and time taken to complete those modules.

We also have a dynamic leaderboard now which shows the scores of all the users playing the game for each module. For example, if I play the ransomware module, then my scores will appear under the ransomware leaderboard dynamically.

Experimenting 🔍🌘

Until this point, we had to go through many trials and errors to figure out how the environment would come together. The three.js documentation was our main source of guidance while implementing this project. We experimented with creating clouds, different positioning of the buildings, shadowing, and sphere geometry. In our environment, we have the moon, clouds, and buildings so far and of course, the game character that interacts with its environment. Since the moon was the very first component of the environment we worked on, I want to provide some code snippets to explain it.

The moon 🌙

We started by working on the moon for a night sky. There are many things to consider while making a game environment. We find textures and think of the camera setup, renderer setup, and light directions.

As shown in the code snippet below, we first defined the moon.

// <Define Env Components

const moon = new Group(); 

moon.add(

new Mesh(new SphereGeometry(200, 1800, 1800), new MeshPhongMaterial({ map: this.textures.moonTexture, displacementMap: this.textures.moonDisplacementMap, displacementScale: 0.0, bumpMap: this.textures.moonDisplacementMap, bumpScale: 0.04, reflectivity: 0, shininess: 0, emissive: 0xffffffff, emissiveMap: this.textures.moonTexture, emissiveIntensity: 12 })),

new PointLight(0xffffff, 1, 5000),

);

moon.position.set(1200, 350, 0);

What is mesh?

A mesh is a collection of vertices, edges, and faces that describe the shape of a 3D object:

A vertex is a single point. The plural is "vertices".
An edge is a straight line segment connecting two vertices.
A face is a flat surface enclosed by edges.

We can kind of imagine it to be like the skeleton of an environment, to which we need to add texture on top to make it realistic.

What is texture?

Textures add artistic control and realism of a game. For creating our moon, we had to download some realistic moon textures and then use the textureLoader function to load them. We then read the documentation of sphere geometry and displacement maps to build the moon. Afterward, we set the moon's positions and gave it a point light. So, what is point light? As written in their documentation, "A light that gets emitted from a single point in all directions. A common use case for this is to replicate the light emitted from a bare lightbulb."

const moonDisplacementMap = textureLoader.load('displacement.jpg');

const moonTexture = textureLoader.load('moon.jpg');

const moonBody = new Mesh(new SphereGeometry(200, 1800, 1800), new MeshPhongMaterial({ map: moonTexture, displacementMap: moonDisplacementMap, displacementScale: 0.0, bumpMap: moonDisplacementMap, bumpScale: 0.04, reflectivity: 0, shininess: 0, emissive: 0xffffffff, emissiveMap: moonTexture, emissiveIntensity: 12 }));

const moon = new three.PointLight(0xffffff, 1, 5000);

moon.position.set(1200, 350, 0);

moonBody.position.set(1200, 350, 0);

What is game physics? 👀

Physics simulation is a field within computer science that aims to reproduce physical phenomena using a computer. In general, these simulations apply numerical methods to existing theories to obtain results that are as close as possible to what we observe in the real world. (Source: Toptal)

Games are getting more and more realistic and part of this realism is also ensuring that the laws of physics we see in the real world also apply to the virtual gaming world. Things such as collision detection, gravity, joint movements, inertia, acceleration, and mass are all part of game physics. As someone who loves science, thinking of the game from a physics perspective was very exciting.

Three.js usually works better with another physics engine such as Ammo.js. There are a handful of JavaScript physics engines available such as Matter.js, Planck.js, Cannon.js, Oimojs, and Ammo.js. For this project, we will be experimenting with Ammo.js. We are not entirely sure yet how that will go in our initial release of this project, given the time constraint. We will find that out in the next blog.

Thoughts 💭

This is, by far, the most challenging project I worked on in my college life. It is also occupying most of my time as learning all this amazing new JavaScript 3D library is time-consuming but also rewarding.

Moving forward...🚀

1) Better use of GitHub

As a team, we have not been keeping everything clean on GitHub. Moving forward it is going to be our focus to write cleaner code and organize the folders more to enhance professionalism.

2) Continuous improvement

And of course.. we have a LOT to debug and keep working on for the game environments.

This is going to be a many-part series so stay tuned for the next blog!

Thank you all for reading and being part of this crazy game-building journey!! 🪐

Forem: Samina Rahman Purba

Building Disco Week 2: Making Event Networking Less Random 🪩

Finding the right people to build with ✨

What Disco is hoping to solve 🪩

The Disco Build 🪩 Week 1: MVP Sprint

If You Have an Idea, Build It

If You Don’t Try, You’ll Never Know

Early Signs of Validation

Cultivating a Culture of Building

From 10-Week Project to Long-Term Partnership

Thank you, from the bottom of my heart 💌

Recent Project Highlight

How We Went From 10 Weeks to a Partnership

From Dev.to Posts to Running a Startup

The Brutal Start

Baby Steps, But We're Getting Somewhere

Outside the Comfort Zone

A 17K Win and Then Silence

The Tipping Point

Scrappy and Happy

What's Next

2022 Highlights: Open Source Development! ✨

Tech Skills Gained ✅

Cool projects I worked on

Open-Source Development 💻

Two most recent open-source contributions 2️⃣

1. My favorite repository: My-Photohub 📸

The issue: GitHub Action to Generate Website and Commit to Repo

GitHub Action to Generate Website and Commit to Repo #5

The solution 💡

GitHub Action to Generate Website and Commit to Repository #34

Preview of the website

To test

2. Risky contribution: Flutter 🔵

A little bit of backstory... 📽️

The Issue 📝

Add a way to flip/mirror an widget #116702

Use case

Proposal

The Solution ✅

Add transform flip #116705

Pre-launch Checklist

Going forward... 🚀

✨Day in the life of a college student during finals week - self reflection blog

Back to reality.... 💭

7 hours later ⏰

Time to study again 🥹📖

Another 6 hours later ⏰

What's going good? 😃 ✨

What's not going good 🥲

☃️ My December Goals🎄: ending the year right by learning new things ✨

1) More Open Source Project Contributions 🚀

2) Advent of Cyber 🤖

3) Advent of Code 💻

4) Advent of JavaScript 📺

Some Non-Code Stuff 📝

✨Today I learned: Using Octokit! 🐙✨

A little reflection...

The Project

Teamwork

My Contribution

Issue: "Figure out how to 'upload' resources to GitHub"

What is Octokit? 🐙

Going forward... 🚀

What's so cool about Fig Autocomplete? 💭

The Perfect Trio ³

What's So Cool About Fig Autocomplete ❓📺

Issue: hyperfine missing spec

What's Hyperfine❓ 🤖

What Are Completion Specs❓ 📝

Measuring My Progress 📏

✨Today I Learned: The Subtle Art of Code Reviews 💡✨

Some code review best practices 🌱

Time. Attention. Communication ⏳‼️

Start small 🐌 🌱

My code reviews

Review 1

Review 2

In linters we trust 🚀

Closing thoughts on productivity 💭

What's So Cool About `Fig Autocomplete` ❓📺

What's `Hyperfine`❓ 🤖

What Are `Completion Specs`❓ 📝

In `linters` we trust 🚀

Why `unittest` framework❓