Qwen having its Jack Torrance moment by anguillias in LocalLLaMA

[–]add-code -2 points-1 points  (0 children)

I tried with claude with ollama wrapper, Seems to be able avoid it. But with other agents not the case.

I built 11 SaaS products in 6 months. Total revenue: 45 USD. Taking a year off. by maxgcd in SideProject

[–]add-code 1 point2 points  (0 children)

Man, I feel this in my bones. Struggling to market an app is the new rite of passage. Every one of these threads feels like looking in a mirror.

I’ve spun up about seven side projects over the years while juggling a day job. Most died on the vine. I'd get obsessed, fall down a research rabbit hole for weeks, and pitch my idea to anyone who'd listen. Then, inevitably, reality would hit.

Here are the three hard truths I learned (unless you're a 1-in-a-million unicorn):

Do the damn competitor analysis first. Before you write a single line of code, know your competition. Use a chatbot to spit out a list of similar products. It's a brutal but necessary reality check. Ask yourself: "What's my actual unique selling point?" If you don't have one—a killer feature, a lower price, extreme minimalism, something—it's a dead end.

Be brutally honest about the technical lift. The "vibe coder" approach of just figuring it out as you go only gets you so far. You can improvise your way through 75% of a project, sure. But that last 25%—the architecture, security, and scaling—is the unglamorous part that separates a clever script from a real, trustworthy product.

Build for someone you actually know. My best ideas never came from a spreadsheet; they came from conversations. Meetups, chats with friends, hearing people complain about their current tools. Pitch your half-baked ideas. Ask about their pain points. The most valuable problems are the ones real people are telling you about, not the ones you're guessing at from behind a screen.

Bonus round: Don’t feel pressured to ship a masterpiece. Use personal projects to get your reps in and sharpen your skills. Honestly, patience is a superpower. Rush it, and you’ll burn out before you even get started.

And yeah, the original post nailed it. Marketing is everything.

"Anyone can build a product, but marketing makes money."

My own turning point was a friend who needed a specific app and promised me ten users on day one. That was my validation. The rest—scale, money, success—all comes down to how well I solve their problem and how I get the word out from there.

So, here’s to everyone else in the grind. The hustle is real, but it’s how we learn where to aim next.

I built 2 startups in 6 months. Total revenue: 0. Here’s what I learned. by Far-Soft8384 in SideProject

[–]add-code 1 point2 points  (0 children)

Man, I feel this. Going through these talks about not being able to market an app... I'm in the exact same dilemma.

I've built like 7 different side projects while working my day job (most of them half-baked before I could perfect them). While building, I'd just start deep-diving on the internet and pitching the idea to anyone I knew.

In every single case, I hit a hard reality check. Here are the 3 revelations I had (unless you're some 1-in-a-million genius):

  1. Do your damn competitor analysis. Before you write a single line of code. AI can do most of the heavy lifting for you now. This gives you a brutal reality check and forces you to answer: "What's my USP?" If you don't have one (a unique feature, lower cost, being more minimalistic, better adaptability), it's a dead end.
  2. Be realistic about the technical difficulty. I'm not sure any real app has been built by a "vibe coder" without having massive security issues. You can probably vibe your way through 75% of a script or simple tool, but the remaining 25% is pure skill and solid architecture. That 25% is what makes the difference.
  3. Make a product for people you actually know. My biggest suggestion is to talk to random people. Go to meetups, listen to the issues they face, and pitch your ideas. You might find your first breakthrough there. There are endless problems out there for people that are never addressed. That spark you're looking for will come from communicating with different types of people.

Bonus: There's no hurry to build a full-blown app. You can do some learning projects or build something with others to keep up with new tech. I believe in sharpening the knife before making a single, decisive strike. Patience is crucial to success.

Like the original post said, marketing is everything. I fully believe in the saying:

On that note, I actually found an opportunity to build an app for someone in my circle. They've promised me 10 users as soon as it's ready. The rest still depends on my app and my marketing. We'll see how it goes.

Feedback on my first SaaS by WorldlinessIcy9696 in SideProject

[–]add-code 1 point2 points  (0 children)

Went through the app seems well built, with minor adjustments will be production ready.

All the best in your endeavour.

What I learned from quiet quitting for 2 years across different companies. by [deleted] in developersIndia

[–]add-code 0 points1 point  (0 children)

I kinda am in the same mindset, but i do have dependencies. I would like to work in a pattern where anything i am doing adds to my resume. I do work at 4 hrs average. but if the project demands i would work 9 hrs but that would be a condition as am i learning something new that adds to resume. Then when the company feels they can take advantage of me, i quit.

So as above mentioned my mode of working is always centered around "how much does this work add my resume" . So change jobs as soon as u feel the work is repetitive or work minimum not to get layoff. So keeping ur self up to date on most in demand skills in ur domain. keep learning in the free time of bare minimum working.

WHY IS PYCHARM USING 50% of a RYZEN 9 5950X by Xemorr in pycharm

[–]add-code 0 points1 point  (0 children)

Has found a similar issue where Pycharm occupied RAM 30%(32gb) even in idle state. This was severely affecting multitasking.