VibeBuilders.ai Logo
VibeBuilders.ai

Fundamentals

Explore resources related to fundamentals to help implement AI solutions for your business.

AI Agents Fundamentals In 21 Minutes
youtube
LLM Vibe Score0.422
Human Vibe Score0.9
Tina HuangFeb 16, 2025

AI Agents Fundamentals In 21 Minutes

Improve your AI skills with the FREE Prompting QuickStart Guide I made in collaboration with Hubspot: https://clickhubspot.com/1gg9 Want to get ahead in your career using AI? Join my FREE workshop: https://www.lonelyoctopus.com/workshop A few notebooks to try out from crewAI & Autogen that are easy to follow and get started. All credit goes to these companies and Deep Learning AI. Please make a copy: https://drive.google.com/file/d/1mtv-gdKV9HMsGvGIqZZ9tSdW-nXq6kEf/view?usp=sharing https://drive.google.com/file/d/1u9gGPqWSJ4PacLNWbUWPhSvxen3Bvx/view?usp=sharing https://drive.google.com/file/d/1T07WHydxBN-T-kcgi6qme-j1T94efBYf/view?usp=sharing https://drive.google.com/file/d/1vPWpYvcHPROMC3BOEK3alT1QFSIvgA8P/view?usp=sharing Resources I consulted in making this video: crewAI course: https://www.deeplearning.ai/short-courses/multi-ai-agent-systems-with-crewai/ Autogen course: https://www.deeplearning.ai/short-courses/ai-agentic-design-patterns-with-autogen/ LangGraph course: https://www.deeplearning.ai/short-courses/ai-agents-in-langgraph/ David Ondrej n8n tutorial: https://youtu.be/XVO3zsHdvio?si=AQcMnYn8kJOogqLr Andrew Ng Snowflake agentic design patterns: https://youtu.be/KrRD7r7y7NY?si=tFtd6wJKB6idtfKb Andrew Ng Sequoia agentic design patterns: https://youtu.be/sal78ACtGTc?si=2i8Wyy57n8m6TbBK YC business advice: https://youtu.be/ASABxNenD_U?si=k19a310Tj3USuKNe 🐙 Lonely Octopus: https://www.lonelyoctopus.com/ Check it out if you're interested in learning AI & data skill, then applying them to real freelance projects! 🤝 Business Inquiries: https://tally.so/r/mRDV99 🖱️Links mentioned in video ======================== 🔗Affiliates ======================== My SQL for data science interviews course (10 full interviews): https://365datascience.com/learn-sql-for-data-science-interviews/ 365 Data Science: https://365datascience.pxf.io/WD0za3 (link for 57% discount for their complete data science training) Check out StrataScratch for data science interview prep: https://stratascratch.com/?via=tina 🎥 My filming setup ======================== 📷 camera: https://amzn.to/3LHbi7N 🎤 mic: https://amzn.to/3LqoFJb 🔭 tripod: https://amzn.to/3DkjGHe 💡 lights: https://amzn.to/3LmOhqk ⏰Timestamps ======================== 00:00 intro 📲Socials ======================== instagram: https://www.instagram.com/hellotinah/ linkedin: https://www.linkedin.com/in/tinaw-h/ discord: https://discord.gg/5mMAtprshX 🎥Other videos you might be interested in ======================== How I consistently study with a full time job: https://www.youtube.com/watch?v=INymz5VwLmk How I would learn to code (if I could start over): https://www.youtube.com/watch?v=MHPGeQD8TvI&t=84s 🐈‍⬛🐈‍⬛About me ======================== Hi, my name is Tina and I'm an ex-Meta data scientist turned internet person! 📧Contact ======================== youtube: youtube comments are by far the best way to get a response from me! linkedin: https://www.linkedin.com/in/tinaw-h/ email for business inquiries only: hellotinah@gmail.com ======================== Some links are affiliate links and I may receive a small portion of sales price at no cost to you. I really appreciate your support in helping improve this channel! :)

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a web product, and got zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a web product, and got zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I have stuff to post on Reddit very rarely, but I share how my project is going on, random stuff, and memes on X. Just in case few might want to keep in touch 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a web product, and got zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a web product, and got zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I have stuff to post on Reddit very rarely, but I share how my project is going on, random stuff, and memes on X. Just in case few might want to keep in touch 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a web product, and got zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a web product, and got zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I have stuff to post on Reddit very rarely, but I share how my project is going on, random stuff, and memes on X. Just in case few might want to keep in touch 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

List of free educational ML resources I used to become a FAANG ML Engineer
reddit
LLM Vibe Score0
Human Vibe Score1
aifordevsThis week

List of free educational ML resources I used to become a FAANG ML Engineer

Full commentary and notes here ➡️: https://www.trybackprop.com/blog/top\ml\learning\resources Used these to brush up on math and teach myself AI/ML over the course of two years. I'm now a staff ML engineer at FAANG. Hope these help. Fundamentals Linear Algebra – 3Blue1Brown's Essence of Linear Algebra series, binged all these videos on a one hour train ride visiting my parents Multivariable Calculus – Khan Academy's Multivariable Calculus lessons were a great refresher of what I had learned in college. Looking back, I just needed to have reviewed Unit 1 – intro and Unit 2 – derivatives. Calculus for ML – this amazing animated video explains calculus and backpropagation Information Theory – easy-to-understand book on information theory called Information Theory: A Tutorial Introduction. Statistics and Probability – the StatQuest YouTube channel Machine Learning Stanford Intro to Machine Learning by Andrew Ng – Stanford's CS229, the intro to machine learning course, published their lectures on YouTube for free. I watched lectures 1, 2, 3, 4, 8, 9, 11, 12, and 13, and I skipped the rest since I was eager to move onto deep learning. The course also offers a free set of course notes, which are very well written. Caltech Machine Learning – Caltech's machine learning lectures on YouTube, less mathematical and more intuition based Deep Learning Andrej Karpathy's Zero to Hero Series – Andrej Karpathy, an AI researcher who graduated with a Stanford PhD and led Tesla AI for several years, released an amazing series of hands on lectures on YouTube. highly highly recommend Neural networks – Stanford's CS231n course notes and lecture videos were my gateway drug*, so to speak, into the world of deep learning. Transformers and LLMs Transformers – watched these two lectures: lecture from the University of Waterloo and lecture from the University of Michigan. I have also heard good things about Jay Alammar's The Illustrated Transformer guide ChatGPT Explainer – Wolfram's YouTube explainer video on ChatGPT Interactive LLM Visualization – This LLM visualization that you can play with in your browser is hands down the best interactive experience with an LLM. Financial Times' Transformer Explainer – The Financial Times released a lovely interactive article that explains the transformer very well. Residual Learning – 2023 Future Science Prize Laureates Lecture on residual learning. Efficient ML and GPUs How are Microchips Made? – This YouTube video by Branch Education is one of the best free educational videos on the internet, regardless of subject, but also, it's the best video on understanding microchips. CUDA – My L8 and L9 FAANG coworkers acquired their CUDA knowledge from this series of lectures. TinyML and Efficient Deep Learning Computing – 2023 lectures on efficient ML techniques online. Chip War – Chip War is a bestselling book published in 2022 about microchip technology whose beginning chapters on the invention of the microchip actually explain CPUs very well

ZeroToHeroML: Beginner-Friendly ML & AI Course (Free)
reddit
LLM Vibe Score0
Human Vibe Score0
DizDThis week

ZeroToHeroML: Beginner-Friendly ML & AI Course (Free)

Hey r/learnmachinelearning! A friend of mine, who's been a software developer at Sony for 10 years, recently expressed interest in learning Machine Learning (ML) and Artificial Intelligence (AI). Leveraging my background in ML and neural computation (learned at UCSD) to create a beginner-friendly course guiding him through the basics and into more complex projects. Foundational Concepts: Predicting House Prices (Regression): Master regression techniques to forecast housing prices based on various factors. Iris Flower Species Prediction (Classification): Learn classification algorithms by predicting flower species using the famous Iris dataset. Overcoming Overfitting: Explore methods to prevent models from overfitting and enhance their generalizability. In Progress: Customer Segmentation (Unsupervised Learning): Delve into unsupervised learning to group customers based on purchase history or demographics (valuable for targeted marketing campaigns). Deep Learning for Image Recognition: Implement Convolutional Neural Networks (CNNs) to build models that recognize objects or scenes in images. Natural Language Processing Sentiment Analysis: Analyze the sentiment (positive, negative, or neutral) expressed in text data (e.g., reviews, social media posts) using NLP techniques. Introduction to Reinforcement Learning: Get acquainted with the fundamentals of reinforcement learning by creating an agent that learns to navigate a maze. Want to Learn or Contribute? I thought I'd share ZeroToHeroML here so others who want to learn ML/AI or know someone who does can benefit from this free resource! &#x200B; Fork the repo: https://github.com/DilrajS/ZeroToHeroML Share with others interested in ML/AI! Pull requests welcome (help the community grow!). All help is appriciated! Let's conquer ML/AI together!

Advice Needed
reddit
LLM Vibe Score0
Human Vibe Score1
Suspicious_Dig_3849This week

Advice Needed

Hey everyone, I’ve been diving into Artificial Intelligence, Machine Learning, and Deep Learning recently, but I find myself a little confused about how to approach the learning process effectively. My goal isn’t just to secure a job but to actually build cool AI products or startups—something innovative and impactful, like what companies such as OpenAI, Anthropic, or ElevenLabs are doing. I often see founders or engineers building incredible AI-driven startups, and I can’t help but wonder: • What kind of learning path did these people follow? • Surely they didn’t just stick to basic Udemy or YouTube courses that most people use for job prep. • What resources or approaches do serious AI practitioners use? I’ve heard that implementing research papers is a great way to gain a deep, intuitive understanding of AI concepts. But as someone who is still a beginner, I’m unsure how to start implementing papers without feeling overwhelmed. Here’s what I’m hoping to get clarity on: Where should I begin as a complete beginner? What resources, projects, or habits would you recommend to build solid fundamentals in AI/ML? How do I progress from beginner to a level where I can implement research papers? Are there intermediate steps I need to take before diving into papers? What would the ideal roadmap look like for someone who wants to build startups in AI? If you’re an AI practitioner, researcher, or startup founder, I’d love to hear about your experiences and learning pathways. What worked for you? What didn’t? Any advice or resources would be immensely appreciated. I’m ready to put in the hard work, I just want to make sure I’m moving in the right direction. Thanks in advance! Looking forward to learning from this community.

Learning Resources + Side Project Ideas
reddit
LLM Vibe Score0
Human Vibe Score1
Any-Reserve-4403This week

Learning Resources + Side Project Ideas

I made a post last night about my journey to landing an AI internship and have received a lot of responses asking about side projects and learning resources, so I am making another thread here consolidating this information for all those that are curious! Learning Process Step 1) Learn the basic fundamentals of the Math USE YOUTUBE!!! Literally just type in 'Machine Learning Math" and you will get tons of playlists covering nearly every topic. Personally I would focus on Linear Algebra and Calculus - specifically matrices/vector operations, dot products, eigenvectors/eigenvalues, derivatives and gradients. It might take a few tries until you find someone that meshes well with your learning style, but 3Blue1Brown is my top recommendation. I also read the book "Why Machines Learn" and found that extremely insightful. Work on implementing the math both with pen and paper then in Python. Step 2) Once you have a grip on the math fundamentals, I would pick up Hands-on Machine Learning with Sci-kit Learn, Keras and TensorFlow. This book was a game changer for me. It goes more in depth on the math and covers every topic from Linear Regression to the Transformers architecture. It also introduces you to Kaggle and some beginner level side projects. Step 3) After that book I would begin on side projects and also checking out other similar books, specifically Hands on Large Language Models and Hands on Generative AI. Step 4) If you have read all three of these books, and fully comprehend everything, then I would start looking up papers. I would just ask ChatGPT to feed you papers that are most relevant to your interests. Beginner Side Project Ideas 1) Build a Neural Network from scratch, using just Numpy. It can be super basic - have one input layer with 2 nodes, 1 hidden layer with 2 nodes, and output layer with one node. Learn about the forward feed process and play around with different activation functions and loss functions. Learn how these activation functions and loss functions impact backpropagation (hint: the derivatives of the activation functions and loss functions are all different). Get really good at this and understand the difference between regression models and classification models and which activation/loss functions go with which type of model. If you are really feeling crazy and are more focused on a SWE type of role, try doing it in a language other than python and try building a frontend for it so there is an interface where a user can input data and select their model architecture. 2) Build a CNN Image Classifier for the MNIST - Get familiar with the intricacies of CNN's, image manipulation, and basic computer vision concepts. 3) Build on top of open source LLM's. Go to Hugging Face's models page and start playing around with some. 4) KAGGLE COMPETITIONS - I will not explain further, do Kaggle Competitions. Other Resources I've mentioned YouTube, several books and Hugging Face. I also recommend: DataLemur.com \- Python practice, SQL practices, ML questions - his book Ace the Data Science Interview is also very good. X.com \- follow people that are prominent in the space. I joined an AI and Math Group that is constantly posting resources in there deep-ml.com If you have found any of this helpful - feel free to give me a follow on X and stay in touch @ x.com/hark0nnen\

Starting with Deep Learning in 2025 - Suggestion
reddit
LLM Vibe Score0
Human Vibe Score0
oba2311This week

Starting with Deep Learning in 2025 - Suggestion

I'm aware this has been asked many times here. so I'm not here to ask for a general advice - I've done some homework. My questions is - what do you think about this curriculum I put together (research + GPT)? Context: \- I'm a product manger with technical background and want to get back to a more technical depth. \- BSc in stats, familiar with all basic ML concepts, some maths (linear algebra etc), python. Basically, I got the basics covered a while ago so I'm looking to go back into the basics and I can learn and relearn anything I might need to with the internet. My focus is on getting hands on feel on where AI and deep learning is at in 2025, and understand the "under the hood" of key models used and LLMs specifically. Veterans - whats missing? what's redundant? Thanks so much! 🙏🏻 PS - hoping others will find this useful, you very well might too! |Week/Day|Goals|Resource|Activity| |:-|:-|:-|:-| |Week 1|Foundations of AI and Deep Learning||| |Day 1-2|Learn AI terminology and applications|DeepLearning.AI's "AI for Everyone"|Complete Module 1. Understand basic AI concepts and its applications.| |Day 3-5|Explore deep learning fundamentals|Fast.ai's Practical Deep Learning for Coders (2024)|Watch first 2 lessons. Code an image classifier as your first DL project.| |Day 6-7|Familiarize with ML/LLM terminology|Hugging Face Machine Learning Glossary|Study glossary terms and review foundational ML/LLM concepts.| |Week 2|Practical Deep Learning||| |Day 8-10|Build with PyTorch basics|PyTorch Beginner Tutorials|Complete the 60-minute blitz and create a simple neural network.| |Day 11-12|Explore more projects|Fast.ai Lesson 3|Implement a project such as text classification or tabular data analysis.| |Day 13-14|Fine-tune pre-trained models|Hugging Face Tutorials|Learn and apply fine-tuning techniques for a pre-trained model on a simple dataset.| |Week 3|Understanding LLMs||| |Day 15-17|Learn GPT architecture basics|OpenAI Documentation|Explore GPT architecture and experiment with OpenAI API Playground.| |Day 18-19|Understand tokenization and transformers|Hugging Face NLP Course|Complete the tokenization and transformers sections of the course.| |Day 20-21|Build LLM-based projects|TensorFlow NLP Tutorials|Create a text generator or summarizer using LLM techniques.| |Week 4|Advanced Concepts and Applications||| |Day 22-24|Review cutting-edge LLM research|Stanford's CRFM|Read recent LLM-related research and discuss its product management implications.| |Day 25-27|Apply knowledge to real-world projects|Kaggle|Select a dataset and build an NLP project using Hugging Face tools.| |Day 28-30|Explore advanced API use cases|OpenAI Cookbook and Forums|Experiment with advanced OpenAI API scenarios and engage in discussions to solidify knowledge.|

Randomly asked ChatGPT and Claude for a 4 year roadmap for an ML Engineer
reddit
LLM Vibe Score0
Human Vibe Score1
Brilliant_Fishing110This week

Randomly asked ChatGPT and Claude for a 4 year roadmap for an ML Engineer

Title, Is it actually a good plan ?? If no, why not ?? \\🚀 4-Year Roadmap to Becoming a High-Earning ML Engineer & Entrepreneur\\ \\(With Smartwork & Realistic 60-70% Execution Feasibility)\\ \\🟢 Year 1: Strong Foundation & Initial Projects (0-12 Months)\\ 🎯 \\Goal: Master Python & ML Fundamentals\\ \\🔹 1-4 Months (Python & Math Strengthening)\\ ✅ Python Mastery \- Daily LeetCode Easy problems (minimum 2) \- Build automation projects \- NumPy & Pandas mastery \- DSA fundamentals ✅ Mathematics Foundation \- Linear Algebra basics \- Statistics fundamentals \- Basic calculus concepts ✅ First Mini-Hackathon Participation \- Join beginner-friendly hackathons \- Focus on Python-based challenges \- Team up with other beginners 💡 \\Smart Move:\\ \- Join Discord/Slack hackathon communities \- Practice collaborative coding \- Build network with fellow participants \\🔹 5-8 Months (ML Foundations)\\ ✅ Machine Learning Basics \- Supervised Learning \- Model evaluation \- Feature engineering \- scikit-learn projects ✅ Participate in 2-3 ML Hackathons \- Kaggle Getting Started competitions \- Local ML hackathons \- University hackathons ✅ Start LinkedIn & GitHub Portfolio 💡 \\Smart Move:\\ \- Document hackathon experiences \- Share learnings on LinkedIn \- Focus on completion over winning \\🔹 9-12 Months (Deep Learning Introduction)\\ ✅ Basic Deep Learning \- Neural network fundamentals \- PyTorch basics \- Computer vision tasks \- Basic NLP ✅ Advanced Hackathon Participation \- AI/ML specific hackathons \- Team lead in 1-2 hackathons \- Start mentoring beginners \\🔵 Year 1 Expected Outcome (60-70% Execution)\\ ✔ \\Strong Python & ML foundations\\ ✔ \\5-6 hackathon participations\\ ✔ \\Active GitHub (100+ commits)\\ ✔ \\Growing LinkedIn (300+ connections)\\ 💰 \\Earning Expectation → ₹8K-₹20K per month (Projects/Internship)\\ \\🟢 Year 2: Professional Growth & Specialization (12-24 Months)\\ 🎯 \\Goal: Build Professional Experience & Recognition\\ \\🔹 1-6 Months (Technical Depth)\\ ✅ Advanced ML Topics \- Deep Learning architectures \- Computer Vision OR NLP \- MLOps basics (Docker, FastAPI) \- Cloud fundamentals (AWS/GCP) ✅ Hackathon Achievements \- Win minor prizes in 2-3 hackathons \- Lead teams in major hackathons \- Network with sponsors ✅ Start Technical Blogging 💡 \\Smart Move:\\ \- Focus on hackathon projects that align with career goals \- Build relationships with companies at hackathons \- Create detailed project documentation \\🔹 7-12 Months (Professional Experience)\\ ✅ Secure ML Role/Internship ✅ Advanced Project Building ✅ Open Source Contributions ✅ Organize Small Hackathons 💡 \\Smart Move:\\ \- Use hackathon network for job referrals \- Convert hackathon projects into full products \- Build mentor reputation \\🔵 Year 2 Expected Outcome (60-70% Execution)\\ ✔ \\Professional ML experience\\ ✔ \\10+ hackathon participations\\ ✔ \\1-2 hackathon wins\\ ✔ \\Strong industry network\\ 💰 \\Earning Expectation → ₹40K-₹70K per month (Job/Freelancing)\\ \\🟢 Year 3: Scaling & Business Foundation (24-36 Months)\\ 🎯 \\Goal: Establish Multiple Income Streams\\ \\🔹 1-4 Months (Expertise Building)\\ ✅ Choose Specialization \- MLOps \- Computer Vision \- NLP/LLMs \- Generative AI ✅ Advanced Competitions \- International hackathons \- High-prize competitions \- Corporate ML challenges ✅ Start Consulting Services 💡 \\Smart Move:\\ \- Use hackathon wins for marketing \- Build service packages around expertise \- Network with corporate sponsors \\🔹 5-8 Months (Business Development)\\ ✅ Scale Services ✅ Build Client Network ✅ Create Training Programs ✅ Hackathon Mentorship Program 💡 \\Smart Move:\\ \- Convert hackathon projects to products \- Use event networks for client acquisition \- Build authority through speaking \\🔹 9-12 Months (Growth & Innovation)\\ ✅ Product Development ✅ Team Building ✅ Innovation Focus ✅ Hackathon Organization \\🔵 Year 3 Expected Outcome (60-70% Execution)\\ ✔ \\Established ML business/career\\ ✔ \\Known in hackathon community\\ ✔ \\Multiple income streams\\ ✔ \\Strong industry presence\\ 💰 \\Earning Expectation → ₹1L-₹2L per month (Multiple Streams)\\ \\🟢 Year 4: Scale & Leadership (36-48 Months)\\ 🎯 \\Goal: Build AI Company & Achieve Financial Freedom\\ \\🔹 1-4 Months (Business Scaling)\\ ✅ Company Formation \- AI consulting firm \- Product development \- Training programs ✅ Hackathon Innovation \- Launch own hackathon series \- Corporate partnerships \- Prize sponsorships ✅ Team Expansion 💡 \\Smart Move:\\ \- Use hackathon network for hiring \- Create unique event formats \- Build corporate relationships \\🔹 5-8 Months (Market Leadership)\\ ✅ Product Launch ✅ Service Expansion ✅ International Presence ✅ Innovation Hub Creation 💡 \\Smart Move:\\ \- Create hackathon-to-hiring pipeline \- Build educational programs \- Establish thought leadership \\🔹 9-12 Months (Empire Building)\\ ✅ Multiple Revenue Streams \- AI products \- Consulting services \- Educational programs \- Event organization \- Investment returns ✅ Industry Leadership \- Conference speaking \- Published content \- Community leadership \\🔵 Year 4 Expected Outcome (60-70% Execution)\\ ✔ \\Established AI company\\ ✔ \\Major hackathon organizer\\ ✔ \\Multiple product lines\\ ✔ \\Industry authority status\\ 💰 \\Earning Expectation → ₹3L-₹5L+ per month (Business Income)\\ \\📊 FINAL RATING\\ ✅ \\Comprehensive growth plan\\ ✅ \\Strong community focus\\ ✅ \\Multiple income pathways\\ 💡 \\If 100% Execution → 8.5/10 Feasibility\\ 💡 \\If 50% Execution → 6/10 Feasibility\\ 🔥 \\Conclusion: A balanced path to ML mastery and entrepreneurship, built through consistent growth and community engagement!\\ 🚀 \\Key Success Factors:\\ Regular hackathon participation Strong community involvement Consistent skill development Strategic network building Focus on both technical and business growth

AI Noob where to start?
reddit
LLM Vibe Score0
Human Vibe Score1
alin_imThis week

AI Noob where to start?

Hello, TL;DR: Where do I get started with AI from an ICT engineer POV? I find the subject complex and vague, and I have no idea where to start. A little bit about myself, I am a telecoms engineer with 7 years of experience in networking, servers (virtualisation and containers), Audio-visual and industrial/home automations and CAD, but I am more specialised in the first 4 layers of the OSI model with a little experience in Python, YAML and Ansible (nowhere near a software engineer, but decent enough to make simple automations work if needed). I am starting to have clients that ask questions about AI and its use for their business, and I am not confident in answering them. Where should I start? My only knowledge about AI was gathered from a course I have done “AI Infrastructure and Operations Fundamentals” from Nvidia and the fact that Lamma is an open-source model from Meta (which I absolutely adore the idea of local open-source AI). I am do not think I want to be an AI developer and pivot, but more like how AI can enhance my current skill set. I want to understand what the technical requirements are, technical terminology, how the different models can be used for different purposes (text, images, etc.). From a HW perspective, I am long overdue for a workstation upgrade (currently i7 9^(th) Gen, RTX 2060 Super 8Gb VRAM, 16Gb DDR4 RAM) I use my workstation as a homelab and for CAD and gaming. My hope is that by the time intel 15^(th) gen and Nvidia 5000 will be released, I will have some kind of idea of what I want to do with it from an AI perspective. I have seen a lot of knowledgeable people in this subreddit and wanted to know what it was their journey and how did they get started? What do you recommend (courses, books, HW/SW, etc.)?

Randomly asked ChatGPT and Claude for a 4 year roadmap for an ML Engineer
reddit
LLM Vibe Score0
Human Vibe Score1
Brilliant_Fishing110This week

Randomly asked ChatGPT and Claude for a 4 year roadmap for an ML Engineer

