Navlio retweeted
My actual eCom SEO routine:
1. Open Search Console
2. Find the top /collections/
3. Google the target keyword for each page
4. Look at the top-ranking pages with my own 2 eyes (no AI scraping tool)
5. Make each collection look like the top pages (target keyword, length, supporting entities, internal links, schema, etc)
6. Repeat for all major collections
7. Identify missing collection pages/missed KW opportunities
8. Repeat steps 3-5 for the new collections
9. Build internal links between similar collections (both old & new)
10. Make sure they're all within 2-3 clicks of the homepage
11. Build a few backlinks each month to the main collections
12. Build more backlinks to the homepage
It's mind numbingly boring and it's still the most effective way to do eCommerce SEO.
Navlio retweeted
Introducing Zod 4.5 and its flagship feature: SCHEMA COMPILATION
Just z.compile() any schema and get back a new precompiled schema that's 3-9x faster
Navlio retweeted
I just coined a new term:
Agent saturation
/ˈeɪdʒənt ˌsætʃəˈreɪʃən/
is a state in vibe coding in which a developer, intending to fix bugs and rapidly build features, begins a session by parallel-prompting multiple agents (typically more than five) using goal, ultrawork, and multi-hour sessions. While each agent performs its task, the developer continues to spawn additional agents in order to work faster. Each new agent produces the impression of working hard. Eventually, so many chats are open that the developer's own context becomes saturated. The developer loses track of which agent is doing what and ends up asking each one what it was working on. By the end of the day, none of the implemented features have been tested, no PRs have been merged, and the code shipped is of far lower quality than what a single session would have produced. The developer realizes that more would have been accomplished by working on a single feature at a time in a single chat session.
Navlio retweeted
I priced my homelab as if I had to rent it.
On-demand AWS: $49,452 a year. The electricity it replaces: $274.
That is 180x, and it is not about AWS being expensive. It is about what you are billed for.
104 vCPU and 235 GiB allocated across 22 Proxmox guests and a six-node k3s cluster. Actually doing work: 4.3 cores and 76 GiB.
In the cloud you pay for what you allocate. At home you pay for what you plug in. My machines are 96% idle, and idle is free in exactly one of those two places.
Compute is 92.8% of that AWS bill, and compute is the part I never use.
The honest version: my hardware is a sunk cost, not a zero. Amortised over five years it is nearer $80 a month than $23, which puts a rightsized cloud build within 2.1x, not 180x. The 180x is against a lift-and-shift nobody sane would perform.
You do not need a datacenter. You need one machine you are not afraid to break. My second Proxmox node is a used office cast-off running half the cluster.
Five tables, three diagrams:
geekendzone.com/posts/the-id…
Navlio retweeted
open interest on hyperliquid is $3.18b against $4.35b traded in the last day, so the book clears more than everything it holds, daily.
compare hype: $1.95b of oi on $842m of volume, about two and a half days of turnover to work through the position base.
xitter.cf/WatcherGuru/status/209…
