Beige & Brown color scheme went so hard against the grain for like 2 decades, it is unmistakably and forever Noctua.
It's so insanely visible in any system, any YT video, any media photo—and now we instantly associate Beige & Brown fans with high quality. Remarkable brand strategy.
Noctua is a proof that you can brand yourself distinctly different from the sea of sameness and beat them all through excellence across the board.
I'm gonna take the contrarian view:
Good
Stop making useless throwaway apps and start caring about your craft, your time, and your legacy on this planet
Put effort into things that will be used on people's phones while they hold them a foot from their faces
Respect yourself
OVERRATED: running tons of agents in parallel; working on too many things at once; perpetual context-switching; opening lots of low-quality PRs that may never land.
UNDERRATED: using one or two agents at a time; focusing on the task in front of you; thinking deeply; finishing stuff; making your code works in prod.
I keep thinking I miss having someone like Steve Jobs in the industry.
He had some standards. He cared about quality, coherence, and making great products. He could be ruthless and he had plenty of flaws, but it still felt like he and Apple were trying to make something genuinely great above all else. They had their opinions and you could respect that. They didn't try to force you, but make their case why they think it's good.
Now tech feels driven by trend chasing, fear, scale, revenue comparisons, endless games and everyone talks their book. Investors come first, business goals next, and users last if not at all.
I wish there would still someone like Steve still around
The loudest story about AI is a lonely one. One person with an army of chatbots. Other humans are friction.
That gets the future wrong. The best things aren’t built alone.
In a moment of change, we want to remind the world (and ourselves) what Notion stands for:
— Think Together
Here’s what I’d do if I was in charge of GitHub, in order:
1. Establish a North Star plan around being critical infrastructure for agentic code lifecycles and determine a set of ways to measure that.
2. Fire everyone who works on or advocates for copilot and shut it down. It’s not about the people, Im sure theres many talented people, youre just working at the wrong company.
3. Buy Pierre and launch agentic repo hosting as the first agentic product. Repos would be separate from the legacy web product to start since they’re likely burdened with legacy cross product interactions.
4. Re-evaluate all product lines and initiatives against the new North Star. I suspect 50% get cut (to make room for different ones).
The big idea is all agentic interactions should critically rely on GitHub APIs. Code review should be agentic but the labs should be building that into GH (not bolted in through GHA like today, real first class platform primitives). GH should absolutely launch an agent chat primitive, agent mailboxes are obviously good. Etc. GH should be a platform and not an agent itself.
This is going to be very obviously lacking since I only have external ideas to work off of and have no idea how GitHub internals are working, what their KPIs are or what North Star they define, etc.
But, with imperfect information, this is what I’d do.
La CLI es super interesante porque ejectuta comandos de bash (read-only) contra la repo, lo que permite que cualquier coding agent local lea los archivos que necesite y saque sus propias conclusiones.
Además, no necesita login y es 100% gratis.
Hicimos una tool que responde preguntas sobre cualquier repo de GitHub leyendo el código directamente.
Usala en la web o dejá que tu agente la use mediante MCP o CLI + Skill.
Forums
Ask an LLM questions about any GitHub repo, and let it grep and list and explore the source code directly.
Now available via:
→ Web
→ CLI (and Skill) 🆕
→ MCP 🆕
This week in Forums:
- Pinned posts & other moderation features
- New branch selector & better model selector
- Collapsed research & thinking. Go straight to the answers
ironically github's terrible home feed would be perfect if they made it the best place to stay up to date with/review agent work.
unfortunately they're going to realize this too late.
excited to see @cursor_ai x @graphite nail an agents-first feed though.
@JohnPhamous@opencode@Cursor@geminicli@windsurf Nice. Interesting that it's installed as a Claude Code command, so it can't be triggered automatically. Is this on purpose? Wouldn't a skill that the agent can invoke proactively when doing UI work be more useful?
Admin panel after 1 prompt asking Claude to match the site's aesthetics.
There's an initial insecurity in not writing every line yourself. But when code stops being the bottleneck, you can start building things you'd never have justified the time for before.
Introducing Forums: turn any github repo into an ai-powered forum.
Replace https://t.co/aWtaa7gyqY with https://t.co/3I21adc3Ev — ask questions, get answers straight from the source code.
Been using @mattpocockuk's rule to condense agent responses for a few days. The time and mental fatigue savings are really noticeable. 100% recommend.
"When reporting information to me, be extremely concise and sacrifice grammar for the sake of concision."
there is a hierarchy of context access simplicity where web products have a disadvantage
local fs > public web > private apis
as you move right it becomes harder to successfully get the right context for the task at hand
Files, Agents, and the Future of BaseHub
While there’s still work before a release, we wanted to share our plans.
🔸 Re-architecting BaseHub to bet on the file system, Git, and coding agents
🔸 Open sourcing "BaseHub Core": self-host and contribute
https://t.co/c5oOhgaQkR