Title, Is it actually a good plan ?? If no, why not ?? \\🚀 4-Year Roadmap to Becoming a High-Earning ML Engineer & Entrepreneur\\ \\(With Smartwork & Realistic 60-70% Execution Feasibility)\\ \\🟢 Year 1: Strong Foundation & Initial Projects (0-12 Months)\\ 🎯 \\Goal: Master Python & ML Fundamentals\\ \\🔹 1-4 Months (Python & Math Strengthening)\\ ✅ Python Mastery \- Daily LeetCode Easy problems (minimum 2) \- Build automation projects \- NumPy & Pandas mastery \- DSA fundamentals ✅ Mathematics Foundation \- Linear Algebra basics \- Statistics fundamentals \- Basic calculus concepts ✅ First Mini-Hackathon Participation \- Join beginner-friendly hackathons \- Focus on Python-based challenges \- Team up with other beginners 💡 \\Smart Move:\\ \- Join Discord/Slack hackathon communities \- Practice collaborative coding \- Build network with fellow participants \\🔹 5-8 Months (ML Foundations)\\ ✅ Machine Learning Basics \- Supervised Learning \- Model evaluation \- Feature engineering \- scikit-learn projects ✅ Participate in 2-3 ML Hackathons \- Kaggle Getting Started competitions \- Local ML hackathons \- University hackathons ✅ Start LinkedIn & GitHub Portfolio 💡 \\Smart Move:\\ \- Document hackathon experiences \- Share learnings on LinkedIn \- Focus on completion over winning \\🔹 9-12 Months (Deep Learning Introduction)\\ ✅ Basic Deep Learning \- Neural network fundamentals \- PyTorch basics \- Computer vision tasks \- Basic NLP ✅ Advanced Hackathon Participation \- AI/ML specific hackathons \- Team lead in 1-2 hackathons \- Start mentoring beginners \\🔵 Year 1 Expected Outcome (60-70% Execution)\\ ✔ \\Strong Python & ML foundations\\ ✔ \\5-6 hackathon participations\\ ✔ \\Active GitHub (100+ commits)\\ ✔ \\Growing LinkedIn (300+ connections)\\ 💰 \\Earning Expectation → ₹8K-₹20K per month (Projects/Internship)\\ \\🟢 Year 2: Professional Growth & Specialization (12-24 Months)\\ 🎯 \\Goal: Build Professional Experience & Recognition\\ \\🔹 1-6 Months (Technical Depth)\\ ✅ Advanced ML Topics \- Deep Learning architectures \- Computer Vision OR NLP \- MLOps basics (Docker, FastAPI) \- Cloud fundamentals (AWS/GCP) ✅ Hackathon Achievements \- Win minor prizes in 2-3 hackathons \- Lead teams in major hackathons \- Network with sponsors ✅ Start Technical Blogging 💡 \\Smart Move:\\ \- Focus on hackathon projects that align with career goals \- Build relationships with companies at hackathons \- Create detailed project documentation \\🔹 7-12 Months (Professional Experience)\\ ✅ Secure ML Role/Internship ✅ Advanced Project Building ✅ Open Source Contributions ✅ Organize Small Hackathons 💡 \\Smart Move:\\ \- Use hackathon network for job referrals \- Convert hackathon projects into full products \- Build mentor reputation \\🔵 Year 2 Expected Outcome (60-70% Execution)\\ ✔ \\Professional ML experience\\ ✔ \\10+ hackathon participations\\ ✔ \\1-2 hackathon wins\\ ✔ \\Strong industry network\\ 💰 \\Earning Expectation → ₹40K-₹70K per month (Job/Freelancing)\\ \\🟢 Year 3: Scaling & Business Foundation (24-36 Months)\\ 🎯 \\Goal: Establish Multiple Income Streams\\ \\🔹 1-4 Months (Expertise Building)\\ ✅ Choose Specialization \- MLOps \- Computer Vision \- NLP/LLMs \- Generative AI ✅ Advanced Competitions \- International hackathons \- High-prize competitions \- Corporate ML challenges ✅ Start Consulting Services 💡 \\Smart Move:\\ \- Use hackathon wins for marketing \- Build service packages around expertise \- Network with corporate sponsors \\🔹 5-8 Months (Business Development)\\ ✅ Scale Services ✅ Build Client Network ✅ Create Training Programs ✅ Hackathon Mentorship Program 💡 \\Smart Move:\\ \- Convert hackathon projects to products \- Use event networks for client acquisition \- Build authority through speaking \\🔹 9-12 Months (Growth & Innovation)\\ ✅ Product Development ✅ Team Building ✅ Innovation Focus ✅ Hackathon Organization \\🔵 Year 3 Expected Outcome (60-70% Execution)\\ ✔ \\Established ML business/career\\ ✔ \\Known in hackathon community\\ ✔ \\Multiple income streams\\ ✔ \\Strong industry presence\\ 💰 \\Earning Expectation → ₹1L-₹2L per month (Multiple Streams)\\ \\🟢 Year 4: Scale & Leadership (36-48 Months)\\ 🎯 \\Goal: Build AI Company & Achieve Financial Freedom\\ \\🔹 1-4 Months (Business Scaling)\\ ✅ Company Formation \- AI consulting firm \- Product development \- Training programs ✅ Hackathon Innovation \- Launch own hackathon series \- Corporate partnerships \- Prize sponsorships ✅ Team Expansion 💡 \\Smart Move:\\ \- Use hackathon network for hiring \- Create unique event formats \- Build corporate relationships \\🔹 5-8 Months (Market Leadership)\\ ✅ Product Launch ✅ Service Expansion ✅ International Presence ✅ Innovation Hub Creation 💡 \\Smart Move:\\ \- Create hackathon-to-hiring pipeline \- Build educational programs \- Establish thought leadership \\🔹 9-12 Months (Empire Building)\\ ✅ Multiple Revenue Streams \- AI products \- Consulting services \- Educational programs \- Event organization \- Investment returns ✅ Industry Leadership \- Conference speaking \- Published content \- Community leadership \\🔵 Year 4 Expected Outcome (60-70% Execution)\\ ✔ \\Established AI company\\ ✔ \\Major hackathon organizer\\ ✔ \\Multiple product lines\\ ✔ \\Industry authority status\\ 💰 \\Earning Expectation → ₹3L-₹5L+ per month (Business Income)\\ \\📊 FINAL RATING\\ ✅ \\Comprehensive growth plan\\ ✅ \\Strong community focus\\ ✅ \\Multiple income pathways\\ 💡 \\If 100% Execution → 8.5/10 Feasibility\\ 💡 \\If 50% Execution → 6/10 Feasibility\\ 🔥 \\Conclusion: A balanced path to ML mastery and entrepreneurship, built through consistent growth and community engagement!\\ 🚀 \\Key Success Factors:\\ Regular hackathon participation Strong community involvement Consistent skill development Strategic network building Focus on both technical and business growth

I started with 0 AI knowledge on the 2nd of Jan 2024 and blogged and studied it for 365. Here is a summary.
reddit
LLM Vibe Score0
Human Vibe Score0
BobsthejobThis week

I started with 0 AI knowledge on the 2nd of Jan 2024 and blogged and studied it for 365. Here is a summary.

FULL BLOG POST AND MORE INFO IN THE FIRST COMMENT :) Edit in title: 365 days\* (and spelling) Coming from a background in accounting and data analysis, my familiarity with AI was minimal. Prior to this, my understanding was limited to linear regression, R-squared, the power rule in differential calculus, and working experience using Python and SQL for data manipulation. I studied free online lectures, courses, read books. \Time Spent on Theory vs Practice\ At the end it turns out I spent almost the same amount of time on theory and practice. While reviewing my year, I found that after learning something from a course/lecture in one of the next days I immediately applied it - either through exercises, making a Kaggle notebook or by working on a project. \2024 Learning Journey Topic Breakdown\ One thing I learned is that \fundamentals\ matter. I discovered that anyone can make a model, but it's important to make models that add business value. In addition, in order to properly understand the inner-workings of models I wanted to do a proper coverage of stats & probability, and the math behind AI. I also delved into 'traditional' ML (linear models, trees), and also deep learning (NLP, CV, Speech, Graphs) which was great. It's important to note that I didn't start with stats & math, I was guiding myself and I started with traditional and some GenAI but soon after I started to ask a lot of 'why's as to why things work and this led me to study more about stats&math. Soon I also realised \Data is King\ so I delved into data engineering and all the practices and ideas it covers. In addition to Data Eng, I got interested in MLOps. I wanted to know what happens with models after we evaluate them on a test set - well it turns out there is a whole field behind it, and I was immediately hooked. Making a model is not just taking data from Kaggle and doing train/test eval, we need to start with a business case, present a proper case to add business value and then it is a whole lifecycle of development, testing, maintenance and monitoring. \Wordcloud\ After removing some of the generically repeated words, I created this work cloud from the most used works in my 365 blog posts. The top words being:- model and data - not surprising as they go hand in hand- value - as models need to deliver value- feature (engineering) - a crucial step in model development- system - this is mostly because of my interest in data engineering and MLOps I hope you find my summary and blog interesting. https://preview.redd.it/pxohznpy4dae1.png?width=2134&format=png&auto=webp&s=03c16bb3535d75d1f009b44ee5164cc3e6483ac4 https://preview.redd.it/0y47rrpy4dae1.png?width=1040&format=png&auto=webp&s=f1fdf7764c7151ff0a05ae92777c5bb7d52f4359 https://preview.redd.it/e59inppy4dae1.png?width=1566&format=png&auto=webp&s=2566033777a90410277350947617d3ce8406be15

Learning AI for Business Leaders
reddit
LLM Vibe Score0
Human Vibe Score0
Bills-WideRightThis week

Learning AI for Business Leaders

Hello Community, For the better part of 2 months I have been reading up on everything in getting a better understanding of the fundamentals of AI - from history of AI to reading the Google 8’s peer reviewed paper on the advent of transformers. I feel as though I am running in circles at times an not following a guided path approach to learning. I’m 40, work in international development in a leadership role - though I have a background in corporate finance and tech. I’m not an engineer, nor do I have the ambition of such a career pivot. However I do want to learn, be abreast, and know enough about the space when evaluating (and proposing) AI related opportunities - my role now should be a path towards a chief innovation officer for a development agency within the next 3-4 years. My sources have been basically everything I can find from tech blogs, WaPo, financial times, economist, and random internet searches. I have completed IBM’s Fundamental on AI course. However, I feel there no structure in learning as I have been piecemealing from so many different sources. Essentially I care about business cases and being able to confidently talk about AI. And not building and deploying a product. MIT and UPenn have some courses on AI for leaders, however, as the space is moving so fast I’m not confident how current their materials are. My ask: Are there any courses (or learning approaches) you recommend that is less-code and more focus on concept and applications I should do? Is my approach to learning too broad and I should focus on a subset of AI such as ML or specifically GenAI since it seems most applications are currently byproducts of it. Many thanks in advance for any support - truly appreciate it.

Backend dev wants to learn ML
reddit
LLM Vibe Score0
Human Vibe Score1
chipmuxThis week

Backend dev wants to learn ML

Hello ML Experts, I am staff engineer, working in a product based organization, handling the backend services. I see myself becoming Solution Architect and then Enterprise Architect one day. With the AI and ML trending now a days, So i feel ML should be an additional skill that i should acquire which can help me leading and architecting providing solutions to the problems more efficiently, I think however it might not replace the traditional SWEs working on backend APIs completely, but ML will be just an additional diamention similar to the knowledge of Cloud services and DevOps. So i would like to acquire ML knowledge, I dont have any plans to be an expert at it right now, nor i want to become a full time data scientist or ML engineer as of today. But who knows i might diverge, but thats not the plan currently. I did some quick promting with ChatGPT and was able to comeup with below learning path for me. So i would appreciate if some of you ML experts can take a look at below learning path and provide your suggestions 📌 PHASE 1: Core AI/ML & Python for AI (3-4 Months) Goal: Build a solid foundation in AI/ML with Python, focusing on practical applications. 1️⃣ Python for AI/ML (2-3 Weeks) Course: [Python for Data Science and Machine Learning Bootcamp]() (Udemy) Topics: Python, Pandas, NumPy, Matplotlib, Scikit-learn basics 2️⃣ Machine Learning Fundamentals (4-6 Weeks) Course: Machine Learning Specialization by Andrew Ng (C0ursera) Topics: Linear & logistic regression, decision trees, SVMs, overfitting, feature engineering Project: Build an ML model using Scikit-learn (e.g., predicting house prices) 3️⃣ Deep Learning & AI Basics (4-6 Weeks) Course: Deep Learning Specialization by Andrew Ng (C0ursera) Topics: Neural networks, CNNs, RNNs, transformers, generative AI (GPT, Stable Diffusion) Project: Train an image classifier using TensorFlow/Keras 📌 PHASE 2: AI/ML for Enterprise & Cloud Applications (3-4 Months) Goal: Learn how AI is integrated into cloud applications & enterprise solutions. 4️⃣ AI/ML Deployment & MLOps (4 Weeks) Course: MLOps Specialization by Andrew Ng (C0ursera) Topics: Model deployment, monitoring, CI/CD for ML, MLflow, TensorFlow Serving Project: Deploy an ML model as an API using FastAPI & Docker 5️⃣ AI/ML in Cloud (Azure, AWS, OpenAI APIs) (4-6 Weeks) Azure AI Services: Course: Microsoft AI Fundamentals (C0ursera) Topics: Azure ML, Azure OpenAI API, Cognitive Services AWS AI Services: Course: [AWS Certified Machine Learning – Specialty]() (Udemy) Topics: AWS Sagemaker, AI workflows, AutoML 📌 PHASE 3: AI Applications in Software Development & Future Trends (Ongoing Learning) Goal: Explore AI-powered tools & future-ready AI applications. 6️⃣ Generative AI & LLMs (ChatGPT, GPT-4, LangChain, RAG, Vector DBs) (4 Weeks) Course: [ChatGPT Prompt Engineering for Developers]() (DeepLearning.AI) Topics: LangChain, fine-tuning, RAG (Retrieval-Augmented Generation) Project: Build an LLM-based chatbot with Pinecone + OpenAI API 7️⃣ AI-Powered Search & Recommendations (Semantic Search, Personalization) (4 Weeks) Course: [Building Recommendation Systems with Python]() (Udemy) Topics: Collaborative filtering, knowledge graphs, AI search 8️⃣ AI-Driven Software Development (Copilot, AI Code Generation, Security) (Ongoing) Course: AI-Powered Software Engineering (C0ursera) Topics: AI code completion, AI-powered security scanning 🚀 Final Step: Hands-on Projects & Portfolio Once comfortable, work on real-world AI projects: AI-powered document processing (OCR + LLM) AI-enhanced search (Vector Databases) Automated ML pipelines with MLOps Enterprise AI Chatbot using LLMs ⏳ Suggested Timeline 📅 6-9 Months Total (10-12 hours/week) 1️⃣ Core ML & Python (3-4 months) 2️⃣ Enterprise AI/ML & Cloud (3-4 months) 3️⃣ AI Future Trends & Applications (Ongoing) Would you like a customized plan with weekly breakdowns? 🚀

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I very rarely have stuff to post on Reddit, but I share how my project is going on, just random stuff, and memes on X. In case few might want to keep up 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2B products beats building B2C products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

Introducing Vest: Your AI-Powered Due Diligence Partner - Looking for feedback!
reddit
LLM Vibe Score0
Human Vibe Score1
nervousslinkyThis week

Introducing Vest: Your AI-Powered Due Diligence Partner - Looking for feedback!

TLDR; We are introducing Vest, an AI powered due-diligence and stock recommendation platform. We have bootstrapped ourselves so far and are wanting to get as much feedback from Reddit as we can to see where we can improve, but also what we are doing right. So please have a look around, give us feedback and if you like it, feel free to use it. Hi Reddit, My name is Drian and I'm one of the founders of Vest. We believe we are crafting something special at Vest and we want to get the word out and gather as much feedback as possible! Our major goal at Vest is to help new retail investors make sense of the investment landscape and get AI powered assistance, or even help experienced investors get confirmation of their potential moves. Overall, we want people to start their journey to financial freedom and not be daunted by the complexity of it. So how do we do this? Vest is a user-friendly service that harnesses fundamental metrics, social and news sentiment, and technical analysis, that we feed into some advanced AI models to generate clear buy, sell, or hold signals for US-based (for now!) stocks, offering our users transparent due-diligence for confident investing. The service is currently free with no ads - however, at some point we do plan on adding a paid tier. What's included: &#x200B; Financial Metrics. Our financial metrics take all the potentially complex mathematical equations and present the fundamentals of a company to users in a simple 1 pager, with a score displaying if the metric is positive for a stock. We also provide publicly available analyst ratings from investment banks as well as price targets they have set. News Sentiment. We take publications about a specific stock from new articles, journals and socials and give these all a rating to determine if social sentiment is positive around a stock or not. Each article and its rating is visible to our users through through our dashboard. AI assisted Stock Signals. We have developed an algorithm to take all the metrics, sentiment and technical analysis we collate and analyze this with historic performance data for every stock to attempt to figure out if a stock is undervalued (great time to buy) or overvalued (great time to sell). 155 US stock tickers and counting. We currently have trained our models for around 155 US based stocks on the NASDAQ and NYSE exchanges. As we get more funding/runway we do plan on adding more, with the eventual goal to expand to more exchanges, countries and securities. Knowledge base and community. Our knowledge base & community contains explanations and articles for all metrics and the other good stuff behind Vest. We don’t want to just tell users what to do, but to also assist in their financial education. We hope our knowledge base can also become a thriving community where users can interact with us and each, ask questions around investing and keep gaining knowledge. Is it 100% accurate? Absolutely not. While we do a pretty great job at tracking and surfacing signals, we are not presenting a fool-proof, silver bullet with a guarantee here - rather a starting point for users to make more informed decisions, find potential new investment opportunities and hopefully learn about investing as they do so. We encourage our users to do their own research and due-diligence and not just take our signals as gospel - we know each and every person has a different risk appetite and goals, and we encourage you to use Vest in a way that fits with your own financial goals and risk appetite. We also display our win rates, average returns, and comparisons with buy and hold for each stock - and we are transparent about it when we’ve fallen short. Next steps: &#x200B; Hope over to vestapp.ai and sign-up From the dashboard, play around, inspect our stock information and add some stocks to your watchlist. If you like what you see, and you’ve done your homework - use your favourite brokerage account to make an investment and watch Vest for changes in a stocks signals. If you don’t have one, we have a pop-up when you click buy/sell on any given stock with some non-affiliated brokerage options for the US, Australia and New Zealand - we don’t get a kickback from these brokerages, they are just what we’ve personally been using. FEEDBACK - We’re just getting started and we know the value of a fresh pair of eyes - our current mission is to get as much feedback as possible - anything you think of please send it through here or on the dedicated feedback form on our website in the sidebar on the left. Features we’re working on We're quietly thrilled about the direction Vest is headed, and we want to give you a sneak peek of what's in store for the next couple of quarters. Some of these may roll out as premium features, but we're diligently fine-tuning the details. Here's what you can expect: &#x200B; Insider Trading Insights: Get daily reports on major stock moves by whales and company insiders. Institutional Holders: We're adding daily reports on institutional holders, keeping you informed about their moves. Lobbying Activity: We're actively working on daily updates about lobbying activities, so you can stay informed. Government Contracts Data: We'll provide a quarterly snapshot of government contract values for the companies you're tracking. US Congress Stock Activity: Keep an eye on daily trading actions of House and Senate members. Daily Summaries & Signal Alerts: We're currently hard at work on this feature. Soon, receive daily email summaries covering signals, watchlist updates, and key news. Personalized Risk Management: Tailor signals to match your unique risk management strategy. Your investments, your way. AI Assistant: Our LLM integration is almost ready, allowing you to ask it straightforward questions about particular securities in plain English. It will provide you with real-time context on fundamentals, news, and all the metrics and data points we monitor.

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I very rarely have stuff to post on Reddit, but I share how my project is going on, just random stuff, and memes on X. In case few might want to keep up 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2B products beats building B2C products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

[D] Advanced courses update
reddit
LLM Vibe Score0
Human Vibe Score1
actbshThis week

[D] Advanced courses update

EDIT Jan 2021 : I am still updating the list as of Jan, 2021 and will most probably continue to do so for foreseeable future. So, please feel free to message me any courses you find interesting that fit here. - - We have a PhD level or Advanced courses thread in the sidebar but it's three year old now. There were two other 7-8 month old threads (1, 2) but they don't have many quality responses either. So, can we have a new one here? To reiterate - CS231n, CS229, ones from Udemy etc are not advanced. Advanced ML/DL/RL, attempts at building theory of DL, optimization theory, advanced applications etc are some examples of what I believe should belong here, much like the original sidebar post. You can also suggest (new) categories for the courses you share. :) - - Here are some courses we've found so far. ML >> Learning Discrete Latent Structure - sta4273/csc2547 Spring'18 Learning to Search - csc2547 Fall'19 Scalable and Flexible Models of Uncertainty - csc2541 Fundamentals of Machine Learning Over Networks - ep3260 Machine Learning on Graphs - cs224w, videos Mining Massive Data Sets - cs246 Interactive Learning - cse599 Machine Learning for Sequential Decision Making Under Uncertainty - ee290s/cs194 Probabilistic Graphical Methods - 10-708 Introduction to Causal Inference ML >> Theory Statistical Machine Learning - 10-702/36-702 with videos, 2016 videos Statistical Learning Theory - cs229T/stats231 Stanford Autumn'18-19 Statistical Learning Theory - cs281b /stat241b UC Berkeley, Spring'14 Statistical Learning Theory - csc2532 Uni of Toronto, Spring'20 ML >> Bayesian Bayesian Data Analysis Bayesian Methods Research Group, Moscow, Bayesian Methods in ML - spring2020, fall2020 Deep Learning and Bayesian Methods - summer school, videos available for 2019 version ML >> Systems and Operations Stanford MLSys Seminar Series Visual Computing Systems- cs348v - Another systems course that discusses hardware from a persepective of visual computing but is relevant to ML as well Advanced Machine Learning Systems - cs6787 - lecture 9 and onwards discuss hardware side of things Machine Learning Systems Design - cs329S Topics in Deployable ML - 6.S979 Machine Learning in Production / AI Engineering (17-445/17-645/17-745/11-695) AutoML - Automated Machine Learning DL >> Deep Unsupervised Learning - cs294 Deep Multi-task and Meta learning - cs330 Topics in Deep Learning - stat991 UPenn/Wharton most chapters start with introductory topics and dig into advanced ones towards the end. Deep Generative Models - cs236 Deep Geometric Learning of Big Data and Applications Deep Implicit Layers - NeurIPS 2020 tutorial DL >> Theory Topics course on Mathematics of Deep Learning - CSCI-GA 3033 Topics Course on Deep Learning - stat212b Analyses of Deep Learning - stats385, videos from 2017 version Mathematics of Deep Learning Geometry of Deep Learning RL >> Meta-Learning - ICML 2019 Tutorial , Metalearning: Applications to Data Mining - google books link Deep Multi-Task and Meta Learning - cs330, videos Deep Reinforcement Learning - cs285 Advanced robotics - cs287 Reinforcement Learning - cs234, videos for 2019 run Reinforcement Learning Summer School 2019: Bandits, RL & Deep RL Optimization >> Convex Optimization I - ee364a, has quite recent videos too. Convex Optimization II - ee364b, 2008 videos Convex Optimization and Approximation - ee227c Convex Optimization - ee227bt Variational Methods for Computer Vision Advanced Optimization and Randomized Algorithms - 10-801, videos Optimization Methods for Machine Learning and Engineering - Karlsruhe Institute of Technology Applications >> Computer Vision Computational Video Manipulation - cs448v Advanced Topics in ML: Modeling and Segmentation of Multivariate Mixed Data TUM AI Guest lecture series - many influential researchers in DL, vision, graphics talk about latest advances and their latest works. Advanced Deep Learning for Computer Vision - TUM ADL4CV Detection, Segmentation and Tracking - TUM CV3DST Guest lectures at TUM Dynamic Vision and Learning group Vision Seminar at MIT Autonomous Vision Group, Talk@Tübingen Seminar Applications >> Natural Language Processing Natural Language Processing with Deep Learning - cs224n ( not sure if it belongs here, people working in NLP can help me out) Neural networks for NLP - cs11-747 Natural Language Understanding - cs224u, video Applications >> 3D Graphics Non-Euclidean Methods in Machine Learning - cs468, 2020 Machine Learning for 3D Data - cs468, spring 2017 Data-Driven Shape Analysis - cs468, 2014 Geometric Deep Learning - Not a course but the website links a few tutorials on Geometric DL Deep Learning for Computer Graphics - SIGGRAPH 2019 Machine Learning for Machine Vision as Inverse Graphics - csc2547 Winter'20 Machine Learning Meets Geometry, winter 2020; Machine Learning for 3D Data, winter 2018 Edit: Upon suggestion, categorized the courses. There might be some misclassifications as I'm not trained on this task ;). Added some good ones from older (linked above) discussions.

[D] A Jobless Rant - ML is a Fool's Gold
reddit
LLM Vibe Score0
Human Vibe Score1
good_riceThis week

[D] A Jobless Rant - ML is a Fool's Gold

Aside from the clickbait title, I am earnestly looking for some advice and discussion from people who are actually employed. That being said, here's my gripe: I have been relentlessly inundated by the words "AI, ML, Big Data" throughout my undergrad from other CS majors, business and sales oriented people, media, and .ai type startups. It seems like everyone was peddling ML as the go to solution, the big money earner, and the future of the field. I've heard college freshman ask stuff like, "if I want to do CS, am I going to need to learn ML to be relevant" - if you're on this sub, I probably do not need to continue to elaborate on just how ridiculous the ML craze is. Every single university has opened up ML departments or programs and are pumping out ML graduates at an unprecedented rate. Surely, there'd be a job market to meet the incredible supply of graduates and cultural interest? Swept up in a mixture of genuine interest and hype, I decided to pursue computer vision. I majored in Math-CS at a top-10 CS university (based on at least one arbitrary ranking). I had three computer vision internships, two at startups, one at NASA JPL, in each doing non-trivial CV work; I (re)implemented and integrated CV systems from mixtures of recently published papers. I have a bunch of projects showing both CV and CS fundamentals (OS, networking, data structures, algorithms, etc) knowledge. I have taken graduate level ML coursework. I was accepted to Carnegie Mellon for an MS in Computer Vision, but I deferred to 2021 - all in all, I worked my ass off to try to simultaneously get a solid background in math AND computer science AND computer vision. That brings me to where I am now, which is unemployed and looking for jobs. Almost every single position I have seen requires a PhD and/or 5+ years of experience, and whatever I have applied for has ghosted me so far. The notion that ML is a high paying in-demand field seems to only be true if your name is Andrej Karpathy - and I'm only sort of joking. It seems like unless you have a PhD from one of the big 4 in CS and multiple publications in top tier journals you're out of luck, or at least vying for one of the few remaining positions at small companies. This seems normalized in ML, but this is not the case for quite literally every other subfield or even generalized CS positions. Getting a high paying job at a Big N company is possible as a new grad with just a bachelors and general SWE knowledge, and there are a plethora of positions elsewhere. Getting the equivalent with basically every specialization, whether operating systems, distributed systems, security, networking, etc, is also possible, and doesn't require 5 CVPR publications. TL;DR From my personal perspective, if you want to do ML because of career prospects, salaries, or job security, pick almost any other CS specialization. In ML, you'll find yourself working 2x as hard through difficult theory and math to find yourself competing with more applicants for fewer positions. I am absolutely complaining and would love to hear a more positive perspective, but in the meanwhile I'll be applying to jobs, working on more post-grad projects, and contemplating switching fields.

