Your client's 'vibe code' & the playbook for getting paid (finally!)
Here is this week's digest:
Ask HN: Client took over development by vibe coding. What to do?
A developer is dealing with a client who's taken over project development using AI-powered "vibe coding," injecting 10,000 lines of code in a week and compromising performance and maintainability.
Key strategies shared include:
- Shift Ownership: Treat the client's AI-generated code as their responsibility for long-term maintenance and fixes, clearly defining boundaries for different code areas.
- Monetize Maintenance: Anticipate future debugging needs and prepare to charge premium rates for untangling the inevitable "slop code."
- Set Boundaries: Establish contractual limits on client code contributions, potentially requiring AI-generated specifications rather than direct code, or implementing strict pull request reviews.
- Focus on Core Expertise: Prioritize critical infrastructure (DevOps, architecture) where human expertise is indispensable, letting the client learn the hard way about their self-inflicted technical debt.
- Consider Exit: If a significant values mismatch or trust breakdown persists, documenting issues and preparing for a professional exit might be the best long-term solution.
Ask HN: European Tech Alternatives?
Many individuals are seeking European alternatives for software and hardware due to concerns about data privacy, digital sovereignty, and a preference for supporting local EU companies. A key challenge is the lack of maintained directories, as the widely used european-alternatives.eu appears unresponsive.
Useful resources suggested include:
switching.software: For ethical and easy-to-use alternatives (broader focus).euro-stack.com: A newer EU-focused directory, though with some reported categorization issues.eucloudcost.com/providers/: Specific to EU cloud providers.- GitHub
awesome-privacyandawesome-selfhostedlists: For general privacy and self-hosting options. - Hetzner and Scaleway: Frequently recommended for EU-based cloud VPS, object storage, and cold storage.
The discussion also highlighted the complexity of defining "EU-based" for companies with international operations and emphasized jurisdiction's importance for data processing.
Ask HN: How do you handle clients who don't pay on time?
Effectively managing late client payments requires a firm, multi-pronged approach. Key strategies include demanding upfront payments or offering discounts for early settlement, and establishing clear payment terms with explicit consequences. When invoices are overdue, move beyond automated reminders to direct communication, like calls to accounts payable. Be prepared to implement late fees, suspend services, or withhold deliverables. Crucially, recognize that persistent late payment often signals a client's financial distress, making a perceived "relationship" less valuable than securing timely revenue. Always be ready to enforce contract terms and, if necessary, disengage from non-paying clients.
Ask HN: How do systems (or people) detect when a text is written by an LLM
Detecting AI-generated text often relies on human pattern matching, identifying common stylistic cues like overuse of em-dashes, specific phrases (e.g., "It's not X, it's Y," "delve," "The Core Insight"), verbose lists lacking substance, and a monotonous tone. While system detectors using ML or perplexity exist, they face an "arms race" against evolving LLMs, making watermarking a potentially more reliable but less common approach. A pragmatic shift suggests evaluating content solely on its merit or demanding proof of human process (like version history or keystroke logging) instead of relying on fallible detection methods.
Ask HN: How do you handle marketing as a solo technical founder?
Solo technical founders often build great products but struggle with marketing. Key advice centers on shifting from a purely "builder" mindset to actively engaging with potential users.
- Engage Customers Early: Talk to 30-50 potential users before building to validate pain points and ensure product-market fit. Build what they need.
- Persevere & Support: Don't give up after initial quiet days. Once you have customers, make direct contact, understand their needs, build requested features thoughtfully, and offer excellent support. This fosters word-of-mouth.
- Find Your Niche Distribution: Explore specific channels beyond generic social media. Think direct outreach via forums, LinkedIn, subreddits, app stores, or leveraging SEO with free tools.
- Marketing is a Skill: It's not just "building." Consider marketing a consistent "gym" routine. For a potential marketing co-founder, a paid trial period with clear deliverables can de-risk equity decisions.
Add a comment: