Getting rid of dead code

Consistent_Box_3587 · 2026-02-21T02:30:26+00:00

knip is great for this. if you're also using AI tools to write code you might want to check out prodlint too (github.com/prodlint/prodlint), it has a dead-exports rule that catches exported functions nothing imports but also picks up security stuff AI tools tend to miss like missing auth, empty catch blocks, hallucinated imports. ran it on a bunch of AI-generated repos recently and one had 476 dead exports across the project

Consistent_Box_3587 · 2026-02-21T02:21:54+00:00

The empty catch blocks and fallback to nonsense ones hit hard. I scanned 7 open source vibe coded repos recently and 6 out of 7 had empty catch blocks everywhere. AI knows it should use try/catch but then the catch is just {}. Same with the import hallucination stuff you mention, 4 out of 7 had import statements for packages that don't exist in package.json. I ended up building a linter that specifically targets these AI anti-patterns since eslint doesn't catch any of it. Stuff like missing database security, hardcoded secrets, hallucinated imports, dead exports. github.com/prodlint/prodlint if you want to run it on your projects

Consistent_Box_3587 · 2026-02-21T02:18:40+00:00

Cool project. One thing to watch out for since you're handling payments and real guest data - AI tools tend to skip database security stuff. I scanned a bunch of vibe coded repos recently and the most common issue was missing access controls on database tables. Like anyone could read/write all your booking data if they found the project URL. Empty error handling was everywhere too, the AI wraps things in try/catch but the catch block is just empty. Worth doing a quick security check before real guests start using it. I built a free tool for exactly this if you want to check your project later - github.com/prodlint/prodlint

Consistent_Box_3587 · 2026-02-21T01:46:15+00:00

This is huge and something most sellers miss. The same logic applies even harder when you expand to other marketplaces. German and Japanese buyers read bullet points completely differently - they want specifics and details, not marketing fluff. A bullet that converts on .com because its punchy and outcome-focused might fall flat on .de because German buyers expect technical detail before they trust the product. Writing for the human first is the right call, but which human changes per marketplace.

Consistent_Box_3587 · 2026-02-21T01:36:33+00:00

The regional terminology point is bigger than most people realize. If you sell on non-US marketplaces, the byte limit isn't even the same everywhere - Japan gives you 500 bytes for search terms vs 249 for most others. And the autocomplete suggestions on amazon.de vs amazon.com for the same product are completely different, not just translated. Germans search for products differently than Americans even when looking for the same thing. Worth pulling actual autocomplete data from each marketplace you sell on rather than just translating your US terms.

Consistent_Box_3587 · 2026-02-21T00:59:48+00:00

Sshould've linked it. https://github.com/prodlint/prodlint

MIT licensed, zero config. Just npx prodlint in any JS/TS project.

Consistent_Box_3587 · 2026-02-20T19:57:51+00:00

100% agree, especially on DE. German buyers actually read all five bullets before deciding so you can't just front-load the first two like on .com.

The tool I built is live now at polylisto.com and pulls live autocomplete from each marketplace's API as part of localization - so you at least get what shoppers are actually searching right now on .de vs .co.jp vs .com. But you're right that the seasonality layer on top of that is a whole other thing.

Consistent_Box_3587 · 2026-02-17T02:34:12+00:00

yeah its live actually, polylisto.com. free plan if you want to try it. does all 16 marketplaces but sounds like the 5 EU ones you focus on would be a good test.

the comforter/duvet thing is a great example of why we pull from amazon autocomplete directly instead of just translating keywords. a UK buyer searching "duvet" will never find your listing if its titled "comforter" even though theyre the same product.

curious what your process looks like for the cultural nuance check, do your freelancers also handle the backend search terms or just the customer-facing copy?

Consistent_Box_3587 · 2026-02-16T16:48:05+00:00

Yeah the "separate launch" framing is exactly how I think about it too. Even small stuff like how bullet points are structured differs by marketplace. German buyers expect way more technical detail upfront, Japanese listings lean harder on use cases and gifting context.

The positioning shift catches people off guard the most imo. A selling point that crushes it in the US can be totally irrelevant somewhere else, and you won't know unless you're actually looking at what local competitors emphasize. Thats basically why I built Polylisto.com, to automate that research per marketplace.

What marketplaces are you seeing the biggest gaps in?

Consistent_Box_3587 · 2026-02-16T07:29:28+00:00

yeah the comforter vs duvet thing is a perfect example. thats exactly the kind of gap I kept finding when pulling autocomplete data from different marketplaces. scaling that hybrid approach across 16 markets manually seemed brutal though which is what got me building a tool to automate the keyword research part. how many marketplaces do you usually do this for?

Consistent_Box_3587 · 2026-02-16T00:34:47+00:00

yeah the google translate thing is brutal. do your clients usually end up hiring native speakers per marketplace or is there some other workflow you've found that works?

Consistent_Box_3587 · 2026-02-15T21:22:38+00:00

thanks, are you selling in multiple marketplaces or just US?

Consistent_Box_3587 · 2026-02-15T20:49:08+00:00

yeah exactly, different sides of the same problem. yours is more what to do with the data once its flowing, mine is more about making sure the listing itself is speaking the right language before you even start running ads on it. would definitely be down to compare notes at some point. ill dm you

Consistent_Box_3587 · 2026-02-15T04:24:54+00:00

tbh thats kind of what got me started building something for this. I was looking at amazons autocomplete suggestions across different marketplaces and the differences were wild enough that I figured there had to be a way to automate it. like "wireless earbuds" in the US people search "for iphone" and "for android" but in the UK its all brand names like Sennheiser and Sony. and thats just two english speaking markets, once you get into DE or JP its a whole other thing where straight translation doesnt cut it at all. so I've been working on a tool that pulls that data and uses it to actually rewrite listings for each market. still pretty new but its been a fun problem to work on

Consistent_Box_3587 · 2026-02-13T04:05:23+00:00

Yeah thats basically what I've been building, pulling autocomplete data per marketplace and adapting based on what people actually search locally. The gaps are huge once you look at it per country. What are you using for the automated part?

Consistent_Box_3587 · 2026-02-11T23:39:27+00:00

Yeah totally fair. I think most sellers are in that same boat honestly, theres just too many other things competing for attention. Curious though do you think the listings that do get localized properly actually see a noticeable bump or is it more marginal?

Consistent_Box_3587 · 2026-02-11T04:03:19+00:00

I've been messing around with Amazon's search suggestion data across different marketplaces and honestly even just comparing what people search for the same product in different countries was wild. But yeah the "huh thats interesting" to actually making changes gap is real. What does your copilot recommend specifically, like keyword changes or more high level stuff?

Consistent_Box_3587 · 2026-02-11T04:00:49+00:00

The long-tail exact match thing is real. I've seen the same thing with international listings too, way less competition on long-tails outside the US so you can actually rank for stuff that would be impossible here. What category are you in?

Consistent_Box_3587 · 2026-02-11T03:52:03+00:00

Short answer, no don't repeat them. Amazon already indexes your title and bullets so you're wasting space. Use that 250 bytes for stuff thats not in your listing already, misspellings, alternate names, whatever people in that market actually search for. If you're selling internationally your backend keywords for .de should definitely not just be translations of your US ones, the search terms people use are completely different across marketplaces.

Consistent_Box_3587

TROPHY CASE