[CASE STUDY] From 217/m to $2,836/m in 9 months - Sold for $59,000; I grow and monetise web traffic of 5, 6, 7 figures USD valued passive income content sites [AMA]
reddit
LLM Vibe Score0
Human Vibe Score1
jamesackerman1234This week

[CASE STUDY] From 217/m to $2,836/m in 9 months - Sold for $59,000; I grow and monetise web traffic of 5, 6, 7 figures USD valued passive income content sites [AMA]

Hello Everyone (VERY LONG CASE STUDY AHEAD) - 355% return in 9 months Note: I own a 7-figures USD valued portfolio of 41+ content sites that generates 5-6 figures USD a month in passive income. This is my first time posting in this sub and my goal is to NOT share generic advice but precise numbers, data and highly refined processes so you can also get started with this business yourself or if you already have an existing business, drive huge traffic to it and scale it substantially (get more customers). I will use a case study to explain the whole process. As most of us are entrepreneurs here, explaining an actual project would be more meaningful. In this case study I used AI assisted content to grow an existing site from $217/m to $2,836/m in 9 months (NO BACKLINKS) and sold it for $59,000. ROI of 3 months: 355% Previous case studies (before I give an overview of the model) Amazon Affiliate Content Site: $371/m to $19,263/m in 14 MONTHS - $900K CASE STUDY \[AMA\] Affiliate Website from $267/m to $21,853/m in 19 months (CASE STUDY - Amazon?) \[AMA\] Amazon Affiliate Website from $0 to $7,786/month in 11 months Amazon Affiliate Site from $118/m to $3,103/m in 8 MONTHS (SOLD it for $62,000+) Note: You can check pinned posts on my profile. Do go through the comments as well as a lot of questions are answered in those. However, if you still have any questions, feel free to reach out. This is an \[AMA\]. Quick Overview of the Model Approach: High traffic, niche specific, informative content websites that monetise its traffic through highly automated methods like display ads and affiliate. The same model can be applied to existing businesses to drive traffic and get customers. Main idea: Make passive income in a highly automated way Easy to understand analogy You have real estate (here you have digital asset like a website) You get rental income (here you get ads and affiliate income with no physical hassle, in case you have a business like service, product etc. then you can get customers for that too but if not, it's alright) Real estate has value (this digital asset also has value that can be appreciated with less effort) Real estate can be sold (this can be sold too but faster) IMPORTANT NOTE: Search traffic is the BEST way to reach HUGE target audience and it's important when it comes to scaling. This essentially means that you can either monetise that via affiliate, display etc. or if you have a business then you can reach a bigger audience to scale. Overview of this website's valuation (then and now: Oct. 2022 and June 2023) Oct 2022: $217/m Valuation: $5,750.5 (26.5x) - set it the same as the multiple it was sold for June 2023: $2,836/m Traffic and revenue trend: growing fast Last 3 months avg: $2,223 Valuation now: $59,000 (26.5x) Description: The domain was registered in 2016, it grew and then the project was left unattended. I decided to grow it again using properly planned AI assisted content. Backlink profile: 500+ Referring domains (Ahrefs). Backlinks mean the sites linking back to you. This is important when it comes to ranking. Summary of Results of This Website - Before and After Note: If the terms seem technical, do not worry. I will explain them in detail later. Still if you have any questions. Feel free to comment or reach out. |Metric|Oct 2022|June 2023|Difference|Comments| |:-|:-|:-|:-|:-| |Articles|314|804|\+490|AI Assisted content published in 3 months| |Traffic|9,394|31,972|\+22,578|Organic| |Revenue|$217|$2,836|\+$2,619|Multiple sources| |RPM (revenue/1000 web traffic)|23.09|$88.7|\+$65.61|Result of Conversion rate optimisation (CRO). You make changes to the site for better conversions| |EEAT (expertise, experience, authority and trust of website)|2 main authors|8 authors|6|Tables, video ads and 11 other fixations| |CRO|Nothing|Tables, video ads |Tables, video ads and 11 other fixations || &#x200B; Month by Month Growth |Month|Revenue|Steps| |:-|:-|:-| |Sept 2022|NA|Content Plan| |Oct 2022|$217|Content Production| |Nov 2022|$243|Content production + EEAT authors| |Dec 2022|$320|Content production + EEAT authors| |Jan 2023|$400|Monitoring| |Feb 2023|$223|Content production + EEAT authors| |Mar 2023|$2,128|CRO & Fixations| |April 2023|$1,609|CRO & Fixations| |May 2023|$2,223|Content production + EEAT authors| |June 2023|$2,836|CRO and Fixations| |Total|$10,199|| &#x200B; What will I share Content plan and Website structure Content Writing Content Uploading, formatting and onsite SEO Faster indexing Conversion rate optimisation Guest Posting EEAT (Experience, Expertise, Authority, Trust) Costing ROI The plans moving forward with these sites &#x200B; Website Structure and Content Plan This is probably the most important important part of the whole process. The team spends around a month just to get this right. It's like defining the direction of the project. Description: Complete blueprint of the site's structure in terms of organisation of categories, subcategories and sorting of articles in each one of them. It also includes the essential pages. The sorted articles target main keyword, relevant entities and similar keywords. This has to be highly data driven and we look at over 100 variables just to get it right. It's like beating Google's algorithm to ensure you have a blueprint for a site that will rank. It needs to be done right. If there is a mistake, then even if you do everything right - it's not going to work out and after 8-16 months you will realise that everything went to waste. Process For this project, we had a niche selected already so we didn't need to do a lot of research pertaining to that. We also knew the topic since the website was already getting good traffic on that. We just validated from Ahrefs, SEMRUSH and manual analysis if it would be worth it to move forward with that topic. &#x200B; Find entities related to the topic: We used Ahrefs and InLinks to get an idea about the related entities (topics) to create a proper topical relevance. In order to be certain and have a better idea, we used ChatGPT to find relevant entities as well \> Ahrefs (tool): Enter main keyword in keywords explorer. Check the left pain for popular topics \> Inlinks (tool): Enter the main keyword, check the entity maps \> ChatGPT (tool): Ask it to list down the most important and relevant entities in order of their priority Based on this info, you can map out the most relevant topics that are semantically associated to your main topic Sorting the entities in topics (categories) and subtopics (subcategories): Based on the information above, cluster them properly. The most relevant ones must be grouped together. Each group must be sorted into its relevant category. \> Example: Site about cycling. \> Categories/entities: bicycles, gear and equipment, techniques, safety, routes etc. \> The subcategories/subentities for let's say "techniques" would be: Bike handling, pedaling, drafting etc. Extract keywords for each subcategory/subentity: You can do this using Ahrefs or Semrush. Each keyword would be an article. Ensure that you target the similar keywords in one article. For example: how to ride a bicycle and how can I ride a bicycle will be targeted by one article. Make the more important keyword in terms of volume and difficulty as the main keyword and the other one(s) as secondary Define main focus vs secondary focus: Out of all these categories/entities - there will be one that you would want to dominate in every way. So, focus on just that in the start. This will be your main focus. Try to answer ALL the questions pertaining to that. You can extract the questions using Ahrefs. \> Ahrefs > keywords explorer \> enter keyword \> Questions \> Download the list and cluster the similar ones. This will populate your main focus category/entity and will drive most of the traffic. Now, you need to write in other categories/subentities as well. This is not just important, but crucial to complete the topical map loop. In simple words, if you do this Google sees you as a comprehensive source on the topic - otherwise, it ignores you and you don't get ranked Define the URLs End result: List of all the entities and sub-entities about the main site topic in the form of categories and subcategories respectively. A complete list of ALL the questions about the main focus and at around 10 questions for each one of the subcategories/subentities that are the secondary focus Content Writing So, now that there's a plan. Content needs to be produced. Pick out a keyword (which is going to be a question) and... Answer the question Write about 5 relevant entities Answer 10 relevant questions Write a conclusion Keep the format the same for all the articles. Content Uploading, formatting and onsite SEO Ensure the following is taken care of: H1 Permalink H2s H3s Lists Tables Meta description Socials description Featured image 2 images in text \\Schema Relevant YouTube video (if there is) Note: There are other pointers link internal linking in a semantically relevant way but this should be good to start with. Faster Indexing Indexing means Google has read your page. Ranking only after this step has been done. Otherwise, you can't rank if Google hasn't read the page. Naturally, this is a slow process. But, we expedite it in multiple ways. You can use RankMath to quickly index the content. Since, there are a lot of bulk pages you need a reliable method. Now, this method isn't perfect. But, it's better than most. Use Google Indexing API and developers tools to get indexed. Rank Math plugin is used. I don't want to bore you and write the process here. But, a simple Google search can help you set everything up. Additionally, whenever you post something - there will be an option to INDEX NOW. Just press that and it would be indexed quite fast. Conversion rate optimisation Once you get traffic, try adding tables right after the introduction of an article. These tables would feature a relevant product on Amazon. This step alone increased our earnings significantly. Even though the content is informational and NOT review. This still worked like a charm. Try checking out the top pages every single day in Google analytics and add the table to each one of them. Moreover, we used EZOIC video ads as well. That increased the RPM significantly as well. Both of these steps are highly recommended. Overall, we implemented over 11 fixations but these two contribute the most towards increasing the RPM so I would suggest you stick to these two in the start. Guest Posting We made additional income by selling links on the site as well. However, we were VERY careful about who we offered a backlink to. We didn't entertain any objectionable links. Moreover, we didn't actively reach out to anyone. We had a professional email clearly stated on the website and a particularly designated page for "editorial guidelines" A lot of people reached out to us because of that. As a matter of fact, the guy who bought the website is in the link selling business and plans to use the site primarily for selling links. According to him, he can easily make $4000+ from that alone. Just by replying to the prospects who reached out to us. We didn't allow a lot of people to be published on the site due to strict quality control. However, the new owner is willing to be lenient and cash it out. EEAT (Experience, Expertise, Authority, Trust) This is an important ranking factor. You need to prove on the site that your site has authors that are experienced, have expertise, authority and trust. A lot of people were reaching out to publish on our site and among them were a few established authors as well. We let them publish on our site for free, added them on our official team, connected their socials and shared them on all our socials. In return, we wanted them to write 3 articles each for us and share everything on all the social profiles. You can refer to the tables I shared above to check out the months it was implemented. We added a total of 6 writers (credible authors). Their articles were featured on the homepage and so were their profiles. Costing Well, we already had the site and the backlinks on it. Referring domains (backlinks) were already 500+. We just needed to focus on smart content and content. Here is the summary of the costs involved. Articles: 490 Avg word count per article: 1500 Total words: 735,000 (approximately) Cost per word: 2 cents (includes research, entities, production, quality assurance, uploading, formatting, adding images, featured image, alt texts, onsite SEO, publishing/scheduling etc.) Total: $14,700 ROI (Return on investment) Earning: Oct 22 - June 23 Earnings: $10,199 Sold for: $59,000 Total: $69,199 Expenses: Content: $14,700 Misc (hosting and others): $500 Total: $15,200 ROI over a 9 months period: 355.25% The plans moving forward This website was a part of a research and development experiment we did. With AI, we wanted to test new waters and transition more towards automation. Ideally, we want to use ChatGPT or some other API to produce these articles and bulk publish on the site. The costs with this approach are going to be much lower and the ROI is much more impressive. It's not the the 7-figures projects I created earlier (as you may have checked the older case studies on my profile), but it's highly scalable. We plan to refine this model even further, test more and automate everything completely to bring down our costs significantly. Once we have a model, we are going to scale it to 100s of sites. The process of my existing 7-figures websites portfolio was quite similar. I tested out a few sites, refined the model and scaled it to over 41 sites. Now, the fundamentals are the same however, we are using AI in a smarter way to do the same but at a lower cost, with a smaller team and much better returns. The best thing in my opinion is to run numerous experiments now. Our experimentation was slowed down a lot in the past since we couldn't write using AI but now it's much faster. The costs are 3-6 times lower so when it used to take $50-100k to start, grow and sell a site. Now you can pump 3-6 more sites for the same budget. This is a good news for existing business owners as well who want to grow their brand. Anyway, I am excited to see the results of more sites. In the meantime, if you have any questions - feel free to let me know. Best of luck for everything. Feel free to ask questions. I'd be happy to help. This is an AMA.

How To Learn About AI Agents (A Road Map From Someone Who's Done It)
reddit
LLM Vibe Score0
Human Vibe Score0.882
laddermanUSThis week

How To Learn About AI Agents (A Road Map From Someone Who's Done It)

If you are a newb to AI Agents, welcome, I love newbies and this fledgling industry needs you! You've hear all about AI Agents and you want some of that action right?  You might even feel like this is a watershed moment in tech, remember how it felt when the internet became 'a thing'?  When apps were all the rage?  You missed that boat right?   Well you may have missed that boat, but I can promise you one thing..... THIS BOAT IS BIGGER !  So if you are reading this you are getting in just at the right time.  Let me answer some quick questions before we go much further: Q: Am I too late already to learn about AI agents? A: Heck no, you are literally getting in at the beginning, call yourself and 'early adopter' and pin a badge on your chest! Q: Don't I need a degree or a college education to learn this stuff?  I can only just about work out how my smart TV works! A: NO you do not.  Of course if you have a degree in a computer science area then it does help because you have covered all of the fundamentals in depth... However 100000% you do not need a degree or college education to learn AI Agents.  Q: Where the heck do I even start though?  Its like sooooooo confusing A: You start right here my friend, and yeh I know its confusing, but chill, im going to try and guide you as best i can. Q: Wait i can't code, I can barely write my name, can I still do this? A: The simple answer is YES you can. However it is great to learn some basics of python.  I say his because there are some fabulous nocode tools like n8n that allow you to build agents without having to learn how to code...... Having said that, at the very least understanding the basics is highly preferable. That being said, if you can't be bothered or are totally freaked about by looking at some code, the simple answer is YES YOU CAN DO THIS. Q: I got like no money, can I still learn? A: YES 100% absolutely.  There are free options to learn about AI agents and there are paid options to fast track you.  But defiantly you do not need to spend crap loads of cash on learning this.  So who am I anyway? (lets get some context)  I am an AI Engineer and I own and run my own AI Consultancy business where I design, build and deploy AI agents and AI automations.  I do also run a small academy where I teach this stuff, but I am not self promoting or posting links in this post because im not spamming this group.  If you want links send me a DM or something and I can forward them to you.  Alright so on to the good stuff, you're a newb, you've already read a 100 posts and are now totally confused and every day you consume about 26 hours of youtube videos on AI agents.....I get you, we've all been there.  So here is my 'Worth Its Weight In Gold' road map on what to do: \[1\]  First of all you need learn some fundamental concepts.  Whilst you can defiantly jump right in start building, I strongly recommend you learn some of the basics.  Like HOW to LLMs work, what is a system prompt, what is long term memory, what is Python, who the heck is this guy named Json that everyone goes on about?  Google is your old friend who used to know everything, but you've also got your new buddy who can help you if you want to learn for FREE.  Chat GPT is an awesome resource to create your own mini learning courses to understand the basics. Start with a prompt such as: "I want to learn about AI agents but this dude on reddit said I need to know the fundamentals to this ai tech, write for me a short course on Json so I can learn all about it. Im a beginner so keep the content easy for me to understand. I want to also learn some code so give me code samples and explain it like a 10 year old" If you want some actual structured course material on the fundamentals, like what the Terminal is and how to use it, and how LLMs work, just hit me, Im not going to spam this post with a hundred links. \[2\] Alright so let's assume you got some of the fundamentals down.  Now what? Well now you really have 2 options.  You either start to pick up some proper learning content (short courses) to deep dive further and really learn about agents or you can skip that sh\*t and start building!  Honestly my advice is to seek out some short courses on agents, Hugging Face have an awesome free course on agents and DeepLearningAI also have numerous free courses. Both are really excellent places to start.  If you want a proper list of these with links, let me know.  If you want to jump in because you already know it all, then learn the n8n platform!   And no im not a share holder and n8n are not paying me to say this.  I can code, im an AI Engineer and I use n8n sometimes.   N8N is a nocode platform that gives you a drag and drop interface to build automations and agents.  Its very versatile and you can self host it.  Its also reasonably easy to actually deploy a workflow in the cloud so it can be used by an actual paying customer.  Please understand that i literally get hate mail from devs and experienced AI enthusiasts for recommending no code platforms like n8n.  So im risking my mental wellbeing for you!!!    \[3\] Keep building!   ((WTF THAT'S IT?????))  Yep. the more you build the more you will learn.  Learn by doing my young Jedi learner.  I would call myself pretty experienced in building AI Agents, and I only know a tiny proportion of this tech.  But I learn but building projects and writing about AI Agents.  The more you build the more you will learn.  There are more intermediate courses you can take at this point as well if you really want to deep dive (I was forced to - send help) and I would recommend you do if you like short courses because if you want to do well then you do need to understand not just the underlying tech but also more advanced concepts like Vector Databases and how to implement long term memory.  Where to next? Well if you want to get some recommended links just DM me or leave a comment and I will DM you, as i said im not writing this with the intention of spamming the crap out of the group. So its up to you.  Im also happy to chew the fat if you wanna chat, so hit me up.  I can't always reply immediately because im in a weird time zone, but I promise I will reply if you have any questions. THE LAST WORD (Warning - Im going to motivate the crap out of you now) Please listen to me:  YOU CAN DO THIS.  I don't care what background you have, what education you have, what language you speak or what country you are from..... I believe in you and anyway can do this.  All you need is determination, some motivation to want to learn and a computer (last one is essential really, the other 2 are optional!) But seriously you can do it and its totally worth it.  You are getting in right at the beginning of the gold rush, and yeh I believe that.   AI Agents are going to be HUGE. I believe this will be the new internet gold rush.

101 best SEO tips to help you drive traffic in 2k21
reddit
LLM Vibe Score0
Human Vibe Score0.543
DrJigsawThis week

101 best SEO tips to help you drive traffic in 2k21

Hey guys! I don't have to tell you how SEO can be good for your business - you can drive leads to your SaaS on autopilot, drive traffic to your store/gym/bar/whatever, etc. The thing with SEO, though, is that most SEO tips on the internet are just not that good. Most of the said tips: Are way too simple & basic (“add meta descriptions to your images”*) Are not impactful. Sure, adding that meta tag to an image is important, but that’s not what’s going to drive traffic to your website Don’t talk much about SEO strategy (which is ultimately the most important thing for SEO). Sure, on-page SEO is great, but you sure as hell won't drive much traffic if you can't hire the right writers to scale your content. And to drive serious SEO traffic, you'll need a LOT more than that. Over the past few years, my and my co-founder have helped grow websites to over 200k+ monthly traffic (check out our older Reddit post if you want to learn more about us, our process, and what we do), and we compiled all our most important SEO tips and tricks, as well as case studies, research, and experiments from the web, into this article. Hope you like it ;) If you think we missed something super important, let us know and we'll add it to the list. And btw, we also published this article on our own blog with images, smart filters, and all that good stuff. If you want to check it out, click here. That said, grab some coffee (or beer) & let's dive in - this is going to be a long one. SEO Strategy Tips Tip #1. A Lot of SEO Tips On The Internet Are NOT Necessarily Factual A lot of the SEO content you’ll read on the internet will be based on personal experiences and hearsay. Unfortunately, Google is a bit vague about SEO advice, so you have to rely more on experiments conducted by SEO pros in the community. So, sometimes, a lot of this information is questionable, wrong, or simply based on inaccurate data.  What we’re getting at here is, whenever you hear some new SEO advice, take it with a grain of salt. Google it to double-check other sources, and really understand what this SEO advice is based on (instead of just taking it at face value). Tip #2. SEO Takes Time - Get Used to It Any way you spin it, SEO takes time.  It can take around 6 months to 2 years (depending on the competition in your niche) before you start seeing some serious results.  So, don’t get disappointed if you don’t see any results within 3 months of publishing content. Tip #3. SEO Isn’t The Best Channel for Everyone That said, if you need results for your business tomorrow, you might want to reconsider SEO altogether.  If you just started your business, for example, and are trying to get to break-even ASAP, SEO is a bad idea - you’ll quit before you even start seeing any results.  If that’s the case, focus on other marketing channels that can have faster results like content marketing, PPC, outreach, etc. Tip #4. Use PPC to Validate Keywords Not sure if SEO is right for your business? Do this: set up Google Search ads for the most high-intent keywords in your niche. See how well the traffic converts and then decide if it’s worthwhile to focus on SEO (and rank on these keywords organically). Tip #5. Use GSC to See If SEO Is Working While it takes a while to see SEO results, it IS possible to see if you’re going in the right direction. On a monthly basis, you can use Search Console to check if your articles are indexed by Google and if their average position is improving over time. Tip #6. Publish a TON of Content The more content you publish on your blog, the better. We recommend a minimum of 10,000 words per month and optimally 20,000 - 30,000 (especially if your website is fresh). If an agency offers you the typical “4 500-word articles per month” deal, stay away. No one’s ever gotten results in SEO with short, once-per-week articles. Tip #7. Upgrade Your Writers Got a writer that’s performing well? Hire them as an editor and get them to oversee content operations / edit other writers’ content. Then, upgrade your best editor to Head of Content and get them to manage the entire editor / writer ops. Tip #8. Use Backlink Data to Prioritize Content When doing keyword research, gather the backlink data of the top 3 ranking articles and add it to your sheet. Then, use this data to help you prioritize which keywords to focus on first. We usually prioritize keywords that have lower competition, high traffic, and a medium to high buyer intent. Tip #9. Conduct In-Depth Keyword Research Make your initial keyword research as comprehensive as possible. This will give you a much more realistic view of your niche and allow you to prioritize content the right way. We usually aim for 100 to 300 keywords (depending on the niche) for the initial keyword research when we start working with a client. Tip #10. Start With Competitive Analysis Start every keyword research with competitive analysis. Extract the keywords your top 3 competitors are ranking on.  Then, use them as inspiration and build upon it. Use tools like UberSuggest to help generate new keyword ideas. Tip #11. Get SEMrush of Ahrefs You NEED SEMrush or Ahrefs, there’s no doubt about it. While they might seem expensive at a glance (99 USD per month billed annually), they’re going to save you a lot of manpower doing menial SEO tasks. Tip #12. Don’t Overdo It With SEO Tools Don’t overdo it with SEO tools. There are hundreds of those out there, and if you’re the type that’s into SaaS, you might be tempted to play around with dozens at a time. And yes, to be fair, most of these tools ARE helpful one way or another. To effectively do organic SEO, though, you don’t really need that many tools. In most cases, you just need the following: SEMrush/Ahrefs Screaming Frog RankMath/Yoast SEO Whichever outreach tool you prefer (our favorite is snov.io). Tip #13. Try Some of the Optional Tools In addition to the tools we mentioned before, you can also try the following 2 which are pretty useful & popular in the SEO community: Surfer SEO - helps with on-page SEO and creating content briefs for writers. ClusterAI - tool that helps simplify keyword research & save time. Tip #14. Constantly Source Writers Want to take your content production to the next level? You’ll need to hire more writers.  There is, however, one thing that makes this really, really difficult: 95 - 99% of writers applying for your gigs won’t be relevant. Up to 80% will be awful at writing, and the remainder just won’t be relevant for your niche. So, in order to scale your writing team, we recommend sourcing constantly, and not just once every few months. Tip #15. Create a Process for Writer Filtering As we just mentioned, when sourcing writers, you’ll be getting a ton of applicants, but most won’t be qualified. Fun fact \- every single time we post a job ad on ProBlogger, we get around 300 - 500 applications (most of which are totally not relevant). Trust us, you don’t want to spend your time going through such a huge list and checking out the writer samples. So, instead, we recommend you do this: Hire a virtual assistant to own the process of evaluating and short-listing writers. Create a process for evaluating writers. We recommend evaluating writers by: Level of English. If their samples aren’t fluent, they’re not relevant. Quality of Samples. Are the samples engaging / long-form content, or are they boring 500-word copy-pastes? Technical Knowledge. Has the writer written about a hard-to-explain topic before? Anyone can write about simple topics like traveling - you want to look for someone who knows how to research a new topic and explain it in a simple and easy to read way. If someone’s written about how to create a perfect cover letter, they can probably write about traveling, but the opposite isn’t true. The VA constantly evaluates new applicants and forwards the relevant ones to the editor. The editor goes through the short-listed writers and gives them trial tasks and hires the ones that perform well. Tip #16. Use The Right Websites to Source Writers “Is UpWork any good?” This question pops up on social media time and time again. If you ask us, no, UpWork is not good at all. Of course, there are qualified writers there (just like anywhere else), but from our experience, those writers are few and far in-between. Instead, here are some of our favorite ways to source writers: Cult of Copy Job Board ProBlogger Headhunting on LinkedIn If you really want to use UpWork, use it for headhunting (instead of posting a job ad) Tip #17. Hire Writers the Right Way If you want to seriously scale your content production, hire your writers full-time. This (especially) makes sense if you’re a content marketing agency that creates a TON of content for clients all the time. If you’re doing SEO just for your own blog, though, it usually makes more sense to use freelancers. Tip #18. Topic Authority Matters Google keeps your website's authoritativeness in mind. Meaning, if you have 100 articles on digital marketing, you’re probably more of an authority on the topic than someone that has just 10. Hence, Google is a lot more likely to reward you with better rankings. This is also partially why content volume really matters: the more frequently you publish content, the sooner Google will view you as an authority. Tip #19. Focus on One Niche at a Time Let’s say your blog covers the following topics: sales, accounting, and business management.  You’re more likely to rank if you have 30 articles on a single topic (e.g. accounting) than if you have 10 articles on each. So, we recommend you double-down on one niche instead of spreading your content team thin with different topics. Tip #20. Don’t Fret on the Details While technical SEO is important, you shouldn’t get too hung up on it.  Sure, there are thousands of technical tips you can find on the internet, and most of them DO matter. The truth, though, is that Google won’t punish you just because your website doesn’t load in 3 milliseconds or there’s a meta description missing on a single page. Especially if you have SEO fundamentals done right: Get your website to run as fast as possible. Create a ton of good SEO content. Get backlinks for your website on a regular basis. You’ll still rank, even if your website isn’t 100% optimized. Tip #21. Do Yourself a Favor and Hire a VA There are a TON of boring SEO tasks that your team should really not be wasting time with. So, hire a full-time VA to help with all that. Some tasks you want to outsource include gathering contacts to reach out to for link-building, uploading articles on WordPress, etc. Tip #22. Google Isn’t Everything While Google IS the dominant search engine in most parts of the world, there ARE countries with other popular search engines.  If you want to improve your SEO in China, for example, you should be more concerned with ranking on Baidu. Targeting Russia? Focus on Yandex. Tip #23. No, Voice Search is Still Not Relevant Voice search is not and will not be relevant (no matter what sensationalist articles might say). It’s just too impractical for most search queries to use voice (as opposed to traditional search). Tip #24. SEO Is Not Dead SEO is not dead and will still be relevant decades down the line. Every year, there’s a sensationalist article talking about this.  Ignore those. Tip #25. Doing Local SEO? Focus on Service Pages If you’re doing local SEO, focus on creating service-based landing pages instead of content.  E.g. if you’re an accounting firm based in Boston, you can make a landing page about /accounting-firm-boston/, /tax-accounting-boston/, /cpa-boston/, and so on. Thing is, you don’t really need to rank on global search terms - you just won’t get leads from there. Even if you ranked on the term “financial accounting,” it wouldn’t really matter for your bottom line that much. Tip #26. Learn More on Local SEO Speaking of local SEO, we definitely don’t do the topic justice in this guide. There’s a lot more you need to know to do local SEO effectively and some of it goes against the general SEO advice we talk about in this article (e.g. you don't necessarily need blog content for local SEO). We're going to publish an article on that soon enough, so if you want to check it out, DM me and I'll hit you up when it's up. Tip #27. Avoid Vanity Metrics Don’t get side-tracked by vanity metrics.  At the end of the day, you should care about how your traffic impacts your bottom line. Fat graphs and lots of traffic are nice and all, but none of it matters if the traffic doesn’t have the right search intent to convert to your product/service. Tip #28. Struggling With SEO? Hire an Expert Failing to make SEO work for your business? When in doubt, hire an organic SEO consultant or an SEO agency.  The #1 benefit of hiring an SEO agency or consultant is that they’ve been there and done that - more than once. They might be able to catch issues an inexperienced SEO can’t. Tip #29. Engage With the Community Need a couple of SEO questions answered?  SEO pros are super helpful & easy to reach! Join these Facebook groups and ask your question - you’ll get about a dozen helpful answers! SEO Signals Lab SEO & Content Marketing The Proper SEO Group. Tip #30. Stay Up to Date With SEO Trends SEO is always changing - Google is constantly pumping out new updates that have a significant impact on how the game is played.  Make sure to stay up to date with the latest SEO trends and Google updates by following the Google Search Central blog. Tip #31. Increase Organic CTR With PPC Want to get the most out of your rankings? Run PPC ads for your best keywords. Googlers who first see your ad are more likely to click your organic listing. Content & On-Page SEO Tips Tip #32. Create 50% Longer Content On average, we recommend you create an article that’s around 50% longer than the best article ranking on the keyword.  One small exception, though, is if you’re in a super competitive niche and all top-ranking articles are already as comprehensive as they can be. For example, in the VPN niche, all articles ranking for the keyword “best VPN” are around 10,000 - 11,000 words long. And that’s the optimal word count - even if you go beyond, you won’t be able to deliver that much value for the reader to make it worth the effort of creating the content. Tip #33. Longer Is Not Always Better Sometimes, a short-form article can get the job done much better.  For example, let’s say you’re targeting the keyword “how to tie a tie.”  The reader expects a short and simple guide, something under 500 words, and not “The Ultimate Guide to Tie Tying for 2021 \[11 Best Tips and Tricks\]” Tip #34. SEO is Not Just About Written Content Written content is not always best. Sometimes, videos can perform significantly better. E.g. If the Googler is looking to learn how to get a deadlift form right, they’re most likely going to be looking for a video. Tip #35. Don’t Forget to Follow Basic Optimization Tips For all your web pages (articles included), follow basic SEO optimization tips. E.g. include the keyword in the URL, use the right headings etc.  Just use RankMath or YoastSEO for this and you’re in the clear! Tip #36. Hire Specialized Writers When hiring content writers, try to look for ones that specialize in creating SEO content.  There are a LOT of writers on the internet, plenty of which are really good.  However, if they haven’t written SEO content before, chances are, they won’t do that good of a job. Tip #37. Use Content Outlines Speaking of writers - when working with writers, create a content outline that summarizes what the article should be about and what kind of topics it needs to cover instead of giving them a keyword and asking them to “knock themselves out.”   This makes it a lot more likely for the writer to create something that ranks. When creating content outlines, we recommend you include the following information: Target keyword Related keywords that should be mentioned in the article Article structure - which headings should the writer use? In what order? Article title Tip #38. Find Writers With Niche Knowledge Try to find a SEO content writer with some experience or past knowledge about your niche. Otherwise, they’re going to take around a month or two to become an expert. Alternatively, if you’re having difficulty finding a writer with niche knowledge, try to find someone with experience in technical or hard to explain topics. Writers who’ve written about cybersecurity in the past, for example, are a lot more likely to successfully cover other complicated topics (as opposed to, for example, a food or travel blogger). Tip #39. Keep Your Audience’s Knowledge in Mind When creating SEO content, always keep your audience’s knowledge in mind. If you’re writing about advanced finance, for example, you don’t need to teach your reader what an income statement is. If you’re writing about income statements, on the other hand, you’d want to start from the very barebone basics. Tip #40. Write for Your Audience If your readers are suit-and-tie lawyers, they’re going to expect professionally written content. 20-something hipsters? You can get away with throwing a Rick and Morty reference here and there. Tip #41. Use Grammarly Trust us, it’ll seriously make your life easier! Keep in mind, though, that the app is not a replacement for a professional editor. Tip #42. Use Hemingway Online content should be very easy to read & follow for everyone, whether they’re a senior profession with a Ph.D. or a college kid looking to learn a new topic. As such, your content should be written in a simple manner - and that’s where Hemingway comes in. It helps you keep your blog content simple. Tip #43. Create Compelling Headlines Want to drive clicks to your articles? You’ll need compelling headlines. Compare the two headlines below; which one would you click? 101 Productivity Tips \[To Get Things Done in 2021\] VS Productivity Tips Guide Exactly! To create clickable headlines, we recommend you include the following elements: Keyword Numbers Results Year (If Relevant) Tip #44. Nail Your Blog Content Formatting Format your blog posts well and avoid overly long walls of text. There’s a reason Backlinko content is so popular - it’s extremely easy to read and follow. Tip #45. Use Relevant Images In Your SEO Content Key here - relevant. Don’t just spray random stock photos of “office people smiling” around your posts; no one likes those.  Instead, add graphs, charts, screenshots, quote blocks, CSS boxes, and other engaging elements. Tip #46. Implement the Skyscraper Technique (The Right Way) Want to implement Backlinko’s skyscraper technique?  Keep this in mind before you do: not all content is meant to be promoted.  Pick a topic that fits the following criteria if you want the internet to care: It’s on an important topic. “Mega-Guide to SaaS Marketing” is good, “top 5 benefits of SaaS marketing” is not. You’re creating something significantly better than the original material. The internet is filled with mediocre content - strive to do better. Tip #47. Get The URL Slug Right for Seasonal Content If you want to rank on a seasonal keyword with one piece of content (e.g. you want to rank on “saas trends 2020, 2021, etc.”), don’t mention the year in the URL slug - keep it /saas-trends/ and just change the headline every year instead.  If you want to rank with separate articles, on the other hand (e.g. you publish a new trends report every year), include the year in the URL. Tip #48. Avoid content cannibalization.  Meaning, don’t write 2+ articles on one topic. This will confuse Google on which article it should rank. Tip #49. Don’t Overdo Outbound Links Don’t include too many outbound links in your content. Yes, including sources is good, but there is such a thing as overdoing it.  If your 1,000 word article has 20 outbound links, Google might consider it as spam (even if all those links are relevant). Tip #50. Consider “People Also Ask” To get the most out of SERP, you want to grab as many spots on the search result as possible, and this includes “people also ask (PAA):” Make a list of the topic’s PAA questions and ensure that your article answers them.  If you can’t fit the questions & answers within the article, though, you can also add an FAQ section at the end where you directly pose these questions and provide the answers. Tip #51. Optimize For Google Snippet Optimize your content for the Google Snippet. Check what’s currently ranking as the snippet. Then, try to do something similar (or even better) in terms of content and formatting. Tip #52. Get Inspired by Viral Content Want to create content that gets insane shares & links?  Reverse-engineer what has worked in the past. Look up content in your niche that went viral on Reddit, Hacker News, Facebook groups, Buzzsumo, etc. and create something similar, but significantly better. Tip #53. Avoid AI Content Tools No, robots can’t write SEO content.  If you’ve seen any of those “AI generated content tools,” you should know to stay away. The only thing those tools are (currently) good for is creating news content. Tip #54. Avoid Bad Content You will never, ever, ever rank with one 500-word article per week.  There are some SEO agencies (even the more reputable ones) that offer this as part of their service. Trust us, this is a waste of time. Tip #55. Update Your Content Regularly Check your top-performing articles annually and see if there’s anything you can do to improve them.  When most companies finally get the #1 ranking for a keyword, they leave the article alone and never touch it again… ...Until they get outranked, of course, by someone who one-upped their original article. Want to prevent this from happening? Analyze your top-performing content once a year and improve it when possible. Tip #56. Experiment With CTR Do your articles have low CTR? Experiment with different headlines and see if you can improve it.  Keep in mind, though, that what a “good CTR” is really depends on the keyword.  In some cases, the first ranking will drive 50% of the traffic. In others, it’s going to be less than 15%. Link-Building Tips Tip #57. Yes, Links Matter. Here’s What You Need to Know “Do I need backlinks to rank?” is probably one of the most common SEO questions.  The answer to the question (alongside all other SEO-related questions) is that it depends on the niche.  If your competitors don’t have a lot of backlinks, chances are, you can rank solely by creating superior content. If you’re in an extremely competitive niche (e.g. VPN, insurance, etc.), though, everyone has amazing, quality content - that’s just the baseline.  What sets top-ranking content apart from the rest is backlinks. Tip #58. Sometimes, You’ll Have to Pay For Links Unfortunately, in some niches, paying for links is unavoidable - e.g. gambling, CBD, and others. In such cases, you either need a hefty link-building budget, or a very creative link-building campaign (create a viral infographic, news-worthy story based on interesting data, etc.). Tip #59. Build Relationships, Not Links The very best link-building is actually relationship building.  Make a list of websites in your niche and build a relationship with them - don’t just spam them with the standard “hey, I have this amazing article, can you link to it?”.  If you spam, you risk ruining your reputation (and this is going to make further outreach much harder). Tip #60. Stick With The Classics At the end of the day, the most effective link-building tactics are the most straightforward ones:  Direct Outreach Broken Link-Building Guest Posting Skyscraper Technique Creating Viral Content Guestposting With Infographics Tip #61. Give, Don’t Just Take! If you’re doing link-building outreach, don’t just ask for links - give something in return.  This will significantly improve the reply rate from your outreach email. If you own a SaaS tool, for example, you can offer the bloggers you’re reaching out to free access to your software. Or, alternatively, if you’re doing a lot of guest posting, you can offer the website owner a link from the guest post in exchange for the link to your website. Tip #62. Avoid Link Resellers That guy DMing you on LinkedIn, trying to sell you links from a Google Sheet?  Don’t fall for it - most of those links are PBNs and are likely to backfire on you. Tip #63. Avoid Fiverr Like The Plague Speaking of spammy links, don’t touch anything that’s sold on Fiverr - pretty much all of the links there are useless. Tip #64. Focus on Quality Links Not all links are created equal. A link is of higher quality if it’s linked from a page that: Is NOT a PBN. Doesn’t have a lot of outbound links. If the page links to 20 other websites, each of them gets less link juice. Has a lot of (quality) backlinks. Is part of a website with a high domain authority. Is about a topic relevant to the page it’s linking to. If your article about pets has a link from an accounting blog, Google will consider it a bit suspicious. Tip #65. Data-Backed Content Just Works Data-backed content can get insane results for link-building.  For example, OKCupid used to publish interesting data & research based on how people interacted with their platform and it never failed to go viral. Each of their reports ended up being covered by dozens of news media (which got them a ton of easy links). Tip #66. Be Creative - SEO Is Marketing, After All Be novel & creative with your link-building initiatives.  Here’s the thing: the very best link-builders are not going to write about the tactics they’re using.  If they did, you’d see half the internet using the exact same tactic as them in less than a week! Which, as you can guess, would make the tactic cliche and significantly less effective. In order to get superior results with your link-building, you’ll need to be creative - think about how you can make your outreach different from what everyone does. Experiment it, measure it, and improve it till it works! Tip #67. Try HARO HARO, or Help a Reporter Out, is a platform that matches journalists with sources. You get an email every day with journalists looking for experts in specific niches, and if you pitch them right, they might feature you in their article or link to your website. Tip #68. No-Follow Links Aren’t That Bad Contrary to what you might’ve heard, no-follow links are not useless. Google uses no-follow as more of a suggestion than anything else.  There have been case studies that prove Google can disregard the no-follow tag and still reward you with increased rankings. Tip #69. Start Fresh With an Expired Domain Starting a new website? It might make sense to buy an expired one with existing backlinks (that’s in a similar niche as yours). The right domain can give you a serious boost to how fast you can rank. Tip #70. Don’t Overspend on Useless Links “Rel=sponsored” links don’t pass pagerank and hence, won’t help increase your website rankings.  So, avoid buying links from media websites like Forbes, Entrepreneur, etc. Tip #71. Promote Your Content Other than link-building, focus on organic content promotion. For example, you can repost your content on Facebook groups, LinkedIn, Reddit, etc. and focus on driving traffic.  This will actually lead to you getting links, too. We got around 95 backlinks to our SEO case study article just because of our successful content promotion. Tons of people saw the article on the net, liked it, and linked to it from their website. Tip #72. Do Expert Roundups Want to build relationships with influencers in your niche, but don’t know where to start?  Create an expert roundup article. If you’re in the sales niche, for example, you can write about Top 21 Sales Influencers in 2021 and reach out to the said influencers letting them know that they got featured. Trust us, they’ll love you for this! Tip #73. .Edu Links are Overhyped .edu links are overrated. According to John Mueller, .edu domains tend to have a ton of outbound links, and as such, Google ignores a big chunk of them. Tip #74. Build Relationships With Your Customers Little-known link-building hack: if you’re a SaaS company doing SEO, you can build relationships with your customers (the ones that are in the same topical niche as you are) and help each other build links! Tip #75. Reciprocal Links Aren’t That Bad Reciprocal links are not nearly as bad as Google makes them out to be. Sure, they can be bad at scale (if trading links is all you’re doing). Exchanging a link or two with another website / blog, though, is completely harmless in 99% of cases. Tip #76. Don’t Overspam Don’t do outreach for every single post you publish - just the big ones.  Most people already don’t care about your outreach email. Chances are, they’re going to care even less if you’re asking them to link to this new amazing article you wrote (which is about the top 5 benefits of adopting a puppy). Technical SEO Tips Tip #77. Use PageSpeed Insights If your website is extremely slow, it’s definitely going to impact your rankings. Use PageSpeed Insights to see how your website is currently performing. Tip #78. Load Speed Matters While load speed doesn’t impact rankings directly, it DOES impact your user experience. Chances are, if your page takes 5 seconds to load, but your competition’s loads instantly, the average Googler will drop off and pick them over you. Tip #79. Stick to a Low Crawl Depth Crawl depth of any page on your website should be lower than 4 (meaning, any given page should be possible to reach in no more than 3 clicks from the homepage).  Tip #80. Use Next-Gen Image Formats Next-gen image formats such as JPEG 2000, JPEG XR, and WebP can be compressed a lot better than PNG or JPG. So, when possible, use next-get formats for images on your website. Tip #81. De-Index Irrelevant Pages Hide the pages you don’t want Google to index (e.g: non-public, or unimportant pages) via your Robots.txt. If you’re a SaaS, for example, this would include most of your in-app pages or your internal knowledge base pages. Tip #82. Make Your Website Mobile-Friendly Make sure that your website is mobile-friendly. Google uses “mobile-first indexing.” Meaning, unless you have a working mobile version of your website, your rankings will seriously suffer. Tip #83. Lazy-Load Images Lazy-load your images. If your pages contain a lot of images, you MUST activate lazy-loading. This allows images that are below the screen, to be loaded only once the visitor scrolls down enough to see the image. Tip #84. Enable Gzip Compression Enable Gzip compression to allow your HTML, CSS and JS files to load faster. Tip #85. Clean Up Your Code If your website loads slowly because you have 100+ external javascript files and stylesheets being requested from the server, you can try minifying, aggregating, and inlining some of those files. Tip 86. Use Rel-Canonical Have duplicate content on your website? Use rel-canonical to show Google which version is the original (and should be prioritized for search results). Tip #87. Install an SSL Certificate Not only does an SSL certificate help keep your website safe, but it’s also a direct ranking factor. Google prioritizes websites that have SSL certificates over the ones that don’t. Tip #88. Use Correct Anchor Texts for Internal Links When linking to an internal page, mention the keyword you’re trying to rank for on that page in the anchor text. This helps Google understand that the page is, indeed, about the keyword you’re associating it with. Tip #89. Use GSC to Make Sure Your Content is Interlinked Internal links can have a serious impact on your rankings. So, make sure that all your blog posts (especially the new ones) are properly linked to/from your past content.  You can check how many links any given page has via Google Search Console. Tip #90. Bounce rate is NOT a Google ranking factor. Meaning, you can still rank high-up even with a high bounce rate. Tip #91. Don’t Fret About a High Bounce Rate Speaking of the bounce rate, you’ll see that some of your web pages have a higher-than-average bounce rate (70%+).  While this can sometimes be a cause for alarm, it’s not necessarily so. Sometimes, the search intent behind a given keyword means that you WILL have a high bounce rate even if your article is the most amazing thing ever.  E.g. if it’s a recipe page, the reader gets the recipe and bounces off (since they don’t need anything else). Tip #92. Google Will Ignore Your Meta Description More often than not, Google won’t use the meta description you provide - that’s normal. It will, instead, automatically pick a part of the text that it thinks is most relevant and use it as a meta description. Despite this, you should always add a meta description to all pages. Tip #93. Disavow Spammy & PBN Links Keep track of your backlinks and disavow anything that’s obviously spammy or PBNy. In most cases, Google will ignore these links anyway. However, you never know when a competitor is deliberately targeting you with too many spammy or PBN links (which might put you at risk for being penalized). Tip #94. Use The Correct Redirect  When permanently migrating your pages, use 301 redirect to pass on the link juice from the old page to the new one. If the redirect is temporary, use a 302 redirect instead. Tip #95. When A/B Testing, Do This A/B testing two pages? Use rel-canonical to show Google which page is the original. Tip #96. Avoid Amp DON’T use Amp.  Unless you’re a media company, Amp will negatively impact your website. Tip #97. Get Your URL Slugs Right Keep your blog URLs short and to-the-point. Good Example: apollodigital.io/blog/seo-case-study Bad Example: apollodigital.io/blog/seo-case-study-2021-0-to-200,000/ Tip #98. Avoid Dates in URLs An outdated date in your URL can hurt your CTR. Readers are more likely to click / read articles published recently than the ones written years back. Tip #99. Social Signals Matter Social signals impact your Google rankings, just not in the way you think. No, your number of shares and likes does NOT impact your ranking at all.  However, if your article goes viral and people use Google to find your article, click it, and read it, then yes, it will impact your rankings.  E.g. you read our SaaS marketing guide on Facebook, then look up “SaaS marketing” on Google, click it, and read it from there. Tip #100. Audit Your Website Frequently Every other month, crawl your website with ScreamingFrog and see if you have any broken links, 404s, etc. Tip #101. Use WordPress Not sure which CMS platform to use?  99% of the time, you’re better off with WordPress.  It has a TON of plugins that will make your life easier.  Want a drag & drop builder? Use Elementor. Wix, SiteGround and similar drag & drops are bad for SEO. Tip #102. Check Rankings the Right Way When checking on how well a post is ranking on Google Search Console, make sure to check Page AND Query to get the accurate number.  If you check just the page, it’s going to give you the average ranking on all keywords the page is ranking for (which is almost always going to be useless data). Conclusion Aaand that's about it - thanks for the read! Now, let's circle back to Tip #1 for a sec. Remember when we said a big chunk of what you read on SEO is based on personal experiences, experiments, and the like? Well, the tips we've mentioned are part of OUR experience. Chances are, you've done something that might be different (or completely goes against) our advice in this article. If that's the case, we'd love it if you let us know down in the comments. If you mention something extra-spicy, we'll even include it in this article.

