The Overlooked Power of URLs ![rw-book-cover](https://wsrv.nl/?url=https%3A%2F%2Fcdn.changelog.com%2Fstatic%2Fimages%2Fpodcasts%2Fmaster-original-3922a5ce5ede81d973adc3cd618f7e64.png&w=512&h=512) ## Metadata - Author: [[Changelog Master Feed]] - Full Title: The Overlooked Power of URLs - Category: #podcasts - URL: https://share.snipd.com/episode/62be0e2b-2869-4164-9558-fcecacb4b6e0 ## Document Notes ## Highlights - **URL Reconstructed A Full Dev Setup** - Ahmad Alfy found a comment containing a URL that fully reconstructed his PrismJS setup. - The single link encoded themes, languages, and plugins so no database or local storage was needed. Transcript: Jerod Santo Ahmad Alfie found an old comment in his code that contained a powerful link. Quote, I clicked the URL and it was the PrismJS download page with every checkbox, dropdown, and option preselected to match my exact configuration. Themes chosen, languages selected, plugins enabled, everything perfectly reconstructed from that single URL. Here was a URL doing far more than just pointing to a page. It was storing state, encoding intent, and making my entire setup shareable and recoverable. No database, no cookies, no local storage, just a URL. ([Time 0:00:47](https://share.snipd.com/snip/f0a8e0b7-551e-4b2f-afba-0be81831389f)) - **URLs As State Containers** - URLs can act as state containers encoding intent and configuration without servers or storage. - The podcast argues we underuse URLs' virtues compared to heavy state libraries. Transcript: Jerod Santo In this article, Akhmat explains how URLs are even more than user interface. They're state containers. They have their limitations, yes, but Pareto tells me we're not benefiting from the virtues of the URL nearly enough. Akhmat agrees. Quote, we've built increasingly sophisticated state management libraries like Redux, MobX, ZooStand, Recoil, and others. They all have their place, but sometimes the best solution is the one that's been there all along. ([Time 0:01:31](https://share.snipd.com/snip/5fb2293a-447a-495a-bfd5-84d800c87389)) - **Cherry-Pick Cloud Code Features** - Read Shrivu Shankar's feature dump to cherry-pick useful Cloud Code workflows. - Use others' writeups to avoid learning every feature surface by trial and error. Transcript: Jerod Santo How I use every Cloud Code feature. The more I use Cloud Code, the more I want to use Cloud Code. That's a strong indicator of good product design. The challenge I have is the surface area of the product feels overwhelming. Not that I'm holding it wrong, necessarily, but that I could be holding it better. But if I'm being honest, which I actually always try to be, so I don't know why I feel compelled to prefix the following, or any statement, with that phrase, but here we are, aren't we? I don't know how much of Cloud Code's feature set is worth investing in. Are slash commands here to stay? Are sub-agents even worth it? Will I switch to AMP or Codex or Gemini CLI next week and make any Cloud Code-specific learnings moot? With those questions in my mind, I love posts like this one linked in the newsletter from Shrivu Shankar, a brain dump of all the ways he's been using Cloud Code for me to cherry pick from. ([Time 0:02:01](https://share.snipd.com/snip/52f4985e-c92b-4842-809c-1144523d7688)) - **AI Disrupts Technical Interviews** - Yusuf Aytas argues AI has broken technical interviews by making perfect answers widely available. - This levels the field for inexperienced candidates and undermines traditional vetting methods. Transcript: Jerod Santo AI broke interviews. I'm not sure the software industry's interview process was functional prior to October of 22, but as Yusuf Atis laments in this post, it's certainly busted now. Quote, everyone now has access to perfect code, perfect explanations, perfect system design diagrams, and even perfect behavioral answers. You don't need a network. You don't need experience. You just need a second monitor lying. You don't even need that. Check this out. End quote. The this that he referenced in that quote is an interview coder service that has been recently upgraded with audio support and 20 plus cutting edge undetectability features to keep You invisible across every interview check. ([Time 0:02:58](https://share.snipd.com/snip/18c1d1ca-3d93-42f5-a09f-6bcc9424a5ee)) - **Intern's Rust Port Saved $300k** - Intern Wu Zhaoyun ported a TikTok payment service from Go to Rust, doubling performance. - That optimization yielded a projected ~$300,000 annual cloud-cost saving. Transcript: Jerod Santo Intern saves TikTok $300,000 per year because Rust. During his internship at TikTok, Wu Zhaoyun ported a core payment service from Go to Rust. Quote, we faced a classic engineering dilemma. How do you squeeze more performance out of a critical system without compromising stability or breaking the bank? This is the story of how I tackle that challenge by selectively rewriting a performance bottleneck in Rust, resulting in a 2x performance gain and nearly $300,000 in projected annual Savings in cloud costs. End quote. One of our industry's favorite principles is premature optimization is the root of all evil, but it's important to note how much heavy lifting the word premature is doing in that axiom. Well-timed optimizations can yield huge wins like the one Wu and his colleagues deployed. ([Time 0:04:32](https://share.snipd.com/snip/72fcd923-3b41-480c-8dd3-02d3d2e6fc36)) - **Tune Cuts LLM Token Costs** - Tune (Token Oriented Object Notation) converts JSON to a compact format to save LLM tokens. - This can reduce token usage by ~40–60% for LLM inputs and lowers cost. Transcript: Jerod Santo Oh, and if you think this experience soured Wu on Go, quote, paradoxically, this project gave me an even deeper appreciation for golang go's incredible developer productivity and Well-rounded performance makes it the ideal choice for 95 of our services json for llm proms at half the tokens tune which stands for token oriented object notation is a compact human Serialization format designed for passing structured data to large language models with significantly reduced token usage. The idea here is to still use JSON programmatically, but convert to Tune for LLM input, saving about 40 to 60% of tokens. ([Time 0:05:23](https://share.snipd.com/snip/8658da33-fde0-43e5-975b-e8225b847c2d))