Search for a command to run...
Why should we stop our paused projects?
No comments yet. Be the first to comment.
Reflections on trust, synthetic media, and why the real challenge isn't the technology but it's what happens when we stop knowing what to believe.
This week I attended "Retrieval in the Age of Agents", a meetup organized by Qdrant and hosted at the Merantix AI Campus in Berlin. The event brought together representatives from Qdrant, Haystack (de
Vibe Coding vs AI Assissted Development
Disappointment A few weeks ago, I was in a fireside chat with Bob van Luijt, CEO & co-founder of Weaviate, where someone asked him about Knowledge Graphs. He ended his answer by saying, “I think that knowledge graphs are gonna cease to exist.”(You ca...
In this blog post I want to just simply gather any useful resource I found and updating it during my learning journey. Development LangChain What is LangChain? (YouTube video) (8mins) MCP MCP: Build Rich-Context AI Apps with Anthropic Knowledg...
We all know that starting a project and forming a team can be challenging, and we usually try to learn how to improve our approach for a faster and more optimal take-off. However, we often forget how important it is to stop a project as well.
We often have many projects that have been "stopped" gradually or suddenly, and they always try to stay alive somewhere in our mind.
It usually starts with a new, possibly innovative idea, and if you're lucky, you can form a team to work on it. You continue for some time, spending either full-time or part of your daily work on it. Then, after a few failures, changes in a teammate's schedule, or shifts in motivation, you realize that the working speed is slowing down or has even suddenly dropped to zero.
Then you find yourself working on another project or continuing your day-to-day tasks while always looking back at the not-truly-stopped project, hoping it might be revived sometime in the future.
Well... yes and no. It is good to keep the experience in mind and use it somewhere in the future when you are working on a similar topic. But it shouldn't reserve too much of your resources (time, money, cognitive capacity, network, etc.) and make you less agile.
So if we are actually pausing the project and not properly stopping, it is important to consider how much resource we are still spending and how much freedom we are loosing.
I mean we are in a fast-changing world and it is ok if after some time we feel something else is more interesting, and we need to shift all of our attention. But be careful, the world is changing so fast and changes are making so much noise. Therefore, on the other hand, we need to have balance here.
I would like to focus on it this year and see how I can close my paused projects properly and make room for a couple of new projects that are more interesting and practical. So far I found the following resources interesting. Please feel free to share any resources you may have, so we can make a better list for people who have the same problem.
