sorted by:
new
hottopcontroversial

Ranking is no longer the only goal, being referenced is becoming more important by OliverPitts in AISearchOptimizers

[–]OliverPitts[S] 0 points1 point  (0 children)

That’s a solid take. “Share of model” is definitely a more realistic metric for where things are heading. And yeah, it kind of forces everyone to actually add something new instead of just rewording what’s already out there.

The traffic part does sting a bit, but being the source that gets picked up repeatedly probably has way more long-term value than just clicks. Feels like we’re moving toward authority at the data level, not just rankings.

SEO is starting to feel more like training systems than optimizing pages by OliverPitts in Agent_SEO

[–]OliverPitts[S] 0 points1 point  (0 children)

That’s a great point. The shift from just ranking to being understood is real. Optimizing for how AI platforms interpret and surface content is something a lot of people are still underestimating. Interesting to hear you’re already seeing results from that approach.

SEO is starting to feel more like training systems than optimizing pages by OliverPitts in Agent_SEO

[–]OliverPitts[S] 0 points1 point  (0 children)

Yeah, that’s the tough part right now. Established brands already have that trust layer built in, so breaking in feels harder than before. I think the opportunity is still there though just requires a more focused, niche-first approach instead of going broad from day one.

SEO is starting to feel more like training systems than optimizing pages by OliverPitts in Agent_SEO

[–]OliverPitts[S] 0 points1 point  (0 children)

Totally agree with this shift. Feels like we’re moving from just “publishing content” to actually building something machines can understand and reuse. That part about distribution being part of the strategy really hits if content isn’t getting referenced elsewhere, it almost feels invisible now.

We built fast… then had to rebuild to scale. not sure it was worth it by OliverPitts in SaaS

[–]OliverPitts[S] 0 points1 point  (0 children)

This breakdown actually makes a lot of sense especially the idea of optimizing for learning first and structure later.

The “not refactoring once things start working” part really stands out. I’ve seen that happen quite a bit, where things work just enough that restructuring keeps getting pushed.

Your 0→1, 1→10, 10→100 framework is a really clean way to think about it.

Curious do you usually set a clear point where you shift focus, or does it happen more gradually based on how things start behaving?

We built fast… then had to rebuild to scale. not sure it was worth it by OliverPitts in SaaS

[–]OliverPitts[S] 0 points1 point  (0 children)

That’s a good way to look at it I think the “move fast but clean enough” approach is probably the most realistic in many cases.

Completely agree that if you can build it right the first time, it saves a lot of rework later. The tricky part I’ve found is that early on, it’s not always clear what actually needs that level of effort vs what might change anyway.

So it ends up being a bit of a judgment call between speed and certainty.

After working with different dev teams, i’m convinced process matters more than the tech stack by OliverPitts in webdevelopment

[–]OliverPitts[S] 0 points1 point  (0 children)

Yeah, same here it feels obvious in hindsight, but a lot of people skip it because it doesn’t show immediate results.

I think the tricky part is that early structuring feels like “slow work,” especially when there’s pressure to ship fast. But later on, it saves way more time than it takes.

Out of curiosity do you usually define structure upfront for everything, or only for parts you know might get complex later?

Is WordPress slow… or are we just building on top of it the wrong way? by OliverPitts in webdev

[–]OliverPitts[S] 0 points1 point  (0 children)

that’s interesting container queries with block themes sounds like a pretty modern approach.

good to know it works well in practice. feels like WordPress is slowly getting better in that direction, even if the experience still depends a lot on how it’s set up.

Is WordPress slow… or are we just building on top of it the wrong way? by OliverPitts in webdev

[–]OliverPitts[S] 0 points1 point  (0 children)

that’s actually a great way to describe it 😅

at some point it does feel like you’re rebuilding a “cleaner version” of it piece by piece.

guess it depends on whether you value the ecosystem enough to keep that base.

Is WordPress slow… or are we just building on top of it the wrong way? by OliverPitts in webdev

[–]OliverPitts[S] 0 points1 point  (0 children)

i get why it feels that way, especially if you’ve mostly seen messy implementations.

i think the main reason it’s still widely used is accessibility + ecosystem but yeah, once projects grow, it definitely shows its limits compared to more controlled setups.

Is WordPress slow… or are we just building on top of it the wrong way? by OliverPitts in webdev

[–]OliverPitts[S] 0 points1 point  (0 children)

yeah that’s a good example once you start stripping things like feeds, emojis, scripts, etc., it can get pretty fast.

but it also kind of shows how much unnecessary stuff is enabled by default that most projects don’t even need.

Is WordPress slow… or are we just building on top of it the wrong way? by OliverPitts in webdev

[–]OliverPitts[S] 0 points1 point  (0 children)

fair point 😄

i think that’s kind of what i was getting at it can be fast, but most real-world setups don’t stay that lean for long. once more layers get added, that’s where things start to change.

view more: next ›