[CASE STUDY] From 217/m to $2,836/m in 9 months - Sold for $59,000; I grow and monetise web traffic of 5, 6, 7 figures USD valued passive income content sites [AMA]
reddit
LLM Vibe Score0
Human Vibe Score1
jamesackerman1234This week

[CASE STUDY] From 217/m to $2,836/m in 9 months - Sold for $59,000; I grow and monetise web traffic of 5, 6, 7 figures USD valued passive income content sites [AMA]

Hello Everyone (VERY LONG CASE STUDY AHEAD) - 355% return in 9 months Note: I own a 7-figures USD valued portfolio of 41+ content sites that generates 5-6 figures USD a month in passive income. This is my first time posting in this sub and my goal is to NOT share generic advice but precise numbers, data and highly refined processes so you can also get started with this business yourself or if you already have an existing business, drive huge traffic to it and scale it substantially (get more customers). I will use a case study to explain the whole process. As most of us are entrepreneurs here, explaining an actual project would be more meaningful. In this case study I used AI assisted content to grow an existing site from $217/m to $2,836/m in 9 months (NO BACKLINKS) and sold it for $59,000. ROI of 3 months: 355% Previous case studies (before I give an overview of the model) Amazon Affiliate Content Site: $371/m to $19,263/m in 14 MONTHS - $900K CASE STUDY \[AMA\] Affiliate Website from $267/m to $21,853/m in 19 months (CASE STUDY - Amazon?) \[AMA\] Amazon Affiliate Website from $0 to $7,786/month in 11 months Amazon Affiliate Site from $118/m to $3,103/m in 8 MONTHS (SOLD it for $62,000+) Note: You can check pinned posts on my profile. Do go through the comments as well as a lot of questions are answered in those. However, if you still have any questions, feel free to reach out. This is an \[AMA\]. Quick Overview of the Model Approach: High traffic, niche specific, informative content websites that monetise its traffic through highly automated methods like display ads and affiliate. The same model can be applied to existing businesses to drive traffic and get customers. Main idea: Make passive income in a highly automated way Easy to understand analogy You have real estate (here you have digital asset like a website) You get rental income (here you get ads and affiliate income with no physical hassle, in case you have a business like service, product etc. then you can get customers for that too but if not, it's alright) Real estate has value (this digital asset also has value that can be appreciated with less effort) Real estate can be sold (this can be sold too but faster) IMPORTANT NOTE: Search traffic is the BEST way to reach HUGE target audience and it's important when it comes to scaling. This essentially means that you can either monetise that via affiliate, display etc. or if you have a business then you can reach a bigger audience to scale. Overview of this website's valuation (then and now: Oct. 2022 and June 2023) Oct 2022: $217/m Valuation: $5,750.5 (26.5x) - set it the same as the multiple it was sold for June 2023: $2,836/m Traffic and revenue trend: growing fast Last 3 months avg: $2,223 Valuation now: $59,000 (26.5x) Description: The domain was registered in 2016, it grew and then the project was left unattended. I decided to grow it again using properly planned AI assisted content. Backlink profile: 500+ Referring domains (Ahrefs). Backlinks mean the sites linking back to you. This is important when it comes to ranking. Summary of Results of This Website - Before and After Note: If the terms seem technical, do not worry. I will explain them in detail later. Still if you have any questions. Feel free to comment or reach out. |Metric|Oct 2022|June 2023|Difference|Comments| |:-|:-|:-|:-|:-| |Articles|314|804|\+490|AI Assisted content published in 3 months| |Traffic|9,394|31,972|\+22,578|Organic| |Revenue|$217|$2,836|\+$2,619|Multiple sources| |RPM (revenue/1000 web traffic)|23.09|$88.7|\+$65.61|Result of Conversion rate optimisation (CRO). You make changes to the site for better conversions| |EEAT (expertise, experience, authority and trust of website)|2 main authors|8 authors|6|Tables, video ads and 11 other fixations| |CRO|Nothing|Tables, video ads |Tables, video ads and 11 other fixations || &#x200B; Month by Month Growth |Month|Revenue|Steps| |:-|:-|:-| |Sept 2022|NA|Content Plan| |Oct 2022|$217|Content Production| |Nov 2022|$243|Content production + EEAT authors| |Dec 2022|$320|Content production + EEAT authors| |Jan 2023|$400|Monitoring| |Feb 2023|$223|Content production + EEAT authors| |Mar 2023|$2,128|CRO & Fixations| |April 2023|$1,609|CRO & Fixations| |May 2023|$2,223|Content production + EEAT authors| |June 2023|$2,836|CRO and Fixations| |Total|$10,199|| &#x200B; What will I share Content plan and Website structure Content Writing Content Uploading, formatting and onsite SEO Faster indexing Conversion rate optimisation Guest Posting EEAT (Experience, Expertise, Authority, Trust) Costing ROI The plans moving forward with these sites &#x200B; Website Structure and Content Plan This is probably the most important important part of the whole process. The team spends around a month just to get this right. It's like defining the direction of the project. Description: Complete blueprint of the site's structure in terms of organisation of categories, subcategories and sorting of articles in each one of them. It also includes the essential pages. The sorted articles target main keyword, relevant entities and similar keywords. This has to be highly data driven and we look at over 100 variables just to get it right. It's like beating Google's algorithm to ensure you have a blueprint for a site that will rank. It needs to be done right. If there is a mistake, then even if you do everything right - it's not going to work out and after 8-16 months you will realise that everything went to waste. Process For this project, we had a niche selected already so we didn't need to do a lot of research pertaining to that. We also knew the topic since the website was already getting good traffic on that. We just validated from Ahrefs, SEMRUSH and manual analysis if it would be worth it to move forward with that topic. &#x200B; Find entities related to the topic: We used Ahrefs and InLinks to get an idea about the related entities (topics) to create a proper topical relevance. In order to be certain and have a better idea, we used ChatGPT to find relevant entities as well \> Ahrefs (tool): Enter main keyword in keywords explorer. Check the left pain for popular topics \> Inlinks (tool): Enter the main keyword, check the entity maps \> ChatGPT (tool): Ask it to list down the most important and relevant entities in order of their priority Based on this info, you can map out the most relevant topics that are semantically associated to your main topic Sorting the entities in topics (categories) and subtopics (subcategories): Based on the information above, cluster them properly. The most relevant ones must be grouped together. Each group must be sorted into its relevant category. \> Example: Site about cycling. \> Categories/entities: bicycles, gear and equipment, techniques, safety, routes etc. \> The subcategories/subentities for let's say "techniques" would be: Bike handling, pedaling, drafting etc. Extract keywords for each subcategory/subentity: You can do this using Ahrefs or Semrush. Each keyword would be an article. Ensure that you target the similar keywords in one article. For example: how to ride a bicycle and how can I ride a bicycle will be targeted by one article. Make the more important keyword in terms of volume and difficulty as the main keyword and the other one(s) as secondary Define main focus vs secondary focus: Out of all these categories/entities - there will be one that you would want to dominate in every way. So, focus on just that in the start. This will be your main focus. Try to answer ALL the questions pertaining to that. You can extract the questions using Ahrefs. \> Ahrefs > keywords explorer \> enter keyword \> Questions \> Download the list and cluster the similar ones. This will populate your main focus category/entity and will drive most of the traffic. Now, you need to write in other categories/subentities as well. This is not just important, but crucial to complete the topical map loop. In simple words, if you do this Google sees you as a comprehensive source on the topic - otherwise, it ignores you and you don't get ranked Define the URLs End result: List of all the entities and sub-entities about the main site topic in the form of categories and subcategories respectively. A complete list of ALL the questions about the main focus and at around 10 questions for each one of the subcategories/subentities that are the secondary focus Content Writing So, now that there's a plan. Content needs to be produced. Pick out a keyword (which is going to be a question) and... Answer the question Write about 5 relevant entities Answer 10 relevant questions Write a conclusion Keep the format the same for all the articles. Content Uploading, formatting and onsite SEO Ensure the following is taken care of: H1 Permalink H2s H3s Lists Tables Meta description Socials description Featured image 2 images in text \\Schema Relevant YouTube video (if there is) Note: There are other pointers link internal linking in a semantically relevant way but this should be good to start with. Faster Indexing Indexing means Google has read your page. Ranking only after this step has been done. Otherwise, you can't rank if Google hasn't read the page. Naturally, this is a slow process. But, we expedite it in multiple ways. You can use RankMath to quickly index the content. Since, there are a lot of bulk pages you need a reliable method. Now, this method isn't perfect. But, it's better than most. Use Google Indexing API and developers tools to get indexed. Rank Math plugin is used. I don't want to bore you and write the process here. But, a simple Google search can help you set everything up. Additionally, whenever you post something - there will be an option to INDEX NOW. Just press that and it would be indexed quite fast. Conversion rate optimisation Once you get traffic, try adding tables right after the introduction of an article. These tables would feature a relevant product on Amazon. This step alone increased our earnings significantly. Even though the content is informational and NOT review. This still worked like a charm. Try checking out the top pages every single day in Google analytics and add the table to each one of them. Moreover, we used EZOIC video ads as well. That increased the RPM significantly as well. Both of these steps are highly recommended. Overall, we implemented over 11 fixations but these two contribute the most towards increasing the RPM so I would suggest you stick to these two in the start. Guest Posting We made additional income by selling links on the site as well. However, we were VERY careful about who we offered a backlink to. We didn't entertain any objectionable links. Moreover, we didn't actively reach out to anyone. We had a professional email clearly stated on the website and a particularly designated page for "editorial guidelines" A lot of people reached out to us because of that. As a matter of fact, the guy who bought the website is in the link selling business and plans to use the site primarily for selling links. According to him, he can easily make $4000+ from that alone. Just by replying to the prospects who reached out to us. We didn't allow a lot of people to be published on the site due to strict quality control. However, the new owner is willing to be lenient and cash it out. EEAT (Experience, Expertise, Authority, Trust) This is an important ranking factor. You need to prove on the site that your site has authors that are experienced, have expertise, authority and trust. A lot of people were reaching out to publish on our site and among them were a few established authors as well. We let them publish on our site for free, added them on our official team, connected their socials and shared them on all our socials. In return, we wanted them to write 3 articles each for us and share everything on all the social profiles. You can refer to the tables I shared above to check out the months it was implemented. We added a total of 6 writers (credible authors). Their articles were featured on the homepage and so were their profiles. Costing Well, we already had the site and the backlinks on it. Referring domains (backlinks) were already 500+. We just needed to focus on smart content and content. Here is the summary of the costs involved. Articles: 490 Avg word count per article: 1500 Total words: 735,000 (approximately) Cost per word: 2 cents (includes research, entities, production, quality assurance, uploading, formatting, adding images, featured image, alt texts, onsite SEO, publishing/scheduling etc.) Total: $14,700 ROI (Return on investment) Earning: Oct 22 - June 23 Earnings: $10,199 Sold for: $59,000 Total: $69,199 Expenses: Content: $14,700 Misc (hosting and others): $500 Total: $15,200 ROI over a 9 months period: 355.25% The plans moving forward This website was a part of a research and development experiment we did. With AI, we wanted to test new waters and transition more towards automation. Ideally, we want to use ChatGPT or some other API to produce these articles and bulk publish on the site. The costs with this approach are going to be much lower and the ROI is much more impressive. It's not the the 7-figures projects I created earlier (as you may have checked the older case studies on my profile), but it's highly scalable. We plan to refine this model even further, test more and automate everything completely to bring down our costs significantly. Once we have a model, we are going to scale it to 100s of sites. The process of my existing 7-figures websites portfolio was quite similar. I tested out a few sites, refined the model and scaled it to over 41 sites. Now, the fundamentals are the same however, we are using AI in a smarter way to do the same but at a lower cost, with a smaller team and much better returns. The best thing in my opinion is to run numerous experiments now. Our experimentation was slowed down a lot in the past since we couldn't write using AI but now it's much faster. The costs are 3-6 times lower so when it used to take $50-100k to start, grow and sell a site. Now you can pump 3-6 more sites for the same budget. This is a good news for existing business owners as well who want to grow their brand. Anyway, I am excited to see the results of more sites. In the meantime, if you have any questions - feel free to let me know. Best of luck for everything. Feel free to ask questions. I'd be happy to help. This is an AMA.

I’m building a “DesignPickle” for all things Funnels. Would love your feedback...
reddit
LLM Vibe Score0
Human Vibe Score0.846
Gluteous_MaximusThis week

I’m building a “DesignPickle” for all things Funnels. Would love your feedback...

Hey Entrepreneurs, Early next year I’m rolling out a productized service business along the lines of Design Pickle, but instead of design assets, we create on-demand marketing assets: Things like landing pages, lead magnets, email campaigns, etc. This is NOT an agency with client engagements, etc.  It is an on-demand, menu-item style fulfillment platform where we do a few predefined things really, really well, and as much as possible try to reduce the complexity (and required customer inputs) so that creating your next killer Funnel is as easy as ordering dinner on Skip the Dishes. Below I’ve laid out our current thinking (we’re still distilling this into a deck), just so you have the full context.  And at the end, I pose 5 feedback questions. So if this “deck” seems interesting to you, then I’d love to get your feedback at the end 🙂 Thanks! And here goes... \--- The current elevator pitch:  We will research your business, your market and your competitors to develop a killer Lead Magnet, Landing Page, Ad Creatives and a 30-Day Email Drip campaign designed to turn your traffic into a rabid, lifelong buyer tribe (that you can email for years... like having your own, on-demand cash printer).  The overall thesis:  While AI is getting continually better at creating things like one-off graphics, article content, and so on - we do not think it can deeply understand market psychology, what keeps your customers up at night, or the underlying emotions that drive purchase decisions at the individual level, for your specific offer(s). Moreover, it’s also this psychological aspect of marketing where most businesses simply do not have the talent, resources or frankly the experience to create high-performing funnels themselves, regardless of how much "automation" they might have at their fingertips. And that’s because this is where you need to know who your customer really is, and what they’re actually buying (hint: not your features). Few marketers focus on these fundamentals, let alone understand the selling process. This is also why tools like ClickFunnels, HighLevel, LeadPages, etc. while very helpful, can only help with the logistics of selling. It’s still on each business to figure out how to actually tell their story, capture demand, and sell effectively. This is why a productized service that nails market research, competitor analysis & world-class copywriting that can actually turn cold traffic into lifelong customers is going to be a no-brainer for a business that’s currently struggling to actually get a steady flow of online sales. This is not something we see AI replacing effectively, any time soon. Current gaps & unknowns:  At a top level, I’m not overly worried about validation or viability; there are several existing competitors, and obviously the automation platforms have substantial customer bases (ClickFunnels etc). There will be a certain cohort that will want experts to do the actual thinking for them, storytelling, etc. Even if it’s a relatively small cohort, given the CLTV of a service like this, it still makes for a decent sized business. But where I’m less confident is in who our ideal customer actually is... Yes, basically every direct-response internet business needs an effective funnel that can sell. Whether you’re an Enterprise SaaS platform or a solopreneur launching your first $39 ebook, you will benefit from a killer funnel. As a “DesignPickle” type service though, here’s the challenges I see with each core customer category... B2B SaaS: While sales decisions are still emotional, it’s more about account-based considerations; people usually aren’t spending their own money, so it’s more about not looking stupid vs. gaining some benefit. Harder to systemize. Very high stakes. Consumer / SMB SaaS: While I think in general these are ideal customers, there will be resistance to leaning in hard on personality (and personal brand); founders usually want to sell at some point, so if they become the face of the platform, then boosting performance with a high-personality funnel might ironically make it a harder business to sell. SaaS founders are also generally very technical and stereotypically avoid marketing like the plague. Ecommerce: Most DTC brands think of funnels as an extension of their FB ad campaigns; few see their customers as a long-term audience that can become a significant asset. However, certain lifestyle / luxury brands might differ. Online Courses / Coaches: Of all the customer profiles, this group probably has the most appreciation for the effectiveness of marketing psychology, copywriting, etc. and would get the value prop quickly. The problem is that most won’t have the budget or traction to outsource asset creation. This is the “poorest” segment of the market. Service Businesses: Agencies, consultancies, and so on would greatly benefit from having a strong personal brand + storytelling premise (funnel). However, they’re also the worst offenders when it comes to never practicing what they preach / do for others. Client work soaks up all their resources. Local & Brick/Mortar: Generally speaking most local businesses are going to have smaller audiences (email lists under 2K subs), where funnel ops might have limited value long-term due to a lack of scale. And for larger B&M brands with franchises across various locations, you get into stakeholder friction; messaging usually gets watered down to basic corporate-speak as a result. Now, to be clear, I still see a ton of opportunity in each of those main customer categories as well, but I like to be clear-eyed about the overall resistance each niche will have - mainly because this helps to refine messaging to an ideal customer profile within them. In this case though, so far, nothing’s really jumping out at me as a clear “winner” at a category level. So far, what I’m thinking is our ICP might be situational / conditional. For example: A business has a funnel / is invested in the process, but it’s not working yet A business sees their competitor killing it with a funnel, and they’re ultra motivated to do it even better A business has one funnel that’s working awesome, and everything else they try sucks (so they can’t scale / expand) Etc. Basically, our most ideal customer might be ANY type of business who gets it, who’s tried to do this themselves, and now needs the pros to come in and fix things. \--- This is where your feedback would be incredibly valuable... First, if you’ve made it all the way down to this point - thanks for enduring my rambling mess above! But I did think the context might be helpful. Based on our overall biz plan & go-to-market considerations discussed above, if you run a business (or work with one) that might benefit from something like this, I’d love to ask a few questions... What is the nature of your business? (What do you sell)? What do you find hardest about selling to your online audience? Have you built a funnel in the past / are you running one currently? If not, what’s stopping you from building a high-performing funnel? If you had a “magic marketing lamp” where a genie could create ONE amazing marketing asset for you (eg. a killer landing page, video ad, launch strategy, etc), but you could only use it ONCE, what would you have the genie do for you? Please reply below as a comment, or DM me if you’d prefer to keep answers anonymous.  Thanks so much And again, apologies for the novel... Cheers

ChatGPT Full Course For 2025 | ChatGPT Tutorial For Beginnners | ChatGPT Course | Simplilearn
youtube
LLM Vibe Score0.369
Human Vibe Score0.26
SimplilearnMar 28, 2025

ChatGPT Full Course For 2025 | ChatGPT Tutorial For Beginnners | ChatGPT Course | Simplilearn

🔥Purdue - Applied Generative AI Specialization - https://www.simplilearn.com/applied-ai-course?utmcampaign=C4lBsBlloL0&utmmedium=Lives&utm_source=Youtube 🔥Professional Certificate Program in Generative AI and Machine Learning - IITG (India Only) - https://www.simplilearn.com/iitg-generative-ai-machine-learning-program?utmcampaign=C4lBsBlloL0&utmmedium=Lives&utm_source=Youtube 🔥Advanced Executive Program In Applied Generative AI - https://www.simplilearn.com/applied-generative-ai-course?utmcampaign=C4lBsBlloL0&utmmedium=Lives&utm_source=Youtube This ChatGPT Full Course 2025 by Simplilearn provides a comprehensive learning journey, starting with an introduction to ChatGPT and Generative AI, followed by insights into AI job opportunities and a comparison between ChatGPT 4.0 and 4.0 Turbo. The tutorial covers prompt engineering techniques, machine learning fundamentals, and running Llama models privately. Learners will explore ChatGPT-powered application development, its role in programming, and Excel automation. The course also dives into blogging, PowerPoint automation, customer support, and finance applications. Advanced topics like RAG vs. Prompt Tuning, prompt injection, and LangChain are included, along with discussions on OpenAI's latest innovations, including Sora and Strawberry. By the end, participants will gain a strong understanding of ChatGPT’s capabilities and monetization strategies. 🚀 Following are the topics covered in the ChatGPT Full Course 2025: 00:00:00 - Introduction to ChatGPT Full Course 2025 00:09:26 - What is ChatGPT 00:10:11 - What is Gen AI 00:26:29 - How to get Job in AI 00:27:06 - ChatGPT 40 vs ChatGPT 4 01:03:14 - Chatgpt analyse 02:13:57 - Prompt Engineering Tutorial 03:10:34 - What is Machine Learning 04:07:06 - Machine Learning Tutorial 04:08:13 - Run Lama Privately 04:23:50 - Search GPT 04:25:31 - Build App Using ChatGPT 06:31:11 - ChatGPT for Programming 06:46:08 - Prompt Formulae Chatgpt 07:58:38 - Automate Excel using Chatgpt 08:00:06 - Blogging with ChatGpt 08:27:25 - Powerpoint using Chatgpt 08:28:31 - Rag Vs Prompt Tuning 09:37:43 - Chatgpt for Customer Support 11:11:06 - ChatGPT for finance 11:17:38 - Prompt injection 11:18:38 - How to Earn Money using ChatGPT 11:41:46 - Open AI Strawberry 11:52:42 - Openai sora 11:54:57 - Langchain 12:22:19 - Open ai chatgpt o1 model ✅ Subscribe to our Channel to learn more about the top Technologies: https://bit.ly/2VT4WtH ⏩ Check out the Artificial Intelligence training videos: https://youtube.com/playlist?list=PLEiEAq2VkUULa5aOQmO_al2VVmhC-eqeI #gpt #chatgpt #chatgptforbeginners #chatgptcourse #genai #generativeai #artificialintelligence #ai #machinelearning #llm #simplilearn #2025 ➡️ About Professional Certificate Program in Generative AI and Machine Learning Dive into the future of AI with our Generative AI & Machine Learning course, in collaboration with E&ICT Academy, IIT Guwahati. Learn tools like ChatGPT, OpenAI, Hugging Face, Python, and more. Join masterclasses led by IITG faculty, engage in hands-on projects, and earn Executive Alumni Status. Key Features: ✅ Program completion certificate from E&ICT Academy, IIT Guwahati ✅ Curriculum delivered in live virtual classes by seasoned industry experts ✅ Exposure to the latest AI advancements, such as generative AI, LLMs, and prompt engineering ✅ Interactive live-virtual masterclasses delivered by esteemed IIT Guwahati faculty ✅ Opportunity to earn an 'Executive Alumni Status' from E&ICT Academy, IIT Guwahati ✅ Eligibility for a campus immersion program organized at IIT Guwahati ✅ Exclusive hackathons and “ask-me-anything” sessions by IBM ✅ Certificates for IBM courses and industry masterclasses by IBM experts ✅ Practical learning through 25+ hands-on projects and 3 industry-oriented capstone projects ✅ Access to a wide array of AI tools such as ChatGPT, Hugging Face, DALL-E 2, Midjourney and more ✅ Simplilearn's JobAssist helps you get noticed by top hiring companies Skills Covered: ✅ Generative AI ✅ Prompt Engineering ✅ Chatbot Development ✅ Supervised and Unsupervised Learning ✅ Model Training and Optimization ✅ Model Evaluation and Validation ✅ Ensemble Methods ✅ Deep Learning ✅ Natural Language Processing ✅ Computer Vision ✅ Reinforcement Learning ✅ Machine Learning Algorithms ✅ Speech Recognition ✅ Statistics Learning Path: ✅ Program Induction ✅ Programming Fundamentals ✅ Python for Data Science (IBM) ✅ Applied Data Science with Python ✅ Machine Learning ✅ Deep Learning with TensorFlow (IBM) ✅ Deep Learning Specialization ✅ Essentials of Generative AI, Prompt Engineering & ChatGPT ✅ Advanced Generative AI ✅ Capstone Electives: ✅ ADL & Computer Vision ✅ NLP and Speech Recognition ✅ Reinforcement Learning ✅ Academic Masterclass ✅ Industry Masterclass 👉 Learn More At: https://www.simplilearn.com/iitg-generative-ai-machine-learning-program?utmcampaign=C4lBsBlloL0&utmmedium=Lives&utm_source=Youtube

ARENA_2.0
github
LLM Vibe Score0.544
Human Vibe Score0.08491210825084358
callummcdougallMar 28, 2025

ARENA_2.0

This GitHub repo hosts the exercises and Streamlit pages for the ARENA 2.0 program. You can find a summary of each of the chapters below. For more detailed information (including the different ways you can access the exercises), click on the links in the chapter headings. Additionally, see this Notion page for a guide to the virtual study materials available. Chapter 0: Fundamentals The material on this page covers the first five days of the curriculum. It can be seen as a grounding in all the fundamentals necessary to complete the more advanced sections of this course (such as RL, transformers, mechanistic interpretability, and generative models). Some highlights from this chapter include: Building your own 1D and 2D convolution functions Building and loading weights into a Residual Neural Network, and finetuning it on a classification task Working with weights and biases to optimise hyperparameters Implementing your own backpropagation mechanism Chapter 1: Transformers & Mech Interp The material on this page covers the next 8 days of the curriculum. It will cover transformers (what they are, how they are trained, how they are used to generate output) as well as mechanistic interpretability (what it is, what are some of the most important results in the field so far, why it might be important for alignment). Some highlights from this chapter include: Building your own transformer from scratch, and using it to sample autoregressive output Using the TransformerLens library developed by Neel Nanda to locate induction heads in a 2-layer model Finding a circuit for indirect object identification in GPT-2 small Intepreting model trained on toy tasks, e.g. classification of bracket strings, or modular arithmetic Replicating Anthropic's results on superposition Unlike the first chapter (where all the material was compulsory), this chapter has 4 days of compulsory content and 4 days of bonus content. During the compulsory days you will build and train transformers, and get a basic understanding of mechanistic interpretability of transformer models which includes induction heads & use of TransformerLens. The next 4 days, you have the option to continue with whatever material interests you out of the remaining sets of exercises. There will also be bonus material if you want to leave the beaten track of exercises all together! Chapter 2: Reinforcement Learning Reinforcement learning is an important field of machine learning. It works by teaching agents to take actions in an environment to maximise their accumulated reward. In this chapter, you will be learning about some of the fundamentals of RL, and working with OpenAI’s Gym environment to run your own experiments. Some highlights from this chapter include: Building your own agent to play the multi-armed bandit problem, implementing methods from Sutton & Bardo Implementing a Deep Q-Network (DQN) and Proximal Policy Optimization (PPO) to play the CartPole game Applying RLHF to autoregressive transformers like the ones you built in the previous chapter Chapter 3: Training at Scale With the advent of large language models, training at scale has become a necessity to create highly competent models. In this chapter we will go through the basics of GPUs and distributed training, along with introductions to libraries that make training at scale easier. Some highlights from this chapter include: Quantizing your model to INT8 for blazing fast inference Implementing distributed training loops using torch.dist Getting hands on with Huggingface Accelerate and Microsoft DeepsSpeed

awesome-quantum-machine-learning
github
LLM Vibe Score0.64
Human Vibe Score1
krishnakumarsekarMar 27, 2025

awesome-quantum-machine-learning

Awesome Quantum Machine Learning A curated list of awesome quantum machine learning algorithms,study materials,libraries and software (by language). Table of Contents INTRODUCTION Why Quantum Machine Learning? BASICS What is Quantum Mechanics? What is Quantum Computing? What is Topological Quantum Computing? Quantum Computing vs Classical Computing QUANTUM COMPUTING Atom Structure Photon wave Electron Fluctuation or spin States SuperPosition SuperPosition specific for machine learning(Quantum Walks) Classical Bit Quantum Bit or Qubit or Qbit Basic Gates in Quantum Computing Quantum Diode Quantum Transistor Quantum Processor Quantum Registery QRAM Quantum Entanglement QUANTUM COMPUTING MACHINE LEARNING BRIDGE Complex Numbers Tensors Tensors Network Oracle Hadamard transform Hilbert Space eigenvalues and eigenvectors Schr¨odinger Operators Quantum lambda calculus Quantum Amplitute Phase Qubits Encode and Decode convert classical bit to qubit Quantum Dirac and Kets Quantum Complexity Arbitrary State Generation QUANTUM ALGORITHMS Quantum Fourier Transform Variational-Quantum-Eigensolver Grovers Algorithm Shor's algorithm Hamiltonian Oracle Model Bernstein-Vazirani Algorithm Simon’s Algorithm Deutsch-Jozsa Algorithm Gradient Descent Phase Estimation Haar Tansform Quantum Ridgelet Transform Quantum NP Problem QUANTUM MACHINE LEARNING ALGORITHMS Quantum K-Nearest Neighbour Quantum K-Means Quantum Fuzzy C-Means Quantum Support Vector Machine Quantum Genetic Algorithm Quantum Hidden Morkov Models Quantum state classification with Bayesian methods Quantum Ant Colony Optimization Quantum Cellular Automata Quantum Classification using Principle Component Analysis Quantum Inspired Evolutionary Algorithm Quantum Approximate Optimization Algorithm Quantum Elephant Herding Optimization Quantum-behaved Particle Swarm Optimization Quantum Annealing Expectation-Maximization QAUNTUM NEURAL NETWORK Quantum perceptrons Qurons Quantum Auto Encoder Quantum Annealing Photonic Implementation of Quantum Neural Network Quantum Feed Forward Neural Network Quantum Boltzman Neural Network Quantum Neural Net Weight Storage Quantum Upside Down Neural Net Quantum Hamiltonian Neural Net QANN QPN SAL Quantum Hamiltonian Learning Compressed Quantum Hamiltonian Learning QAUNTUM STATISTICAL DATA ANALYSIS Quantum Probability Theory Kolmogorovian Theory Quantum Measurement Problem Intuitionistic Logic Heyting Algebra Quantum Filtering Paradoxes Quantum Stochastic Process Double Negation Quantum Stochastic Calculus Hamiltonian Calculus Quantum Ito's Formula Quantum Stochastic Differential Equations(QSDE) Quantum Stochastic Integration Itō Integral Quasiprobability Distributions Quantum Wiener Processes Quantum Statistical Ensemble Quantum Density Operator or Density Matrix Gibbs Canonical Ensemble Quantum Mean Quantum Variance Envariance Polynomial Optimization Quadratic Unconstrained Binary Optimization Quantum Gradient Descent Quantum Based Newton's Method for Constrained Optimization Quantum Based Newton's Method for UnConstrained Optimization Quantum Ensemble Quantum Topology Quantum Topological Data Analysis Quantum Bayesian Hypothesis Quantum Statistical Decision Theory Quantum Minimax Theorem Quantum Hunt-Stein Theorem Quantum Locally Asymptotic Normality Quantum Ising Model Quantum Metropolis Sampling Quantum Monte Carlo Approximation Quantum Bootstrapping Quantum Bootstrap Aggregation Quantum Decision Tree Classifier Quantum Outlier Detection Cholesky-Decomposition for Quantum Chemistry Quantum Statistical Inference Asymptotic Quantum Statistical Inference Quantum Gaussian Mixture Modal Quantum t-design Quantum Central Limit Theorem Quantum Hypothesis Testing Quantum Chi-squared and Goodness of Fit Testing Quantum Estimation Theory Quantum Way of Linear Regression Asymptotic Properties of Quantum Outlier Detection in Quantum Concepts QAUNTUM ARTIFICIAL INTELLIGENCE Heuristic Quantum Mechanics Consistent Quantum Reasoning Quantum Reinforcement Learning QAUNTUM COMPUTER VISION QUANTUM PROGRAMMING LANGUAGES , TOOLs and SOFTWARES ALL QUANTUM ALGORITHMS SOURCE CODES , GITHUBS QUANTUM HOT TOPICS Quantum Cognition Quantum Camera Quantum Mathematics Quantum Information Processing Quantum Image Processing Quantum Cryptography Quantum Elastic Search Quantum DNA Computing Adiabetic Quantum Computing Topological Big Data Anlytics using Quantum Hamiltonian Time Based Quantum Computing Deep Quantum Learning Quantum Tunneling Quantum Entanglment Quantum Eigen Spectrum Quantum Dots Quantum elctro dynamics Quantum teleportation Quantum Supremacy Quantum Zeno Effect Quantum Cohomology Quantum Chromodynamics Quantum Darwinism Quantum Coherence Quantum Decoherence Topological Quantum Computing Topological Quantum Field Theory Quantum Knots Topological Entanglment Boson Sampling Quantum Convolutional Code Stabilizer Code Quantum Chaos Quantum Game Theory Quantum Channel Tensor Space Theory Quantum Leap Quantum Mechanics for Time Travel Quantum Secured Block Chain Quantum Internet Quantum Optical Network Quantum Interference Quantum Optical Network Quantum Operating System Electron Fractionalization Flip-Flop Quantum Computer Quantum Information with Gaussian States Quantum Anomaly Detection Distributed Secure Quantum Machine Learning Decentralized Quantum Machine Learning Artificial Agents for Quantum Designs Light Based Quantum Chips for AI Training QUANTUM STATE PREPARATION ALGORITHM FOR MACHINE LEARNING Pure Quantum State Product State Matrix Product State Greenberger–Horne–Zeilinger State W state AKLT model Majumdar–Ghosh Model Multistate Landau–Zener Models Projected entangled-pair States Infinite Projected entangled-pair States Corner Transfer Matrix Method Tensor-entanglement Renormalization Tree Tensor Network for Supervised Learning QUANTUM MACHINE LEARNING VS DEEP LEARNING QUANTUM MEETUPS QUANTUM GOOGLE GROUPS QUANTUM BASED COMPANIES QUANTUM LINKEDLIN QUANTUM BASED DEGREES CONSOLIDATED QUANTUM ML BOOKS CONSOLIDATED QUANTUM ML VIDEOS CONSOLIDATED QUANTUM ML Reserach Papers CONSOLIDATED QUANTUM ML Reserach Scientist RECENT QUANTUM UPDATES FORUM ,PAGES AND NEWSLETTER INTRODUCTION Why Quantum Machine Learning? Machine Learning(ML) is just a term in recent days but the work effort start from 18th century. What is Machine Learning ? , In Simple word the answer is making the computer or application to learn themselves . So its totally related with computing fields like computer science and IT ? ,The answer is not true . ML is a common platform which is mingled in all the aspects of the life from agriculture to mechanics . Computing is a key component to use ML easily and effectively . To be more clear ,Who is the mother of ML ?, As no option Mathematics is the mother of ML . The world tremendous invention complex numbers given birth to this field . Applying mathematics to the real life problem always gives a solution . From Neural Network to the complex DNA is running under some specific mathematical formulas and theorems. As computing technology growing faster and faster mathematics entered into this field and makes the solution via computing to the real world . In the computing technology timeline once a certain achievements reached peoples interested to use advanced mathematical ideas such as complex numbers ,eigen etc and its the kick start for the ML field such as Artificial Neural Network ,DNA Computing etc. Now the main question, why this field is getting boomed now a days ? , From the business perspective , 8-10 Years before during the kick start time for ML ,the big barrier is to merge mathematics into computing field . people knows well in computing has no idea on mathematics and research mathematician has no idea on what is computing . The education as well as the Job Opportunities is like that in that time . Even if a person tried to study both then the business value for making a product be not good. Then the top product companies like Google ,IBM ,Microsoft decided to form a team with mathematician ,a physician and a computer science person to come up with various ideas in this field . Success of this team made some wonderful products and they started by providing cloud services using this product . Now we are in this stage. So what's next ? , As mathematics reached the level of time travel concepts but the computing is still running under classical mechanics . the companies understood, the computing field must have a change from classical to quantum, and they started working on the big Quantum computing field, and the market named this field as Quantum Information Science .The kick start is from Google and IBM with the Quantum Computing processor (D-Wave) for making Quantum Neural Network .The field of Quantum Computer Science and Quantum Information Science will do a big change in AI in the next 10 years. Waiting to see that........... .(google, ibm). References D-Wave - Owner of a quantum processor Google - Quantum AI Lab IBM - Quantum Computer Lab Quora - Question Regarding future of quantum AI NASA - NASA Quantum Works Youtube - Google Video of a Quantum Processor external-link - MIT Review microsoft new product - Newly Launched Microsoft Quantum Language and Development Kit microsoft - Microsoft Quantum Related Works Google2 - Google Quantum Machine Learning Blog BBC - About Google Quantum Supremacy,IBM Quantum Computer and Microsoft Q Google Quantum Supremacy - Latest 2019 Google Quantum Supremacy Achievement IBM Quantum Supremacy - IBM Talk on Quantum Supremacy as a Primer VICE on the fight - IBM Message on Google Quantum Supremacy IBM Zurich Quantum Safe Cryptography - An interesting startup to replace all our Certificate Authority Via Cloud and IBM Q BASICS What is Quantum Mechanics? In a single line study of an electron moved out of the atom then its classical mechanic ,vibrates inside the atom its quantum mechanics WIKIPEDIA - Basic History and outline LIVESCIENCE. - A survey YOUTUBE - Simple Animation Video Explanining Great. What is Quantum Computing? A way of parallel execution of multiple processess in a same time using qubit ,It reduces the computation time and size of the processor probably in neuro size WIKIPEDIA - Basic History and outline WEBOPEDIA. - A survey YOUTUBE - Simple Animation Video Explanining Great. Quantum Computing vs Classical Computing LINK - Basic outline Quantum Computing Atom Structure one line : Electron Orbiting around the nucleous in an eliptical format YOUTUBE - A nice animation video about the basic atom structure Photon Wave one line : Light nornmally called as wave transmitted as photons as similar as atoms in solid particles YOUTUBE - A nice animation video about the basic photon 1 YOUTUBE - A nice animation video about the basic photon 2 Electron Fluctuation or spin one line : When a laser light collide with solid particles the electrons of the atom will get spin between the orbitary layers of the atom ) YOUTUBE - A nice animation video about the basic Electron Spin 1 YOUTUBE - A nice animation video about the basic Electron Spin 2 YOUTUBE - A nice animation video about the basic Electron Spin 3 States one line : Put a point on the spinning electron ,if the point is in the top then state 1 and its in bottom state 0 YOUTUBE - A nice animation video about the Quantum States SuperPosition two line : During the spin of the electron the point may be in the middle of upper and lower position, So an effective decision needs to take on the point location either 0 or 1 . Better option to analyse it along with other electrons using probability and is called superposition YOUTUBE - A nice animation video about the Quantum Superposition SuperPosition specific for machine learning(Quantum Walks) one line : As due to computational complexity ,quantum computing only consider superposition between limited electrons ,In case to merge more than one set quantum walk be the idea YOUTUBE - A nice video about the Quantum Walks Classical Bits one line : If electron moved from one one atom to other ,from ground state to excited state a bit value 1 is used else bit value 0 used Qubit one line : The superposition value of states of a set of electrons is Qubit YOUTUBE - A nice video about the Quantum Bits 1 YOUTUBE - A nice video about the Bits and Qubits 2 Basic Gates in Quantum Computing one line : As like NOT, OR and AND , Basic Gates like NOT, Hadamard gate , SWAP, Phase shift etc can be made with quantum gates YOUTUBE - A nice video about the Quantum Gates Quantum Diode one line : Quantum Diodes using a different idea from normal diode, A bunch of laser photons trigger the electron to spin and the quantum magnetic flux will capture the information YOUTUBE - A nice video about the Quantum Diode Quantum Transistors one line : A transistor default have Source ,drain and gate ,Here source is photon wave ,drain is flux and gate is classical to quantum bits QUORA -Discussion about the Quantum Transistor YOUTUBE - Well Explained Quantum Processor one line : A nano integration circuit performing the quantum gates operation sorrounded by cooling units to reduce the tremendous amount of heat YOUTUBE - Well Explained Quantum Registery QRAM one line : Comapring the normal ram ,its ultrafast and very small in size ,the address location can be access using qubits superposition value ,for a very large memory set coherent superposition(address of address) be used PDF - very Well Explained QUANTUM COMPUTING MACHINE LEARNING BRIDGE Complex Numbers one line : Normally Waves Interference is in n dimensional structure , to find a polynomial equation n order curves ,better option is complex number YOUTUBE - Wonderful Series very super Explained Tensors one line : Vectors have a direction in 2D vector space ,If on a n dimensional vector space ,vectors direction can be specify with the tensor ,The best solution to find the superposition of a n vector electrons spin space is representing vectors as tensors and doing tensor calculus YOUTUBE - Wonderful super Explained tensors basics YOUTUBE - Quantum tensors basics Tensors Network one line : As like connecting multiple vectors ,multple tensors form a network ,solving such a network reduce the complexity of processing qubits YOUTUBE - Tensors Network Some ideas specifically for quantum algorithms QUANTUM MACHINE LEARNING ALGORITHMS Quantum K-Nearest Neighbour info : Here the centroid(euclidean distance) can be detected using the swap gates test between two states of the qubit , As KNN is regerssive loss can be tally using the average PDF1 from Microsoft - Theory Explanation PDF2 - A Good Material to understand the basics Matlab - Yet to come soon Python - Yet to come soon Quantum K-Means info : Two Approaches possible ,1. FFT and iFFT to make an oracle and calculate the means of superposition 2. Adiobtic Hamiltonian generation and solve the hamiltonian to determine the cluster PDF1 - Applying Quantum Kmeans on Images in a nice way PDF2 - Theory PDF3 - Explaining well the K-means clustering using hamiltonian Matlab - Yet to come soon Python - Yet to come soon Quantum Fuzzy C-Means info : As similar to kmeans fcm also using the oracle dialect ,but instead of means,here oracle optimization followed by a rotation gate is giving a good result PDF1 - Theory Matlab - Yet to come soon Python - Yet to come soon Quantum Support Vector Machine info : A little different from above as here kernel preparation is via classical and the whole training be in oracles and oracle will do the classification, As SVM is linear ,An optimal Error(Optimum of the Least Squares Dual Formulation) Based regression is needed to improve the performance PDF1 - Nice Explanation but little hard to understand :) PDF2 - Nice Application of QSVM Matlab - Yet to come soon Python - Yet to come soon Quantum Genetic Algorithm info : One of the best algorithm suited for Quantum Field ,Here the chromosomes act as qubit vectors ,the crossover part carrying by an evaluation and the mutation part carrying by the rotation of gates ![Flow Chart]() PDF1 - Very Beautiful Article , well explained and superp PDF2 - A big theory :) PDF3 - Super Comparison Matlab - Simulation Python1 - Simulation Python2 - Yet to come Quantum Hidden Morkov Models info : As HMM is already state based ,Here the quantum states acts as normal for the markov chain and the shift between states is using quantum operation based on probability distribution ![Flow Chart]() PDF1 - Nice idea and explanation PDF2 - Nice but a different concept little Matlab - Yet to come Python1 - Yet to come Python2 - Yet to come Quantum state classification with Bayesian methods info : Quantum Bayesian Network having the same states concept using quantum states,But here the states classification to make the training data as reusable is based on the density of the states(Interference) ![Bayesian Network Sample1]() ![Bayesian Network Sample2]() ![Bayesian Network Sample3]() PDF1 - Good Theory PDF2 - Good Explanation Matlab - Yet to come Python1 - Yet to come Python2 - Yet to come Quantum Ant Colony Optimization info : A good algorithm to process multi dimensional equations, ACO is best suited for Sales man issue , QACO is best suited for Sales man in three or more dimension, Here the quantum rotation circuit is doing the peromene update and qubits based colony communicating all around the colony in complex space ![Ant Colony Optimization 1]() PDF1 - Good Concept PDF2 - Good Application Matlab - Yet to come Python1 - Yet to come Python2 - Yet to come Quantum Cellular Automata info : One of the very complex algorithm with various types specifically used for polynomial equations and to design the optimistic gates for a problem, Here the lattice is formed using the quatum states and time calculation is based on the change of the state between two qubits ,Best suited for nano electronics ![Quantum Cellular Automata]() Wikipedia - Basic PDF1 - Just to get the keywords PDF2 - Nice Explanation and an easily understandable application Matlab - Yet to come Python1 - Yet to come Python2 - Yet to come QAUNTUM NEURAL NETWORK one line : Its really one of the hardest topic , To understand easily ,Normal Neural Network is doing parallel procss ,QNN is doing parallel of parallel processess ,In theory combination of various activation functions is possible in QNN ,In Normal NN more than one activation function reduce the performance and increase the complexity Quantum perceptrons info : Perceptron(layer) is the basic unit in Neural Network ,The quantum version of perceptron must satisfy both linear and non linear problems , Quantum Concepts is combination of linear(calculus of superposition) and nonlinear(State approximation using probability) ,To make a perceptron in quantum world ,Transformation(activation function) of non linearity to certain limit is needed ,which is carrying by phase estimation algorithm ![Quantum Perceptron 3]() PDF1 - Good Theory PDF2 - Good Explanation Matlab - Yet to come Python1 - Yet to come Python2 - Yet to come QAUNTUM STATISTICAL DATA ANALYSIS one line : An under research concept ,It can be seen in multiple ways, one best way if you want to apply n derivative for a problem in current classical theory its difficult to compute as its serialization problem instead if you do parallelization of differentiation you must estimate via probability the value in all flows ,Quantum Probability Helps to achieve this ,as the loss calculation is very less . the other way comparatively booming is Quantum Bayesianism, its a solution to solve most of the uncertainity problem in statistics to combine time and space in highly advanced physical research QUANTUM PROGRAMMING LANGUAGES , TOOLs and SOFTWARES All info : All Programming languages ,softwares and tools in alphabetical order Software - Nice content of all Python library - A python library Matlab based python library - Matlab Python Library Quantum Tensor Network Github - Tensor Network Bayesforge - A Beautiful Amazon Web Service Enabled Framework for Quantum Alogorithms and Data Analytics Rigetti - A best tools repository to use quantum computer in real time Rigetti Forest - An API to connect Quantum Computer quil/pyQuil - A quantum instruction language to use forest framework Grove - Grove is a repository to showcase quantum Fourier transform, phase estimation, the quantum approximate optimization algorithm, and others developed using Forest QISKit - A IBM Kit to access quantum computer and mainly for quantum circuits IBM Bluemix Simulator - A Bluemix Simulator for Quantum Circuits Microsoft Quantum Development Kit - Microsoft Visual Studio Enbaled Kit for Quantum Circuit Creation Microsoft "Q#" - Microsoft Q Sharp a new Programming Language for Quantum Circuit Creation qiskit api python - An API to connect IBM Quantum Computer ,With the generated token its easy to connect ,but very limited utils ,Lot of new utils will come soon Cyclops Tensor Framework - A framework to do tensor network simulations Python ToolKit for chemistry and physics Quantum Algorithm simulations - A New Started Project for simulating molecule and solids Bayesian Based Quatum Projects Repository - A nice repository and the kickstarter of bayesforge Google Fermion Products - A newly launched product specifivally for chemistry simulation Tree Tensor Networks - Interesting Tensor Network in Incubator Deep Tensor Neural Network - Some useful information about Tensor Neural Network in Incubator Generative Tensorial Networks - A startup to apply machine learning via tensor network for drug discovery Google Bristlecone - A new Quantum Processor from Google , Aimed for Future Hardwares with full fledged AI support XANADU - A Light based Quantum Hardware(chips supports) and Software Company Started in Preparation Stage. Soon will be in market fathom computing - A new concept to train the ai in a processor using light and quantum based concepts. soon products will be launch Alibaba Quantum Computing Cloud Service - Cloud Service to access 11 Bit Quantum Computing Processor Atomistic Machine Learning Project - Seems something Interesting with Deep Tensor Network for Quantum Chemistry Applications circQ and Google Works - Google Top Efforts on Tools IBM Safe Cryptography on Cloud - IBM Started and Developing a Quantm Safe Cryptography to replace all our Certificate Authority via Cloud Google Tensor Network Open Source - Google Started the Most Scientist Preferred Way To Use a Quantum Computer Circuit. Tensor Flow Which Makes Easy to Design the Network and Will Leave the Work Effect Of Gates, Processor Preparation and also going to tell the beauty of Maths Google Tensor Network Github - Github Project of Google Tensor Network Quantum Tensorflow - Yet to come soon Quantum Spark - Yet to come soon Quatum Map Reduce - Yet to come soon Quantum Database - Yet to come soon Quantum Server - Yet to come soon Quantum Data Analytics - Yet to come soon QUANTUM HOT TOPICS Deep Quantum Learning why and what is deep learning? In one line , If you know deep learning you can get a good job :) ,Even a different platform undergraduated and graduated person done a master specialization in deep learning can work in this big sector :), Practically speaking machine learning (vector mathematics) , deep learning (vector space(Graphics) mathematics) and big data are the terms created by big companies to make a trend in the market ,but in science and research there is no word such that , Now a days if you ask a junior person working in this big companies ,what is deep learning ,you will get some reply as "doing linear regression with stochastic gradient for a unsupervised data using Convolutional Neural Network :)" ,They knows the words clearly and knows how to do programming using that on a bunch of "relative data" , If you ask them about the FCM , SVM and HMM etc algorithms ,they will simply say these are olden days algorithms , deep learning replaced all :), But actually they dont know from the birth to the till level and the effectiveness of algorithms and mathematics ,How many mathematical theorems in vector, spaces , tensors etc solved to find this "hiding the complexity technology", They did not played with real non relative data like medical images, astro images , geology images etc , finding a relation and features is really complex and looping over n number of images to do pattern matching is a giant work , Now a days the items mentioned as deep learning (= multiple hidden artifical neural network) is not suitable for that why quantum deep learning or deep quantum learning? In the mid of Artificial Neural Network Research people realised at the maximum extreme only certain mathematical operations possible to do with ANN and the aim of this ANN is to achieve parallel execution of many mathematical operations , In artificial Intelligence ,the world intelligence stands for mathematics ,how effective if a probem can be solvable is based on the mathematics logic applying on the problem , more the logic will give more performance(more intelligent), This goal open the gate for quantum artificial neural network, On applying the ideas behind the deep learning to quantum mechanics environment, its possible to apply complex mathematical equations to n number of non relational data to find more features and can improve the performance Quantum Machine Learning vs Deep Learning Its fun to discuss about this , In recent days most of the employees from Product Based Companies Like google,microsoft etc using the word deep learning ,What actually Deep Learning ? and is it a new inventions ? how to learn this ? Is it replacing machine learning ? these question come to the mind of junior research scholars and mid level employees The one answer to all questions is deep learning = parallel "for" loops ,No more than that ,Its an effective way of executing multiple tasks repeatly and to reduce the computation cost, But it introduce a big cap between mathematics and computerscience , How ? All classical algorithms based on serial processing ,Its depends on the feedback of the first loop ,On applying a serial classical algorithm in multiple clusters wont give a good result ,but some light weight parallel classical algorithms(Deep learning) doing the job in multiple clusters and its not suitable for complex problems, What is the solution for then? As in the title Quantum Machine Learning ,The advantage behind is deep learning is doing the batch processing simply on the data ,but quantum machine learning designed to do batch processing as per the algorithm The product companies realised this one and they started migrating to quantum machine learning and executing the classical algorithms on quantum concept gives better result than deep learning algorithms on classical computer and the target to merge both to give very wonderful result References Quora - Good Discussion Quora - The Bridge Discussion Pdf - Nice Discussion Google - Google Research Discussion Microsoft - Microsoft plan to merge both IBM - IBM plan to merge both IBM Project - IBM Project idea MIT and Google - Solutions for all questions QUANTUM MEETUPS Meetup 1 - Quantum Physics Meetup 2 - Quantum Computing London Meetup 3 - Quantum Computing New York Meetup 4 - Quantum Computing Canada Meetup 5 - Quantum Artificial Intelligence Texas Meetup 6 - Genarl Quantum Mechanics , Mathematics New York Meetup 7 - Quantum Computing Mountain View California Meetup 8 - Statistical Analysis New York Meetup 9 - Quantum Mechanics London UK Meetup 10 - Quantum Physics Sydney Australia Meetup 11 - Quantum Physics Berkeley CA Meetup 12 - Quantum Computing London UK Meetup 13 - Quantum Mechanics Carmichael CA Meetup 14 - Maths and Science Group Portland Meetup 15 - Quantum Physics Santa Monica, CA Meetup 16 - Quantum Mechanics London Meetup 17 - Quantum Computing London Meetup 18 - Quantum Meta Physics ,Kansas City , Missouri ,US Meetup 19 - Quantum Mechanics and Physics ,Boston ,Massachusetts ,US Meetup 20 - Quantum Physics and Mechanics ,San Francisco ,California Meetup 21 - Quantum Mechanics ,Langhorne, Pennsylvania Meetup 22 - Quantum Mechanics ,Portland QUANTUM BASED DEGREES Plenty of courses around the world and many Universities Launching it day by day ,Instead of covering only Quantum ML , Covering all Quantum Related topics gives more idea in the order below Available Courses Quantum Mechanics for Science and Engineers Online Standford university - Nice Preparatory Course edx - Quantum Mechanics for Everyone NPTEL 1 - Nice Series of Courses to understand basics and backbone of quantum mechanics NPTEL 2 NPTEL 3 NPTEL 4 NPTEL 5 Class Based Course UK Bristol Australia Australian National University Europe Maxs Planks University Quantum Physics Online MIT - Super Explanation and well basics NPTEL - Nice Series of Courses to understand basics and backbone of quantum Physics Class Based Course Europe University of Copenhagen Quantum Chemistry Online NPTEL 1 - Nice Series of Courses to understand basics and backbone of quantum Chemistry NPTEL 2 - Class Based Course Europe UGent Belgium Quantum Computing Online MIT - Super Explanation and well basics edx - Nice Explanation NPTEL - Nice Series of Courses to understand basics and backbone of quantum Computing Class Based Course Canada uwaterloo Singapore National University Singapore USA Berkley China Baidu Quantum Technology Class Based Course Canada uwaterloo Singapore National University Singapore Europe Munich Russia Skoltech Quantum Information Science External Links quantwiki Online MIT - Super Explanation and well basics edx - Nice Explanation NPTEL - Nice Series of Courses to understand basics and backbone of quantum information and computing Class Based Course USA MIT Standford University Joint Center for Quantum Information and Computer Science - University of Maryland Canada Perimeter Institute Singapore National University Singapore Europe ULB Belgium IQOQI Quantum Electronics Online MIT - Wonderful Course NPTEL - Nice Series of Courses to understand basics and backbone of quantum Electronics Class Based Course USA Texas Europe Zurich ICFO Asia Tata Institute Quantum Field Theory Online Standford university - Nice Preparatory Course edx - Some QFT Concepts available Class Based Course UK Imperial Europe Vrije Quantum Computer Science Class Based Course USA Oxford Joint Center for Quantum Information and Computer Science - University of Maryland Quantum Artificial Intelligence and Machine Learning External Links Quora 1 Quora 1 Artificial Agents Research for Quantum Designs Quantum Mathematics Class Based Course USA University of Notre CONSOLIDATED Quantum Research Papers scirate - Plenty of Quantum Research Papers Available Peter Wittek - Famous Researcher for the Quantum Machine Leanrning , Published a book in this topic [Murphy Yuezhen Niu] (https://scholar.google.com/citations?user=0wJPxfkAAAAJ&hl=en) - A good researcher published some nice articles Recent Quantum Updates forum ,pages and newsletter Quantum-Tech - A Beautiful Newsletter Page Publishing Amazing Links facebook Quantum Machine Learning - Running By me . Not that much good :). You can get some ideas Linkedlin Quantum Machine Learning - A nice page running by experts. Can get plenty of ideas FOSDEM 2019 Quantum Talks - A one day talk in fosdem 2019 with more than 10 research topics,tools and ideas FOSDEM 2020 Quantum Talks - Live talk in fosdem 2020 with plenty new research topics,tools and ideas License Dedicated Opensources ![Dedicated Opensources]() Source code of plenty of Algortihms in Image Processing , Data Mining ,etc in Matlab, Python ,Java and VC++ Scripts Good Explanations of Plenty of algorithms with flow chart etc Comparison Matrix of plenty of algorithms Is Quantum Machine Learning Will Reveal the Secret Maths behind Astrology? Awesome Machine Learning and Deep Learning Mathematics is online Published Basic Presentation of the series Quantum Machine Learning Contribution If you think this page might helpful. Please help for World Education Charity or kids who wants to learn

introduction-to-ai-orchestration-with-langchain-and-llamaindex-3820082
github
LLM Vibe Score0.43
Human Vibe Score0.050863657300783044
LinkedInLearningFeb 28, 2025

introduction-to-ai-orchestration-with-langchain-and-llamaindex-3820082

Introduction to AI Orchestration with LangChain and LlamaIndex This is the repository for the LinkedIn Learning course Introduction to AI Orchestration with LangChain and LlamaIndex. The full course is available from [LinkedIn Learning][lil-course-url]. ![lil-thumbnail-url] Are you ready to dive into the world of AI applications? This course was designed for you. AI orchestration frameworks let you step back from the details of artificial intelligence tools and APIs and instead focus on building more general, effective systems that solve real-world problems. Join instructor M.Joel Dubinko as he explores the business benefits of AI orchestration—faster development, smarter interfaces, lower costs, and more. This course provides an overview of AI fundamentals and key capabilities, like accessing external tools and databases, with a special focus on exploring local models running on your own hardware, alongside or instead of cloud services like those from OpenAI. Every step of the way, Joel offers hands-on demonstrations of two industry-leading frameworks: LangChain and LlamaIndex. By the end of this course, you’ll be prepared to start building chatbots, intelligent agents, and other useful tools, while monitoring for errors and troubleshooting as you go. Welcome to the course! AI is a fast-changing field, so be sure to check this repo for newer versions of the sample code. Installing Clone this repository into your local machine using the terminal (Mac), CMD (Windows), or a GUI tool like SourceTree. Ensure you have Python 3.10 or later (version 3.11 recommended) To prevent conflicts with other installed software on your computer, the author recommends setting up a virtual environment as follows: python3.11 -m venv .venv Activate the virtual environment with one of these commands: Install the necessary Python packages: (use the upgrade flag to ensure you have current versions) Specific projects in this course might have additional optional requirements. If so, it will be noted within the relevant video. Updates Recent versions of LM Studio have changed the UI from what's shown in the videos. These are generally welcome improvements. For example the maximum context length and other model parameters are viewable in the sidebar. Recent versions of LlamaIndex have changed their import and package structure in a way that breaks existing code. In many cases, you can fix imports as follows: Specific third party components require installing new packages. These will be noted in comments. Example: For code in Chap04, From March 1, 2024, LlamaHub has been deprecated and most projects migrated into LlamaIndex. (sort of--it's complicated) Specifically: Additionally, LlamaIndex ServiceContext has been deprecated and replaced with Settings. See Ch02/rag_llamaindex.py for updated sample code. LangChain too has changed their import structure, though as of this writing it produces warnings rather than errors. In many cases you will need to import from langchaincommunity or langchainopenai as follows: Instructor M. Joel Dubinko Software Generalist | Consultant | Instructor | Problem Solver Check out my other courses on [LinkedIn Learning][URL-instructor-home]. [lil-course-url]: https://www.linkedin.com/learning/introduction-to-ai-orchestration-with-langchain-and-llamaindex [lil-thumbnail-url]: https://media.licdn.com/dms/image/D560DAQEi6KQmA4fF1Q/learning-public-crop6751200/0/1707936616297?e=2147483647&v=beta&t=3vzvDRzpKq9Nd99ss8r2pqMZmyTOKYgKwk825XoSEHU [URL-instructor-home]: https://www.linkedin.com/learning/instructors/m-joel-dubinko?u=104

