Give people something to link to so they can talk about your features and ideas
Creating dedicated web pages for projects, ideas, or product features aids discussions and sharing. Examples like ChatGPT Code Interpreter and Boring Technology showcase this. Proper documentation enhances usability and SEO.
Read original articleThe article discusses the importance of providing dedicated web pages for projects, ideas, or product features to facilitate discussions and sharing. It highlights examples like the ChatGPT Code Interpreter and the concept of Boring Technology. The ChatGPT Code Interpreter feature, despite its power, lacks proper documentation, making it challenging for users to discover and utilize. On the other hand, Boring Technology, introduced by Dan McKinley, emphasizes using well-understood technologies for non-unique aspects of a product. The article stresses the significance of having a clear webpage for ideas to enhance SEO and streamline conversations by providing a definitive link for reference. It concludes by encouraging creators to create dedicated pages for their concepts to foster understanding and engagement.
Related
Surfing the (Human-Made) Internet
The internet's evolution prompts a return to its human side, advocating for personal sites, niche content, and self-hosted platforms. Strategies include exploring blogrolls, creating link directories, and using alternative search engines. Embrace decentralized social media and RSS feeds for enriched online experiences.
Microfeatures I love in blogs and personal websites
The article explores microfeatures for blogs and websites inspired by programming concepts. It highlights sidenotes, navigation tools, progress indicators, and interactive elements to improve user experience subtly. Examples demonstrate practical implementations.
Waves of Writing for Google
The article explores the evolution of writing for Google, highlighting shifts from keyword stuffing to user-focused content and AI's impact on writing jobs. Writers are advised to adapt, focus on personal branding, and embrace technology for relevance.
Let's Treat Docs Like Code
Treating documentation like code involves using tools like GitHub, automation, and static site generators. Importance of learning these tools, best practices for efficient writing, protecting branches, case studies, and resources are discussed. Insights on building documentation sites are provided.
Why We Build Simple Software
Simplicity in software development, likened to a Toyota Corolla's reliability, is crucial. Emphasizing straightforward tools and reducing complexity enhances reliability. Prioritizing simplicity over unnecessary features offers better value and reliability.
I don't know if it's really useful since I don't think I've ever needed to forward anything to any CEO, but I'm not even a customer and this page is the first thing that came to mind when reading the article.
And for the rest of the stuff, stay as boring as possible.
So many times I see dev teams get innovating the whole way down and end up losing the focus as to how they provide value.
I need to burn this slide deck into my world view!
I literally built this concept into my new project last night, because I wanted to add evidence to the story about the Google Gemini App moderating yt-dlp, by showing that the Gemini API does not. Also to enable a funnel to the project and the other business-y reasons Simon outlines.
https://topicalsource.dev/chat/84a0d6dd-f66f-4f12-af17-5e99c...
The other thing I did was use localStorage to keep a list of public chats you've visited, so that when you come back you can see the other chats you have read. Also easier lookup than trying to find wherever you may have gotten the original link from. (like scrolling back in text history)
I'm still not clear not how to do it though. I expected some easy option or button, and didn't find it. I admit I could have spent more effort trying to figure out how to do it, but a handy link/tutorial would have helped me keep doing it instead of pretty much ignoring GPT most of the times.
Back in 2014, my team had an internal tool to view the state of resources in our system. All resources and their states were stored in a SQL database. Yet, the web app they developed was a SPA (before the invention of routers and stuff) and it never updated its url or supported deep linking. Whenever you wanted to send someone an email or an IM about an issue with a specific resource, you had to tell them “go to X tool, search for Y, click on Z -> W -> M -> O -> K, then you’ll see the issue there”. I found that so fucking infuriating. Why can’t I just use an https://X.com/Y/Z/W/M/O/K link to share that deeply nested state? When I brought it up multiple times i was always told “it’s not a priority and it’s not that big of a deal”
One time we were given 2 weeks to work on whatever we thought needed fixing. I decided to build an alternative that supported deep linking. But I also decided that all deep links should accept an `/api/` prefix that just returned the content in JSON format. It was just a hit with everyone in the team/company that the usage of X tool almost diminished over night even though my tool was much more rudimentary and didn’t have all the features that tool had. Nonetheless, turns out most people just wanted an easy way to share links rather than a “really powerful SPA that lets you dig down and investigate things”.
A month later the team that worked on that tool X announced that they now support deep links in a huge email to the whole company. Yet they thought the simple feature of returning JSON data on `/api/` prefix is irrelevant. 5 years after, my tool’s UI became obsolete but the actual service was promoted to a “vital internal service” because so many other teams built automation around the `/api/` prefix URLs and that team had to take that code and maintain it.
simon is often the very first person to write up a developing story in ai that most people close to the matter know about, but he can do it fast and link to all the relevant facts quickly and make it accessible for the people further away from the story to discuss.
Indeed. Well, hyperlinks and URLs.
URLs are the cornerstone of the web. A precise, universal (hopefully), long-lasting (hopefully) way of referencing articles and other resources. It's always frustrating to see people fail to appreciate their brilliance, e.g. search this on YouTube rather than just pasting a link into a message. Giving a write-up a permanent home on the web can certainly help give it visibility, and help the author avoid writing up the same ideas again.
Related classic essay: Cool URIs don't change. [0][1]
Related
Surfing the (Human-Made) Internet
The internet's evolution prompts a return to its human side, advocating for personal sites, niche content, and self-hosted platforms. Strategies include exploring blogrolls, creating link directories, and using alternative search engines. Embrace decentralized social media and RSS feeds for enriched online experiences.
Microfeatures I love in blogs and personal websites
The article explores microfeatures for blogs and websites inspired by programming concepts. It highlights sidenotes, navigation tools, progress indicators, and interactive elements to improve user experience subtly. Examples demonstrate practical implementations.
Waves of Writing for Google
The article explores the evolution of writing for Google, highlighting shifts from keyword stuffing to user-focused content and AI's impact on writing jobs. Writers are advised to adapt, focus on personal branding, and embrace technology for relevance.
Let's Treat Docs Like Code
Treating documentation like code involves using tools like GitHub, automation, and static site generators. Importance of learning these tools, best practices for efficient writing, protecting branches, case studies, and resources are discussed. Insights on building documentation sites are provided.
Why We Build Simple Software
Simplicity in software development, likened to a Toyota Corolla's reliability, is crucial. Emphasizing straightforward tools and reducing complexity enhances reliability. Prioritizing simplicity over unnecessary features offers better value and reliability.