Building & Learning in Public

Photo by luis gomes

What is building & learning in public

Building in public is sharing your journey, processes, successes, and failures while creating a product, service, or project & learning in public is openly documenting and sharing your learning journey, including insights, mistakes, and growth experiences.

The reason I'm thinking of doing this is because I find that I work on a lot of projects, and I always think results should only be shown upon completion or perfection of the project or when learning something is completed.

Benefits of building & learning in public

Building in public, allowing others to comment on the project and provide feedback can lead to new ideas, effective ways to accomplish things and other benefits. This also presents an opportunity to grow and learn from other developers and hopefully, other developers can learn and be inspired by these projects.

Learning in public shares the same benefits as building in public, as well as allowing others to learn from your experiences and offer helpful advice and building a community of like-minded individuals.

Side note, your commit graph on GitHub is going to make you look like a hard worker, my teammates figured out my scam, I write a single word in a text file, and I'll commit to a public repo, check my profile (In case you read this paragraph, I don't do that😂😂)

What is going to be built & learned

Currently, there are a few things that have gained my interest.

• SAAS & web applications 👨💻. There are a lot of SAAS 7 web applications out there, but If I plan on learning, making my own will help me grow. For example, if there is an authentication SAAS I'm making, I could just use Clerk, Firebase Auth, Supabase Auth, or any other SAAS out there, but I would not learn how auth works under the hood. I want to implement password resets, two-factor authentication, and OAuth and learn how those work. By making my own, I run into these problems and I am forced to come up with or research solutions that reinforce what I have learned. (Another benefit is if I am successful, I can use the SAAS in my other pet projects). The aim is not to make a successful company but to learn & grow.
• Learning the cloud ☁️. For some time, I've had an interest in the cloud. The idea that I can rent computing resources from companies like AWS, Azure or Google Cloud Platform is fascinating. I don't have a beast of a laptop, nor do I have a bunch of servers lying around, so using (let's forget the fact that I recently finished school and that I am an unemployed adult with no money😂😂) so spinning up resources that I can deploy SAAS and web applications sound cool. If you think this is cool, you are a geek, my friend.
• Learning about the data world. In a recent screening assessment, I heard the title, Data Engineer I did not know what that was, so as soon as the assessment was done, I ran to YouTube, and searched what a data engineer is (I saw things about pipelines, data lakes/warehouses, uses of python & SQL aka squeal). The more I saw, the more I saw other cool
• Other cool stuff like Webflow/Framer etc... I'll see if something cool pops up.

Results

All of this will result in absolutely nothing😂. I think it's all cool, I'm learning new things and I want to share the different things I'm exploring & learning.