Finding interesting programming content: taking back the ranking with Brave Goggles
How to use Brave Search Goggles and why I created a Goggle dedicated to software craftsmanship.
Navigating the endless stream of information online requires systems that help us filter and prioritise content. Handing this entire process over to someone else isn't ideal: the algorithms we depend on, when we don't understand them, we endure, and they shape us.
Filtering and prioritising: a job too important to leave to others
The most widespread search engines sort results with an algorithm built and calibrated by someone else: you don't know how it works, you can't inspect it, you can't change it.
Brave Search has an interesting feature for taking back this control: Goggles. I've been using them to filter and prioritise search results when I research programming topics, but they can be used for far more interesting use cases. Doing it is simple: the official documentation is public and well written, and in this post I'll walk through how I built mine.
Brave's solution: Goggles
Goggles (not to be confused with “Google”) are simple, self-contained text files that apply a personalised re-ranking to Brave Search results: they operate on the results the engine finds, redefining their order according to the instructions in the file.
In practice, a Goggle is a list of instructions with a minimal syntax:
$boost=N,site=example.commoves results from that domain up$downrank=N,site=example.compushes them down$discard,site=example.comremoves them entirely- lines starting with
!are comments and metadata
The number N, from 1 to 10, is a priority level: the higher it is, the more weight the instruction carries on the ranking.
Ready-made Goggles are plentiful (excluding the 1,000 most visited websites, removing Pinterest from results, favouring independent tech blogs), they can be followed like bookmarks and, most importantly, anyone can create their own and share it. According to the documentation, files are hosted on GitHub or GitLab and registered on the official page (search.brave.com/goggles/create), where Brave validates and caches them so they can be used in searches. Brave's stated goal is algorithmic transparency: instead of one imposed ranking, a nearly limitless number of possible rankings, controlled by users.
A privacy note, from Brave's documentation: Brave doesn't track queries, but warns that a Goggle used by very few people can effectively become an identifier. That's why I published and shared the Goggle presented here: being public, this specific risk doesn't apply.
Why a Goggle about software craftsmanship
I created the Software Craftsmanship Goggle with a precise goal: when I search for software development information, I want to hear first from the people who contributed to inventing the disciplines I'm searching for, namely the signatories of the Agile Manifesto, the authors of the books that have shaped generations of developers, the maintainers of projects I use every day, and the tech blogs publishing in-depth analysis instead of SEO-optimised content. These are indicative criteria: the list also includes writers and companies I appreciate for other reasons.
The design principle is a descending priority scale, chosen by me, that reflects how much I consider each source authoritative:
- boost 6: the pillars, those who defined the practices I look for
- boost 5: verified authoritative authors, reference blogs
- boost 4: excellent personal blogs on dissemination and craft
- boost 3: corporate blogs, valid content but less neutral, more product-oriented
![]()
Who decides what shows up at the top of the results? Now that's my call
The sources, one by one
Pillars (boost 6)
Ron Jeffries (ronjeffries.com) Agile Manifesto signatory, co-author of Extreme Programming. He still writes today about XP, TDD and Agile “without tricks”. Maximum boost: when I search for TDD or Agile, I want the voice of someone who practised it from the beginning, not a training centre's report card.
Robert C. “Uncle Bob” Martin (blog.cleancoder.com) Author of Clean Code and Clean Architecture, a polarising but undeniably formative figure for how the industry reasons about design and maintainability. Maximum boost: his arguments are, for me, a starting point on SOLID and architecture.
Martin Fowler (martinfowler.com) Chief Scientist at Thoughtworks, author of Refactoring and Patterns of Enterprise Application Architecture. His site is my reference on refactoring, microservice architecture and enterprise patterns. Maximum boost: it's among the most cited sources on these topics.
Portland Pattern Repository / WikiWikiWeb (wiki.c2.com) Ward Cunningham's wiki, where (among other things) the expression “technical debt” was born, along with a good part of the design patterns culture. Maximum boost: it's a primary source of craft history, impossible to replicate.
Signatories and authoritative authors (boost 5)
Alistair Cockburn (alistair.cockburn.us) Agile Manifesto signatory, author of Agile Software Development. Boost 5: authoritative, but publishes less frequently than the pillars.
Jeff Sutherland (jeffsutherland.blogspot.com) Co-creator of Scrum. Boost 5: primary source on Scrum, though with more promotional content than others.
Scrum.org (scrum.org) The platform founded by Ken Schwaber, co-creator of Scrum. Boost 5: institutional reference on Scrum, official guides included.
Dave Thomas (pragdave.me) Agile Manifesto signatory, co-author of The Pragmatic Programmer. Boost 5: one of the most influential texts on the profession; his blog is low-volume but high quality.
Kent Beck (kentbeck.com)
Creator of Extreme Programming and TDD, co-creator of xUnit. Boost 5: his voice remains my reference on TDD and evolutionary design. (Technical note: the previous version of the Goggle also included his Medium profile, but Brave's validation rejected the @ character in the site value.)
Jim Highsmith (jimhighsmith.com) Agile Manifesto signatory, creator of Adaptive Software Development (Jolt Award 2000, Stevens Award 2005), author of Agile Project Management and EDGE. Boost 5: a piece of agility history who still publishes today.
James Grenning (blog.wingman-sw.com) Pioneer of TDD for embedded C, Agile Manifesto signatory. Boost 5: for me one of the few authoritative voices on embedded TDD, a domain with little dedicated literature.
Sandro Mancuso (craftedsw.blogspot.com) Founder of Codurance and author of The Software Craftsman, a reference text of the movement. Boost 5: in my view the European reference point for software craftsmanship.
Simon Willison (simonwillison.net) Django co-creator, today one of the most followed bloggers on the practical application of LLMs to software development. Boost 5: for searches about AI and development, this is the most complete niche source I know.
Joel Spolsky (joelonsoftware.com) Fog Creek and Stack Overflow founder, author of the famous “Joel Test”. Boost 5: for me his essays remain among the best writings on software management.
Jeff Atwood (codinghorror.com) Stack Overflow founder and author of the Coding Horror blog. Boost 5: quality dissemination with a humanistic approach to craft.
Sandi Metz (sandimetz.com) Author of Practical Object-Oriented Design in Ruby (POODR) and 99 Bottles of OOP. Boost 5: her design rules and “The Wrong Abstraction” are, for me, reference texts for OOP.
Casey Muratori (caseymuratori.com, computerenhance.com) Game engine programmer (Handmade Hero), author of “Semantic Compression” and the Performance-Aware Programming course. Boost 5 and 4: in my view the leading voice of the “handmade” school on low-level performance design.
DHH (David Heinemeier Hansson) (dhh.dk, world.hey.com/dhh) Creator of Ruby on Rails, CTO of 37signals. Boost 5 and 4: a position I find coherent and heavily debated on anti-complexity and, today, on the use of AI in development.
Mitchell Hashimoto (mitchellh.com) HashiCorp co-founder, creator of Vagrant, Terraform, Vault and the Ghostty terminal. Boost 5: he writes little, but on Zig, terminals and open source he raises arguments hard to find elsewhere.
Fabien Sanglard (fabiensanglard.net) Author of the Game Engine Black Book series (DOOM, Wolfenstein 3D). Boost 5: his source code analyses of historic engines are unique in their genre.
J.B. Rainsberger (jbrains.ca) Trainer and author on TDD, design and team management. Boost 5: for me one of the best craft educators still active.
Reference personal blogs (boost 4)
Joshua Kerievsky / Industrial Logic (industriallogic.com) Founder of Industrial Logic in 1996, one of the longest-running agile consultancies; Extreme Programming pioneer and author of Refactoring to Patterns. Boost 4: the site hosts a high-level technical blog written by coaches and authors, including Tim Ottinger.
Julia Evans (jvns.ca) Extraordinary technical writing: debugging, networking, Unix tools, explained like nobody else. Boost 4: excellent for learning “how things really work”.
Dan Luu (danluu.com) Deep, contrarian analysis: hardware, development tools, software production economics. Boost 4: every essay is a monograph, rarely published but always relevant.
Rachel by the Bay (rachelbythebay.com) Debugging and sysadmin “war stories” from real experience, of enormous didactic value. Boost 4: a practical complement to more theoretical blogs.
Hillel Wayne (hillelwayne.com) Formal methods applied to industrial software, TLA+, testing. Boost 4: for me one of the few mainstream voices making formal methods accessible.
Drew DeVault (drewdevault.com) Free software developer (Sway, Sourcehut) and radical commentator on open source sustainability. Boost 4: constant intellectual stimulus, to be read with due critical thinking.
Aphyr (Kyle Kingsbury) (aphyr.com) Author of Jepsen, the suite that exposed the consistency guarantees of dozens of distributed databases. Boost 4: his Jepsen tests are, for anyone working with distributed systems, reading I consider essential.
Dan Abramov (overreacted.io) Redux co-creator, longtime member of the React team. Boost 4: his deep-dives on modern JavaScript are among the best, but the blog is very topic-specific.
Kent C. Dodds (kentcdodds.com) Educator on React, testing and the JavaScript toolchain. Boost 4: excellent teaching material, with a strong paid educational component.
Corporate blogs (boost 3)
Cloudflare (blog.cloudflare.com) The corporate blog I appreciate most for technical depth: memory allocators, protocols, cryptography, explained in detail by real engineers. Boost 3, not 5: excellent but commercial and oriented towards their own products.
Netflix Tech Blog (netflixtechblog.com) Architecture at extreme scale: microservices, chaos engineering, observability. Boost 3: an industrial paradigm of reference, but tied to Netflix's specific context.
GitHub Blog (github.blog) Announcements and insights about Git and the most widespread versioning platform. Boost 3: more news than critical takes, but indispensable for tooling updates.
Pragmatic Engineer (pragmaticengineer.com) Gergely Orosz's newsletter, one of the most followed analysts in the software industry. Boost 3: strong on culture and the job market, mostly behind a paywall.
![]()
I type, I filter, I reorder: with Goggles, search is mine again
How to use this Goggle
- Open the Goggle's page: Software Craftsmanship Goggle on Brave Search
- Or search for it by name (“Software Craftsmanship”) on the discover page of search.brave.com
- Activate it and, if the results convince you, click “follow” to have it always available
- The source file of this project is public on GitLab (gitlab.com/LarryBros/goggles): browsable, freely forkable and released under the CC-BY-4.0 licence. Suggestions for additions or changes are discussed in the repository's issues.
You can also use it on the fly, with a single search:
https://search.brave.com/search?q=<your-query>&goggles=https%3A%2F%2Fgitlab.com%2FLarryBros%2Fgoggles%2F-%2Fraw%2Fmain%2FSoftware_Craftsmanship.goggles
Why talk about software craftsmanship in the age of AI?
With the advent of AI, the software development industry that most of the people in this Goggle helped create is undergoing a profound transformation. Every role around the software development process is involved: how we write code, test it, design it, teach it. Following this transformation through the eyes and perspective of those who helped create it can only be interesting. The goal of this Goggle is exactly to favour those voices: not the answer of a generative model, but the reflection of those who went through every previous transition of our profession and are living through this one too.
A note of honesty
A Goggle is not revealed truth: it's a declared preference. It puts on top the voices I consider most authoritative, and it's only fair that every reader can see the complete list, which is why the sources are public and commented. The advantage over the default ranking, for the sources defined in the Goggle, is that here the bias is visible, inspectable and modifiable by anyone. The opposite of a black box.
If your favourite blog or Goggle is missing from the list, open an issue on gitlab.com/LarryBros/goggles: the Goggle is meant to grow with the community that uses it.
“Free technology isn't just code — it's the freedom to look under the hood.”
👤 Lorenzo | ItsMeLarry all about me here
🧪 AI & Open Source Experiments | 🕹️ Retro Gaming & Graphic Novels 🎸 Rock, Folk, Jazz, Punk | 🔒 Privacy First 📍 Tuscany / Digital