I love conceiving ideas.
I am not sure where this proclivity comes from, but as far as I can remember it has been with me since my childhood.
My Achilles heel was I was never able to follow through with my ideas. If I ever did, I would make some complicated document. Inside it would be some strict timeline of tasks I "had" to do.
You can guess how it goes next...
I wouldn't even be able to finish the first task. 😰
Why am I writing this blog post?
In the last 3 years, I have been burnt severely from work. Within those 3 years, I lost my childhood self.
Only recently have I found him, and I have no intentions of loosing him or the first idea he has given me, again. This is why I am making this post.
I want to heal my Achilles heel. I want to use this forum as a way to keep myself accountable and ultimately, be able to follow through on my idea, to the end.
So, what is my idea and why am I so passionate about it?
The Idea
I hate brainless CRUD microservices. I think every webservice can be boiled down into a simple ETL process. They simply extract one or multiple sources of data, transform said data, then pass that data to another service or process.
Microservice Killer (MK) is my vision for automating the creation, testing, and analytics of microservices with AI. It would be a low-code platform that lets you define processes and tests for those processes in a node-based editor, manually and with an LLM.
You will be able to create the services you want faster. You get assurance on all your changes immediate feedback on the changes you make.
Timeline
Now, I want to make something very clear. The description I gave for MK is my ideal vision of what MK could be. I CANNOT and WILL NOT create that version of MK at the end of 2 months.
My goal is to create a dirty MVP of MK in 2 months.
I hesitate to include a timeline because I have failed to follow one every. single. time. And as they say, "insanity is doing the same thing over and expecting different results."
So, what am I doing differently?
I intend to work week by week. Each week I will post a project update that will include:
- What I did that week
- What I learnt that week
- And what is my one task for next week.
Week 1
Post Due: 6th July
One Task: Test a simple "add record to redis" process
Here is where you can help
Share what worked has for you?
I am interested in your story, especially those small crappy projects you've never showed to others. I want to learn everything I can.
Share your feedback no matter how harsh.
I want you to kick me in the ass. I believe in radical transparency. I don't see any value in unnecessary flattery and praise.
Spam me with messages, especially when I miss a weekly post.
I want this journey to be one that you and I can look back on fondly regardless of whether I fail to build MK or not.
Top comments (0)