... rabbit hole on luxury cigar humidors of all things. Weird category to end up in, but it turned out to be a pretty good case study in a pattern I think shows up everywhere in product design. At the entrylevel of that category, almost every product looks and performs about the same. But once you get into the higher tier, the marketing copy across brands starts converging on the same vague language (premium materials, precision engineering, timeless craftsmanship) while ... ... actual functional differences get harder to spot unless you know exactly what to look for. In that specific case it turned out to be things like active

... always thought having a cheap entrylevel plan was necessary to catch hesitant buyers. But after struggling with flat sales despite copy rewrites removing that budget option was what finally worked for us. Instead of boosting signups the cheapest tier was just acting as a safety net that kept users from choosing the product version that provided real value. Curious if other founders have experienced this did removing your cheapest option helps or hurt your overall revenue ...

... them grow into it over time, review their code, build them up. Now with AI handling a lot of basic implementation well, curious if that math still holds. Is anyone still bringing on interns or junior developers for entrylevel coding work, or has AI quietly replaced that hiring category for a lot of teams already. Genuinely trying to understand if this is still a real starting point for someone entering the field, or if that

... difficult to explain in plain text to AI. But with chrome in claude, it was a dream. - AI confuses some variables and enum s lower and upper cases. Keep an eye on it. - If you can only afford entrylevel developers, AI can do a way better job instead. I still think talented and experienced developers have an edge. - After significant development is done, ask AI to audit the whole repo on certain parameters. It will find out many gaps ...

... from Nika(@busmark_w_nika): @ceciliatran  Can you give any example of the most unusual positions you have seen because of AI rise? Comment from Anneliese Niebauer(@anneliese): @henrikpedersen  love this POV. youth has been wasted on entry-level

... from Nika(@busmark_w_nika): @allurepixel  I think it is not certainly perfect. Even when I want something to code, AI will mess it up somehow :D Comment from Henrik Pedersen(@henrikpedersen): @busmark_w_nika  Exactly passive vs active is a cleaner way to put it. The moment AI acts as you rather than for you, the trust equation changes completely. Comment from Nika(@busmark_w_nika): @flowti  especially, when AI agents will do most ... ... stay the same (same data, same location, etc) from one moment to the next... NOPE. I don't even have plans to integrate AI even as an assistant. Comment from Nika(@busmark_w_nika): @couldashouldawoulda  :D Teenage vs

... took us 3+ years to reach meaningful traction, and we were making $2k MRR in the first 2 years. Unfortunately, there's no formula to know whether you are on the right track or running a zombie. Sunk cost vs. strategic persistence. You bet with your time. 9. SaaS multiples are often fantasy, especially for smaller businesses. If you are below $1M ARR and/or have no aggressive growth potential, do not expect 7-12x multipliers. 10. Lifetime deal buyers ... ... what actually moved the needle. 14. Technical complexity doesn't guarantee success Building more features, next feature fallacy, reaching feature parity with competitors

... with the time versus who isn t. As a beginner I see code like a puzzle a very large and colourful one, and that you have to adapt to the puzzle as or if it changes or grows. Every entry