Mastering-AI-for-Entrepreneurs-9-Free-Courses
github
LLM Vibe Score0.203
Human Vibe Score0
Softtechhub1Feb 1, 2025

Mastering-AI-for-Entrepreneurs-9-Free-Courses

Mastering-AI-for-Entrepreneurs-9-Free-Courses Introduction: The Entrepreneur's AI RevolutionArtificial Intelligence (AI) is changing the way we do business. It's not just for tech giants anymore. Small businesses and startups are using AI to work smarter, not harder. As an entrepreneur, you need to understand AI to stay ahead.Why AI is a must-have skill for entrepreneursAI is everywhere. It's in the apps we use, the products we buy, and the services we rely on. Businesses that use AI are seeing big improvements:They're making better decisions with data-driven insightsThey're automating routine tasks, freeing up time for creativityThey're personalizing customer experiences, boosting satisfaction and salesIf you're not using AI, you're falling behind. But here's the good news: you don't need to be a tech wizard to harness the power of AI.Breaking the barriers to AI learningThink AI is too complex? Think again. You don't need a computer science degree to understand and use AI in your business. Many AI tools are designed for non-technical users. They're intuitive and user-friendly.The best part? You can learn about AI for free. There are tons of high-quality courses available at no cost. These courses are designed for busy entrepreneurs like you. They cut through the jargon and focus on practical applications.What to expect from this articleWe've handpicked nine free courses that will turn you into an AI-savvy entrepreneur. Each course is unique, offering different perspectives and skills. We'll cover:What makes each course specialWhat you'll learnHow it applies to your businessWho it's best suited forReady to dive in? Let's explore these game-changing courses that will boost your AI knowledge and give your business an edge.1. Google AI Essentials: A Beginner's Guide to Practical AIWhy This Course Is EssentialGoogle AI Essentials is perfect if you're just starting out. It's designed for people who don't have a tech background. The course focuses on how AI can help you in your day-to-day work, not on complex theories.What You'll LearnThis course is all about making AI work for you. You'll discover how to:Use AI to boost your productivity. Generate ideas, create content, and manage tasks more efficiently.Streamline your workflows. Learn how AI can help with everyday tasks like drafting emails and organizing your schedule.Use AI responsibly. Understand the potential biases in AI and how to use it ethically.Key TakeawaysYou'll earn a certificate from Google. This looks great on your resume or LinkedIn profile.You'll learn how to work alongside AI tools to get better results in your business.You'll gain practical skills you can use right away to improve your work.Get StartedEnroll in Google AI Essentials2. Introduction to Generative AI: A Quick Start for EntrepreneursWhy This Course Works for Busy EntrepreneursThis course is short and sweet. In just 30 minutes, you'll get a solid grasp of generative AI. It's perfect if you're short on time but want to understand the basics.What You'll LearnThe fundamentals of generative AI: what it is, how it works, and its limitsHow generative AI differs from other types of AIReal-world applications of generative AI in businessHow It Helps Your BusinessAfter this course, you'll be able to:Make smarter decisions about using AI tools in your businessSpot opportunities where generative AI could solve problems or create valueUnderstand the potential and limitations of this technologyGet StartedEnroll in Introduction to Generative AI3. Generative AI with Large Language Models: Advanced Skills for EntrepreneursWhy This Course Stands OutThis course digs deeper into the technical side of AI. It's ideal if you have some coding experience and want to understand how AI models work under the hood.What You'll LearnYou'll gain key skills for working with Large Language Models (LLMs):How to gather and prepare data for AI modelsChoosing the right model for your needsEvaluating model performance and improving resultsYou'll also learn about:The architecture behind transformer models (the tech powering many AI tools)Techniques for fine-tuning models to your specific business needsWho Should Take This CourseThis course is best for entrepreneurs who:Have basic Python programming skillsUnderstand the fundamentals of machine learningWant to go beyond using AI tools to actually building and customizing themGet StartedEnroll in Generative AI with Large Language Models4. AI for Everyone by Andrew Ng: Simplifying AI for Business LeadersWhy It's Perfect for BeginnersAndrew Ng is a leading figure in AI education. He's known for making complex topics easy to understand. This course is designed for non-technical learners. You don't need any coding or math skills to benefit from it.What You'll LearnHow AI works at a high levelHow to spot problems in your business that AI can solveWays to assess how AI might impact your business processes and strategiesWhy Entrepreneurs Love This CourseIt explains AI concepts in plain English, without technical jargonYou can complete it in just 8 hours, fitting it into your busy scheduleIt focuses on the business value of AI, not just the technologyGet StartedStart with AI for Everyone on Coursera5. Generative AI: Introduction and ApplicationsWhy This Course Is Ideal for EntrepreneursThis course offers a broad view of generative AI applications. You'll learn about AI in text, image, audio, and more. It's packed with hands-on experience using popular AI tools.What You'll LearnThe basics and history of generative AI technologiesHow different industries are using AI, from marketing to creative projectsPractical skills through labs using tools like ChatGPT, DALL-E, and Stable DiffusionHow It Stands OutYou'll hear from real AI practitioners about their experiencesThe course teaches you how to use generative AI to innovate and improve efficiency in your businessGet StartedEnroll in Generative AI: Introduction and Applications6. Generative AI for Everyone by Andrew Ng: Unlocking ProductivityWhy This Course Is a Must-HaveThis course focuses on using generative AI tools for everyday business tasks. It's all about boosting your productivity and efficiency.What You'll LearnHands-on exercises to integrate AI tools into your daily workReal examples of how businesses are using generative AI to save time and moneyTechniques for prompt engineering to get better results from AI toolsHow It Helps EntrepreneursYou'll learn to automate repetitive tasks, freeing up time for strategic thinkingYou'll discover new ways to use AI tools in your business processesYou'll gain confidence in experimenting with AI to solve business challengesGet StartedGo deeper with DeepLearning.AI7. Generative AI for Business Leaders by LinkedIn LearningWhy This Course Focuses on Business ApplicationsThis course is tailored for leaders who want to integrate AI into their business operations. It provides practical insights for improving workflows and decision-making.What You'll LearnStrategies for using AI to optimize your business operationsHow to save time and resources with AI-powered toolsPractical methods for implementing AI in your company, regardless of sizeKey BenefitsThe course is designed for busy professionals, allowing you to learn at your own paceYou'll gain insights you can apply immediately to your businessIt covers both the potential and the limitations of AI in business settingsGet StartedLevel up on LinkedIn Learning8. AI for Beginners by Microsoft: A Structured Learning PathWhy This Course Builds a Strong AI FoundationMicrosoft's AI for Beginners is a comprehensive 12-week program. It covers core AI concepts in a structured, easy-to-follow format. The course combines theoretical knowledge with hands-on practice through quizzes and labs.What You'll LearnThe basics of AI, machine learning, and data scienceStep-by-step guidance to build a strong knowledge basePractical applications of AI in various business contextsHow to Approach This CourseDedicate 2-3 hours per week to complete the curriculumUse the structured format to gradually build your confidence in AI conceptsApply what you learn to real business scenarios as you progressGet StartedBuild foundations with Microsoft9. AI for Business Specialization by UPenn: Strategic Thinking with AIWhy This Course Is Perfect for Business LeadersThis specialization focuses on AI's transformative impact on core business functions. It covers how AI is changing marketing, finance, and operations.What You'll LearnHow to build an AI strategy tailored to your business needsWays to leverage AI to drive innovation across different departmentsTechniques for integrating AI into your business modelHow to Make the Most of This CourseTake detailed notes on how each module applies to your own business challengesUse the specialization to develop a long-term AI vision for your companyNetwork with other business leaders taking the course to share insights and experiencesGet StartedScale up with UPenn's business focusConclusion: Your Path to Becoming an AI-powered EntrepreneurWe've covered nine fantastic free courses that can transform you into an AI-savvy entrepreneur. Let's recap:Google AI Essentials: Perfect for beginners, focusing on practical AI applications.Introduction to Generative AI: A quick start to understand the basics of generative AI.Generative AI with Large Language Models: For those ready to dive into the technical side.AI for Everyone: A non-technical introduction to AI's business impact.Generative AI: Introduction and Applications: A broad look at generative AI across industries.Generative AI for Everyone: Focused on boosting productivity with AI tools.Generative AI for Business Leaders: Tailored for integrating AI into business operations.AI for Beginners: A structured path to build a strong AI foundation.AI for Business Specialization: Strategic thinking about AI in business functions.Remember, you don't need to tackle all these courses at once. Start small and build your knowledge gradually. Pick the course that aligns best with your current needs and business goals.Embracing AI is not just about staying competitive; it's about opening new doors for innovation and growth. These courses will help you see opportunities where AI can solve problems, improve efficiency, and create value for your business.The AI revolution is happening now. The sooner you start learning, the better positioned you'll be to lead in this new era. Each step you take in understanding AI is a step towards future-proofing your business.So, what are you waiting for? Choose a course, dive in, and start your journey to becoming an AI-powered entrepreneur today. The future of your business may depend on it.MORE ARTICLES FOR YOUHumanizzer Fastpass Bundle – OTO1 to OTO4: Get (Humanizzer + All OTOs) Fastpass for Massive 75% Discount Available Limited-Time OneHumanizzer Review: Build Lifelike Human AI Agents That Talk, Listen & Engage Face-To-Face!—In Your Voice, Just Like You!EasyListDetox App Review: A Windows tool with Giveaway Rights for effortlessly cleaning your email lists of duplicates, invalid, and disposable addresses. Simple, efficient, and time-savingAI Copy Kit Review: Google’s Latest AI Tech Tensorflow (Tf) Create Jaw-Dropping And Advanced Ultra HD Videos, Ultra Shorts, 4K Images, Voiceovers, and Any Other GPT 4-Powered Amazing Content In Minutes Without Any Complicated Tools!From Good to Great: 15 Books to Inspire Personal and Business TransformationFTC Affiliate Commission Disclaimer: Some links in this article may earn us a commission if you make a purchase. This doesn't affect our recommendations.

