Hello everyone,
As I mentioned in a previous article, I’ve embarked on a new series called The 10-Minute Company. This idea has been on my to-do list for years. Now that it’s finally happening, I can’t decide whether to feel thrilled or terrified—probably a mix of both! Over the next few months, I’ll be dedicating significant effort to this project.
In short, the concept behind this series is simple: pick an idea (ideally a small one), develop it, and journal the process publicly. It aligns closely with the “build in public” philosophy but on a smaller, more approachable scale.
I’m fully aware this won’t be an easy journey. Creating software is already challenging, and doing it in public adds a whole new layer of difficulty—at least for me.
Why This Series?
This is a challenge, no doubt about it, especially because it requires consistency. However, I believe the potential benefits make it worthwhile.
Before diving into my goals and expectations, let me share some context about my life and why I think this series could be beneficial, both for me and for others in my field.
A Few Facts About Me
I love learning about tech-related topics, often after my daily work hours.
I rarely create tangible examples or demos for the challenges I explore.
My interests span various domains beyond software, which often spark ideas for my projects.
I enjoy designing software to solve specific problems.
My free time is limited.
I need a structured way to stay focused on my side projects.
Since I began working in the field in 2011, I noticed that many job opportunities in the Italian tech scene came from consultancy firms that typically handle diverse projects and tech stacks. This led me to focus on broadening my knowledge across multiple topics, as it provided a more straightforward path to staying relevant and valuable in such a dynamic environment.
As a result, I adopted the habit of learning outside work, focusing on topics unrelated to my current job. This strategy has shaped my professional journey.
The Pros and Cons of My Approach
Pros
Expanding knowledge while staying updated on trends and concepts.
Participating in developer meetups to learn from peers working on diverse projects.
Practicing coding and mastering new technologies.
Reducing job-related risks by broadening my skill set.
Connecting dots between technologies, architectures, and methodologies.
Discovering better solutions by knowing more options.
Identifying recurring patterns and requirements across different projects and tech stacks, which helps prioritize learning.
Cons
Time constraints: The day is still only 24 hours, and this approach has forced me to sacrifice other passions.
Surface-level engagement: While I value adaptability, I sometimes feel that “use the right tool for the job” oversimplifies reality. Learning a new framework or language should be a necessity that arises after maximizing the tools already at your disposal.
Misaligned perceptions: Some employers—especially those outside the tech core business—fail to recognize the value of this knowledge. This can lead to undervaluing professional expertise and bypassing important processes like documentation, skill development, and fostering innovation.
A Shift in Perspective
While my focus on continuous learning has served me well, it’s time to shift gears. I want to channel the skills I’ve built over the years into concrete projects. Instead of just expanding my knowledge, I’ll now prioritize applying it to bring my ideas to life.
This blog and the 10-Minute Company series are tools to keep me focused and accountable. Turning an idea into a working example requires a mix of skills—not just coding—which will push me to explore new perspectives.
I’m excited about the opportunity to grow, not only technically but also in terms of communication and networking.
I’d love to hear your thoughts! Any constructive feedback or support you can offer would make a huge difference in keeping this series alive and thriving.
Top comments (0)