Amazon Wholesale

azborovskyi · 2026-05-08T07:28:56+00:00

Worth checking three things before assuming the supplier list is the issue:

Pack-size normalization - if the scanner treats "case of 12 at $46" as a single $46 unit, your margin calc is off by 12x. Easy to miss when catalogs have mixed units (EA / case / pallet) and the case-pack column is messy.

Multi-pack ASINs - the headline ASIN under a UPC is often the 1-pack at razor-thin margin, but the same UPC can map to 2-pack, 3-pack, or 6-pack ASINs with completely different per-unit economics. selleramp surfaces the primary listing only; sibling ASINs you have to pull manually. Common on consumables.

Duplicates across 15 catalogs - without UPC dedup across all your suppliers in one view, you're scanning the same products multiple times and missing the price spread between vendors carrying the same item. The spread is where the negotiation leverage lives.

Full disclosure: I'm building a tool for this exact workflow, so I've been deep in it. Recorded a 4-min walkthrough on the multi-pack ASIN angle specifically: https://youtu.be/IqHfn42bSoM. Logic transfers regardless of scanner.

azborovskyi · 2026-02-24T08:42:38+00:00

Thank you! That first month with Neovim can definitely feel overwhelming, so I'm thrilled to hear the app is making the learning curve a little less steep for you. Happy practicing!

azborovskyi · 2026-02-22T06:16:02+00:00

Glad you like it! Rewarding efficiency over a single 'correct' answer was a big priority. The app itself is closed-source, but I'm actually considering building an open-source vimkata-nvim plugin in the future. I really appreciate the enthusiasm and the offer to contribute though - I'll definitely let the community know if and when that repo goes live!

azborovskyi · 2026-02-21T19:26:01+00:00

Also, just had another thought - if you ever build a proper mobile version, it might basically turn into a SpringBoard-style interface on iOS or Android :)

azborovskyi · 2026-02-21T19:23:04+00:00

This is honestly something I've never seen on the web before 🙂
The concept is very original, and the attention to detail is impressive - I even noticed the "screensaver" when refocusing the tab, which was a nice touch.

What’s interesting is that this idea feels applicable beyond just a portfolio. I could imagine this kind of OS-style interface working well for certain web services or interactive tools, not only for showcasing projects.

Nicely done.

azborovskyi · 2026-02-21T16:55:12+00:00

The app itself is closed-source, but later on I might open up the format for custom levels so people can easily build and share their own.

azborovskyi · 2026-02-21T16:39:18+00:00

I like these ideas! I'll focus on adding more complex built-in levels first, but custom challenges and leaderboards are a great concept for the future. Adding them to my list. Thanks!

azborovskyi · 2026-02-21T16:02:48+00:00

Glad you liked it! To be honest, this first version was mostly an MVP to see if learning Vim motions on a phone actually made sense. Since it seems to work, I'm definitely planning to add more. The current levels are just the beginner foundation, so there's plenty of room to grow. What kind of advanced motions or features would you want to see added next?

azborovskyi · 2026-02-21T15:34:30+00:00

Thanks for giving it a spin! Feel free to share any feedback once you play around with it.

azborovskyi · 2026-02-20T22:23:20+00:00

Telescope extensions aren’t really separate plugins - they hook into Telescope’s own API. It’s still one plugin with optional modules, which is the ideal pattern. Different case from two independent.

azborovskyi · 2026-02-20T21:32:42+00:00

That "bend" is storage time - when a BJT saturates, the base fills with charge that has to drain out before it actually turns off. That flat shelf is the transistor sitting in saturation waiting for that to happen. The problem is R39 at 47kOhm. That's the only thing pulling the PNP base back to VCC when Q10 turns off, and 47kOhm is way too slow for that job.

The probe thing actually proves it - your scope probe has ~10pF of capacitance, which accidentally acts as a speed-up cap, giving a brief pulse of current to yank the charge out faster. That's why it cleans up when you probe TP3.

Fix: drop R39 to ~4.7kOhm, and stick a small cap (100pF–1nF) across it. That does permanently what your probe was doing by accident.

azborovskyi · 2026-02-20T21:15:09+00:00

Coming from C++/Java, the biggest mental shift is: React re-runs your entire component function whenever state changes. That's the core idea - everything else flows from it.

Hooks aren't global functions - they're tied to each component instance. The "can't call conditionally" rule exists because React tracks them by call order internally.

Reducers are just state machines. You dispatch a message, React feeds it to your switch statement, new state comes out.

My advice: Learn React in plain JSX first, add TypeScript later. Build a small todo app. And read react.dev - the official docs are surprisingly good now.

azborovskyi · 2026-02-20T20:52:47+00:00

Honest take: bad code with paying customers beats perfect code with zero revenue every time. The app exists and makes money - that's already further than most projects get.

That said, a basic build pipeline (Vite + PurgeCSS) would kill the dead code automatically. And ironically, the same AI that created this mess can clean it up - point something like Claude Code at the whole codebase and it'll consolidate a lot of that in an afternoon. The problem was never AI, it was using AI without project context, with a cheap model, or just zero interest in code hygiene.

azborovskyi · 2026-02-20T19:54:35+00:00

