Full Stack JS Dev
As programmers, we know how important it is to be up to date in terms of programming languages, frameworks, methodologies and tools in general. We must always be in continuous learning. One of the best ways to stay up-to-date is by attending technology conferences and events, but many of these events are not in our city or we simply cannot attend. The positive part is that most of these events are recorded and are available for free through different video platforms (mainly Youtube or Vimeo), which is great, but there are a couple of problems:
❌ There are plenty of interesting events and talks around the world every week and it’s hard to be aware that they exist.
❌ Each event is on a different date and is published on different accounts and video platforms, which makes it very complicated to track the events that interest us.
That’s why we decided to create Codetalks.tv, a platform for developers that brings together the best programming talks around the world in one place. Each video is grouped by tags and event so that it is incredibly easy to discover conferences, watch lectures and keep learning.
Considering that this is a MVP (minimum viable product) we wouldn’t want to extend the development time too much, therefore, we tried to identify the key functionalities that would give meaning to the project, in this way we could validate if our idea made sense or not before continuing to invest more time and effort in it. The characteristics we identified as most important were:
As for the design, it had to be simple and intuitive. It didn’t make sense to create anything new and extravagant and that’s why we opted for a design similar to that of Youtube, so that anyone can instantly feel familiar with it.
Focusing more on the look and feel, we decided to make a small wink to our potential users, the developers, for this reason we gave it the appearance of a code editor (VS Code?), and even… we used the famous Monokai color palette.
And it’s time to code!
One of the interesting things about a side-project is that you can afford to experiment and try new things out, so, we didn’t want to miss this opportunity.
Here is a brief summary of the technology stack we used, both for the backend and for the frontend. If you find it interesting, we will publish more articles explaining part of the development process in more detail.
Other libraries or tools that have helped us a lot:
Third party tools:
And then came the moment of truth…
The truth is that if we are taken out of the technical or product part we will feel like a fish out of water, one could say that marketing is not our strong point. That’s why, to define our launch strategy, we simply asked ourselves a question: Where are our potential users?, and based on the answers we found, we drew up a list of possible acquisition channels:
☠ Big portals (Disaster):
At this point, and after a truly horrible initial release, we wondered if CodeTalks actually made sense, are we really solving a problem and bringing something to the community? our motivation crashed.
However, after a few days of decline, we decided to continue trying in other ways and this time, fortunately, it was better:
✌ ️Niche media (Not bad):
Despite not having had a spectacular launch, we have seen over the last month how traffic has been increasing day after day steadily. In addition, we have received a lot of positive feedback, so the general feeling is that people like it, and although we think we have not reached product-market-fit yet, we do believe that we are going in the right direction and that it is worth continuing to invest some more time.
In addition, we have a few very cool ideas for version 2.0, and…. why not, we’ll make another release later with lessons learned, maybe this time we’ll be luckier hehehe.
If we had to draw some key lessons, these would be:
Create your free account to unlock your custom reading experience.