Claude Code worked non stop for 5 hours and 5 mins doing this refactor.
Another level
05.03.2026 18:00
👍 0
🔁 0
💬 1
📌 0
Claude Code worked non stop for 5 hours and 5 mins doing this refactor.
Another level
I hear this a lot: Junior folks are screwed with AI. No one is going to hire juniors.
This is sooo wrong.
AI-native Juniors are going to eat up the senior folk's lunch that think they have all this experience and are AI late adopters
Someone with taste, who knows which problems are worth solving, not just whoever's in front of them.
Someone with judgment, not just skills.
Someone who can take things end-to-end.
The problem? That person is rare. And they're probably already building something of their own.
Everyone's hiring for the same person right now.
Someone who can BUILD and THINK.
These Marketing Claude Code Skills are just excellent
www.aibuilder.sh/search?auth...
How many Vibe Coding projects have you started?
How many have you finished?
the opposite of listening is waiting to speak
Nice Excalidraw Claude Code Skill
www.aibuilder.sh/skills/ooiy...
fun little feature for a Friday
Love this notion of BrainGrid being your Technical Co-founder
"Understanding technology is not the hard part anymore. The hard part is making decisions about what is useful to others."
The technical/non-technical divide is dead.
What matters now: curiosity, persistence, product taste.
AI made the barrier to building disappear.
SEO in 2026 is just a checklist:
- Canonical URLs
- JSON-LD schemas (Website, Organization, BreadcrumbList)
- hreflang tags
- DNS prefetch for third-party domains
- RSS feed
- Proper OG images
The magic isn't in knowing the list—it's in actually doing every item.
4 - If you're an AI builder solo or in a small team, you are doing both.
That for me is when magic happens.
3 - With AI coding, this artificial breakdown is going to feel even more broken. Engineers will make more product decisions, and PMs will get deeper into implementation.
2 - The what/how are very closely tied. I have a deep conviction that the attributes of the solution are deeply tied to the how. Hard to imagine Elon not caring about the how.
1 - Best products are built by engineers. Early Stripe, Twilio, now Claude Code. Engineers drive the why/what.
The product = why/what and engineering = how has never sat well with me.
New website just dropped!
Dream. Scope. Prioritize.
Let me know what you think!
Installed Notion, Slack, Gmail, Google Drive, and Google Calendar MCP in Claude Code.
Here is how my setup ended up. Unusable.
Can't wait for Claude Code implements tool search
This Evolution of the Programmer in 2024–2026 by Steve Yegge is spot on.
I myself am somewhere between stage 6-7.
It made me wonder if brand should be treated like any other system dependency. Explicit, versioned, and shared with both people and machines.
Curious if others are experimenting with “brand as code” or solving this problem in different ways.
A /brand.json and a /brand.txt that describe tone, voice, terminology, and visual guidelines in a way both humans and LLMs can understand.
Once that context existed, coding agents were able to update branding across our docs with very little back and forth.
When we recently rebranded BrainGrid, it was surprisingly annoying to explain our brand consistently to different LLMs and coding agents. So we tried something simple: we defined the brand in machine-readable form.
New idea: Brand as Code
As more teams use LLMs and coding agents to build products, I’ve noticed something missing from our workflows.
We treat APIs as code.
We treat infrastructure as code.
But brand is still mostly tribal knowledge.
AWS does not even try to simplify things these days.
These are their Sonnet 4.5 service quotas.
Cross-region model inference vs Global cross-region model inference
Super obvious
Advice I give people looking for new jobs:
There are three things:
❖ The company
❖ The role
❖ The hiring manager/team
You have to be REALLY excited about at least one of them. In the ideal world, you are very excited about all of them.
If you are meh on the three, move on
Its time to rethink the “technical vs. non-technical” labels we've used in the software industry
I don’t think the binary framing is accurate at all, and I think it’s getting in our way as roles shift and AI moves into our organizations.
