lostinthefield

7 ms·

1.
by lostinthefield 5y ago
Yeah, you're totally right. With cloud (or other) vendors, it's often a "lesser of many evils" kinda thing. Amazon is just particularly and notoriously bad.
2.
by lostinthefield 5y ago
Yes, exactly. The downside is that most of that is black-box magic. It's not clear to me whether it's a secret npm server, some serverless function, or something else entirely doing that "intelligent build process". But
3.
by lostinthefield 5y ago
Amazon treats their work staff poorly (at least on the Amazon.com side, if not AWS), and Bezos isn't a very nice human. They throw a lot of their weight around and bully small local governments into succumbing to their conquests. They
4.
by lostinthefield 5y ago
> It means users won't get instant deployment of their edits though, which depending on your use-case may be a non-starter. That's what the "incremental static regeneration" I mentioned does. Every time the data chang
5.
by lostinthefield 5y ago
Next.js (and probably its competitors) does this same thing ( https://nextjs.org/docs/basic-features/data-fetching#getstat... ), just much more elegantly and modularly, allowing you to work with any headless CMS whi
6.
by lostinthefield 5y ago
It doesn't necessarily solve RoAS tracking either. If you only have information on some % of your purchasers* and you optimize against that small, self-selecting sample, you may entirely miss other groups of higher spenders who just do
7.
by lostinthefield 5y ago
As someone who's not trained in math, what does "optimal transport" mean?
8.
by lostinthefield 5y ago
I've never seen a Wordpress site meeting only its "bare use case" that wouldn't have been better served by Wordpress.com itself (the hosted managed service) or Squarespace. The clients who've hired me did so explici
9.
by lostinthefield 5y ago
Wordpress is low-code in the sense that somebody else wrote most of the code already, but it's incredibly high-maintenance. At some point some plugin is going to break or the cache is going to be stale in some obscure way and you'
10.
by lostinthefield 5y ago
In terms of modeling, it handles nesting extremely well (repeater fields, Flexible Content Field). It has powerful conditionals (show X button if Y field = Z). In terms of layout, it can present a layout of fields like this sample ( https:&
11.
by lostinthefield 5y ago
Hey, we're in a similar situation and we just evaluated a bunch of different options. Just wanted to share some findings. One, in terms of integration, if you're considering headless you probably already are thinking of a decouple
12.
Ask HN: Collaborative SQL Playground?
1 points by lostinthefield 5y ago|0 comments
13.
by lostinthefield 5y ago
"Really bad" is an exaggeration, I think. The auto-transcription features in both Google Meet and Zoom are more than acceptable, they're often very useful in catching missed words during a meeting. They trip up on technical j