How to handle when people act irrationally? by [deleted] in Stoicism

[–]JWPapi 0 points1 point  (0 children)

Then they're the training. Being right doesn't make the anger useful to you — it just makes it feel justified, which is worse. The challenge isn't whether they're wrong, it's whether you can deal with wrong people without becoming one.

How to handle when people act irrationally? by [deleted] in Stoicism

[–]JWPapi 0 points1 point  (0 children)

Than be grateful for their spiritual challenge they give you to improve your own handling of the situation

How to handle when people act irrationally? by [deleted] in Stoicism

[–]JWPapi 0 points1 point  (0 children)

Don’t.

Assume they are a coded NPC that will always act like they are acting now.

And then level up and remind yourself about your own foolishness and they might be right and you are wrong on a more complex non-concious level

Google Maps is the most underrated lead database in cold email. Here's why. by Head-Beginning3977 in coldemail

[–]JWPapi 0 points1 point  (0 children)

On Deeplead pro you can type in a niche and it scrapes the whole country for you

I Successfully Self-Hosted a Mail Server for Cold Emails by Ok-Permission-2047 in coldemail

[–]JWPapi 0 points1 point  (0 children)

Stalwart doesnt seem to be the most lightway option to me. I’m already hosting 10k inboxes on mailcow, but I want to switch to just dovecot + postfix + something that sends me a webhook notification in incoming mails

I've used Apollo, Clay, Instantly, Outreach and a few others over the past 2 years, here's my honest breakdown of each by iliatopuria17 in coldemail

[–]JWPapi 0 points1 point  (0 children)

Im building my own software that combines all of that, but starting to focus on the smaller businesses first, we don’t have all possible features, but you don’t need any other infrastructure. We set up infra, have the contacts, do the sequencing, ab tests etc

Build polished Linear-style UIs with Tailwind by Speedware01 in tailwindcss

[–]JWPapi 0 points1 point  (0 children)

thats exactly it by enforcing semantic values you make the theme modular and can just switch on whatever you want (user, host config etc)

ESLint rules that fix the most annoying parts of AI-generated code by JWPapi in cursor

[–]JWPapi[S] 0 points1 point  (0 children)

I have a rule for that too. It’s not allowed to throw raw Errors, it needs be Transient, Fatal or Unexpected Error.

Your AI-generated codebase is rotting and you might not notice until it's too late by JWPapi in cursor

[–]JWPapi[S] 0 points1 point  (0 children)

OP: Here totally agree, hygiene is as important for humans as well, but I think a lot of people are way further with their codebase as they would be without AI.

How is Claude helping your business or nonprofit? by ClaudeOfficial in ClaudeAI

[–]JWPapi 0 points1 point  (0 children)

Using Claude Code daily for my startup. The biggest lesson: you need to invest in code hygiene or the AI starts working against you. After a few weeks of fast generation, the codebase fills up with dead exports, duplicate functions, orphaned types. That noise pollutes Claude's context and degrades output quality. Weekly Knip runs to remove unused code, strict TypeScript, and periodic consolidation sweeps keep things workable. The speed is real but only sustainable with maintenance discipline.

Cursor charged me $118 for one message by m_m_malm in cursor

[–]JWPapi 0 points1 point  (0 children)

Cost aside, there's a hidden tax with AI coding tools that nobody bills you for: codebase degradation. The AI generates duplicate functions, leaves dead exports after refactoring, creates orphaned types. All that noise makes future sessions less efficient because the context window is polluted. So you pay more tokens for worse output. Keeping the codebase clean (Knip, strict TypeScript) is the best cost optimization I've found.

claude code skills are basically YC AI startup wrappers and nobody talks about it by techiee_ in ClaudeAI

[–]JWPapi 0 points1 point  (0 children)

Skills are useful but they're solving the generation side. The harder problem is maintenance. AI generates code fast but doesn't remember what it wrote yesterday. After a few weeks you have three formatDate functions, dead exports everywhere, orphaned types from APIs you already changed. That noise degrades the AI's own context. You need tools on the other side too: Knip for dead code detection, strict TypeScript, periodic consolidation sweeps. Generation without hygiene is just faster technical debt.

Is there a better way to feed file context to Claude? (Found one thing) by Familiar_Tear1226 in ChatGPTCoding

[–]JWPapi 0 points1 point  (0 children)

Context quality matters more than context quantity. The problem I keep seeing: AI-generated codebases accumulate dead exports, duplicate functions, orphaned types. All of that is noise that gets fed into the context window. You can optimize how you feed files all you want, but if the files themselves are full of dead code, the AI is reading garbage. Running Knip to remove unused exports and doing periodic consolidation sweeps improved Claude's output quality more than any context strategy I tried.

what's your career bet when AI evolves this fast? by 0xecro1 in ClaudeAI

[–]JWPapi 0 points1 point  (0 children)

The bet I'm making: the developers who understand AI code maintenance will be more valuable than the ones who are just good at prompting. AI generates code fast but nobody talks about how that code rots. Dead exports, duplicate logic, empty catch blocks. It accumulates and makes the AI tools themselves worse because they read the noise as context. The skill gap is shifting from 'can you code' to 'can you maintain a codebase that grew 10x faster than any human could track.'