teach-AI-in-business
github
LLM Vibe Score0.443
Human Vibe Score0.018525334165293606
aenyneJan 9, 2025

teach-AI-in-business

Teaching AI in Business ![HitCount] I am collecting material for teaching AI-related issues to non-tech people. The links should provide for a general understanding of AI without going too deep into technical issues. Please contribute! Make this Issue your First Issue I am collecting material for teaching AI-related issues to non-tech people. The links should have provide for a general understanding of AI without going too deep into technical issues. Please contribute! Kindly use only those Resources with NO CODE NEW Check out also the AI Wiki NEW Online Videos & Courses | Link to Issue | Description | |---|---| | Top Trending Technologies | Youtube Channel to master top trending technologyies including artificial intelligence | | AI4All | AI 4 All is a resource for AI facilitators to bring AI to scholars and students | | Elements of AI | Elements of AI is a free open online course to teach AI principles | | Visual Introduction to Machine Learning | Visual introduction to Machine Learning is a beautiful website that gives a comprehensive introduction and easily understood first encounter with machine learning | | CS50's Introduction to Artificial Intelligence with Python | Learn to use machine learning in Python in this introductory course on artificial intelligence.| | Crash course for AI | This is a fun video series that introduces students and educators to Artificial Intelligence and also offers additional more advanced videos. Learn about the basics, neural networks, algorithms, and more. | Youtuber Channel Machine Learning Tutorial | Youtube Channel Turorial Teachable Machine for beginner | | Artificial Intelligence (AI) |Learn the fundamentals of Artificial Intelligence (AI), and apply them. Design intelligent agents to solve real-world problems including, search, games, machine learning, logic, and constraint satisfaction problems | | AI For Everyone by Andrew Ng | AI For Everyone is a course especially for people from a non-technical background to understand AI strategies | | How far is too far? The age of AI| This is a Youtube Orignals series by Robert Downey| | Fundamentals of Artificial Intelligence|This course is for absolute beginners with no technical knowledge.| | Bandit Algorithm (Online Machine Learning)|No requirement of technical knowledge, but a basic understending of Probability Ttheory would help| | An Executive's Guide to AI|This is an interactive guide to teaching business professionals how they might employ artificial intelligence in their business| | AI Business School|Series of videos that teach how AI may be incorporated in various business industries| | Artificial Intelligence Tutorial for Beginners | This video will provide you with a comprehensive and detailed knowledge of Artificial Intelligence concepts with hands-on examples. | | Indonesian Machine Learning Tutorial | Turorial Teachable Machine to train a computer for beginner | | Indonesian Youtube Playlist AI Tutorial | Youtube Playlist AI Tutorial For Beginner | | Artificial Intelligence Search Methods For Problem Solving By Prof. Deepak Khemani|These video lectures are for absolute beginners with no technical knowledge| | AI Basics Tutorial | This video starts from the very basics of AI and ML, and finally has a hands-on demo of the standard MNIST Dataset Number Detection model using Keras and Tensorflow.| | Simple brain.js Tutorial | This video explains a very simple javascript AI library called brain.js so you can easily run AI in the browser.| | Google AI| A complete kit for by google official for non-tech guy to start all over from basics, till advanced | | Microsoft AI for Beginners| A self-driven curriculum by Microsoft, which includes 24 lessons on AI. | Train Your Own AI | Link to Issue | Description | |---|---| | Teachable Machine | Use Teachable Machine to train a computer to recognize your own images, sounds, & poses | | eCraft2Learn | Resource and interactive space (Snap, a visual programming environment like Scratch) to learn how to create AI programs | | Google Quick Draw | Train an AI to guess from drawings| | Deepdream Generator| Merge Pictures to Deep Dreams using the Deepdream Generator| | Create ML|Quickly build and train Core ML models on your Mac with no code.| | What-If Tool|Visually probe the behavior of trained machine learning models, with minimal coding.| | Metaranx|Use and build artificial intelligence tools to analyze and make decisions about your data. Drag-and-drop. No code.| | obviously.ai|The total process of building ML algorithms, explaining results, and predicting outcomes in one single click.| Articles | By & Title | Description | |---|---| | Artificial Intelligence | Wikipedia Page of AI | | The Non-Technical AI Guide | One of the good blog post that could help AI more understandable for people without technical background | | LIAI | A detailed introduction to AI and neural networks | | Layman's Intro | A layman's introduction to AI | | AI and Machine Learning: A Nontechnical Overview | AI and Machine Learning: A Nontechnical Overview from OREILLY themselves is a guide to learn anyone everything they need to know about AI, focussed on non-tech people | | What business leaders need to know about artifical intelligence|Short article that summarizes the essential aspects of AI that business leaders need to understand| | How Will No-Code Impact the Future of Conversational AI | A humble explanation to the current state of converstational AI i.e.Chatbots and how it coul evolve with the current trend of no coding. | | Investopedia | Basic explanation of what AI is in a very basic and comprehensive way | | Packtpub | A non programmer’s guide to learning Machine learning | | Builtin | Artificial Intelligence.What is Artificial Intelligence? How Does AI Work? | | Future Of Life | Benefits & Risks of Artificial Intelligence | | NSDM India -Arpit | 100+ AI Tools For Non-Coders That Will Make Your Marketing Better. | | AI in Marketing for Startups & Non-technical Marketers | A practical guide for non-technical people | | Blog - Machine Learning MAstery | Blogs and Articles by Jason Browniee on ML | | AI Chatbots without programming| Chatbots are increasingly in demand among global businesses. This course will teach you how to build, analyze, deploy and monetize chatbots - with the help of IBM Watson and the power of AI.| Book Resources for Further Reading | Author | Book | Description & Notes | |---|---|---| | Ethem Alpaydin|Machine Learning: The New AI | Graph Theory with Applications to Engineering & Computer Science. A concise overview of machine learning—computer programs that learn from data—which underlies applications that include recommendation systems, face recognition, and driverless cars. | | Charu C. Aggarwal| Neural Networks and Deep Learning | This book covers both classical and modern models in deep learning. The primary focus is on the theory and algorithms of deep learning. The book is also rich in discussing different applications in order to give the practitioner a flavor of how neural architectures are designed for different types of problems. | | Hal Daumé III | A Course in Machine Learning | The purpose of this book is to provide a gentle and pedagogically organized introduction to the field. A second goal of this book is to provide a view of machine learning that focuses on ideas and models, not on math. | | Ian Goodfellow and Yoshua Bengio and Aaron Courville| Deep Learning | The book starts with a discussion on machine learning basics, including the applied mathematics and algorithms needed to effectively study deep learning from an academic perspective. There is no code covered in the book, making it perfect for a non-technical AI enthusiast. | | Peter Harrington|Machine Learning in Action| (Source: https://github.com/kerasking/book-1/blob/master/ML%20Machine%20Learning%20in%20Action.pdf) This book acts as a guide to walk newcomers through the techniques needed for machine learning as well as the concepts behind the practices.| | Jeff Heaton| Artificial Intelligence for Humans |This book helps its readers get an overview and understanding of AI algorithms. It is meant to teach AI for those who don’t have an extensive mathematical background. The readers need to have only a basic knowledge of computer programming and college algebra.| | John D. Kelleher, Brian Mac Namee and Aoife D'Arcy|Fundamentals of Machine Learning for Predictive Data Analytics: Algorithms, Worked Examples, and Case Studies (The MIT Press)|This book covers all the fundamentals of machine learning, diving into the theory of the subject and using practical applications, working examples, and case studies to drive the knowledge home.| | Deepak Khemani| [A First Course in Artificial Intelligence] | It is an introductory course on Artificial Intelligence, a knowledge-based approach using agents all across and detailed, well-structured algorithms with proofs. This book mainly follows a bottom-up approach exploring the basic strategies needed problem-solving on the intelligence part. | | Maxim Lapan | Deep Reinforcement Learning Hands-On - Second Edition | Deep Reinforcement Learning Hands-On, Second Edition is an updated and expanded version of the bestselling guide to the very latest reinforcement learning (RL) tools and techniques. It provides you with an introduction to the fundamentals of RL, along with the hands-on ability to code intelligent learning agents to perform a range of practical tasks. | | Tom M Mitchell | Machine Learning | This book covers the field of machine learning, which is the study of algorithms that allow computer programs to automatically improve through experience. The book is intended to support upper level undergraduate and introductory level graduate courses in machine learning. | | John Paul Mueller and Luca Massaron|Machine Learning For Dummies|This book aims to get readers familiar with the basic concepts and theories of machine learning and how it applies to the real world. And "Dummies" here refers to absolute beginners with no technical background.The book introduces a little coding in Python and R used to teach machines to find patterns and analyze results. From those small tasks and patterns, we can extrapolate how machine learning is useful in daily lives through web searches, internet ads, email filters, fraud detection, and so on. With this book, you can take a small step into the realm of machine learning and we can learn some basic coding in Pyton and R (if interested)| | Michael Nielsen| Neural Networks and Deep Learning |Introduction to the core principles of Neural Networks and Deep Learning in AI| | Simon Rogers and Mark Girolami| A Course in Machine Learning |A First Course in Machine Learning by Simon Rogers and Mark Girolami is the best introductory book for ML currently available. It combines rigor and precision with accessibility, starts from a detailed explanation of the basic foundations of Bayesian analysis in the simplest of settings, and goes all the way to the frontiers of the subject such as infinite mixture models, GPs, and MCMC.| |Peter Norvig| Paradigm of Artificial Intelligence Programming |Paradigms of AI Programming is the first text to teach advanced Common Lisp techniques in the context of building major AI systems. By reconstructing authentic, complex AI programs using state-of-the-art Common Lisp, the book teaches students and professionals how to build and debug robust practical programs, while demonstrating superior programming style and important AI concepts.| | Stuart Russel & Peter Norvig | Artificial Intelligence: A Modern Approach, 3rd Edition | This is the prescribed text book for my Introduction to AI university course. It starts off explaining all the basics and definitions of what AI is, before launching into agents, algorithms, and how to apply them. Russel is from the University of California at Berkeley. Norvig is from Google.| | Richard S. Sutton and Andrew G. Barto| Reinforcement Learning: An Introduction |Reinforcement learning, one of the most active research areas in artificial intelligence, is a computational approach to learning whereby an agent tries to maximize the total amount of reward it receives while interacting with a complex, uncertain environment.| | Alex Smola and S.V.N. Vishwanathan | Introduction to Machine Learning | Provides the reader with an overview of the vast applications of ML, including some basic tools of statistics and probability theory. Also includes discussions on sophisticated ideas and concepts. | | Shai Shalev-Shwartz and Shai Ben-David | Understanding Machine Learning From Theory to Algorithms |The primary goal of this book is to provide a rigorous, yet easy to follow, introduction to the main concepts underlying machine learning. | | Chandra S.S.V | Artificial Intelligence and Machine Learning | This book is primarily intended for undergraduate and postgraduate students of computer science and engineering. This textbook covers the gap between the difficult contexts of Artificial Intelligence and Machine Learning. It provides the most number of case studies and worked-out examples. In addition to Artificial Intelligence and Machine Learning, it also covers various types of learning like reinforced, supervised, unsupervised and statistical learning. It features well-explained algorithms and pseudo-codes for each topic which makes this book very useful for students. | | Oliver Theobald|Machine Learning For Absolute Beginners: A Plain English Introduction|This is an absolute beginners ML guide.No mathematical background is needed, nor coding experience — this is the most basic introduction to the topic for anyone interested in machine learning.“Plain” language is highly valued here to prevent beginners from being overwhelmed by technical jargon. Clear, accessible explanations and visual examples accompany the various algorithms to make sure things are easy to follow.| | Tom Taulli | Artificial Intelligence Basics: A Non-Technical Introduction | This book equips you with a fundamental grasp of Artificial Intelligence and its impact. It provides a non-technical introduction to important concepts such as Machine Learning, Deep Learning, Natural Language Processing, Robotics and more. Further the author expands on the questions surrounding the future impact of AI on aspects that include societal trends, ethics, governments, company structures and daily life. | |Cornelius Weber, Mark Elshaw, N. Michael Mayer| Reinforcement Learning |Learning is a very important aspect. This book is on reinforcement learning which involves performing actions to achieve a goal. The first 11 chapters of this book describe and extend the scope of reinforcement learning.| |John D. Kelleher, Brian Mac Namee, Aoife D'arcy| Algorithms, Worked Examples, and Case Studies | A comprehensive introduction to the most important machine learning approaches used in predictive data analytics, covering both theoretical concepts and practical applications. |

ai-learning-roadmap
github
LLM Vibe Score0.442
Human Vibe Score0.035708035270567436
gopala-krNov 30, 2024

ai-learning-roadmap

Lists of all AI related learning materials and practical tools to get started with AI apps Design Thinking – An Introduction Stanford's virtual Crash Course in Design Thinking Amazon Web Services Learning Material AWS AI Session– The session provides an overview of all Amazon AI technology offerings (Lex, Polly, Rekognition, ML, and Deep Learning AMI) Self-Paced Labs AWS self-paced labs provide hands-on practice in a live AWS environment with AWS services and real-world cloud scenarios. Follow step-by-step instructions to learn a service, practice a use case, or prepare for AWS Certification. Introductory Lab Introduction to AWS Lambda Lex Introduction to Amazon Lex Amazon Lex Webinar Amazon Lex: AWS conversational interface (chat bot) Documentation Polly Introduction to Amazon Polly Amazon Polly Webinar - Amazon Polly – AWS Text To Speech (TTS) service Documentation What is Amazon Polly? Developer Resources Rekognition Introduction to Amazon Rekognition Amazon Rekognition - Deep Learning-Based Image Analysis Webinar Amazon Rekognition – AWS image recognition service Documentation – What is Amazon Rekognition? Machine Learning Machine Learning Session 1 – Empowering Developers to Build Smart Applications Session 2 - Predicting Customer Churn with Amazon Machine Learning AWS Machine Learning – End to end, managed service for creating and testing ML models and then deploying those models into production Documentation What is Amazon Machine Learning? Developer Resources AWS Deep Learning AMI – Amazon Machine Image (AMI) optimized for deep learning efforts Recommended Additional Resources Take your skills to the next level with fundamental, advanced, and expert level labs. Creating Amazon EC2 Instances with Microsoft Windows Building Your First Amazon Virtual Private Cloud (VPC) Working with AWS CodeCommit on Windows Working with Amazon DynamoDB Google Cloud - Learning Material Below is the learning material that will help you learn about Google Cloud. Network Networking 101 – 43 mins The codelab provides common cloud developer experience as follows: Set up your lab environment and learn how to work with your GCP environment. Use of common open source tools to explore your network around the world. Deploy a common use case: use of HTTP Load Balancing and Managed Instance Groups to host a scalable, multi-region web server. Testing and monitoring your network and instances. Cleanup. Developing Solutions for Google Cloud Platform – 8 hours Infrastructure Build a Slack Bot with Node.js on Kubernotes – 43 mins Creating a Virtual Machine – 10 mins Getting Started with App Engine (Python) – 13 mins Data Introduction to Google Cloud Data Prep – 7 mins Create a Managed MySQL database with Cloud SQL – 19 mins Upload Objects to Cloud Storage – 11 mins AI, Big Data & Machine Learning Introduction to Google Cloud Machine Learning – 1 hour Machine Learning APIs by Example – 30 min Google Cloud Platform Big Data and Machine Learning Fundamentals Additional AI Materials Auto-awesome: Advanced Data Science on Google Cloud Platform – 45 min Run a Big Data Text Processing Pipeline in Cloud Dataflow – 21 min Image Classification Using Cloud ML Engine & Datalab – 58 min Structured Data Regression Using Cloud ML Engine & Datalab – 58 min (Optional) Deep Learning & Tensorflow Tensorflow and Deep Learning Tutorial – 2:35 hours Deep Learning Course – advanced users only Additional Reference Material Big Data & Machine Learning @ Google Cloud Next '17 - A collection of 49 videos IBM Watson Learning Material (Contributions are welcome in this space) [IBM Watson Overview]() [IBM Watson Cognitive APIs]() [IBM Watson Knowledge Studio]() Visual Studio UCI datasets Microsoft Chat Bots Learning Material Skills Prerequisite Git and Github NodeJS VS Code IDE Training Paths If you have the above Prerequisite skills, then take Advanced Training Path else take Novice Training Path. Prerequisite Tutorials Git and Github Node.js Node.js Tutorials for Beginners Node.js Tutorial in VS Code Introduction To Visual Studio Code Novice Training Path Environment Set Up Download and Install Git Set up GitHub Account_ Download and Install NodeJS Download and Install IDE - Visual Studio Code Download and Install the Bot Framework Emulator Git clone the Bot Education project - git clone Set Up Azure Free Trial Account Cognitive Services (Defining Intelligence) Read Cognitive Services ADS Education Deck – git clone Review the guide for Understanding Natural language with LUIS Complete the NLP (LUIS) Training Lab from the installed Bot Education project – \bot-education\Student-Resources\Labs\CognitiveServices\Lab_SetupLanguageModel.md Bot Framework (Building Chat Bots) Read Bot Framework ADS Education Deck from downloaded - (Your Path)\bot-extras Review Bot Framework documentation (Core Concepts, Bot Builder for NodeJS, and Bot Intelligence) - Setup local environment and run emulator from the installed Bot Education project – \bot-education\Student-Resources\Labs\Node\Lab1_SetupCheckModel.md Review and test in the emulator the “bot-hello” from \bot-education\Student-Resources\BOTs\Node\bot-hello Advanced Training Path Environment Set Up Download and Install Git Set up GitHub Account_ Download and Install NodeJS Download and Install IDE - Visual Studio Code Download and Install the Bot Framework Emulator Git clone the Bot Education project - git clone Set Up Azure Free Trial Account Git clone the Bot Builder Samples – git clone Cognitive Services (Defining Intelligence) Read Cognitive Services ADS Education Deck – git clone Review the guide for Understanding Natural language with LUIS Bot Framework (Building Chat Bots) Read Bot Framework ADS Education Deck from downloaded - (Your Path)\bot-extras Review Bot Framework documentation (Core Concepts, Bot Builder for NodeJS, and Bot Intelligence) - Setup local environment and run emulator from the installed Bot Education project – \bot-education\Student-Resources\Labs\Node\Lab1_SetupCheckModel.md Cognitive Services (Defining Intelligence) - Labs Complete the NLP (LUIS) Training Lab from the installed BOT Education project \bot-education\Student-Resources\Labs\CognitiveServices\Lab_SetupLanguageModel.md Review, Deploy and run the LUIS BOT sample Bot Framework (Building Chat Bots) – Labs Setup local environment and run emulator from the installed Bot Education project \bot-education\Student-Resources\Labs\Node\Lab1_SetupCheckModel.md Review and test in the emulator the “bot-hello” from \bot-education\Student-Resources\BOTs\Node\bot-hello Review and test in the emulator the “bot-recognizers” from \bot-education\Student-Resources\BOTs\Node\bot-recognizers Lecture Videos Source Berkeley Lecture TitleLecturerSemester Lecture 1 Introduction Dan Klein Fall 2012 Lecture 2 Uninformed Search Dan Klein Fall 2012 Lecture 3 Informed Search Dan Klein Fall 2012 Lecture 4 Constraint Satisfaction Problems I Dan Klein Fall 2012 Lecture 5 Constraint Satisfaction Problems II Dan Klein Fall 2012 Lecture 6 Adversarial Search Dan Klein Fall 2012 Lecture 7 Expectimax and Utilities Dan Klein Fall 2012 Lecture 8 Markov Decision Processes I Dan Klein Fall 2012 Lecture 9 Markov Decision Processes II Dan Klein Fall 2012 Lecture 10 Reinforcement Learning I Dan Klein Fall 2012 Lecture 11 Reinforcement Learning II Dan Klein Fall 2012 Lecture 12 Probability Pieter Abbeel Spring 2014 Lecture 13 Markov Models Pieter Abbeel Spring 2014 Lecture 14 Hidden Markov Models Dan Klein Fall 2013 Lecture 15 Applications of HMMs / Speech Pieter Abbeel Spring 2014 Lecture 16 Bayes' Nets: Representation Pieter Abbeel Spring 2014 Lecture 17 Bayes' Nets: Independence Pieter Abbeel Spring 2014 Lecture 18 Bayes' Nets: Inference Pieter Abbeel Spring 2014 Lecture 19 Bayes' Nets: Sampling Pieter Abbeel Fall 2013 Lecture 20 Decision Diagrams / Value of Perfect Information Pieter Abbeel Spring 2014 Lecture 21 Machine Learning: Naive Bayes Nicholas Hay Spring 2014 Lecture 22 Machine Learning: Perceptrons Pieter Abbeel Spring 2014 Lecture 23 Machine Learning: Kernels and Clustering Pieter Abbeel Spring 2014 Lecture 24 Advanced Applications: NLP, Games, and Robotic Cars Pieter Abbeel Spring 2014 Lecture 25 Advanced Applications: Computer Vision and Robotics Pieter Abbeel Spring 2014 Additionally, there are additional Step-By-Step videos which supplement the lecture's materials. These videos are listed below: Lecture TitleLecturerNotes SBS-1 DFS and BFS Pieter Abbeel Lec: Uninformed Search SBS-2 A* Search Pieter Abbeel Lec: Informed Search SBS-3 Alpha-Beta Pruning Pieter Abbeel Lec: Adversarial Search SBS-4 D-Separation Pieter Abbeel Lec: Bayes' Nets: Independence SBS-5 Elimination of One Variable Pieter Abbeel Lec: Bayes' Nets: Inference SBS-6 Variable Elimination Pieter Abbeel Lec: Bayes' Nets: Inference SBS-7 Sampling Pieter Abbeel Lec: Bayes' Nets: Sampling SBS-8 Gibbs' Sampling Michael Liang Lec: Bayes' Nets: Sampling --> SBS-8 Maximum Likelihood Pieter Abbeel Lec: Machine Learning: Naive Bayes SBS-9 Laplace Smoothing Pieter Abbeel Lec: Machine Learning: Naive Bayes SBS-10 Perceptrons Pieter Abbeel Lec: Machine Learning: Perceptrons Per-Semester Video Archive(Berkeley) The lecture videos from the most recent offerings are posted below. Spring 2014 Lecture Videos Fall 2013 Lecture Videos Spring 2013 Lecture Videos Fall 2012 Lecture Videos Spring 2014 Lecture TitleLecturerNotes Lecture 1 Introduction Pieter Abbeel Lecture 2 Uninformed Search Pieter Abbeel Lecture 3 Informed Search Pieter Abbeel Lecture 4 Constraint Satisfaction Problems I Pieter Abbeel Recording is a bit flaky, see Fall 2013 Lecture 4 for alternative Lecture 5 Constraint Satisfaction Problems II Pieter Abbeel Lecture 6 Adversarial Search Pieter Abbeel Lecture 7 Expectimax and Utilities Pieter Abbeel Lecture 8 Markov Decision Processes I Pieter Abbeel Lecture 9 Markov Decision Processes II Pieter Abbeel Lecture 10 Reinforcement Learning I Pieter Abbeel Lecture 11 Reinforcement Learning II Pieter Abbeel Lecture 12 Probability Pieter Abbeel Lecture 13 Markov Models Pieter Abbeel Lecture 14 Hidden Markov Models Pieter Abbeel Recording is a bit flaky, see Fall 2013 Lecture 18 for alternative Lecture 15 Applications of HMMs / Speech Pieter Abbeel Lecture 16 Bayes' Nets: Representation Pieter Abbeel Lecture 17 Bayes' Nets: Independence Pieter Abbeel Lecture 18 Bayes' Nets: Inference Pieter Abbeel Lecture 19 Bayes' Nets: Sampling Pieter Abbeel Unrecorded, see Fall 2013 Lecture 16 Lecture 20 Decision Diagrams / Value of Perfect Information Pieter Abbeel Lecture 21 Machine Learning: Naive Bayes Nicholas Hay Lecture 22 Machine Learning: Perceptrons Pieter Abbeel Lecture 23 Machine Learning: Kernels and Clustering Pieter Abbeel Lecture 24 Advanced Applications: NLP, Games, and Robotic Cars Pieter Abbeel Lecture 25 Advanced Applications: Computer Vision and Robotics Pieter Abbeel Lecture 26 Conclusion Pieter Abbeel Unrecorded Fall 2013 Lecture TitleLecturerNotes Lecture 1 Introduction Dan Klein Lecture 2 Uninformed Search Dan Klein Lecture 3 Informed Search Dan Klein Lecture 4 Constraint Satisfaction Problems I Dan Klein Lecture 5 Constraint Satisfaction Problems II Dan Klein Lecture 6 Adversarial Search Dan Klein Lecture 7 Expectimax and Utilities Dan Klein Lecture 8 Markov Decision Processes I Dan Klein Lecture 9 Markov Decision Processes II Dan Klein Lecture 10 Reinforcement Learning I Dan Klein Lecture 11 Reinforcement Learning II Dan Klein Lecture 12 Probability Pieter Abbeel Lecture 13 Bayes' Nets: Representation Pieter Abbeel Lecture 14 Bayes' Nets: Independence Dan Klein Lecture 15 Bayes' Nets: Inference Pieter Abbeel Lecture 16 Bayes' Nets: Sampling Pieter Abbeel Lecture 17 Decision Diagrams / Value of Perfect Information Pieter Abbeel Lecture 18 Hidden Markov Models Dan Klein Lecture 19 Applications of HMMs / Speech Dan Klein Lecture 20 Machine Learning: Naive Bayes Dan Klein Lecture 21 Machine Learning: Perceptrons Dan Klein Lecture 22 Machine Learning: Kernels and Clustering Pieter Abbeel Lecture 23 Machine Learning: Decision Trees and Neural Nets Pieter Abbeel Lecture 24 Advanced Applications: NLP and Robotic Cars Dan Klein Unrecorded, see Spring 2013 Lecture 24 Lecture 25 Advanced Applications: Computer Vision and Robotics Pieter Abbeel Lecture 26 Conclusion Dan Klein,Pieter Abbeel Unrecorded Spring 2013 Lecture TitleLecturerNotes Lecture 1 Introduction Pieter Abbeel Video Down Lecture 2 Uninformed Search Pieter Abbeel Lecture 3 Informed Search Pieter Abbeel Lecture 4 Constraint Satisfaction Problems I Pieter Abbeel Lecture 5 Constraint Satisfaction Problems II Pieter Abbeel Unrecorded, see Fall 2012 Lecture 5 Lecture 6 Adversarial Search Pieter Abbeel Lecture 7 Expectimax and Utilities Pieter Abbeel Lecture 8 Markov Decision Processes I Pieter Abbeel Lecture 9 Markov Decision Processes II Pieter Abbeel Lecture 10 Reinforcement Learning I Pieter Abbeel Lecture 11 Reinforcement Learning II Pieter Abbeel Lecture 12 Probability Pieter Abbeel Lecture 13 Bayes' Nets: Representation Pieter Abbeel Lecture 14 Bayes' Nets: Independence Pieter Abbeel Lecture 15 Bayes' Nets: Inference Pieter Abbeel Lecture 16 Bayes' Nets: Sampling Pieter Abbeel Lecture 17 Decision Diagrams / Value of Perfect Information Pieter Abbeel Lecture 18 Hidden Markov Models Pieter Abbeel Lecture 19 Applications of HMMs / Speech Pieter Abbeel Lecture 20 Machine Learning: Naive Bayes Pieter Abbeel Lecture 21 Machine Learning: Perceptrons I Nicholas Hay Lecture 22 Machine Learning: Perceptrons II Pieter Abbeel Lecture 23 Machine Learning: Kernels and Clustering Pieter Abbeel Lecture 24 Advanced Applications: NLP and Robotic Cars Pieter Abbeel Lecture 25 Advanced Applications: Computer Vision and Robotics Pieter Abbeel Lecture 26 Conclusion Pieter Abbeel Unrecorded Fall 2012 Lecture TitleLecturerNotes Lecture 1 Introduction Dan Klein Lecture 2 Uninformed Search Dan Klein Lecture 3 Informed Search Dan Klein Lecture 4 Constraint Satisfaction Problems I Dan Klein Lecture 5 Constraint Satisfaction Problems II Dan Klein Lecture 6 Adversarial Search Dan Klein Lecture 7 Expectimax and Utilities Dan Klein Lecture 8 Markov Decision Processes I Dan Klein Lecture 9 Markov Decision Processes II Dan Klein Lecture 10 Reinforcement Learning I Dan Klein Lecture 11 Reinforcement Learning II Dan Klein Lecture 12 Probability Pieter Abbeel Lecture 13 Bayes' Nets: Representation Pieter Abbeel Lecture 14 Bayes' Nets: Independence Pieter Abbeel Lecture 15 Bayes' Nets: Inference Pieter Abbeel Lecture 16 Bayes' Nets: Sampling Pieter Abbeel Lecture 17 Decision Diagrams / Value of Perfect Information Pieter Abbeel Lecture 18 Hidden Markov Models Pieter Abbeel Lecture 19 Applications of HMMs / Speech Dan Klein Lecture 20 Machine Learning: Naive Bayes Dan Klein Lecture 21 Machine Learning: Perceptrons Dan Klein Lecture 22 Machine Learning: Kernels and Clustering Dan Klein Lecture 23 Machine Learning: Decision Trees and Neural Nets Pieter Abbeel Lecture 24 Advanced Applications: Computer Vision and Robotics Pieter Abbeel Lecture 25 Advanced Applications: NLP and Robotic Cars Dan Klein,Pieter Abbeel Unrecorded Lecture 26 Conclusion Dan Klein,Pieter Abbeel Unrecorded Lecture Slides Here is the complete set of lecture slides, including videos, and videos of demos run in lecture: Slides [~3 GB]. The list below contains all the lecture powerpoint slides: Lecture 1: Introduction Lecture 2: Uninformed Search Lecture 3: Informed Search Lecture 4: CSPs I Lecture 5: CSPs II Lecture 6: Adversarial Search Lecture 7: Expectimax Search and Utilities Lecture 8: MDPs I Lecture 9: MDPs II Lecture 10: Reinforcement Learning I Lecture 11: Reinforcement Learning II Lecture 12: Probability Lecture 13: Markov Models Lecture 14: Hidden Markov Models Lecture 15: Particle Filters and Applications of HMMs Lecture 16: Bayes Nets I: Representation Lecture 17: Bayes Nets II: Independence Lecture 18: Bayes Nets III: Inference Lecture 19: Bayes Nets IV: Sampling Lecture 20: Decision Diagrams and VPI Lecture 21: Naive Bayes Lecture 22: Perceptron Lecture 23: Kernels and Clustering Lecture 24: Advanced Applications (NLP, Games, Cars) Lecture 25: Advanced Applications (Computer Vision and Robotics) Lecture 26: Conclusion The source files for all live in-lecture demos are being prepared from Berkeley AI for release Selected Research Papers Latest arxiv paper submissionson AI Peter Norvig-Teach Yourself Programming in Ten Years How to do Research At the MIT AI Lab A Roadmap towards Machine Intelligence Collaborative Filtering with Recurrent Neural Networks (2016) Wide & Deep Learning for Recommender Systems (2016) Deep Collaborative Filtering via Marginalized Denoising Auto-encoder (2015) Nonparametric bayesian multitask collaborative filtering (2013) Tensorflow: Large-scale machine learning on heterogeneous distributed systems https://infoscience.epfl.ch/record/82802/files/rr02-46.pdf Theano: A CPU and GPU math expression compiler. Caffe: Convolutional architecture for fast feature embedding Chainer: A powerful, flexible and intuitive framework of neural networks Large Scale Distributed Deep Networks Large-scale video classification with convolutional neural networks Efficient Estimation of Word Representations in Vector Space Grammar as a Foreign Language Going Deeper with Convolutions ON RECTIFIED LINEAR UNITS FOR SPEECH PROCESSING Deep neural networks for acoustic modeling in speech recognition: The shared views of four research groups. Multi-digit Number Recognition from Street View Imagery using Deep Convolutional Neural Networks google turning its lucrative web search over to AI machines Stanford Syllabus CS 20SI: Tensorflow for Deep Learning Research Crowd-Based Personalized Natural Language Explanations for Recommendations Comparative Study of Deep Learning Software Frameworks RedditML- What Are You Reading AI-Powered Social Bots(16 Jun 2017) The Many Tribes of Artificial Intelligence Source:https://medium.com/intuitionmachine/infographic-best-practices-in-training-deep-learning-networks-b8a3df1db53 The Deep Learning Roadmap Source:https://medium.com/intuitionmachine/the-deep-learning-roadmap-f0b4cac7009a Best Practices for Training Deep Learning Networks Source: https://medium.com/intuitionmachine/infographic-best-practices-in-training-deep-learning-networks-b8a3df1db53 ML/DL Cheatsheets Neural Network Architectures Source: http://www.asimovinstitute.org/neural-network-zoo/ Microsoft Azure Algorithm Flowchart Source: https://docs.microsoft.com/en-us/azure/machine-learning/machine-learning-algorithm-cheat-sheet SAS Algorithm Flowchart Source: http://blogs.sas.com/content/subconsciousmusings/2017/04/12/machine-learning-algorithm-use/ Algorithm Summary Source: http://machinelearningmastery.com/a-tour-of-machine-learning-algorithms/ Source: http://thinkbigdata.in/best-known-machine-learning-algorithms-infographic/ Algorithm Pro/Con Source: https://blog.dataiku.com/machine-learning-explained-algorithms-are-your-friend Python Algorithms Source: https://www.analyticsvidhya.com/blog/2015/09/full-cheatsheet-machine-learning-algorithms/ Python Basics Source: http://datasciencefree.com/python.pdf Source: https://www.datacamp.com/community/tutorials/python-data-science-cheat-sheet-basics#gs.0x1rxEA Numpy Source: https://www.dataquest.io/blog/numpy-cheat-sheet/ Source: http://datasciencefree.com/numpy.pdf Source: https://www.datacamp.com/community/blog/python-numpy-cheat-sheet#gs.Nw3V6CE Source: https://github.com/donnemartin/data-science-ipython-notebooks/blob/master/numpy/numpy.ipynb Pandas Source: http://datasciencefree.com/pandas.pdf Source: https://www.datacamp.com/community/blog/python-pandas-cheat-sheet#gs.S4P4T=U Source: https://github.com/donnemartin/data-science-ipython-notebooks/blob/master/pandas/pandas.ipynb Matplotlib Source: https://www.datacamp.com/community/blog/python-matplotlib-cheat-sheet Source: https://github.com/donnemartin/data-science-ipython-notebooks/blob/master/matplotlib/matplotlib.ipynb Scikit Learn Source: https://www.datacamp.com/community/blog/scikit-learn-cheat-sheet#gs.fZ2A1Jk Source: http://peekaboo-vision.blogspot.de/2013/01/machine-learning-cheat-sheet-for-scikit.html Source: https://github.com/rcompton/mlcheatsheet/blob/master/supervised_learning.ipynb Tensorflow Source: https://github.com/aymericdamien/TensorFlow-Examples/blob/master/notebooks/1Introduction/basicoperations.ipynb Pytorch Source: https://github.com/bfortuner/pytorch-cheatsheet Math Probability Source: http://www.wzchen.com/s/probability_cheatsheet.pdf Linear Algebra Source: https://minireference.com/static/tutorials/linearalgebrain4pages.pdf Statistics Source: http://web.mit.edu/~csvoss/Public/usabo/stats_handout.pdf Calculus Source: http://tutorial.math.lamar.edu/getfile.aspx?file=B,41,N

LearnAI-KnowledgeMiningBootcamp
github
LLM Vibe Score0.438
Human Vibe Score0.05521136990708693
sithukyaw007Jan 29, 2024

LearnAI-KnowledgeMiningBootcamp

LearnAI: Build an Enterprise Knowledge Mining Solution using the Microsoft AI Platform Build an enterprise scale intelligent search solution for searching business documents using Microsoft Azure and Cognitive Search About this Course In this course, you will learn to build an enterprise search solution by applying knowledge mining approach to search an organization’s business documents like Microsoft Office, PDFs and images using Azure search and Cognitive search skillsets and expose the results via a Bot interface. You will learn to perform entity recognition, image analysis, text translation and indexed search on enterprise business documents using Microsoft Cognitive Services and Azure Search. This approach can be used with almost any Azure service to augment a customer’s scenario involving intelligent search. While this course focusses on Azure and Cognitive search capabilities, a depth course on building Bots and integrating various cognitive services is available here - Building Intelligent Agents and Apps. In this course you will learn Fundamentals of Azure Search and its capabilities. Understand Microsoft Cognitive Search and its key scenarios for using them. Build an enriched data pipeline for search using predefined and custom skillsets: a. Text skills like entity recognition, language detection, text manipulation and key phrase extraction. b. Image skills like OCR. c. Language skills like text translation. d. Content moderation skills to block documents with incompliant content. Use the enriched data pipeline for a knowledge mining solution on business documents within an enterprise. Expose the knowledge mining solution using a bot interface for document search and consumption. Architecture !Architecture Technologies Covered !Technology Industry application Intelligent search is relevant to many major industries. Some are listed below. Retail and health care industries employ chatbots with advanced multi-language support capabilities to service their customers. Retail, Housing and Automotive industries for sales/listing. Entertainment industry uses search for relevant/contextual on-demand streaming. Pre-requisites Fundamental working knowledge of Azure Portal, Functions and Azure Search. Familiarity with Visual Studio. Familiarity with Azure Bots and Microsoft Bot Framework v4. If you do not have any familiarity with the above pre-requisites, please find below links To Read (10 minutes): Visual Studio Tutorial To Read (4 minutes): Azure Functions Overview To Read (10 minutes): Azure Search Overview To Read (7 minutes): Postman Tutorial To Do (30 minutes): CQuickstart Pre-Setup before you attend the class Mandatory To Create: You need a Microsoft Azure account to create the services we use in our solution. You can create a free account, use your MSDN account or use any other subscription where you have permission to create services. To Install: Visual Studio 2017 version version 15.5 or later, including the Azure development workload. To Install: Postman. To call the labs APIs. Course Details Primary Audience: Azure AI Developers, Architects. Secondary Audience: Any professional interested in learning AI. Level This content is designed as an intermediate to advanced level course for AI developers and/or architects. Type This course, in its full form, is designed to be taught in-person but you can also use the materials in a self-paced fashion. There are assignments and multiple reference links throughout the materials that support the concepts and skills you will learn. Length Full Course classroom training: 16 hours Related LearnAI Courses Building Intelligent Agents and Apps Course Modules Introduction – Overview of Azure Search, Cognitive Search, Scenarios and industry specific applications. Fundamentals of Azure Search. Architecture – Solution Architecture for building enterprise search solution. Cognitive Search Skillset – Applying text skills. Cognitive Search Skillset – Applying image skills. Cognitive Search Skillset – Applying Language skills. Cognitive Search Skillset – Applying Moderation skills. Build and Integrate a Bot with Cognitive Search API. Group Hands-on Lab to practice skills acquired.