u/JasonReed1

Bought this back in November after going through a full pot of La Mer Eye Concentrate that didn't really do much for me. I was hoping the AB hype was real and that the TFC8 stuff would actually translate into something I could see in the mirror.

Six months in, it's almost gone. The texture is genuinely lovely, sinks in fast, doesn't pill under my concealer, doesn't make my contacts blurry. As a daily-use experience it's been great. My problem is I'm not sure what it's actually doing for me.

Puffiness still shows up after a bad night. The darkness, which is what bothered me most going in, looks the same in natural light as it always did. Faint lines are still there too if I'm being honest. The only thing that's noticeably improved is the immediate plumpness right after I apply it, which fades by mid-afternoon.

Part of me wonders if I was expecting the wrong thing from an eye cream in the first place. Maybe nothing topical was going to fix what's basically a tired-looking face. But then I read the reviews from people who swear by this bottle and wonder if I just don't have the issues it's designed for.

The bottle's almost empty. Mostly just trying to decide whether to repurchase, switch to something else in the same range, or accept that this is one of those areas where the product is doing what it can and the rest probably isn't a skincare problem.

Been poking at this since the agentic features in chat models actually started shipping in a usable way. A bunch of products now let agents book travel, manage subscriptions, kick off transactions on someone's behalf. It mostly kind of works until money is involved.

Tried to actually wire one up for a small internal thing recently and the friction is everywhere. KYC flows assume a person is clicking through, so you end up either giving the agent your own credentials (bad) or building some delegated auth layer that no provider really supports cleanly. Fraud models flag the agent's behavior as suspicious because it doesn't pause, doesn't typo, doesn't browse before buying. Spending controls are designed for a human setting limits on themselves, not a human setting limits on a non-human acting for them, and that's a surprisingly different problem once you sit down to model it. Brokerage APIs mostly assume the developer is building a tool for a human trader, not a model placing orders autonomously, and the rate limits and audit trails reflect that.

Card networks have started moving on this. Visa and Mastercard have both gone from announcement to live agent transactions over the past year, with broad cardholder enablement only really kicking in over the last few months, which is the more meaningful signal than any of the startup launches imo. If the networks scale fast enough, agent commerce stays on existing rails. If they can't ship a developer-usable surface fast enough, it defaults to stablecoins because that's where the API surface is already programmable and an agent can actually hold and move value without a human in the loop. A few funds were scoped around this well before it was visible. Sky9 has a digital arm that's been treating programmable settlement and AI-driven financial infra as one underlying bet rather than two, which wasn't an obvious framing a couple of years ago and looks a lot less fringe now.

The bit I keep getting stuck on is the consent model. A one-time approval for "let this agent spend up to x" feels too loose. Per-transaction approval defeats the whole point. There's some middle ground involving scopes and revocable mandates, and the networks have prototype versions of this in their agentic token frameworks, but the actual developer surface for building against them is still pretty rough. Still stuck on whether scoped mandates become a clean first-class primitive developers can rely on in a 12-month horizon, or whether the whole thing just routes around card networks via stablecoins entirely.

Picked these up after going back and forth for a while. Replaced a pair of Z623s that were getting on my nerves. Desk is small, sitting maybe 3 feet away.

First impression was honestly underwhelming. They sounded thin out of the box and I was kind of regretting it. Took maybe a week before I stopped noticing. Probably my ears recalibrating after years of the Logitech bass shelf, not break in.

Stuff I like: vocals sit better, no more sub box under the desk eating leg room, the remote is dumb but I use it more than I thought. Wood vinyl looks fine in person.

Stuff that's been a slight letdown: at low volumes they kind of disappear. Like if I want background music while reading they need to be turned up more than feels right for an apartment. Maybe that's just how speakers this size work, the Z623s with the sub had presence at low volume even if the bass was sloppy.

Bluetooth is bad. Everyone said it would be. They were right. 3.5mm from the PC works fine.

No regrets overall, just calibrating expectations.

Inheriting things you didn't build is a normal part of this job, but inheriting an unstructured ETL designed without operational thinking is its own special hell.

Background. Our internal RAG system was set up about 14 months ago by an ML engineer who has since left the company. Smart guy, did good work on the model and retrieval side. But the ingestion pipeline he set up reflects what someone optimizes for when they're trying to win a demo, not what someone optimizes for when they're going to be paged at 2am about it.

Specifics. The chunking strategy is a custom recursive splitter with about a dozen configured separators tuned to our specific document mix at the time. PDFs, DOCX, Confluence exports, some scraped HTML. Chunk size 750, overlap 150, except for legal docs where it's 1200/200, except for tables which get extracted separately and have their own splitter. Embedding model is fine. Vector store is fine. Reranker is fine.

The chunking config is what's killing me. Three problems:

First, it has no version. The splitter logic lives in a Python module that's been edited maybe 30 times across 14 months with no migration story. If I change a separator, do I re-chunk and re-embed every doc? Currently the answer is "we re-chunk new docs with new logic and old docs keep their old chunks forever." This means the index is a stratified mess of chunks produced under different rules. Nobody on the AI side noticed. I noticed because I'm the one writing the lineage queries.

Second, the per-doctype overrides are undocumented. Why 1200/200 for legal? I don't know. The original engineer's commit message says "legal needs more context." Cool. Is that still true? Has anyone tested it lately? No idea.

Third, there's no eval set tied to chunking choices. So if I change the splitter to something more sane, I have no way to prove it didn't make retrieval quality worse. I'd be flying blind through a change to a load-bearing config.

What I want to do is rip the whole thing out and replace it with something boring. One splitter, one chunk size, document type stored as metadata, recency stored as metadata, let the retrieval layer handle the rest. But that requires a full re-embed of the corpus, which is its own project, and it requires building an eval set first so I can measure the change, which is another project.

The bit I keep getting stuck on is the eval question. Hard to argue for fixing something when you can't measure whether your fix made it better, and I haven't found a path to a defensible eval set that doesn't eat months.

Still chewing on whether this is worth advocating for or whether it's just debt the company is fine carrying.