Working in public
I participated in a panel discussion this week for path to Citus Con, a series of Discord audio events that are happening in the run up to the Citus Con 2023 later this month.
The topic was “Working in public on open source”, and Citus developer (and pg-cron creator) Marco Slot and myself were interviewed by Claire Giordano and Pino de Candia.
The full hour-long audio conversation is now available on YouTube.
I ran it through Whisper to create my own transcript. Here’s my answer to a question about the benefits of working in public:
The biggest thing for me is that I never want to have to solve the same problem twice, ever.
That’s the most frustrating thing: when you sit down to solve a problem and you think wow, I solved this before and now I’m gonna have to waste my time figuring it out all over again.
A lot of the problems that I solve when I’m engineering are problems that can be captured in some kind of form. Maybe it’s a commit message with a commit that updates something. Maybe it’s a few notes. Maybe it’s just a sketch in an issue description of the approach that I was going to take.
I found that having those out there, just having those in a system massively increases my productivity. Defaulting to putting them in public, partly it’s sort of an insurance scheme.
I’ve worked for companies where I did everything in private. And then I left those companies and I’ve lost all of that work!
Everything that I do in public that has an open source license attached to it is just out there: I will never have to think about those things ever again.
That’s a problem that I’ve solved once and will never have to go back and revisit.
And I love that.
I feel like the work that I’m doing is constantly adding up to me having more capabilities and more tools in my tool belt.
It’s actually very selfish.
I have this website, my TIL website—and I just published my 400th note there.
And on the one hand, it is for other people, so that if somebody else needs to figure out how to copy a table from one SQLite database to another, and they do a Google search, they’ll land on my site, and it’ll solve the problem for them.
But mainly it’s for me.
The fact that I’m publishing causes me to increase the quality of the notes a little bit, so they make more sense to other people.
But it also means they make more sense to me when I come back in a year’s time and I’ve forgotten everything.
So yeah, I feel like you can actually be very selfish in your motivations and still do all of this stuff in public in a way that benefits other people.
Here are links to my posts that I referenced during the discussion:
More recent articles
- Lawyer cites fake cases invented by ChatGPT, judge is not amused - 27th May 2023
- llm, ttok and strip-tags - CLI tools for working with ChatGPT and other LLMs - 18th May 2023
- Delimiters won't save you from prompt injection - 11th May 2023
- Weeknotes: sqlite-utils 3.31, download-esm, Python in a sandbox - 10th May 2023
- Leaked Google document: "We Have No Moat, And Neither Does OpenAI" - 4th May 2023
- Midjourney 5.1 - 4th May 2023
- Prompt injection explained, with video, slides, and a transcript - 2nd May 2023
- download-esm: a tool for downloading ECMAScript modules - 2nd May 2023
- Let's be bear or bunny - 1st May 2023
- Weeknotes: Miscellaneous research into Rye, ChatGPT Code Interpreter and openai-to-sqlite - 1st May 2023