Alper Tayfur

@nikolas_dimitroulakis You’re asking the right questions at the right time. From patterns I’ve seen across successful open-source dev tools, a few hard-earned lessons keep repeating: 1. Be opinionated from day one The biggest early mistake is trying to please everyone. Healthy projects stay clear about: what problems they will solve what’s explicitly out of scope Open source doesn’t mean...

Hello @gleedo This is a really solid reality check, not pessimism. My take: vibe coding is great for getting to truth faster, not for skipping fundamentals. You’re right that the build is no longer the hard part. Shipping an app is almost table stakes now. The hard parts didn’t disappear — they just moved: understanding users deeply deciding what not to build handling edge cases, reliability,...

@alonhmdt This is such a wholesome use of “vibe coding” 😄 Also, building it as a gift instead of a startup pitch makes it way cooler. I really like that you leaned into the linear, no-algorithm surprise aspect. That feeling of just turning something on and letting it run is exactly what streaming lost along the way. The YouTube IFrame workaround for a continuous, ad-free stream is a great find...

@vik_sh This lines up with what I’ve been seeing too. Mobile is great for discovery — scrolling listings, saving jobs, quick interest — but when it comes to actually applying, people still seem to switch to desktop. Resumes, cover letters, forms, attachments… it’s just more comfortable and less error-prone on a bigger screen. So “mobile-first” might be true for browsing, but not for completion...

Thank you for this post @busmark_w_nika . This is a solid list already 👍 One thing I’d add: be consistent in how you show up. If someone clicks your profile after seeing a comment, they should immediately understand what you’re into and why your opinion matters. Random activity across unrelated topics can dilute that. Also, quality > quantity in comments. A few thoughtful replies people upvote...

Possible, but not likely in the way people imagine. Money and compute are accelerating insanely fast — that’s the part that is undeniable. We’ll almost certainly get models that feel more general, more autonomous, and more capable across domains in the next 5 years. But the science side is the bottleneck. We still don’t really understand: reasoning vs pattern matching long-term learning without...

Hello Matt, Yes, there are basically two “defacto” approaches now, depending on whether you want visual eyes (screenshots) or structured inspection (DOM/DevTools). 1) Best for “bad padding/alignment”: Playwright MCP or Chrome DevTools MCP Instead of you screen-capping, the model can: open your page inspect DOM/layout/accessibility tree read computed styles / bounding boxes take screenshots when...

I mostly see a difference between experimentation and avoidance. Early on, trying multiple things quickly is healthy. But when “Founder” repeats 6–10 times with no visible outcomes, it signals a lack of follow-through and comfort with the hard scaling phase. For me, it reduces credibility around execution depth. On LinkedIn, listing every short-lived venture usually hurts more than it helps....