Slight-Explanation29•This week
10y of product development, 2 bankruptcies, and 1 Exit — what next? [Extended Story]
10 years of obsessive pursuit from the bottom to impressive product-market fit and exit. Bootstrapping tech products as Software Developer and 3x Startup Founder (2 bankruptcies and 1 exit).
Hi everyone, your motivation has inspired me to delve deeper into my story. So, as promised to some of you, I've expanded on it a bit more, along with my brief reflections.
There are many founders, product creators, and proactive individuals, I’ve read many of your crazy stories and lessons so I decided to share mine and the lessons I learned from the bottom to impressive product-market fit and exit.
I've spent almost the past 10 years building tech products as a Corporate Team Leader, Senior Software Developer, Online Course Creator, Programming Tutor, Head of Development/CTO, and 3x Startup Founder (2 bankruptcies, and 1 exit).
And what next? good question...
A brief summary of my journey:
Chapter 1: Software Developer / Team Leader / Senior Software Developer
I’ve always wanted to create products that win over users’ hearts, carry value, and influence users. Ever since my school days, I’ve loved the tech part of building digital products.
At the beginning of school, I started hosting servers for games, blogs and internet forums, and other things that did not require much programming knowledge. My classmates and later even over 100 people played on servers that I hosted on my home PC.
Later, as the only person in school, I passed the final exam in computer science.
During my computer science studies, I started my first job as a software developer. It was crazy, I was spending 200–300 hours a month in the office attending also to daily classes. Yes, I didn’t have a life, but it truly was the fulfillment of my dreams. I was able to earn good money doing what I love, and I devoted fully myself to it.
My key to effectively studying IT and growing my knowledge at rocket speed was learning day by day reading guides, building products to the portfolio, watching youtube channels and attending conferences, and even watching them online, even if I didn’t understand everything at the beginning. In one year we’ve been to every possible event within 400km.
We were building healthcare products that were actually used in hospitals and medical facilities. It was a beautiful adventure and tons of knowledge I took from this place.
That time I built my first product teams, hired many great people, and over the years became a senior developer and team leader. Even I convinced my study mates to apply to this company and we studied together and worked as well. Finally, there were 4 of us, when I left a friend of mine took over my position and still works there. If you’re reading this, I’m sending you a flood of love and appreciation.
I joined as the 8th person, and after around 4 years, when I left hungry for change, there were already over 30 of us, now around 100. It was a good time, greetings to everyone. I finished my Master’s and Engineering degrees in Computer Science, and it was time for changes.
Chapter 2: 1st time as a Co-founder — Marketplace
In the meantime, there was also my first startup (a marketplace) with four of my friends. We all worked on the product, each of us spent thousands of hours, after hours, entire weekends… and I think finally over a year of work.
As you might guess, we lacked the most important things: sales, marketing, and product-market fit. We thought users think like us. We all also worked commercially, so the work went very smoothly, but we didn’t know what we should do next with it…
Finally, we didn’t have any customers, but you know what, I don’t regret it, a lot of learning things which I used many times later. The first attempts at validating the idea with the market and business activities.
In the end, the product was Airbnb-sized. Landing pages, listings, user panels, customer panels, admin site, notifications, caches, queues, load balancing, and much more. We wanted to publish the fully ready product to the market.
It was a marketplace, so if you can guess, we had to attract both sides to be valuable.
“Marketplace” — You can imagine something like Uber, if you don’t have passengers it was difficult to convince taxi drivers, if you don’t have a large number of taxi drivers you cannot attract passengers.
After a year of development, we were overloaded, and without business, marketing, sales knowledge, and budget.
Chapter 3: Corp Team Lead / Programming Tutor / Programming Architecture Workshop Leader
Working in a corporation, a totally different environment, an international fintech, another learning experience, large products, and workmates who were waiting for 5 pm to finish — it wasn’t for me.
Very slow product development, huge hierarchy, being an ant at the bottom, and low impact on the final product.
At that time I understood that being a software developer is not anything special and I compared my work to factory worker. Sorry for that. High rates have been pumped only by high demand. Friends of mine from another industry do more difficult things and have a bigger responsibility for lower rates. That’s how the market works.
This lower responsibility time allowed for building the first online course after hours, my own course platform, individual teaching newbies programming, and my first huge success — my first B2C customers, and B2B clients for workshops. I pivoted to full focus on sales, marketing, funnels, advertisements, demand, understanding the market, etc.
It was 10x easier than startups but allowed me to learn and validate my conceptions and ideas on an easier market and showed me that it’s much easier to locate their problem/need/want and create a service/product that responds to it than to convince people of your innovative ideas.
It’s just supply and demand, such a simple and basic statement, in reality, is very deep and difficult to understand without personal experience. If you’re inexperienced and you think you understand, you don’t.
To this day, I love to analyze this catchword in relation to various industries / services / products and rediscover it again and again... While writing this sentence, I’m wondering if I’m not obsessed.
Chapter 4: Next try — 2nd time as a founder — Edtech
Drawing upon my experiences in selling services, offering trainings, and teaching programming, I wanted to broaden my horizons, delve into various fields of knowledge, involve more teachers, and so on.
We started with simple services in different fields of knowledge, mainly relying on teaching in the local area (without online lessons). As I had already gathered some knowledge and experience in marketing and sales, things were going well and were moving in the right direction.
The number of teachers in various fields was growing, as was the number of students. I don’t remember the exact statistics anymore, but it was another significant achievement that brought me a lot of satisfaction and new experiences.
As you know, I’m a technology lover and couldn’t bear to look at manual processes — I wanted to automate everything: lessons, payments, invoices, customer service, etc. That’s when I hired our first developers (if you’re reading this, I’m sending you a flood of love — we spent a lot of time together and I remember it as a very fruitful and great year) and we began the process of tool and automation development. After a year we had really extended tools for students, teachers, franchise owners, etc.
We had really big goals, we wanted to climb higher and higher. Maybe I wouldn’t even fully call it Startup, as the client was paying for the lessons, not for the software. But it gave us positive income, bootstrap financing, and tool development for services provided.
Scaling this model was not as costless as SaaS because customer satisfaction was mainly on the side of the teacher, not the quality of the product (software). Finally, we grew to nearly 10 people and dozens of teachers, with zero external funding, and almost $50k monthly revenue.
We worked very hard, day and night, and by November 2019, we were packed with clients to the brim. And as you know, that’s when the pandemic hit. It turned everything upside down by 180 degrees. Probably no one was ready for it. With a drastic drop in revenues, society started to save. Tired from the previous months, we had to work even harder.
We had to reduce the team, change the model, and save what we had built. We stopped the tool’s development and sales, and with the developers, we started supporting other product teams to not fire them in difficult times.
The tool worked passively for the next two years, reducing incomes month by month. With a smaller team providing programming services, we had full stability and earned more than relying only on educational services. At the peak of the pandemic, I promised myself that it was the last digital product I built… Never say never…
Chapter 5: Time for fintech — Senior Software Developer / Team Lead / Head of Development
I worked for small startups and companies. Building products from scratch, having a significant impact on the product, and complete fulfillment. Thousands of hours and sacrifices.
This article mainly talks about startups that I built, so I don’t want to list all the companies, products, and applications that I supported as a technology consultant. These were mainly start-ups with a couple of people up to around 100 people on board.
Some of the products were just a rescue mission, others were building an entire tech team. I was fully involved in all of them with the hope that we would work together for a long time, but I wasn’t the only one who made mistakes when looking for a product-market fit.
One thing I fully understood: You can’t spend 8–15 hours a day writing code, managing a tech team, and still be able to help build an audience.
In marketing and sales, you need to be rested and very creative to bring results and achieve further results and goals. If you have too many responsibilities related to technology, it becomes ineffective.
I noticed that when I have more free time, more time to think, and more time to bounce the ball against the wall, I come up with really working marketing/sales strategies and solutions. It’s impossible when you are focused on code all day.
You must know that this chapter of my life was long and has continued until now.
Chapter 6: 3rd time as a founder — sold
Never say never… right?\\
It was a time when the crypto market was really high and it was really trending topic. You know that I love technology right? So I cannot miss the blockchain world. I had experience in blockchain topics by learning on my own and from startups where I worked before.
I was involved in crypto communities and I noticed a “starving crowd”. People who did things manually and earned money(crypto) on it.I found potential for building a small product that solves a technological problem.
I said a few years before that I don’t want to start from scratch. I decided to share my observations and possibilities with my good friend. He said, “If you gonna built it, I’m in”.
I couldn’t stop thinking about it. I had thought and planned every aspect of marketing and sales. And you know what. On this huge mindmap “product” was only one block. 90% of the mindmap was focused on marketing and sales.
Now, writing this article, I understood what path I went from my first startup to this one. In the first (described earlier) 90% was the product, but in the last one 90% was sales and marketing. Many years later, I did this approach automatically. What has changed in my head over the years and so many mistakes?
At that time, the company for which I provided services was acquired. The next day I got a thank you for my hard work and all my accounts were blocked.
Life… I was shocked. We were simply replaced by their trusted technology managers. They wanted to get full control. They acted a bit unkindly, but I knew that they had all my knowledge about the product in the documentation, because I’m used to drawing everything so that in the moment of my weakness (illness, whatever) the team could handle it.
That’s what solid leaders do, right? After a time, I know that these are normal procedures in financial companies, the point is that under the influence of emotions, do not do anything inappropriate.
I quickly forgot about it, that I was brutally fired. All that mattered was to bring my plan to life.
And it has been started, 15–20 hours a day every day. You have to believe me, getting back into the game was incredibly satisfying for me. I didn’t even know that I would be so excited.
Then we also noticed that someone was starting to think about the same product as me. So the race began a game against time and the market.
I assume that if you have reached this point, you are interested in product-market fit, marketing, and sales, so let me explain my assumptions to you:
Product:
A very very small tool that allowed you to automate proper tracking and creation of on-chain transactions. Literally, the whole app for the user was located on only three subpages.
Starving Crowd:
We tapped into an underserved market. The crypto market primarily operates via communities on platforms like Discord, Reddit, Twitter, Telegram, and so on. Therefore, our main strategy was directly communicating with users and demonstrating our tool. This was essentially “free marketing” (excluding the time we invested), as we did not need to invest in ads, promotional materials, or convince people about the efficacy of our tool.
The community could directly observe on-chain transactions executed by our algorithms, which were processed at an exceptionally fast rate. This was something they couldn’t accomplish manually, so whenever someone conducted transactions using our algorithm, it was immediately noticeable and stirred a curiosity within the community (how did they do that!).
Tests:
I conducted the initial tests of the application on myself — we had already invested significantly in developing the product, but I preferred risking my own resources over that of the users. I provided the tool access to my wallet, containing 0.3ETH, and went to sleep. Upon waking up, I discovered that the transactions were successful and my wallet had grown to 0.99ETH. My excitement knew no bounds, it felt like a windfall. But, of course, there was a fair chance I could have lost it too.
It worked. As we progressed, some users achieved higher results, but it largely hinged on the parameters set by them. As you can surmise, the strategy was simple — buy low, sell high. There was considerable risk involved.
Churn:
For those versed in marketing, the significance of repeat visitors cannot be overstated. Access to our tool was granted only after email verification and a special technique that I’d prefer to keep confidential. And this was all provided for free. While we had zero followers on social media, we saw an explosion in our email subscriber base and amassed a substantial number of users and advocates.
Revenue Generation:
Our product quickly gained popularity as we were effectively helping users earn — an undeniable value proposition. Now, it was time to capitalize on our efforts. We introduced a subscription model charging $300 per week or $1,000 per month — seemingly high rates, but the demand was so intense that it wasn’t an issue. Being a subscriber meant you were prioritized in the queue, ensuring you were among the first to reap benefits — thus adding more “value”.
Marketing:
The quality of our product and its ability to continually engage users contributed to it achieving what can best be described as viral.
It was both a source of pride and astonishment to witness users sharing charts and analyses derived from our tool in forum discussions. They weren’t actively promoting our product but rather using screenshots from our application to illustrate certain aspects of the crypto world.
By that stage, we had already assembled a team to assist with marketing, and programming, and to provide round-the-clock helpdesk support.
Unforgettable Time:
Despite the hype, my focus remained steadfast on monitoring our servers, their capacity, and speed. Considering we had only been on the market for a few weeks, we were yet to implement alerts, server scaling, etc.
Our active user base spanned from Japan to the West Coast of the United States. Primarily, our application was used daily during the evenings, but considering the variety of time zones, the only time I could afford to sleep was during the evening hours in Far Eastern Europe, where we had the least users. However, someone always needed to be on guard, and as such, my phone was constantly by my side. After all, we couldn’t afford to let our users down.
We found ourselves working 20 hours a day, catering to thousands of users, enduring physical fatigue, engaging in talks with VCs, and participating in conferences.
Sudden Downturn:
Our pinnacle was abruptly interrupted by the war in Ukraine (next macroeconomic shot straight in the face, lucky guy), a precipitous drop in cryptocurrency value, and swiftly emerging competition.
By this time, there were 5–8 comparable tools had infiltrated the market. It was a challenging period as we continually stumbled upon new rivals.
They immediately embarked on swift fundraising endeavors — a strategy we overlooked, which in retrospect was a mistake.
Although our product was superior, the competitors’ rapid advancement and our insufficient funds for expeditious scaling posed significant challenges.
Nonetheless, we made a good decision. We sold the product (exit) to competitors. The revenue from “exit” compensated for all the losses, leaving us with enough rest.
We were a small team without substantial budgets for rapid development, and the risk of forming new teams without money to survive for more than 1–2 months was irresponsible.
You have to believe me that this decision consumed us sleepless nights.
Finally, we sold it. They turned off our app but took algorithms and users.
Whether you believe it or not, after several months of toiling day and night, experiencing burnout, growing weary of the topic, and gaining an extra 15 kg in weight, we finally found our freedom…
The exit wasn’t incredibly profitable, but we knew they had outdone us. The exit covered all our expenses and granted us a well-deserved rest for the subsequent quarter.
It was an insane ride. Despite the uncertainty, stress, struggles, and sleepless nights, the story and experience will remain etched in my memory for the rest of my life.
Swift Takeaways:
Comprehending User Needs: Do you fully understand the product-market fit? Is your offering just an accessory or does it truly satisfy the user’s needs?
The Power of Viral Marketing: Take inspiration from giants like Snapchat, ChatGPT, and Clubhouse. While your product might not attain the same scale (but remember, never say never…), the closer your concept is to theirs, the easier your journey will be. If your user is motivated to text a friend saying, “Hey, check out how cool this is” (like sharing ChatGPT), then you’re on the best track. Really. Even if it doesn’t seem immediately evident, there could be a way to incorporate this into your product. Keep looking until you find it.
Niche targeting — the more specific and tailored your product is to a certain audience, the easier your journey will be
People love buying from people — establishing a personal brand and associating yourself with the product can make things easier.
Value: Seek to understand why users engage with your product and keep returning.
The more specific and critical the issue you’re aiming to solve, the easier your path will be. Consider your offerings in terms of products and services and focus on sales and marketing, regardless of personal sentiments.
These are just a few points, I plan to elaborate on all of them in a separate article.
Many products undergo years of development in search of market fit, refining the user experience, and more. And guess what? There’s absolutely nothing wrong with that.
Each product and market follows its own rules. Many startups have extensive histories before they finally make their mark (for instance, OpenAI).
This entire journey spanned maybe 6–8 months. I grasped and capitalized on the opportunity, but we understood from the start that establishing a startup carried a significant risk, and our crypto product was 10 times riskier.
Was it worth it? Given my passion for product development — absolutely.
Was it profitable? — No, considering the hours spent — we lose.
Did it provide a stable, problem-free life — nope.
Did this entire adventure offer a wealth of happiness, joy, and unforgettable experiences — definitely yes.
One thing is certain — we’ve amassed substantial experience and it’s not over yet :)
So, what lies ahead?
Chapter 7: Reverting to the contractor, developing a product for a crypto StartupReturning to the past, we continue our journey…
I had invested substantial time and passion into the tech rescue mission product. I came on board as the technical Team Leader of a startup that had garnered over $20M in seed round funding, affiliated with the realm of cryptocurrencies. The investors were individuals with extensive backgrounds in the crypto world.
My role was primarily technical, and there was an abundance of work to tackle. I was fully immersed, and genuinely devoted to the role. I was striving for excellence, knowing that if we secured another round of financing, the startup would accelerate rapidly.
As for the product and marketing, I was more of an observer.
After all, there were marketing professionals with decades of experience on board. These were individuals recruited from large crypto-related firms. I had faith in them, kept an eye on their actions, and focused on my own responsibilities. However, the reality was far from satisfactory.
On the last day, the principal investor for the Series A round withdrew. The board made the tough decision to shut down. It was a period of intense observation and gaining experience in product management.
This was a very brief summary of the last 10 years.
And what next?
(Last) Chapter 8: To be announced — Product Owner / Product Consultant / Strategist / CTO
After spending countless hours and days deliberating my next steps, one thing is clear:
My aspiration is to continue traversing the path of software product development, with the hopeful anticipation that one day, I might ride the crest of the next big wave and ascend to the prestigious status of a unicorn company.
I find myself drawn to the process of building products, exploring product-market fit, strategizing, engaging in software development, seeking out new opportunities, networking, attending conferences, and continuously challenging myself by understanding the market and its competitive landscape.
Product Owner / Product Consultant / CTO / COO:
I’m not entirely sure how to categorize this role, as I anticipate that it will largely depend on the product to which I will commit myself fully.
My idea is to find one startup/company that wants to build a product / or already has a product, want to speed up, or simply doesn’t know what’s next.
Alternatively, I could be a part of an established company with a rich business history, which intends to invest in digitization and technological advancements. The goal would be to enrich their customer experience by offering complementary digital products
Rather than initiating a new venture from ground zero with the same team, I am receptive to new challenges. I am confident that my past experiences will prove highly beneficial for the founders of promising, burgeoning startups that already possess a product, or are in the initial phases of development.
‘Consultant’ — I reckon we interpret this term differently. My aim is to be completely absorbed in a single product, crafting funnels, niches, strategies, and all that is necessary to repeatedly achieve the ‘product-market fit’ and significant revenue. To me, ‘consultant’ resonates more akin to freelancing than being an employee.
My current goal is to kickstart as a consultant and aide, dealing with facilitating startups in their journey from point A to B.
Here are two theoretical scenarios to illustrate my approach: Scenario 1:
(Starting from point A) You have a product but struggle with marketing, adoption, software, strategy, sales, fundraising, or something else.
I conduct an analysis and develop a strategy to reach point B.
I take on the “dirty work” and implement necessary changes, including potential pivots or shifts (going all-in) to guide the product to point B.
The goal is to reach point B, which could involve achieving a higher valuation, expanding the user base, increasing sales, or generating monthly revenue, among other metrics.
Scenario 2:
(Starting from point A) You have a plan or idea but face challenges with marketing, adoption, strategy, software, sales, fundraising, or something else.
I analyze the situation and devise a strategy to reach point B.
I tackle the necessary tasks, build the team, and overcome obstacles to propel the product to point B.
I have come across the view that finding the elusive product-market fit is the job of the founder, and it’s hard for me to disagree.
However, I believe that my support and experiences can help save money, many failures, and most importantly, time. I have spent a great deal of time learning from my mistakes, enduring failure after failure, and even had no one to ask for support or opinion, which is why I offer my help. Saving even a couple of years, realistically speaking, seems like a value I’m eager to provide…
I invite you to share your thoughts and insights on these scenarios :)
Closing Remarks:
I appreciate your time and effort in reaching this point. This has been my journey, and I wouldn’t change it for the world. I had an extraordinary adventure, and now I’m ready for the next exciting battle with the market and new software products.
While my entire narrative is centered around startups, especially the ones I personally built, I’m planning to share more insights drawn from all of my experiences, not just those as a co-founder.
If you’re currently developing your product or even just considering the idea, I urge you to reach out to me. Perhaps together, we can create something monumental :)
Thank you for your time and insights. I eagerly look forward to engaging in discussions and hearing your viewpoints. Please remember to like and subscribe. Nothing motivates to write more than positive feedback :)
Matt.
![10y of product development, 2 bankruptcies, and 1 Exit — what next? [Extended Story]](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/startups_AI_for_digital_automation_20250328_184340_processed_image.jpg)
![Looking for a Marketing Partner for an Innovative AI Mobile App [i will not promote]](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/startups_AI_for_business_automation_20250328_183811_processed_image.jpg)
![Looking for an accountability partner as a solo founder. [I will not promote]](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/startups_AI_for_business_automation_20250328_183753_processed_image.jpg)
![We received 25k investment offer, need advice [I will not promote]](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/startups_AI_for_business_20250328_183209_processed_image.jpg)
![Study Plan for Learning Data Science Over the Next 12 Months [D]](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/learnmachinelearning_AI_for_entrepreneurs_20250328_185313_processed_image.jpg)
![[N] 20 hours of new lectures on Deep Learning and Reinforcement Learning with lots of examples](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_Introduction_to_AI_20250328_192244_processed_image.jpg)
![[D] 3 Reasons Why We Are Far From Achieving Artificial General Intelligence](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_Introduction_to_AI_20250328_192239_processed_image.jpg)
![[D] Lessons From the Field in Building Your MLOps Strategy with Harpreet Sahota, Data Scientist at Comet at Enterprise Data & AI - Jan 27 @ 12 PM ET](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_strategy_20250328_191815_processed_image.jpg)
![[D] Playing big league at home on a budget?](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_implementation_for_beginners_20250328_190039_processed_image.jpg)
![[D] The current and future state of AI/ML is shockingly demoralizing with little hope of redemption](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_implementation_20250328_185811_processed_image.jpg)
![[D] Accessibility of Basic Models to Non-Technicals](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_entrepreneurs_20250328_185249_processed_image.jpg)
![[R] From 3D Contour Plots to AI-Generated Art](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_digital_automation_20250328_184558_processed_image.jpg)
![[P]MMML | Deploy HuggingFace training model rapidly based on MetaSpore](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_digital_automation_20250328_184547_processed_image.jpg)
![[D] AI regulation: a review of NTIA's "AI Accountability Policy" doc](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_business_automation_20250328_184021_processed_image.jpg)
![[P]MMML | Deploy HuggingFace training model rapidly based on MetaSpore](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_business_automation_20250328_184030_processed_image.jpg)
![[D] Using AI to navigate the complexities of regulatory frameworks](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_business_automation_20250328_184014_processed_image.jpg)
![[News] AAAI 2025 Workshop on AI for Music 🎶](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_business_automation_20250328_184004_processed_image.jpg)
![[D] LLMs causing more harm than good for the field?](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_for_business_20250328_183415_processed_image.jpg)
![[News] AAAI 2025 Workshop on AI for Music 🎶](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_automation_tools_20250328_191226_processed_image.jpg)
![[P] Utilizing graph attention-based neural networks and generative AI to build a tool to automate debugging and refactoring Python code](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_automation_tools_20250328_191208_processed_image.jpg)
![[D] Is this close enough to be usable? Need your inputs: Automated RAG testing tool. AI Data Pipelines for Real-World Production (Part 3)](https://jfbmhhfxbbrxcmwilqxt.supabase.co/storage/v1/object/public/resource-images/MachineLearning_AI_automation_tools_20250328_191200_processed_image.jpg)