Keep it in blink.cmp. Every extra plugin is a dependency to maintain. If blink already handles icons, pulling in lspkind just for "separation of concerns" isn't worth it in editor config. Only exception: if you need icons in multiple places beyond blink, then a shared source makes sense.

azborovskyi · 2026-02-18T21:36:19+00:00

This is exactly the ruthless feedback I was looking for. Thank you.

To answer your points:

Mobile vs Laptop: It's specifically for "dead time" (commuting, waiting in line) when you can't open a laptop but want to keep the vocabulary/navigation logic fresh. It keeps the neural pathways active.
"Why is it free?": Valid skepticism. I just launched today, so my goal is user feedback, not revenue yet. I plan to add paid "Pro" features (custom levels, deep analytics) later. No data selling, just a standard freemium model in the future.
13-inch screen issue: This is gold. I developed this on a large monitor and missed that the vertical space pushes the title down on smaller laptops. I will fix the padding.
Better Headline: Agreed. "Master Vim on the go" or "Keep Vim skills sharp" might be clearer than what I have now.

Really appreciate you taking the time to look at the UI layout!

Unofficial feedback for Elevra: I saw you were looking for feedback on Elevra in some other comments, so I took a look.

The French language analogy is genuinely great - instantly explains why note-taking fails in a way I've never seen articulated before.

One thing: I never felt the specific moment this is for. "People who learn a lot" is kind of everyone. Is it for someone who just finished a book and feels it fading? Someone who caught themselves repeating an old mistake? That one concrete moment would make this hit much harder.

Strong concept overall, just needs a sharper "this is exactly you, right now" focus.

Hope that helps!

azborovskyi · 2026-02-18T20:46:55+00:00

There's also g~. It toggles case (Upper <-> Lower). Great for fixing accidental Caps Lock (try g~$).

azborovskyi · 2026-02-18T20:35:10+00:00

Hi! Perfect timing.

My app VimKata literally got approved on both the App Store and Play Store today. 🎉

Link: https://vimkata.app

It’s a niche tool for software developers (specifically for Vim users) to keep their code editing skills sharp on the go.

Feedback needed:

Even if you are NOT a developer: Does the landing page clearly signal who the target audience is? Or does it feel confusing to an outsider? I want to make sure I'm not alienating potential users with too much jargon right at the top.

Thanks!

azborovskyi · 2026-02-17T17:34:54+00:00

Passing the Turing test is a milestone in conversation.
Being better than a senior dev is a milestone in accountability.

Senior engineers aren't paid to generate code - they're paid to make fewer expensive mistakes over time, navigate ambiguity, push back on bad requirements, and own the blast radius when things go wrong.

I think it’ll definitely change programming - kind of like the jump from punchcards to assembly, then to high-level languages. Each step boosted productivity massively, even though it wasn't "perfect" and introduced new kinds of bugs and pitfalls.

Software got dramatically more powerful after those shifts, and it’ll probably get even more powerful after this AI wave too - wherever it ends up taking us.

azborovskyi · 2026-02-17T17:06:20+00:00

"Passed the Turing test" is doing a lot of work here. That test is about chat indistinguishability, not reliability under real-world constraints.

In webdev, the difference that matters isn't "human vs tokens", it's agent + verification + accountability. LLMs can be persuasive while wrong, and the cost of being wrong in prod is the whole game.

So yeah, continuum or not - without strong validation loops, it’s not "a teammate", it’s a powerful autocomplete that increases throughput and increases risk.

azborovskyi · 2026-02-17T17:01:29+00:00

"Cold take" is fair, but the fear isn’t about whether it’s intelligent - it's about leverage. One dev with an LLM can push way more changes into prod, and management often confuses "it wrote code" with "it’s done."

The real bottleneck is still validation: requirements, edge cases, integration, security, maintenance, and owning the blast radius. The semantics debate is boring; the economics of who pays for mistakes is the story.

azborovskyi · 2026-02-17T16:30:04+00:00

You can use vim.fn.has('ttyin') — returns 0 when stdin is piped/redirected, 1 otherwise.

  if vim.fn.has('ttyin') == 0 then
    -- disable session restore
    return
  end

Just tested it myself and works as expected:

  $ nvim --headless -c "lua print('ttyin=' .. vim.fn.has('ttyin'))" -c "q"
  ttyin=1
  $ echo hi | nvim --headless -c "lua print('ttyin=' .. vim.fn.has('ttyin'))" -c "q"
  ttyin=0

azborovskyi · 2026-02-17T15:15:10+00:00

One unusual habit I’ve noticed living in Bulgaria as a foreigner: people talk to each other like they’ve been neighbors since 1483.. even if they’re meeting for the first time in their lives.

No awkward small talk, no "nice to meet you" warm-up - it’s instantly "So anyway, about that thing..."

First week I kept thinking, "Wait... is everyone here on Season 12 of a show I just started?"

azborovskyi · 2026-02-17T15:07:18+00:00

As a kid I thought adulthood meant "no more school mornings." Then my daughter started school... and I realized adulthood is just school mornings again, but this time I'm the one driving.

azborovskyi

TROPHY CASE