Written by: Noah Learner Tags: critical thinking, newsletter
Published: Nov 20, 2026 | Last Updated: Nov 20, 2026
Over the years I have realized that Peak Noah does his best work in the face of constraints.
As you know I've been obsessed with building this year. When I was working on this project, I didn't look at anything else for hours and hours.
For me, the thing that made me get so into it are the types of constraints I ran into. It takes a ton of mental energy to work through all the technical bottlenecks that come up when troubleshooting; like an API call limit, or using too much RAM, or expanding to multiple computers.
In the past month or so, I scaled how much I was able to produce, and as I did that, I had to work through bottleneck after bottleneck. Each one of them had a different type of component to it, and each one could have served as a door which going through
The intellectual challenge captured my attention in a way where I became persistent about figuring out each one, and getting through the door to the next one; unlocking a new “level” of efficiency through each. That is the sweet spot. Finding something with really interesting constraints that uncovered something to solve that was hard.
The more of these I got through, the more efficient the thing got, and the more code I could produce. As I started being able to scale the work, I had different constraints, like RAM usage making my computer crash, and how long QA testing took. All of these were limits I had to figure out how to remove.
And now... My main constraint is how much code I can review. I'm at the point where I can produce more code than I have the capacity to test, which is wild.
It could be a deadline, budget, capacity, scaling our Claude Max plans, or in the case of this last week for many, a Cloudflare outage. If I can solve these very difficult things that I am uniquely capable of solving better than other people, that's going to help me compete long-term.
We've also seen some news where Google is prompting searchers to log in to continue their search in some situations. If you're not logged into Google and you perform a search, then reload the page, it'll throw up a pop-up and say, hey, you've got to log into Google. That changes the challenge and cost for rank tracking tools in a big way.
How do we as SEOs make good decisions when we don't have first-party data we can trust? I'm not saying we're there today, but if rank and GSC data becomes much more obfuscated, we're in an eroding data environment, and it's only a matter of time before more and more of us will shift to asking for server logs.
I see a future where our expectations as SEOs shift toward having log access, and convincing clients that they must be on Cloudflare, and our devs that we easy access to files we can read. It means being able to look at our own data and get answers to which crawlers are hitting the site, and how often. I just feel like that's in all of our futures.
And that's where the constraints get interesting, because Cloudflare is a great choice for getting easy access to logs, on top of helping with the security stuff, but an outage is the risk of that.
It was finding something with really interesting constraints that uncovered something that was hard. It allowed me to be my best self, and I encourage you to go look for it, because it's out there. It might be technical, it might be something else, but there's something out there for you that's going to turn you on, the way this got me still excited to work on every day.
Be open to it. Look for what keeps grabbing your attention, what keeps pulling at you. You have to give it space to breathe. You have to be willing to go deep in the thing, you have to be gritty, work your way through the awful bottlenecks, and be willing to suffer a little bit.
What are your constraints lately and how are you using them to move forward instead of be limited by them?