Podcasts about raycast

Scott and Wes break down the state of web browsers in 2025, from the rise and fall of Arc and the fate of Firefox to hot takes on Opera GX, Raycast, and why power users might not be profitable. They compare rendering engines, rant about dev tools, and reveal what browser stats say about Syntax listeners. Show Notes 00:00 Welcome to Syntax! 01:37 Rendering Engines. 02:11 Arc Browser. 02:41 Microsoft Edge. 03:45 Why not Brave? 05:25 Brought to you by Sentry.io. 05:50 Google Manifest v2. 07:32 Opera. OperaGX. 10:13 Vivaldi. 11:23 The death of Arc Browser. 11:44 Dia? 14:43 No revenue from power-users. Letter to Arc Members. 15:38 Arc's transition to a new browser. 17:02 Browser companies need to lock users fast! 19:42 Gecko. 19:45 Firefox. 21:08 Zen. 22:38 Webkit. There Still Arent Any iPhone Browsers With Custom Engines 29:18 Wtf is Ladybird? 34:14 Usage statistics. StatCounter.com. 39:32 Dev Tools experience ranked. 42:06 Tab experience. 43:37 Containers and profiles. Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

This week's episode is a first of its kind because we're doing the ultimate deep dive into one of my favorite products: RaycastWe'll here from the founders, design team, and even the hype team and go deep into all kinds of topics:The hilarious story of Raycast's YC application3 weekly rituals that are perfect for remote teamsWhat they've learned about designing AI experiencesWhat we can learn from how their hype team operatesHow the design team has changed the way they collab with engineersa lot moreThis is easily the most in-depth episode I've ever made so I hope you enjoy it :)Thomas and Petr (Raycast founders)Roy can Rooijen (Designing AI)Jordan Amblin (Designing mobile)Alexander Antonov (Designing windows + DS)Pedro Duarte (Hype lead)Inga Hampton (Designer + Illustrator)

Brew #43: Epic vs Apple: 4 Lata Walki. Stripe Platformą Finansową. Worldcoin Wchodzi do USA. Elon.Wróciliśmy! Cisza wyborcza skończona, a my wpadamy z nowym odcinkiem Brew!W tym odcinku:

In this hosts-only episode, Amy and Brad get real about the developer experience - from the stress of job interviews to the complexities of choosing the right framework. They discuss why companies are comparing candidates more than ever, share strategies for answering behavioral interview questions, and debate the merits of Remix versus Next.js (spoiler: Brad's all-in on Remix). The conversation shifts to feature flags and progressive rollouts, with insights from Brad's work at Stripe. SponsorWorkOS helps you launch enterprise features like SSO and user management with ease. Thanks to the AuthKit SDK for JavaScript, your team can integrate in minutes and focus on what truly matters—building your app. Chapter Marks00:00 - Intro00:41 - Sponsor: WorkOS01:47 - Brad's Keyboard and Mouse Shopping Spree04:30 - Keyboard Layout Discussion07:23 - Apple Ecosystem: Reminders and Notes09:23 - Family Sharing and Raycast Integration09:43 - Notion vs Apple Notes for Project Management11:31 - File Storage and Backup Strategies14:00 - Machine Backup Philosophy16:46 - Job Interview Preparation Tips19:40 - Answering the "Weakness" Question21:53 - Addressing Weaknesses: Delegation Examples24:29 - Conflict Resolution Interview Questions25:46 - Company Research Before Interviews27:00 - Tech Stack Considerations: Remix vs Next.js28:30 - Framework Migration Decisions29:30 - Astro for Content Sites31:02 - Backend Languages: Go vs TypeScript32:30 - React Server Components Future34:23 - Feature Flags and Boolean as a Service35:30 - Feature Flag Segmentation and A/B Testing36:54 - PostHog and Analytics Tools38:30 - Progressive Rollouts and Error Monitoring40:20 - Amy's Picks and Plugs43:35 - Brad's Picks and Plugs  

The gang gets to work defending their Mac login items. Who has the most minimal startup? Who's got the craziest apps? This episode has more new apps mentioned in any episode of Comfort Zone ever! How would you have done our challenges? How would you answer the question at the end of the show? Let us know! Other Things Discussed Chris's hyper key video Marco Arment is just like Niléane - ATP 637 1Password AirPods Sanity Aqua Voice Bartender 5 BetterSnapTool BetterTouchTool CleanShot X Dato Ethernet Menubar FigmaAgent FinderFix Front and Center Hand Mirror Hyperduck iStat Menus Keyboard Maestro MenuBot Moom MotionVFX Pastebot PopClip Quitter Raycast Sleeve SoundSource Supercharge Velja YellowDot United app Disneyland app 12Train.com Follow the Hosts Chris on YouTube Matt on Birchtree Niléane on Mastodon Comfort Zone on Mastodon Comfort Zone on Bluesky

Wed, 30 Apr 2025 20:45:00 GMT http://relay.fm/connected/550 http://relay.fm/connected/550 Baby Jason Snell From 1886 550 Federico Viticci, Stephen Hackett, and Myke Hurley This week: Myke is learning, Federico saw a rumor, Stephen comes clean, and Apple launched a weird webpage. This week: Myke is learning, Federico saw a rumor, Stephen comes clean, and Apple launched a weird webpage. clean 4887 This week: Myke is learning, Federico saw a rumor, Stephen comes clean, and Apple launched a weird webpage. This episode of Connected is sponsored by: Turbulence Forecast: Find out how turbulent will your flight be with tailored and handcrafted forecasts. Download now. Links and Show Notes: Get Connected Pro: Preshow, postshow, no ads. Submit Feedback UniFi Camera Security - Ubiquiti Previewed: smart #1 Premium Interior | Carz Automedia Malaysia Slots of the Past: PDS - 512 Pixels Google is working on a big UI overhaul for Android: Here's an early look - Android Authority ‎Snapshot on Apple Apple launches a new celebrity hub that's all about Apple | The Verge tvOS 18 is now available - Apple"tvOS 18 introduces intelligent features like InSight, which displays timely information about actors, characters, and music from every live-action Apple TV+ movie and show onscreen in real time." Raycast's iOS app is now available for AI chat and notes | The Verge

Wed, 30 Apr 2025 20:45:00 GMT http://relay.fm/connected/550 http://relay.fm/connected/550 Federico Viticci, Stephen Hackett, and Myke Hurley This week: Myke is learning, Federico saw a rumor, Stephen comes clean, and Apple launched a weird webpage. This week: Myke is learning, Federico saw a rumor, Stephen comes clean, and Apple launched a weird webpage. clean 4887 This week: Myke is learning, Federico saw a rumor, Stephen comes clean, and Apple launched a weird webpage. This episode of Connected is sponsored by: Turbulence Forecast: Find out how turbulent will your flight be with tailored and handcrafted forecasts. Download now. Links and Show Notes: Get Connected Pro: Preshow, postshow, no ads. Submit Feedback UniFi Camera Security - Ubiquiti Previewed: smart #1 Premium Interior | Carz Automedia Malaysia Slots of the Past: PDS - 512 Pixels Google is working on a big UI overhaul for Android: Here's an early look - Android Authority ‎Snapshot on Apple Apple launches a new celebrity hub that's all about Apple | The Verge tvOS 18 is now available - Apple"tvOS 18 introduces intelligent features like InSight, which displays timely information about actors, characters, and music from every live-action Apple TV+ movie and show onscreen in real time." Raycast's iOS app is now available for AI chat and notes | The Verge

Thomas Paul Mann is the cofounder of Raycast. I use Raycast every day as a replacement for Spotlight. For me, shortcuts are the most useful feature. I put curl requests I commonly use as well as random things like email snippets. It's a massive time saver and really well built.Raycast is a genuinely well built product so Thomas talks quality, getting feedback and how they ship features. We also talk about their unique YC experience and how they've been building AI into Raycast. This episode is brought to you by WorkOS. If you're thinking about selling to enterprise customers, WorkOS can help you add enterprise features like Single Sign On and audit logs. Links:RaycastRaycast Extensions StoreTerminal Coffee x RaycastThomas on Twitter/X

Matt has built an Obsidian plugin with a fun name, Niléane is keeping the scrobbling dream alive, and everyone tries to find a great new Raycast extension. We want to hear from you! How would you have done our challenges? How would you answer the question at the end of the show? Let us know on Mastodon or Bluesky! Weekly Topics Ghosty Posty Last.fm Other Things Discussed The “meh key” Nintendo Today is Chris's new “calendar” Ulysses Sleeve Quanta Doppler Obsidian Raycast extension Menubar Weather Parcel PopClip Lutron Aurora Smart Bulb Dimmer Switch Follow the Hosts Chris on YouTube Matt on Birchtree Niléane on Mastodon Comfort Zone on Mastodon Comfort Zone on Bluesky

What do Raycast, Daylight, Amo, The Browser Co, and Mainframe all have in common?They all hired Ellis Hamburger to help tell their story.So this episode is a bit different...We're going to get away from the pixels and go deep into how you can use language to tell a compelling story about your product.Some highlights:How to tell a story that people care aboutLessons from the Language team at SnapchatBreaking down specific copywriting strategiesQuestions to help you figure out your product's storyWhat we can learn from the CEOs of Snapchat vs. Browser Co.How to make your product onboarding unforgettablea lot moreEllis talks about the Browser Company's “Peek” videoJordan Singer's Mainframe websiteDaylight computer websiteEllis mentions the 222 onboardingThe Permanent website (”design is how its made”)Ellis quotes the Build bookAmo's “Where did our friends go?” manifestoRaycast's “Why” page and Focus mode

In this episode, Daniel Miessler explores how to supercharge your macOS workflow with Raycast, transforming everyday tasks into lightning-fast, AI-powered actions. He talks about: Raycast as a Universal Launcher:Daniel explains how Raycast replaces traditional launchers like Spotlight and Alfred, offering an all-in-one shortcut to apps, files, and bookmarks for unparalleled efficiency. Quick Links and Custom Searches:He demonstrates how quick links streamline navigation by replacing outdated bookmarks and enabling custom search commands that let you bypass the browser for faster access. Integrated Utilities and Window Management:Discover how Raycast consolidates everyday tools—from color pickers and process killers to custom window arrangements—ensuring that all your essential utilities are just a keystroke away. Advanced AI Integration:Learn how Raycast’s innovative AI commands integrate with platforms like ChatGPT and Fabric, allowing you to interact with, summarize, and analyze web content directly from your command line. Custom Commands and Productivity Hacks:Daniel reveals his secrets for creating personalized hotkeys, snippets, and aliases that reduce friction in your digital workflow, making your daily tasks smoother and more intuitive. Subscribe to the newsletter at:https://danielmiessler.com/newsletter Watch the video on YouTube at:https://www.youtube.com/c/UnsupervisedLearning Follow on Twitter at:https://twitter.com/danielmiessler See you in the next one!Become a Member: https://danielmiessler.com/upgradeSee omnystudio.com/listener for privacy information.

There are many reasons to debate the ethics and implications of AI. But while we do that, hundreds of the world's biggest brands are rushing to implement the technology into creative and coding workflows. At a time when shareholders are being unforgiving and policy making is volatile, business leaders are looking to AI to gain any advantage possible.Jan Emmanuele is one of the experts that these Fortune 500 corporations rely on to identify and build GenAI creative workflow augmentations and automations. He works for Superside —whom you might remember from our episode with Philip Maggs (Listen here)— because they're on the leading edge of creating an LLM that interprets your briefing process, design system, brand guidelines, marketing campaigns, and data to automate high-volume creative tasks. In this episode, we focus on how and where AI is applied within organizations and workflows. It details how organizations can prepare themselves for implementing AI and how to address the core barriers and risks of the technology.Listen on Spotify | Listen on Apple PodcastsWhat was most interesting about this conversation was his prediction that the adoption of AI will explode in enterprise orgs starting in 2026 and that it could continue into the 2030s. He believes that the value of AI in enterprise has already been proven and that more use cases exist than anyone can believe. That adoption thus far has only been limited because of legal and procurement policies.If this is true, organizations that aren't already at least planning for this workflow-automated future will soon be at a huge competitive disadvantage. Finding 10x augmentations of creative output is routinely achieved, and more will be possible for organizations with highly-structured and easily-repeatable workflows. The gains will be largest in orgs that leverage the uniquely-LLM capability of contextualizing outputs based on data. Examples include localizing campaigns to micro-niche segments or regions of the world. Thanks for reading Design of AI: Strategies & insights for product teams! This post is public so feel free to share it.Headwinds will reduce the number of creatives earning a living wageAs we barrel towards the increasingly inevitable reliance on LLMs, it puts creatives in the uncomfortable position of fighting for their survival and protesting for what's ethically correct. The music industry is the canary in the coal mine in this battle. Many artists earn the majority of their income from their back catalogues and LLMS are effectively using those albums as mulch to improve generative capabilities. On one side, you have an entire way of life being threatened; on the other, you have artists that will quickly need to learn how to master generative capabilities to become an indispensable musician regardless of the headwinds that will reduce the amount of music earning a living wage. As platforms get better, we'll just generate the music and images we need instead of hiring professionals.Overcoming the uncanny valley: Not being able to determine what was generated by AIWhat has made all of us feel more comfortable has been that AI still sucks at a lot of creative tasks. Blooper reels and countless articles of AI creative generative fails give us hope that the technology isn't ready to replace anyone yet. But we've learned from our latest episode and many previous ones that the technology is much more ready for primetime than we might believe. Many of the failures we see today result from the false sense of confidence the platforms offer novices. While the simplicity of these tools has exploded the amount of experimentation happening, we're flooded with more fails than fantastic examples.Another factor is that the simplicity of the GenAI interfaces obscures the complexity happening in the background. We believe we can generate a campaign-ready 20-second video by typing in a prompt. But the complexity comes from knowing what models, protocols, data sets, and projects to connect for the best outcomes. This is an era dominated by creative technologists who can see these possibilities and stay up-to-date with the latest capabilities.In the hands of someone who understands how to overcome the rawness of the technology, the possibilities are limitless. And for every project we see published, there are at least another dozen working to push those capabilities further in the near future. Sesame is another example of technology overcoming the uncanny valley by delivering conversational voice capabilities indistinguishable from humans. These developments are happening at such a pace that it's impossible to keep up. For example, researchers have created an agentic, autonomous framework that iteratively structures and refines knowledge in situ.The point is that whether you agree with the hype of an AI-powered future or not, businesses everywhere will implement it because the impact is increasingly undeniable. Action items: What can we do to prepare ourselves and our workI hate that the ethics of AI seem like an afterthought to the beating drum of business automation. It's deeply uncomfortable that many professions and industries must adapt or face extinction. The only way to stare into this abyss and feel hopeful is to believe that the rising tide of resentment against big tech will fuel a renaissance of altruistic misfits building the models and layers that do less harm. But that won't calm the nerves of the musicians and artists who see an end to their way of life today.We can mourn the tidal wave of change while also preparing for the new world order that comes next.If you're a creative:* Stop undervaluing yourself and your work. Listen back to yourself explain the work you do. Recognize all the steps, decisions, and life lessons you neglect to mention. You need to document who you are to such a granular level that you spot where your genius is most pronounced and where you're on autopilot. Then consider how to leverage AI to amplify/automate each of those.* Tap into your most significant creative strengths. You are more than your outputs. You fell into this career for a reason and persist because of at least one exceptional creative strength. Document it and the conditions under which it enhances your work more than others. Now find AI tools that can make that happen more often and for longer periods. * Lead the change you want to see. Don't wait for inspiration and innovative products to land in your inbox. Go find them, test them, implement them, and prove if they can or can't help you achieve your goals.If you're a business leader: * Accept that change is coming fast. You can feel unsure about the technology, worried about the risks, and apprehensive about the costs. But you cannot wait to start imagining what the future of your business and industry might look like. Go through future casting exercises and monitor the countless startups slowly eating away at your competitive moat.* Empower your team to succeed. Even if people tell you they aren't worried about the coming change, they probably are. You need to lead them through this and create a shared vision of what the future version of your business and workforce can look like. Include teams in co-creation processes to determine the best ways to empower them to succeed by eliminating barriers and inefficiencies.* Structure your data and production workflows. AI is most effective in highly repetitive situations where success can be easily evaluated. Businesses will succeed that have standardized their key workflows and have structured data that adds critical context about situations and success. Do the work now before an expensive consultant charges you millions once there's a veritable gun to your head due to competitive concerns. Contact me if you need helpThank you for following the Design of AI podcast and this newsletter. This year, we'll spend more time discussing this seemingly insurmountable challenge of implementing AI effectively. Please comment if there are specific questions or topics you need us to discuss. And feel free to vent about topics that you're most frustrated or concerned about so we know what our community needs.We're also hoping to launch some events in major markets this year to bring together early adopters and experimenters with those eager to leverage this technology effectively.And if you need help with any consulting related work related to envisioning your AI-powered future, email me at arpy@ph1.ca Product of the month: RaycastRaycast is a perfect example of the disruptive potential of AI. While everyone else is running to add bullshitty AI features to make using their products easier, others are rewriting the way we interact with digital experiences. Raycast basically looked at MacOS and said, “Let's rebuild the entire finder and launcher experience.”It's ironic for me because one year ago, I worked on a project where the outcome was the real potential value of AI in a mobile phone experience would be as an assistive launcher experience that eliminates all the inefficiencies of Android. Well, here it is! Thanks for reading Design of AI: Strategies & insights for product teams! This post is public so feel free to share it. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit designofai.substack.com

In this episode, Daniel Miessler explores how to supercharge your macOS workflow with Raycast, transforming everyday tasks into lightning-fast, AI-powered actions. He talks about: Raycast as a Universal Launcher:Daniel explains how Raycast replaces traditional launchers like Spotlight and Alfred, offering an all-in-one shortcut to apps, files, and bookmarks for unparalleled efficiency. Quick Links and Custom Searches:He demonstrates how quick links streamline navigation by replacing outdated bookmarks and enabling custom search commands that let you bypass the browser for faster access. Integrated Utilities and Window Management:Discover how Raycast consolidates everyday tools—from color pickers and process killers to custom window arrangements—ensuring that all your essential utilities are just a keystroke away. Advanced AI Integration:Learn how Raycast’s innovative AI commands integrate with platforms like ChatGPT and Fabric, allowing you to interact with, summarize, and analyze web content directly from your command line. Custom Commands and Productivity Hacks:Daniel reveals his secrets for creating personalized hotkeys, snippets, and aliases that reduce friction in your digital workflow, making your daily tasks smoother and more intuitive. Subscribe to the newsletter at:https://danielmiessler.com/newsletter Watch the video on YouTube at:https://www.youtube.com/c/UnsupervisedLearning Follow on Twitter at:https://twitter.com/danielmiessler See you in the next one!Become a Member: https://danielmiessler.com/upgradeSee omnystudio.com/listener for privacy information.

Show DescriptionDoes layout make CSS difficult to learn from scratch, Chris quizzes Dave about Balatro, getting back into Pokemon, why should Google have to sell Chrome, adding fun features to apps you already have to keep you using them like Raycast, and thoughts on the VS Code forks + AI. Listen on Website →Links Web Awesome Layout Anatomy Balatro Pokémon GO A Little Arm Chair Businessin' about Chrome – Chris Coyier Raycast Focus works really well - daverupert.com Cursor - The AI Code Editor Trae - Ship Faster with Trae Codium is now Qodo | Quality-first AI Coding Platform Windsurf Editor by Codeium Zed - The editor for what's next Ghostty Helix SponsorsComplete CSSGet to a level in development that you never thought would be possible with this expansive CSS course from Andy Bell. You won't be the same developer after completing it.

What happens when eager computer enthusiasts unknowingly download a trojanized hacking tool and find themselves on the wrong side of cybersecurity? A former employee's actions led to chaos and raise urgent questions about the security of cultural treasures. And join us as we explore the alarming trend of social media influencers staging fake kidnappings.All this and much much more is discussed in the latest edition of the "Smashing Security" podcast by cybersecurity veterans Graham Cluley and Carole Theriault, joined this week by Lianne Potter from the "Compromising Positions" podcast.Warning: This podcast may contain nuts, adult themes, and rude language.Episode links:No Honour Among Thieves: Uncovering a Trojanized XWorm RAT Builder Propagated by Threat Actors and Disrupting Its Operations - CloudSEK.British Museum forced to partly close after alleged IT attack by former employee - The Guardian.Chart: What Do You Want to be When You Grow Up?- Statista.Tikked off: What happens when TikTok fame fades - Vox.Influencer burnout is real - Vox.Influencer slammed for staging fake kidnapping plot because she was ‘bored' - Mirror Online."Mom influencer" Katie Sorensen sentenced to jail for falsely claiming couple tried to kidnap her kids at a crafts store - CBS News.Stock market influencer on the way to Coldplay concert kidnapped by data theft gang - The New Indian Express.Raycast.“Thank Goodness You're Here” video game.The We Society Podcast - Academy of Social Sciences. Smashing Security merchandise (t-shirts, mugs, stickers and stuff)Sponsored by:Tailscale – Tailscale is perfect for work or personal projects, making networking simple. Its free plan covers up to 100 devices and 3 users. Get started at tailscale.com and be up and running in less than 10 minutes!1Password – Secure every app, device, and identity – even the...

Hey folks, Alex here

In this episode, Mark and Rob reflect on an eventful 2024, covering everything from travel highlights and their favourite tech purchases to the biggest disappointments of the year. Rob shares his hands-on experience with OneUI 7 Beta, Samsung's latest innovations, and his new tech toys, while Mark looks back on standout reviews and missed opportunities. Plus, a look ahead at what 2025 might bring, including Apple's rumored HomePod with a display, Nintendo's Switch 2, and Samsung's S25 Ultra. Links BookCase by Astropad: https://geni.us/bdfZ Google/Samsung XR headset - basically Android Vision Pro: https://geni.us/0GRPiR ResMed $120 Vision Pro Kontor strap with counterweights: https://geni.us/vhV9 Flow Launcher (basically Raycast for Windows): https://geni.us/x3Sj Official Raycast for Windows waitlist: https://geni.us/THo236T Festivitas app - Christmasify your Mac: https://geni.us/hRS16r If you'd like to get in touch with Rob and Mark, you can email them at contact@eightorsixteen.com. Eight or Sixteen is a Mark Ellis Media Limited production: https://markellisreviews.com

Raycast to narzędzie zwiększające produktywność na macOS, umożliwiające szybkie uruchamianie aplikacji i wykonywanie różnych zadań za pomocą skrótów klawiaturowych. Arkadiusz Świętnicki demonstruje jego funkcje oraz współpracę z czytnikiem ekranu VoiceOver. Audycja dostępna jest również w wygenerowanej automatycznie wersji tekstowej

ブラウザ（Arc） / ブックマークをサムネで管理（Speed Dial 2） / PCで動画の無音をスキップ（Skip silence） / Podcastアプリ（Overcast） / ランチャーアプリ（Raycast） / リマインダー活用法 / 情報収集 / 迷惑電話の判別（電話帳ナビ） ■ 番組への感想・お便りはこちら https://bit.ly/3TK21mu ■ 関連リンク Arc https://arc.net/ Arc Search https://apps.apple.com/jp/app/arc-search-%E6%A4%9C%E7%B4%A2%E3%82%92%E9%AB%98%E9%80%9F%E5%8C%96%E3%81%97%E3%82%88%E3%81%86/id6472513080 Brave https://brave.com/ja/ Speed Dial 2 新しいタブ https://chromewebstore.google.com/detail/speed-dial-2-%E6%96%B0%E3%81%97%E3%81%84%E3%82%BF%E3%83%96/jpfpebmajhhopeonhlcgidhclcccjcik?hl=ja Skip silence https://chromewebstore.google.com/detail/skip-silence/fhdmkhbefcbhakffdihhceaklaigdllh?hl=ja-US Overcast https://overcast.fm/ Raycast https://www.raycast.com/ Alfred https://www.alfredapp.com/ Clipy https://clipy-app.com/ 『全面改訂版 はじめてのGTD ストレスフリーの整理術』 https://amzn.to/3ZFAEvl IFTTT（※LINEでのRSS購読で使用） https://ifttt.com/ 電話帳ナビ－迷惑電話やメールを自動判定（迷惑電話ブロック） https://apps.apple.com/jp/app/%E9%9B%BB%E8%A9%B1%E5%B8%B3%E3%83%8A%E3%83%93-%E8%BF%B7%E6%83%91%E9%9B%BB%E8%A9%B1%E3%82%84%E3%83%A1%E3%83%BC%E3%83%AB%E3%82%92%E8%87%AA%E5%8B%95%E5%88%A4%E5%AE%9A-%E8%BF%B7%E6%83%91%E9%9B%BB%E8%A9%B1%E3%83%96%E3%83%AD%E3%83%83%E3%82%AF/id1024396744https://play.google.com/store/apps/details?id=jp.telnavi.app.phone&hl=ja ■ クレジット Opening Theme : Composed by WATA Cover Artwork : Designed by WATA CG Character : Modeling & Designed by WATA Ending Theme : Composed by TAZAWA ©終わりかけのRadio 番組エンディングテーマ『life』 https://bit.ly/4aHZ1wU #Arc #Raycast #Overcast #リマインダー #電話帳ナビ

The Apps We Use

Capítulo 2622 en el que te cuento la fortuita manera en que llegué a Raycast y cómo lo estoy usando, seguramente desaprovechando gran parte de su potencial.Si te gustan los temas de Emilcar Daily, Weekly te va a encantar. Weekly es mi podcast privado semanal sobre Apple, tecnología, productividad, finanzas personales, domótica y las interioridades de mi negocio como podcaster y creador independiente. Únete a Weekly por solo 6 euros al mes en emilcar.fm/weekly.

Steven Tey is Founder & CEO of Dub.co, the open source link management infrastructure platform for modern marketing teams. Their open source project, also called dub, has almost 18K stars on GitHub and is used by teams at companies like Vercel, Raycast, and Perplexity. In this episode, we dig into starting Dub.co as a side project and how it ultimately turned into a company, their initial positioning as a Bitly alternative, their focus on great design and how that shows up in all parts of their product and marketing, how analytics unlocked much higher ACVs and value for customers, how getting a top Hackernews post helped drive early momentum, their vision to become an end-to-end attribution platform & more!

This episode is sponsored by Reflect. It's the ultra-fast note-taking app that's about to change the way you take notes. To boost your productivity with advanced features like custom prompts and voice transcripts, give Reflect a try by clicking on this link: https://reflect.app/?utm_source=every&utm_medium=sponsorship&utm_campaign=september2024 Simon Eskildsen is a learning machine.  I first interviewed him in 2020 about how he leveled up from an intern at Shopify to the company's director of production engineering by reading and applying insights from hundreds of books. A lot has changed over the last four years. LLMs have made it possible to contextualize information like never before—and in this episode, I sat down with Simon to talk about how this changes the way he learns. Simon is now the cofounder and CEO of AI startup turbopuffer, which is building a search engine that makes vector search easy and affordable to run at scale. We get into: How Simon's learning rituals have evolved over time, as the cofounder of a growing startup and a new parent  The ways Simon has integrated ChatGPT, Claude, and Notion AI to do everything from writing legal documents to maintaining his rural cabin in Quebec  The custom AI commands in productivity tool Raycast that Simon uses to learn new words and cook creative dishes Simon's take on how language models will reshape the future of learning, especially skills like language acquisition, for the next generation  As we talk, we screenshare through his Anki setup, including the flashcard template he finds most useful, and try out his custom AI commands in Raycast to understand the meaning of two of my favorite obscure words, “lambent” and “eigengrau.” This is a must-watch for note-taking aficionados and anyone who wants to supercharge their learning with AI. If you found this episode interesting, please like, subscribe, comment, and share!  Want even more? Sign up for Every to unlock our ultimate guide to prompting ChatGPT here: https://every.ck.page/ultimate-guide-to-prompting-chatgpt. It's usually only for paying subscribers, but you can get it here for free. To hear more from Dan Shipper: Subscribe to Every: https://every.to/subscribe  Follow him on X: https://twitter.com/danshipper  Timestamps: Introduction: 00:01:06 How entrepreneurship and parenthood changed Simon's learning rituals: 00:02:51 How Simon accelerates his learning by using LLMs to find associations: 00:12:59 Simon's Anki setup and the flashcard template he swears by: 00:18:24 The custom AI commands that Simon uses most often: 00:26:02 How Simon uses LLMs for DIY home projects: 00:37:45 Leveraging LLMs as intuitive translators: 00:40:48 Simon's take on how AI is reshaping the future of learning: 00:51:38 How to use Notion AI to write: 00:59:10 The AI tools that Simon uses to write, read, and code: 01:08:53 Links to resources mentioned in the episode:  Simon Eskildsen: @Sirupsen Simon's startup, turbopuffer: turberpuffer.com, @turbopuffer My first interview with Simon in 2020: https://every.to/superorganizers/how-to-build-a-learning-machine-299655  The productivity tool through which Simon uses LLMs, Raycast: https://www.raycast.com/  The other AI tools that Simon is experimenting with: voice-to-text tool superwhisper, copilot for developers Supermaven, code editor Cursor

Jeff Weinstein is a product lead at Stripe, where he helped grow their payment APIs to hundreds of billions in volume and transformed the way founders start companies into a few simple clicks with Atlas. Prior to Stripe, Jeff led several startups and sold companies to Groupon and Box. He's known for his customer obsession, craft, quality, and building beloved products businesses rely on. In our conversation, we discuss:• The power of customer obsession and how to operationalize it in the product development process• How to pick the right metrics and use them to drive impact• Techniques for getting things done at big companies• A group practice Jeff started to uplevel product craft, called Study Group• The story behind Stripe Atlas and its mission to increase entrepreneurship globally• Lessons from working with the founders of Stripe—Brought to you by:• Pendo—The all-in-one platform for product-led companies building breakthrough digital experiences• Cycle—Your feedback hub, on autopilot• Anvil—The fastest way to build software for documents—Find the transcript at: https://www.lennysnewsletter.com/p/creating-a-culture-of-excellence—Where to find Jeff Weinstein:• X: https://x.com/jeff_weinstein• LinkedIn: https://www.linkedin.com/in/jeffwweinstein/• Email: jweinstein@gmail.com—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Jeff's background (10:16)  The “go, go, go ASAP + optimistic, long-term compounding” approach(15:38) The importance of craft and quality(24:15) Effective customer communication strategies(28:57) The importance of speed in customer interactions (33:19) Narrowing your focus(36:53) Why you should pay attention only to paying-customer feedback(40:24) Practicing silence when communicating (45:33) The role of metrics in product success(54:08) Empowering teams with a single metric(58:23) Picking the right metric for your audience(01:05:10) The importance of metric hygiene(01:11:33) How Stripe uses “study groups” for product improvement(01:37:20) Stripe's Atlas: simplifying company formation(01:50:38) Automation and operational efficiency(01:55:13) Diversity and team building(02:03:09) Building new products within a large company(02:21:10) Lightning round—Referenced:• Atlas: https://stripe.com/atlas• Stripe: https://stripe.com/• SQL: https://en.wikipedia.org/wiki/SQL• GitHub: https://github.com/• Linear: https://linear.app/• Figma: https://www.figma.com/• Jeff's tweet about Stripe's bug-finder program: https://x.com/jeff_weinstein/status/1777487507934040300• The “Collison installation”: https://news.ycombinator.com/item?id=18400504• How we use friction logs to improve products at Stripe: https://dev.to/stripe/how-we-use-friction-logs-to-improve-products-at-stripe-i6p• Fidelity: https://www.fidelity.com/• 83(b) election: https://docs.stripe.com/atlas/83b-election• Jeff's tweet about Atlas's NPS score: https://x.com/jeff_weinstein/status/1788644576330469638• What is a Delaware corporation? Here's what makes this state so attractive to businesses: https://stripe.com/resources/more/what-is-a-delaware-corporation• Incorporating in Delaware explained: Why it's such a popular option for businesses: https://stripe.com/resources/more/incorporating-in-delaware-explained• 7 of Pixar's Best Storyboard Examples and the Stories Behind Them: https://boords.com/blog/7-of-pixars-best-storyboard-examples-and-the-stories-behind-them• Alex Kehayias on LinkedIn: https://www.linkedin.com/in/alexkehayias/• Patrick McKenzie on LinkedIn: https://www.linkedin.com/in/patrickmckenzie/• AngelList: https://www.angellist.com/• Dan Hightower on LinkedIn: https://www.linkedin.com/in/danhighto/• Stripe Atlas perks partners: https://support.stripe.com/questions/stripe-atlas-perks-partners• Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma): https://www.lennysnewsletter.com/p/vision-conviction-hype-mihika-kapoor• High Output Management: https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884• Orbiting the Giant Hairball: A Corporate Fool's Guide to Surviving with Grace: https://www.amazon.com/Orbiting-Giant-Hairball-Corporate-Surviving/dp/0670879835• 7 Powers: The Foundations of Business Strategy: https://www.amazon.com/7-Powers-Foundations-Business-Strategy/dp/0998116319• Business strategy with Hamilton Helmer (author of 7 Powers): https://www.lennysnewsletter.com/p/business-strategy-with-hamilton-helmer• Box: https://www.box.com/• Patrick Collison on X: https://x.com/patrickc• How to with John Wilson on HBO: https://www.hbo.com/how-to-with-john-wilson• The Quiet Girl on Hulu: https://www.hulu.com/movie/the-quiet-girl-b50a4b8e-d3ff-4635-b806-5e7dbd292ca4• Raycast: https://www.raycast.com/• Quicksilver: https://qsapp.com/• Alfred: https://www.alfredapp.com/help/workflows/automations/• CleanShot: https://cleanshot.com/• John Collison on X: https://x.com/collision—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Wow, holy s**t, insane, overwhelming, incredible, the future is here!, "still not there", there are many more words to describe this past week. (TL;DR at the end of the blogpost)I had a feeling it's going to be a big week, and the companies did NOT disappoint, so this is going to be a very big newsletter as well. As you may have read last week, I was very lucky to be in San Francisco the weekend before Google IO, to co-host a hackathon with Meta LLama-3 team, and it was a blast, I will add my notes on that in This weeks Buzz section. Then on Monday, we all got to watch the crazy announcements from OpenAI, namely a new flagship model called GPT-4o (we were right, it previously was im-also-a-good-gpt2-chatbot) that's twice faster, 50% cheaper (in English, significantly more so in other languages, more on that later) and is Omni (that's the o) which means it is end to end trained with voice, vision, text on inputs, and can generate text, voice and images on the output. A true MMIO (multimodal on inputs and outputs, that's not the official term) is here and it has some very very surprising capabilities that blew us all away. Namely the ability to ask the model to "talk faster" or "more sarcasm in your voice" or "sing like a pirate", though, we didn't yet get that functionality with the GPT-4o model, it is absolutely and incredibly exciting. Oh and it's available to everyone for free! That's GPT-4 level intelligence, for free for everyone, without having to log in!What's also exciting was how immediate it was, apparently not only the model itself is faster (unclear if it's due to newer GPUs or distillation or some other crazy advancements or all of the above) but that training an end to end omnimodel reduces the latency to incredibly immediate conversation partner, one that you can interrupt, ask to recover from a mistake, and it can hold a conversation very very well. So well, that indeed it seemed like, the Waifu future (digital girlfriends/wives) is very close to some folks who would want it, while we didn't get to try it (we got GPT-4o but not the new voice mode as Sam confirmed) OpenAI released a bunch of videos of their employees chatting with Omni (that's my nickname, use it if you'd like) and many online highlighted how thirsty / flirty it sounded. I downloaded all the videos for an X thread and I named one girlfriend.mp4, and well, just judge for yourself why: Ok, that's not all that OpenAI updated or shipped, they also updated the Tokenizer which is incredible news to folks all around, specifically, the rest of the world. The new tokenizer reduces the previous "foreign language tax" by a LOT, making the model way way cheaper for the rest of the world as wellOne last announcement from OpenAI was the desktop app experience, and this one, I actually got to use a bit, and it's incredible. MacOS only for now, this app comes with a launcher shortcut (kind of like RayCast) that let's you talk to ChatGPT right then and there, without opening a new tab, without additional interruptions, and it even can understand what you see on the screen, help you understand code, or jokes or look up information. Here's just one example I just had over at X. And sure, you could always do this with another tab, but the ability to do it without context switch is a huge win. OpenAI had to do their demo 1 day before GoogleIO, but even during the excitement about GoogleIO, they had announced that Ilya is not only alive, but is also departing from OpenAI, which was followed by an announcement from Jan Leike (who co-headed the superailgnment team together with Ilya) that he left as well. This to me seemed like a well executed timing to give dampen the Google news a bit. Google is BACK, backer than ever, Alex's Google IO recapOn Tuesday morning I showed up to Shoreline theater in Mountain View, together with creators/influencers delegation as we all watch the incredible firehouse of announcements that Google has prepared for us. TL;DR - Google is adding Gemini and AI into all it's products across workspace (Gmail, Chat, Docs), into other cloud services like Photos, where you'll now be able to ask your photo library for specific moments. They introduced over 50 product updates and I don't think it makes sense to cover all of them here, so I'll focus on what we do best."Google with do the Googling for you" Gemini 1.5 pro is now their flagship model (remember Ultra? where is that?

985. Erin Brenner, author of "The Chicago Guide for Freelance Editors," shares time-saving tips including the best practices for using Word, creating macros, and using automation tools like Zapier. You'll also learn about starting and growing a freelance business, including how to figure out what to charge, how to make ends meet at the beginning, and how to handle time management once your business starts to succeed. | Resources mentioned in the podcast:Erin Brenner, Right Touch Editing: https://www.righttouchediting.com/"The Chicago Guide for Freelance Editors" by Erin Brenner: https://press.uchicago.edu/ucp/books/book/chicago/C/bo213434367.htmlAdrienne Montgomerie's book, "Editing in Word 365" https://www.lulu.com/shop/adrienne-montgomerie/editing-in-word-365/ebook/product-p855r4.htmlRhonda Bracey, CyberText Consulting: https://www.cybertext.com.au/Hilary Cadman, Cadman Editing Services: https://www.cadmanediting.com/Erin Servais, AI for Editors: https://www.aiforeditors.com/Jack Lyon, Editor's Toolkit (Word macros): https://www.editorium.com/index.htmPaul Beverley, Archive Publications (Word macros): https://www.archivepub.co.uk/Phrase Expander: https://www.phraseexpander.com/Raycast: https://www.raycast.com/Zapier: https://zapier.com/Intelligent Editing: https://intelligentediting.com/| Edited transcript with links: https://grammar-girl.simplecast.com/episodes/brenner/transcript| Please take our advertising survey. It helps! https://podsurvey.com/GRAMMAR| Grammarpalooza (Get texts from Mignon!): https://joinsubtext.com/grammar or text "hello" to (917) 540-0876.| Subscribe to the newsletter for regular updates.| Watch my LinkedIn Learning writing courses.| Peeve Wars card game. | Grammar Girl books. | HOST: Mignon Fogarty| VOICEMAIL: 833-214-GIRL (833-214-4475) or https://sayhi.chat/grammargirl| Grammar Girl is part of the Quick and Dirty Tips podcast network.Audio Engineer: Nathan SemesDirector of Podcast: Brannan GoetschiusAdvertising Operations Specialist: Morgan ChristiansonMarketing and Publicity Assistant: Davina TomlinDigital Operations Specialist: Holly Hutchings| Theme music by Catherine Rannus.| Grammar Girl Social Media Links: YouTube. TikTok. Facebook. Instagram. LinkedIn. Mastodon.References for the Aging segmentvan Boxtel, W, Lawyer, L. Sentence comprehension in ageing and Alzheimer's disease. Lang Linguist Compass. 2021;e12430.Payne, B. R., Gao, X., Noh, S. R., Anderson, C. J., & Stine-Morrow, E. A. (2012). The effects of print exposure on sentence processing and memory in older adults: Evidence for efficiency and reserve. Aging, Neuropsychology and Cognition, 19(1–2), 122–149.

Hey

More snacks than you can shake a stick at, Weblog posting month 2024, Raycast experiments, and some new game controllers. Pringles Crocs: New shoes, ankle holster and crisp flavor unveiled Jalapeno Popper Cheese Curls – Herr's Chupa Chups Cola Popcorn 110g | Popcorn | B&M Apple Annie's Weblog · Participators in WeblogPoMo 2024 Raycast - Your shortcut to everything Kishi Ultra Mobile Gaming Controller (USB C) | Razer United Kingdom GameSir X2s Type-C Hall Effect Mobile Gaming Controller for iPhone 15 – GameSir Official Store

This week Adam is joined by Thomas Paul Mann, Co-founder and CEO of Raycast, to discuss being productive on a Mac, going beyond their free tier, the extensions built by the community, the Raycast Store, how they're executing on Raycast AI chat which aims to be a single interface to many LLMs. Raycast has gone beyond being an extendable launcher – they've gone full-on productivity mode with access to AI paving the way of their future.

This week Adam is joined by Thomas Paul Mann, Co-founder and CEO of Raycast, to discuss being productive on a Mac, going beyond their free tier, the extensions built by the community, the Raycast Store, how they're executing on Raycast AI chat which aims to be a single interface to many LLMs. Raycast has gone beyond being an extendable launcher – they've gone full-on productivity mode with access to AI paving the way of their future.

In this episode of the Career Journey podcast, Kelvin shares his journey from starting as a professional web developer in 2018 to becoming an entrepreneur and his way of building a 1.2m business. Kelvin's mission as a web development consultant is to make web development teams Ship less JavaScript™️. Kelvin is a web developer and entrepreneur from Nigeria and has launched multiple initiatives, including Ship Less JavaScript™️, Boring JavaScript Stack, SailsJs, and Hackfish. We discuss his work ethic, daily routine, and how he effectively manages his time using tools like Raycast and Basecamp. Kelvin also talks about his goals for the future, his approach to project management and decision-making, and his reading habits. He provides valuable advice for aspiring developers and entrepreneurs on focusing, avoiding mediocrity, and continuously learning and doing bigger and better things. You can connect with Kelvin on - Twitter: https://twitter.com/Dominus_Kelvin Javascript: Shiplessjavascript.com Website: https://sailscasts.com/ --- Support this podcast: https://podcasters.spotify.com/pod/show/vinodsharma/support

Andrew slides in at the 11th hour! So many burger joints! What are you surfing the net with? How about a little Media Corner™? Follow middle, an app suggestion for heaving file transfers, and a time-critical topic. Welcome to episode 107! Andrew's Struggling 00:00:00 Big night out!

Dan is the person behind all of those amazing Twitter deep dive threads on the intricacies of things like dark mode colour and how QR codes work.

Pedro joins us to walk through his favorite features of Raycast and expose the secrets of what we didn't even know Raycast could do! https://codingcat.dev/podcast/4-4-raycast Sponsors:Cloudinary - Build faster with AI powered image and video APIs. https://cld.media/codingcatdev Recorded: December 12, 2023 9:00 AM 00:00 Intro and Welcome Pedro 03:45 Rainbow to Raycast  05:37 Pedros Roll at Raycast 07:57 Sponsor: Cloudinary  08:42 What is Raycast? 11:52 Tech Behind Raycast 12:41 Favorite Features  28:47 Raycast for Teams 32:50 Walkthrough Getting Started 36:40 Scheming  41:17 Scope and Pricing  45:22 Perfect Picks --- Send in a voice message: https://podcasters.spotify.com/pod/show/codingcatdev/message Support this podcast: https://podcasters.spotify.com/pod/show/codingcatdev/support

This episode of the Event Tech Podcast features co-hosts Will Curran and Brandt Krueger engaging in a lively and diverse discussion about the latest trends and applications of AI in event technology, with a particular focus on their personal experiences with various AI tools and platforms.Key Topics:Developments in AI and Event Technology: Discussion of recent advancements in AI and how they are influencing the event tech landscape.Personal Experiences with AI Tools: Will and Brandt share their experiences using different AI tools, such as ChatGPT and MidJourney, highlighting their functionalities and practical applications.Google I.O. Announcements: Insights into Google I.O.'s latest announcements, particularly those related to AI integration into workspace tools and their implications.Security and Ethical Concerns: Addressing security issues in AI tools, including a White House initiative for hacking AI systems at DEF CON to test their vulnerabilities.Future of AI in Everyday Applications: Predictions and expectations for the integration of AI into daily tools and platforms, like Photoshop and Raycast, and how these advancements could shape user experiences.Thanks for listening!(This episode was recorded before Will became Head of Klik for Bizzabo)

W tym odcinku omawiam 15 aplikacji, z których korzystałem w 2023 roku, a które wg mnie bardzo pomagają w automatyzacji procesów biznesowych.Lista aplikacji:Ogólnodostępne:1. Todoist 2. Notion 3. Slack 4. Clickup 5. ArcWebowe/SaaS:1. Airtable 2. Webflow 3. Easytools 4. Zencal5. LoomMacOS:1. Raycast 2. Keyboard Maestro3. Shortcuts4. Paste5. CleanShotX

Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.Honeybadger sponsors this episode - combining error monitoring, uptime monitoring and check-in monitoring into a single, easy to use platform and making you a DevOps hero. (04:00) - Laravel 10.19 released (13:57) - Laravel Forge introduces zero downtime deployments with Envoyer integration (15:49) - Laravel Herd v1.2.0 includes an app creation wizard, Tinkerwell integration, and more (17:56) - Laravel Volt/Folio beta 5 is out, now with named routes (19:52) - Cachet v3 announcement (22:32) - The Laracon AU 2023 schedule is here (23:38) - Generate API documentation for Laravel with Scramble (26:51) - Sponsor: Honeybadger (28:03) - Convert numbers to words in Laravel with SpellNumber (31:12) - SpladePanel - create dashboards using Laravel Splade and Jetstream (32:52) - Shorten URLs in your Laravel ap with the Cuttly package (34:46) - EnumConcern - effortless enumeration handling in PHP (37:41) - Lightweight permissions for Laravel with Ladder (44:15) - UI Colors: Tailwind CSS color generator (45:52) - Search for job son LaraJobs from Raycast (47:42) - PHP max() function (48:25) - Debugging gateway errors

Canal de Telegram: ⁠⁠https://t.me/+zf-KrhlMJQI2NWI5⁠⁠ App del episodio: Raycast Sígueme en Twitter: ⁠https://twitter.com/existeunaapp

Limited edition crisps, the chaos of Bluesky, and Raycast pro. Walkers launches limited-edition Sensations to mark coronation MacStories Unwind: Introducing the New Unwind and Unwind+ - MacStories Robb Knight :prami:: "Bluesky seems to just be a bun…" - social.lol Bluesky Raycast Introduces a Pro Subscription with New AI, Sync, Theming, and Clipboard Functionality - MacStories

Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.This episode is sponsored by Honeybadger - combining error monitoring, uptime monitoring and check-in monitoring into a single, easy to use platform and making you a DevOps hero. (03:30) - Laravel 10.9 released (10:55) - Use ChatGPT to ask a question to the Laravel docs (14:05) - Create repeatable models with Laravel Recurring Models (16:24) - Laravel Artisan Raycast extension (18:38) - PostgreSQL full text search for Laravel Scout (22:20) - Lemon Squeezy for Laravel (26:55) - Sponsor: Honeybadger (27:54) - LDAP framework for PHP (30:24) - Send toas notifications in your Livewire application with Toaster (31:35) - Small but powerful CLI apps with Minicli

Raycast es una alternativa a Spotlight para Mac, vitaminada con extensiones. Parte de su gracia es que se integra con aplicaciones de terceros para ejecutar tareas más rápido o sacar información directamente desde ahí, algo que quizás puede convencer sobre todo a quienes acostumbran a manejar su Mac mediante atajos de teclado. Loop Infinito es un podcast de Applesfera, presentado por Javier Lacort y editado por Santi Araújo. Contacta con el autor en Twitter (@jlacort) o por correo (lacort@xataka.com). Gracias por escuchar este podcast.

Cet épisode explore le thème de l'accompagnement des apprenant·e·s en formation, agrémenté de références, d'anecdotes et de partages d'expériences. Après avoir défini cette notion, nous passons à travers le pourquoi de l'accompagnement en formation : quelles sont les raisons d'accompagner les apprenant·e·s ? Quelle est la plus-value ? Ensuite, nous abordons la question du “comment” : quels types d'accompagnements utilisons-nous ? À quels outils faisons-nous appel ? Quand accompagnez-les apprenants ? Enfin, après notre jeu habituel, nous nous intéressons à l'évaluation et l'évolution de l'accompagnement pour finalement arriver à LA question finale : Peut-on former sans accompagnement des apprenant·e·s ? On a évoqué Pause Giant AI Experiments: An Open Letter Wooclap : Créer des quiz via l'IA Définition de l'accompagnement : Maela Paul, 2009 Martine Beauvais, 2004 Recommandations Jérôme : La newsletter - Evidences par David Vellut Lionel : Le site Goldphish : cyber security awareness Nicolas : L'outil Raycast à découvrir grâce à cette vidéo Hébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

In questa puntata Roberto e Filippo parlano dei c.d. Launcher o lanciatori di Applicazioni, di cosa fanno e perché potrebbero esserti utili su macOS. Note dell'episodio Cosa sono i launcher o lanciatori? Applicazioni che permettono di lanciare altre applicazioni Fare conti Convertire misure Lanciare Script o Comandi Rapidi Eseguire ricerche Aprire cartelle o file Perché sono utili? Non alzi le mani dalla tastiera, molto più rapidi del punta e clicca ⌘ + SPAZIO Tutto è iniziato con Sherlock La spiegazione del termine Sherlocked (https://en.wikipedia.org/wiki/Sherlock_(software)): I sostenitori di Watson fatti da Karelia Software, LLC affermano che Apple ha copiato il loro prodotto senza permesso, compensazione o attribuzione nella produzione di Sherlock 3. Alcuni non sono d'accordo con questa affermazione, affermando che Sherlock 3 era l'evoluzione naturale di Sherlock 2 e che Watson era ovviamente destinato ad avere qualche relazione con Sherlock con il suo stesso nome. Il fenomeno di Apple che rilascia una funzione che soppianta o ovvia software di terze parti è così noto che essere Sherlocked è diventato un termine accettato usato all'interno della comunità di sviluppatori Mac e iOS. Spotlight (https://support.apple.com/it-it/guide/mac-help/mchlp1008/mac) Ne abbiamo già parlato nelle puntate: Episodio 3 (https://a2podcast.fireside.fm/3) Abbreviazione da tastiera (https://support.apple.com/it-it/guide/mac-help/mh26783/13.0/mac/13.0) - Personalizzazione con una o più lettere iniziali dell'app Personalizzazione delle ricerche Impostazioni Siri e Spotlight ### Ricostruire indice di Spotlight su Mac (https://support.apple.com/it-it/HT201716) Impostazioni -> Siri e Spotlight -> Privacy Spotlight Trascinare cartelle da re-indicizzare C'è anche un comando a terminale: sudo mdutil -E / Guida dettagliata in inglese (https://ss64.com/osx/mdutil.html) iOS / iPadOS Solo Spotlight di sistema (https://support.apple.com/it-it/HT201285) Launchbar (https://obdev.at/products/launchbar/index.html) Quello utilizzato da tempo da Filippo: Versione 6.9 Prezzo 29 € Prova gratuita 30 giorni Indicizzazione cartelle Associazione scorciatoie a specifici file o cartelle Muoversi nella struttura a cartelle dell'HD Spostare rapidamente file da tastiera Lanciare comandi rapidi Alfred (https://www.alfredapp.com/) Versione 5: Galleria di flussi di lavoro (da cui “rubare”) Base Gratuito Ma molto ridotto Funzioni di basi simili a Spotlight o poco di più Powerpack A pagamento Maggior parte delle funzioni interessanti 34 sterline Snippets ClipboardHistory Contatti Musica (gestione) Terminale File Navigazione Buffer Workflow Veramente potente Filippo è tentato solo per questo Simile a Comandi Rapidi e Keyboard Maestro Raycast (https://www.raycast.com) Il nuovo ragazzo del quartiere … Raycast è un lanciatore incredibilmente veloce e totalmente estendibile. Ti consente di completare attività, calcolare, condividere collegamenti comuni e molto altro. gratuito per uso personale (https://www.raycast.com/pricing) Basto su estensioni (https://www.raycast.com/store) IA in beta (https://www.raycast.com/ai) Altri sistemi operativi cenni Windows Power tools: PowerToys Run ALT+ Spazio Flow Launcher (https://www.flowlauncher.com) Linux uLancher (https://ulauncher.io) Multipiattaforma Cerebro (https://www.cerebroapp.com) Opensource Dove ci potete trovare? Roberto: Mac e architettura: mach - dot - net.wordpress.com (https://marchdotnet.wordpress.com/) Podcast settimanale Snap - architettura imperfetta (https://www.spreaker.com/show/snap-archiettura-imperfetta) Filippo: Avvocati e Mac punto it (https://www.avvocati-e-mac.it/) Ci sentiamo tra 2 settimane.

Brought to you by Writer—Generative AI for the enterprise | Dovetail—Bring your customer into every decision | Linear—The new standard for modern software development—Josh Miller is the CEO and co-founder of The Browser Company, where he helped build Arc, my go-to web browser. In today's episode, we get an inside look at the unique structure and values of The Browser Company and how their company culture has helped them land some of the best talent in tech. Josh shares ways that his company embraces experimentation, including their “optimizing for feelings” approach to building, and explains why extreme transparency is at the forefront of everything they do.Special invite link to skip the waitlist: https://arc.net/gift/lennyFind the full transcript at: https://www.lennyspodcast.com/competing-with-giants-an-inside-look-at-how-the-browser-company-builds-product-josh-miller-ceo/#transcriptWhere to find Josh Miller:• Twitter: https://twitter.com/joshm• LinkedIn: https://www.linkedin.com/in/josh-miller-b31259106/Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/Referenced:• Early access to Arc: https://arc.net/gift/lenny• The Browser Company: https://thebrowser.company/• Arc: https://arc.net/• Hursh Agrawal on LinkedIn: https://www.linkedin.com/in/hurshagrawal/• Hacker News: https://news.ycombinator.com/• Scott Belsky on LinkedIn: https://www.linkedin.com/in/scottbelsky/• Notes on Roadtrips: https://thebrowser.company/values/• Shahed Khan on Twitter: https://twitter.com/_shahedk• Paper by FiftyThree:  https://www.hellobrio.com/blog/digital-drawing-paper-fiftythree• Vimeo: https://vimeo.com/• Peter Vidani on Twitter: https://twitter.com/pter• The Verge: https://www.theverge.com/• Ellis Hamburger on LinkedIn: https://www.linkedin.com/in/ellishamburger/• Airbnb's Snow White project: https://uxdesign.cc/how-airbnb-proved-that-storytelling-is-the-most-important-skill-in-design-15d04ac71039• General Magic: https://www.generalmagicthemovie.com/• Linear: https://linear.app/• Raycast: https://www.raycast.com/• Cron: https://cron.com/• Thrive Capital: https://thrivecap.com/• Tuple: https://tuple.app/• Figma: https://www.figma.com/• Harold and the Purple Crayon: https://www.amazon.com/Harold-Purple-Crayon-Crockett-Johnson/dp/0062086529• Seeing Is Forgetting the Name of the Thing One Sees: https://www.amazon.com/Seeing-Forgetting-Name-Thing-Sees/dp/0520256093/• God Save Texas: A Journey into the Soul of the Lone Star State: https://www.amazon.com/God-Save-Texas-Journey-State/dp/0525520104• The Last of Us on HBO: https://www.hbo.com/the-last-of-us• Adam Curtis documentaries on YouTube: https://www.youtube.com/playlist?list=PLStWlBRkr0N_aYjPmbrrjm_rsstpkUBLc• Notion: https://www.notion.so/In this episode, we cover:(00:00) Josh's background(03:56) Arc and the metrics they use to track growth(04:42) Arc's retention numbers(08:22) Josh's product-building philosophy and why he believes in optimizing for feelings(18:57) How The Browser Company's values create a culture that allows them to ship so quickly(22:46) The “Notes on Roadtrips” doc about values(27:48) How Josh is able to hire such amazing talent(37:29) The good and bad of building in public(45:16) Some of the odd teams at The Browser Company and why Josh calls it a prototype-driven culture(46:01) The membership team(48:07) The storytelling team(52:00) Why The Browser Company doesn't have traditional PMs(54:07) A case for adding PMs(57:32) The role of data, even in a company that optimizes for feelings(58:30) Airbnb's Snow White project(1:02:14) How impactful moments in Josh's life influenced values at The Browser Company(1:03:08) How the film General Magic has inspired Josh(1:04:32) The value of novel names(1:06:50) Why The Browser Company's approach works for Arc(1:12:47) Why you need to nail latency and why Josh loves Tupl(1:14:33) The shift to cloud computing and the ultimate vision at The Browser Company(1:23:15) Lightning roundProduction and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

In this episode of Syntax, Wes and Scott talk through all the reasons your website might be slow, and how you can troubleshoot a slow website such as issues on the server, large assets, caching, CSS, JavaScript, latency, and more. Sentry - Sponsor If you want to know what's happening with your code, track errors and monitor performance with Sentry. Sentry's Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up. Show Notes 00:11 Welcome Glove 80 keyboard Raycast 03:06 Sponsor: Sentry 05:15 What makes a website slow? Uses.tech 06:29 Server Generation Times 13:33 Large payloads Redis Gzip Brotli compression Cloudflare Cloudinary 18:13 Assets being too large 23:01 Caching assets 28:25 CDN 30:35 Caching 101 37:04 Render blocking requests 40:01 CSS 42:25 JavaScript 44:51 Latency 49:17 Flash of dark mode or unsigned out 55:00 Data uris Content-visibility vite-plugin-singlefile Pool in your URL 58:11 SIIIIICK ××× PIIIICKS ××× ××× SIIIIICK ××× PIIIICKS ××× Scott: 3Blue1Brown Wes: Suavecito Firme Clay Pomade Shameless Plugs Scott: LevelUp Tutorials Wes: Wes Bos Tutorials Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

Diese Episode startet mit einem Follow-Up zur letzten Ausgabe. André erzählt von seinen Phillips Hue Anschaffungen und seinem neuen Shelly Plug S mit dem diverse Stromverbraucher gemessen wurden. Danach geht es um Toms Erfahrungen mit ChatGPT, sowie GitHub Copilot. Als Pick dieser Episode wurde Raycast gewählt, eine neue Launcher Anwendung für den Mac.

Diese Episode startet mit einem Follow-Up zur letzten Ausgabe. André erzählt von seinen Phillips Hue Anschaffungen und seinem neuen Shelly Plug S mit dem diverse Stromverbraucher gemessen wurden. Danach geht es um Toms Erfahrungen mit ChatGPT, sowie GitHub Copilot. Als Pick dieser Episode wurde Raycast gewählt, eine neue Launcher Anwendung für den Mac.

Diese Episode startet mit einem Follow-Up zur letzten Ausgabe. André erzählt von seinen Phillips Hue Anschaffungen und seinem neuen Shelly Plug S mit dem diverse Stromverbraucher gemessen wurden. Danach geht es um Toms Erfahrungen mit ChatGPT, sowie GitHub Copilot. Als Pick dieser Episode wurde Raycast gewählt, eine neue Launcher Anwendung für den Mac.

Cette semaine : Nvidia signe avec Microsoft pour le GeForce Now, Atomic Heart, Valve atomise 40k cheaters d'un coup sur Dota 2, Tohru Okada, le créateur du son de boot PlayStation est décédé le 14 février, les 20 millions pour Elden Ring, Throne and Liberty sera distribué par Amazon Games, Diablo IV bêta, Artifact (iOS / Android), Notion ouvre l'IA à tous, Raycast et de l'IA, AGAIN, Spotify et l'IA DJ et ROTONDJUUUU !!!, UNKLE - Rōnin (The Reflex Revisions), et XG - Shooting Star / Left Right. Lisez plutôt Torréfaction #247 : Nvidia signe avec MS pour le GFN, Atomic Heart, carton pour Elden Ring, dates bêta Diablo IV et des apps avec de l'IA ! Partout ! De l'IAAAAhhhh! avec sa vraie mise en page sur Geekzone. Pensez à vos rétines.

Cette semaine : Lifting Apex Legends - Saison 16, Dark & Darker, les annonces Nintendo - Nintendo Direct février, Transmission 4.0, Raycast, ChatGPT, Bard et Bing dans un bateau, OQEE sur le Web, The Waeve - The Waeve, Poker Face, clavier OnePlus, et Samsung S23. Lisez plutôt Torréfaction #246 : Dark & Darker, annonces Nintendo Direct, Transmission 4.0, Raycast, ChatGPT & friends et Samsung S23 avec sa vraie mise en page sur Geekzone. Pensez à vos rétines.

Rose and David spent some time looking at Raycast, the latest Mac launcher to arrive on the market, and compare it to their current favorite launcher, Alfred.

Rose and David spent some time looking at Raycast, the latest Mac launcher to arrive on the market, and compare it to their current favorite launcher, Alfred.

A command line and a GUI are two completely different ways to operate a computer—but quick launchers and command palettes have found a way to bring them together. Thomas is building Raycast, an extensible quick launcher for macOS. He joins Mark and Adam to discuss the evolution of launchers from Quicksilver to Spotlight to the Chrome address bar; reasons to embed web technologies into a native app; and how voice interfaces like Siri and Alexa fit into this story. @MuseAppHQ hello@museapp.com Show notes Thomas Paul Mann @thomaspaulmann Raycast Spark AR Raycast API Metamuse episode on platforms Spotlight, iOS Search KDE, Krunner Quicksilver Superhuman, Linear, Notion Arc Siri, Alexa

[00:00:39] Go Rails and Discord went crazy for Go Rails this morning, Collin talks about putting out the fires. This reminds Andrew of the issue he had with his dotfiles once. Admit it, we've all been there before! [00:05:31] Collin is enjoying his minimal config setup lately. Andrew talks about how he likes using Znap! to help him with his dot files and reduce his shell's startup time.[00:06:43] Andrew talks more about minimalizing his setup by getting rid of aliases he's not using every couple months, as well as plugins. It's hard to stop hoarding those plugins! [00:07:13] Collin really only uses Vim but has a lot of theme plugins, and the plugins he does have tend to be from Tim Pope.  [00:08:26] Both Collin and Andrew dive deeper into aliases. Collin, he's runs his pretty lean and just uses some mnemonics for Rails commands. Andrew did a lot of house cleaning and now just has a handful for very basic things for Rails and Git.[00:14:06] Andrew discusses functions and thinning the herd. One that he does love is the GitHub labels he made. Andrew talks about how great the GitHub CLI is, and if you haven't checked it out in a while, PLEASE DO.[00:17:59] Andrew recently switched his terminal to Warp, a Rust based terminal. Find out why he's almost as excited about Warp as he is when DoorDash shows up with Chick-fil-a. [00:19:48] The boys talk tmux and Andrew tells us the NUMBER 1 reason why he uses it. Tell us if you've had this happen. Ha! And have we told you how much Andrew loves Warp? He tells us more things it can do to make your life easier.[00:25:39] Collin moved to Vim about six months ago and talks about making the move over to it. Andrew tried it in the past, and he thinks it's time to board the Vim train again. Like he says, and this applies to anything new you bring into your workflow, “You just need to dive in, take your time, and you're gonna be moving slow at first.”[00:28:11] The whole Vim talk evolves into remapping your keyboard to prevent your fingers from contorting.  [00:34:49] After Andrew talks about some of his go to VSCode plugins, Collin wants to know more about his VSCode setup and layout. Andrew talks more about some of the plugins he likes, like Customize UI, and how he likes to keep his VSCode looking clean.[00:36:31] Let's talk monitor setups: Multiple, single, full screen. Find out Collin and Andrew's setup. Collin shares a keyboard shortcut he uses to manage his windows.[00:40:00] One last thing…whether you prefer Alfred or Raycast, it's time to replace your Spotlight. Andrew talks about the benefits it has in his workflow and Collin, who doesn't need another tool, is intrigued. [00:43:23] So, let's summarize it for you. If you're new to coding…bookmark this spot. Learn it, know it, live it. Panelist:Andrew MasonGuest/Panelist:Collin JilbertSponsor:  HoneybadgerLinks:Jason Charnes TwitterChris Oliver TwitterAndrew Mason TwitterCollin Jilbert TwitterZnap!VimtpopewarptmuxRails Fast NavRails Flip-FlopMake VSCode Awesome E-BookCustomize UIBetterTouchToolAlfredRaycast

Welcome to another edition of the Blacksmith's Furnace! This week Pete kicks things off in the hot seat. He talks about how he would address someone who is reading the book of enoch and talks about the difference between vibes and the Spirpit when it comes to worship. We then go on to talk about tradition and it's usefulness in today's society. This was off the back of the royal traditions that had been recently observed in the UK following the Queen's death and the coronation of a new King. For our Hookups, Pete suggested a universal search app for Mac power users called Raycast, check it out here https://www.raycast.com/, Mo suggested checking out his digital exhibition which starts today the 4th of October, check him out on instagram hmuseh https://www.instagram.com/hmuseh/?hl=en-gb, and Rob suggested an album, P Money is Power by an artist called Pmoney check it out here https://open.spotify.com/album/1nvsuuiJHjn42yUApyYtD5?si=rRJWQQ5gSUy9UWDMSZ5iAg We hope you enjoy the episode and if you do please let us know in the comments and let your friends know by sharing, and if you don't, please let us know in the comments and let your friends know by sharing. We're big believers in the "win-win"Take care and stay blessed. Special thanks to RUDE (@itsrudeboy) for the intro and outro music. And to Calvin A Turner founder of Torra Media (facebook , @torramedia) and digital designer extraordinaire for TheOrdinaryAmazing.com logo design.

Wspaniały Januleusz! 444 odcinek podcastu. 8,5 roku prowadzenia podcastu - to dużo czasu. Dobra, a teraz tak. W odcinku mamy rzeczy np. prośba o pomoc przy Safari, o grach, o naszych ludziach co znajdują bugi w MacOS oraz o Raycast! Linki: - https://support.apple.com/en-us/HT213444 - https://twitter.com/_r3ggi - https://objective-see.org/tools.html - https://www.raycast.com/ Zostań mecenasem naszego podcastu. Już od 15 zł lub 3$ odblokuj dostęp do półodcinków After Dark dostępnych tylko dla Patronów. Kliknij tu (https://www.patreon.com/ywp) i wspieraj redakcję Yes Was. Porozmawiaj z nami i naszą cudowną społecznością na forum Yes Was Podcast (https://forum.yeswas.pl). Kanał z dobrymi promkami: YesWasDiscount Możesz być z nami w kontakcie także na: grupie na Telegramie, Twitterze i Facebooku. Prowadzący: Paweł Orzech, Wojtek Wieman Identyfikacja wizualna: Antoni Kwiatkowski Intro: Breakmaster Cylinder 00:00:00 - Intro BMC 00:00:28 - Januleusz 00:01:12 - YouTube i Safari to porażka (u Orzecha) 00:10:12 - KryptoWindowsiarz 00:11:55 - Gierki, gierki 00:17:35 - NASI znajdują bugi 00:27:56 - Raycast 00:41:36 - Cyberpunk 00:52:25 - Patreoniusz 00:54:51 - Outro BMC

In this supper club episode of Syntax, Wes and Scott talk with Thomas Mann about Raycast - an app that can replace Spotlight on your Mac, and do so much more. FireHydrant - Sponsor  Incidents are hard. Managing them shouldn't be. FireHydrant makes it easy for anyone in your organization to respond to incidents efficiently and consistently. Intuitive, guided workflows provide turn-by-turn navigation for incident response, while thoughtful prompts and powerful integrations capture all of your incident data to drive useful retros and actionable analytics.  Did we mention that FireHydrant is free? Get started at Firehydrant.com/syntax   Show Notes @ThomasPaulMann 01:49 What is Raycast? Raycast Raycast Store 08:11 Do you have designers on your team to help guide UI? 10:13 Why build it native instead of HTML and CSS? 13:12 Why did you choose React? 21:54 How do you figure out what's possible in system level APIs? 26:40 Snippets make use of SQLite SQLite 29:05 Encrypted local storage data 33:11 Any plans for theming for Raycast? 35:20 What is the pricing model? 37:06 What was your Y combinator experience like? Y Combinator Careers 42:08 Any plans for future features? 44:08 Supper Club questions Leopold FC660C Black 65% Dye Sub PBT Mechanical Keyboard iTerm Starship 51:25 SIIIIICK ××× PIIIICKS ××× ××× SIIIIICK ××× PIIIICKS ××× Nothing Ear Buds Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

Join us this week with Thomas Paul Mann, one of the founders of Raycast, a new command palette for Mac. We talk about the history of Raycast, how it came to be, and what the future holds for the app. The app is powered by a powerful plugin system that use a custom react renderer. If you haven't checked it out yet, you should definitely give it a try!Join our patreon for the full episode.Thomas' Twitter GitHub raycastTwitter raycastTooltipsAndrewhttps://pnpm.io/https://motion.devJustinhttps://github.com/esamattis/react-zormhttps://github.com/PipedreamHQ/pipedreamThomasMy tooltips: I recently re-discovered newsletters for me. Here are three that I read every week:Console Newsletter - The best tools for developersPointer - A Reading Club For Software DevelopersRefind - Get smarter every dayFor tools, I rely heavily on Raycast. Few of my most used extensions:Visual Studio Recent ProjectsGIF SearchGoogle Translate

CCATP #740 – Allison on Bart's Let's Talk Photography – Mirrorless Camera Conversion Comment on Bodie's Flume water monitor post How I Messed Up And Played the Binoculars Conversation Twice Support the Show Raycast – Spotlight Replacement And Oh So Much More Join the Conversation: allison@podfeet.com podfeet.com/slack Support the Show: Patreon Donation PayPal one-time donation Podfeet Podcasts Mugs at Zazzle Podfeet 15-Year Anniversary Shirts Referral Links: Parallels Toolbox - 3 months free for you and me Learn through MacSparky Field Guides - 15% off for you and me Backblaze - One free month for me and you Setapp - One free month for me and you Eufy - $40 for me if you spend $200. Sadly nothing in it for you. Google Fi - $20 Credit to both of our accounts after 30 days active PIA VPN - One month added to Paid Accounts for both of us

Episodio 180. Los episodios del futuro son todos en blanco y negro con  plomeros en NY y plomeros en Miami y cerveza gratis en negocios de toda la vida. ¿Es eso lo que Europa quiere? ¡Qué buen ganso! Señor Alfredo yo me estoy yendo. ✅ Follow Up ¿Por qué queremos cambiarnos de Streamyard si quedó claro en el episodio pasado que tiene excelente UI? - https://goose.game/ El mejor tip pendejo para macOS que Jaime ha visto (don't wait on drag) Shazam desde el Control Center no triggerea la sincronización con Spotify El clipboard manager de Raycast es amazing American Airlines y el vuelo a San Francisco cambiado ¿Dónde quedarse en Los Ángeles?

[00:02:46] Andrew tells us about being on the Rubber Duck Dev Show livestream with Collin Jilbert. [00:05:14] Have you ever used Alfred? Andrew fills us in on the app and Raycast. [00:12:15] Chris explains the “gem mining” he's been doing.[00:16:38] Andrew and Chris chat about using SQLite.[00:20:41] Andrew asks Chris if he ever thinks how much extra code it is to have to support all these different things. Chris explains why he doesn't think it be a whole lot. [00:23:20] We find out when Chris is evaluating these types of decisions, if he ever tries to write performance tests, benchmarks, or something to evaluate those assumptions and he explains how he thinks about performance in a gem. [00:27:04] Andrew mentions since RBS is becoming better with more integrations and more tools, he asks Chris if he's ever considered adding some typing support.[00:31:30] We hear about an issue Andrew had when rewriting their checkout at Podia and Chris tells us about an issue he ran into with Stripe. They also talk about issues they were having with the new element on Google Pay, Apple Pay, and Afterpay.[00:37:39] Andrew does a shoutout to CJ, Developer Advocate at Stripe, who helped him with some things that weren't working for Andrew and his team, and Chris tells us why he likes Stripe so much. [00:39:12] Chris tells us about his first job as a Rails developer, Andrew shares one more thing about Stripe that they do that's cool, and Chris shares something related to bank accounts on Stripe and the demos they have.[00:43:50] Find out the story about Bruce Wayne. [00:46:15] If you're using RBS, want to talk about it and what's happening in the RBS world, Chris and Andrew would love to talk with you. [00:47:28] Chris does a shout out to firstrubyfriend.org, and if you're a Junior or want to be a Ruby Developer, go to this website.[00:48:25] Andrew and Chris go in depth about mentors and mentees, they explain how there's a lot more aspects to being a developer than coding, and why it's so important to take initiative if you are a mentee. [00:59:57] Andrew highlights something Chris said about promoting the community as a mentor.Panelists:Chris OliverAndrew MasonSponsor:HoneybadgerLinks:Chris Oliver TwitterAndrew Mason TwitterJason Charnes TwitterRubber Duck Dev Show Episode 51 with Andrew Mason and Collin JilbertAlfred RaycastSQLiteStripeCJ Avilla TwitterFirst Ruby FriendRuby Radar NewsletterRuby Radar Twitter

Steph has an update and a question wrapped into one about the work that is being done to migrate the Test::Unit test over to RSpec. Chris got to do something exciting this week using dry-monads. Success or failure? This episode is brought to you by BuildPulse (https://buildpulse.io/bikeshed). Start your 14-day free trial of BuildPulse today. Bartender (https://www.macbartender.com/) dry-rb - dry-monads v1.0 - Pattern matching (https://dry-rb.org/gems/dry-monads/1.0/pattern-matching/) alfred-workflows (https://github.com/tupleapp/alfred-workflows/blob/master/scripts/online_users.rb) Raycast (https://www.raycast.com/) ruby-science (https://github.com/thoughtbot/ruby-science) Inertia.js (https://inertiajs.com/) Remix (https://remix.run/) Become a Sponsor (https://thoughtbot.com/sponsorship) of The Bike Shed! Transcript: AD: Flaky tests take the joy out of programming. You push up some code, wait for the tests to run, and the build fails because of a test that has nothing to do with your change. So you click rebuild, and you wait. Again. And you hope you're lucky enough to get a passing build this time. Flaky tests slow everyone down, break your flow, and make things downright miserable. In a perfect world, tests would only break if there's a legitimate problem that would impact production. They'd fail immediately and consistently, not intermittently. But the world's not perfect, and flaky tests will happen, and you don't have time to fix all of them today. So how do you know where to start? BuildPulse automatically detects and tracks your team's flaky tests. Better still, it pinpoints the ones that are disrupting your team the most. With this list of top offenders, you'll know exactly where to focus your effort for maximum impact on making your builds more stable. In fact, the team at Codecademy was able to identify their flakiest tests with BuildPulse in just a few days. By focusing on those tests first, they reduced their flaky builds by more than 68% in less than a month! And you can do the same because BuildPulse integrates with the tools you're already using. It supports all of the major CI systems, including CircleCI, GitHub Actions, Jenkins, and others. And it analyzes test results for all popular test frameworks and programming languages, like RSpec, Jest, Go, pytest, PHPUnit, and more. So stop letting flaky tests slow you down. Start your 14-day free trial of BuildPulse today. To learn more, visit buildpulse.io/bikeshed. That's buildpulse.io/bikeshed. STEPH: What type of bird is the strongest bird? CHRIS: I don't know. STEPH: A crane. [laughter] STEPH: You're welcome. And on that note, shall we wrap up? CHRIS: Let's wrap up. [laughter] Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Chris Toomey. STEPH: And I'm Steph Viccari. CHRIS: And together, we're here to share a bit of what we've learned along the way. So, Steph, what's new in your world? STEPH: Hey, Chris, I saw a good movie I'd like to tell you about. It was just over the weekend. It's called The Duke, and it's based on a real story. I should ask, have you seen it? Have you heard of this movie called The Duke? CHRIS: I don't think so. STEPH: Okay, cool. It's a true story, and it's based on an individual named Kempton Bunton who then stole a particular portrait, a Goya portrait; if you know your artist, I do not. But he stole a Goya portrait and then essentially held at ransom because he was a big advocate that the BBC News channel should be free for people that are living on a pension or that are war veterans because then they're not able to afford that fee. But then, if you take the BBC channel away from them, it disconnects them from society. And it's a very good movie. I highly recommend it. So I really enjoyed watching that over the weekend. CHRIS: All right. Excellent recommendation. We will, of course, add that to the show notes mostly so that I can find it again later. STEPH: On a more technical note, I have a small update, or it's more of a question. It's an update and a question wrapped into one about the work that is being done to migrate the Test::Unit test over to RSpec. This has been quite a journey that Joël and I have been on for a while now. And we're making progress, but we're realizing that we're spending like 95% of our time in the test setup and porting that over, specifically because we're mapping fixture data over to FactoryBot, and we're just realizing that's really painful. It's taking up a lot of time to do that. And initially, when I realized we were just doing that, we hadn't even really talked about it, but we were moving it over to FactoryBot. I was like, oh, cool. We'll get to delete all these fixtures because there are around 208 files of them. And so that felt like a really good additional accomplishment to migrating the test over. But now that we realize how much time we're spending migrating the data over for that test setup, we've reevaluated, and I shared with Joël in the Slack channel. I was like, crap. I was like, I have a bad idea, and I can't not say it now because it's crossed my mind. And my bad idea was what if we stopped porting over fixtures to FactoryBot and then we just added the fixtures to a directory that RSpec would look so then we can rely on those fixtures? And then that way, we're literally then ideally just copying over from Test::Unit over to RSpec. But it does mean a couple of things. Well, one, it means that we're now running those fixtures at the beginning of RSpec test. We're introducing another pattern of where these tests are already using FactoryBot, but now they have fixtures at the top, and then we won't get to delete the fixtures. So we had a conversation around how to manage and mitigate some of those concerns. And we're still in that exploratory. We're going to test it out and see if this really speeds us up referencing the fixtures. The question that's wrapped up in this is there's something different between how fixtures generate data and how factories generate data. So I've run into this a couple of times now where I moved data over to just call a factory. But then I was hitting these callbacks or after-save-hooks or weird things that were then preventing me from creating the record, even though fixtures was creating them just fine. And then Joël pointed out today that he was running into something similar where there were private methods that were getting called. And there were all sorts of additional code that was getting run with factories versus fixtures. And I don't have an answer. Like, I haven't looked into this. And it's frankly intentional because I was trying hard to not dive into understanding the mechanics. We really want to get through this. But now I'm starting to ponder a little more as to what is different with fixtures and factories? And I liked that factories is running these callbacks; that feels correct. But I'm surprised that fixtures doesn't, or at least that's the experience that I'm having. So there's some funkiness there that I'd like to explore. I'll be honest; I don't know if I'm going to. But if anybody happens to know what that funkiness is or why fixtures and factories are different in that regard, I would be very intrigued because, at some point, I might look into it just because I would like to know. CHRIS: Oh, that is interesting. I have not really worked with fixtures much at all. I've lived a factory life myself, and thus that's where almost all of my experience is. I'm not super surprised if this ends up being the case, like, the idea that fixtures are just some data that gets shoveled into the database directly as opposed to FactoryBot going through the model layer. And so it's sort of like that difference. But I don't know that for certain. That sounds like what this is and makes sense conceptually. But I think this is what you were saying like, that also kind of pushes me more in the direction of factories because it's like, oh, they're now representative. They're using our model layer, where we're defining certain truths. And I don't love callbacks as a mechanism. But if your app has them, then getting data that is representative is useful in tests. Like one of the things I add whenever I'm working with FactoryBot is the FactoryBot lint rake task RSpec thing that basically just says, "Are your factories valid?" which I think is a great baseline to have. Because you may add a migration that adds a default constraint or something like that to the database that suddenly all your factories are invalid, and it's breaking tests, but you don't know it. Like subtly, you change it, and it doesn't actually break a test, but then it's harder later. So that idea of just having more correctness baked in is always nice, especially when it can be automated like that, so definitely a fan of that. But yeah, interested if you do figure out the distinction. I do like your take, though, of like, but also, maybe I just won't figure this out. Maybe this isn't worth figuring it out. Although you were in the interesting spot of, you could just port the fixtures over and then be done and call the larger body of work done. But it's done in sort of a half-complete way, so it's an interesting trade-off space. I'm also interested to hear where you end up on that. STEPH: Yeah, it's a tough trade-off. It's one that we don't feel great about. But then it's also recognizing what's the true value of what we're trying to deliver? And it also comes down to the idea of churn versus complexity. And I feel like we are porting over existing complexity and even adding a smidge, not actual complexity but adding a smidge of indirection in terms that when someone sees this file, they're going to see a mixed-use of fixtures and factories, and that doesn't feel good. And so we've already talked about adding a giant comment above fixtures that just is very honest and says, "Hey, these were ported over. Please don't mimic this. But this is some legacy tests that we have brought over. And we haven't migrated the fixtures over to use factories." And then, in regards to the churn versus complexity, this code isn't likely to get touched like these tests. We really just need them to keep running and keep validating scenarios. But it's not likely that someone's going to come in here and really need to manage these anytime soon. At least, this is what I'm telling myself to make me feel better about it. So there's also that idea of yes, we are porting this over. This is also how they already exist. So if someone did need to manage these tests, then going to Test::Unit, they would have the same experience that they're going to have in RSpec. So that's really the crux of it is that we're not improving that experience. We're just moving it over and then trying to communicate that; yes, we have muddied the waters a little bit by introducing this other pattern. So we're going to find a way to communicate why we've introduced this other pattern, but that way, we can stay focused on actually porting things over to RSpec. As for the factories versus fixtures, I feel like you're onto something in terms of it's just skipping that model layer. And that's why a lot of that functionality isn't getting run. And I do appreciate the accuracy of factories. I'd much rather know is my data representative of real data that can get created in the world? And right now, it feels like some of the fixtures aren't. Like, how they're getting created seemed to bypass really important checks and validations, and that is wrong. That's not what we want to have in our test is, where we're creating data that then the rest of the application can't truly create. But that's another problem for another day. So that's an update on a trade-off that we have made in regards to the testing journey that we are on. What's going on in your world? CHRIS: Well, we got to do something exciting this week. I was working on some code. This is using dry-monads, the dry-rb space. So we have these result objects that we use pretty pervasively throughout the app, and often, we're in a controller. We run one of these command objects. So it's create user, and create user actually encompasses a ton of logic in our app, and that object returns a result. So it's either a success or a failure. And if it's a success, it'll be a success with that new user wrapped up inside of it, or if it's a failure, it's a specific error message. Actually, different structured error messages in different ways, some that would be pushed to the form, some that would be a flash message. There are actually fun, different things that we do there. But in the controller, when we interact with those result objects, typically what we'll do is we'll say result equals create user dot run, (result=createuser.run) and then pass it whatever data it needs. And then on the next line, we'll say results dot either, (results.either), which is a method on these result objects. It's on both the success and failure so you can treat them the same. And then you pass what ends up being a lambda or a stabby proc, or I forget what they are. But one of those sort of inline function type things in Ruby that always feel kind of weird. But you pass one of those, and you actually pass two of them, one for the success case and one for the failure case. And so in the success case, we redirect back with a notice of congratulations, your user was created. Or, in the failure case, we potentially do a flash message of an alert, or we send the errors down, or whatever it ends up being. But it allows us to handle both of those cases. But it's always been syntactically terrible, is how I would describe it. It's, yeah, I'm just going to leave it at that. We are now living in a wonderful, new world. This has been something that I've wanted to try for a while. But I finally realized we're actually on Ruby 2.7, and so thus, we have access to pattern matching in Ruby. So I get to take it for a spin for the first time, realizing that we were already on the correct version. And in particular, dry-monads has a page in their docs specific to how we can take advantage of pattern matching with the result objects that they provide us. There's nothing specific in the library as far as I understand it. This is just them showing a bunch of examples of how one might want to do it if they're working with these result objects. But it's really great because it gives the ability to interact with, you know, success is typically going to be a singular case. There's one success branch to this whole logic, but there are like seven different ways it can fail. And that's the whole idea as to why we use these command objects and the whole Railway Oriented Programming and that whole thing which I have...what is this word? [laughs] I feel like I should know it. It's a positive rant. I have raved; that is how our users kindly pointed that out to us. I have raved about the Railway Oriented Programming that allows us to do. But it's that idea that they're actually, you know, there's one happy path, and there are seven distinct failure modes, seven unhappy paths. And now, using pattern matching, we actually get a really expressive, readable, useful way to destructure each of those distinct failures to work with the particular bits of data that we need. So it was a very happy day, and I got to explore it. This is, again, a feature of Ruby, not a feature of dry-monads. But dry-monads just happens to embrace it and work really well with it. So that was awesome. STEPH: That is awesome. I've seen one or two; I don't know, I've seen a couple of tweets where people are like, yeah, Ruby pattern matching. I haven't found a way to use it. So I'm excited that you just shared a way that you found to use it. I'm also worried what it says about our developer culture that we know the word rant so well, but rave, we always have to reach back into our memory to be like, what's that positive word or something that we like? [laughs] CHRIS: And especially here on The Bike Shed, where we try to gravitate towards the positive. But yeah, it's an interesting point that you make. STEPH: We're a bunch of ranters. It's what we do, pranting ranters. I don't know why we're pranting. [laughs] CHRIS: Because it's that exciting. That's what it is. Actually, there was an interesting thing as we were playing around with the pattern matching code, just poking around in the console session with it, and it prints out a deprecation warning. It's like, warning: this is an experimental feature. Do not use it, be careful. But in the back of my head, I was like, I actually know how this whole thing plays out, Ruby 2.7, and I assure you, it's going to be fine. I have been to the future, at least I'm pretty sure. I think the version that is in Ruby 2.7 did end up getting adopted basically as it stands. And so, I think there is also a setting to turn off that deprecation warning. I haven't done it yet, but I mostly just enjoyed the conversation that I had with this deprecation message of like, listen, I've been to the future, and it's great. Well, it's complicated, but specific to this pattern matching [laughs] in Ruby 3+ versions, it went awesome. And I'm really excited about that future that we now live in. STEPH: I wish we had that for so many more things in our life [laughs] of like, here's a warning, and it's like, no, no, I've seen the future. It's all right. Or you're totally right; I should avoid and back out of this now. CHRIS: If only we could know how the things would play out, you know. But yeah, so pattern matching, very cool. I'll include a link in the show notes to the particular page in the dry-monads docs. But there are also other cool things on the internet. In an unrelated but also cool thing that I found this week, we use Tuple a lot within our organization for pair programming. For anyone who's not familiar with it, it's a really wonderful piece of technology that allows you to pair program pretty seamlessly, better video quality, all of those nice things that we want. But I found there was just the tiniest bit of friction in starting a Tuple call. I know I want to pair with this person. And I have to go up and click on the little menu bar, and then I have to find their name, then I have to click a button. That's just too much. That's not how...I want to live my life at the keyboard. I have a thing called Bartender, which is a little menu bar manager utility app that will collapse down and hide the icons. But it's also got a nice, little hotkey accessible pop-up window that allows me to filter down and open one of the menu bar pop-out menus. But unfortunately, when that happens, the Tuple window isn't interactive at that point. I can't use the arrow keys to go up and down. And so I was like, oh, man, I wonder if there's like an Alfred workflow for this. And it turns out indeed there is actually managed by the kind folks at Tuple themselves. So I was able to find that, install it; it's great. I have it now. I can use that. So that was a nice little upgrade to my workflow. I can just type like TC space and then start typing out the person's name, and then hit enter, and it will start a call immediately. And it doesn't actually make me more productive, but it makes me happier. And some days, that's what matters. STEPH: That's always so impressive to me when that happens where you're like, oh, I need a thing. And then you went through the saga that you just went through. And then the people who manage the application have already gotten there ahead of you, and they're like, don't worry, we've created this for you. That's one of those just beautiful moments of like, wow, y'all have really thought this through on a bunch of different levels and got there before me. CHRIS: It's somewhat unsurprising in this case because it's a very developer-centric organization, and Ben's background being a thoughtbot developer and Alfred user, I'm almost certain. Although I've seen folks talking about Raycast, which is the new hotness on the quick launcher world. I started eons ago in Quicksilver, and then I moved to Alfred, I don't know, ten years ago. I don't know what time it is anymore. But I've been in Alfred land for a while, but Raycast seems very cool. Just as an aside, I have not allowed myself... [laughs] this is another one of those like; I do not have permission to go explore this new tool yet because I don't think it will actually make me more productive, although it could make me happier. So... STEPH: I haven't heard of that one, Raycast. I'm literally adding it to the show notes right now as a way so you can find The Duke later, and I can find Raycast later [chuckles] and take a look at it and check it out. Although I really haven't embraced the whole Alfred workflow. I've seen people really enjoy it and just rave about it and how wonderful it is. But I haven't really leaned into that part of the world; I don't know why. I haven't set any hard and fast rules for myself where I can't play around with these technologies, but I haven't taken the time to do it either. CHRIS: You've also not found yourself writing thousands of lines of Vimscript because you thought that was a good idea. So you don't need as many guardrails it would seem. That's my guess. STEPH: This is true. CHRIS: Whereas I need to be intentional [laughs] with how I structure my interaction with my dev tools. STEPH: Instead, I'm just porting over fixtures from one place to another. [laughs] That's the weird space that I'm living in instead. [laughs] CHRIS: But you're getting paid for that. No one paid me for the Vimscript I wrote. [laughter] STEPH: That's fair. Speaking around process-y things, there's something that's been on my mind that Valeria, another thoughtboter, suggested around how we structure our meetings and the default timing that we have for meetings. So Thursdays are my team-focused day. And it's the day where I have a lot of one on ones. And I realized that I've scheduled them back to back, which is problematic because then I have zero break in between them, which I'm less concerned about that because then I can go for an hour or something and not have a break. And I'm not worried about that part. But it does mean that if one of those discussions happens to go over just even for like two or three minutes, then it means that someone else is waiting for me in those two to three minutes. And that feels unacceptable to me. So Valeria brought up a really good idea where I think it's only with the Google Meet paid version. I could be wrong there. But I think with the paid version of it that then you can set the new default for how long a meeting is going to last. So instead of having it default to 30 minutes, have it default to 25 minutes. So then, that way, you do have that five-minute buffer. So if you do go over just like two or three minutes with someone, you've still got like two minutes to then hop to the next call, and nobody's waiting for you. Or if you want those five minutes to then grab some water or something like that. So we haven't implemented it just yet because then there's discussion around is this a new practice that we want everybody to move to? Because I mean, if just one person does it, it doesn't work. You really need everybody to buy into the concept of we're now defaulting to 25 versus 30-minute meetings. So I'll have to let you know how that goes. But I'm intrigued to try it out because I think that would be very helpful for me. Although there's a part of me that then feels bad because it's like, well, if I have 30 minutes to chat with somebody, but now I'm reducing it to 25 minutes each time, I didn't love that I'm taking time away from our discussion. But that still feels like a better outcome than making somebody wait for three to five minutes if something else goes over. So have you ever run into something like that? How do you manage back-to-back meetings? Do you intentionally schedule a break in between or? CHRIS: I do try to give myself some buffer time. I stack meetings but not so much so that they're just back to back. So I'll stack them like Wednesdays are a meeting-heavy day for me. That's intentional just to be like, all right, I know that my day is going to get chopped up. So let's just really lean into that, chop the heck out of Wednesday afternoons, and then the rest of the week can hopefully have slightly longer deep work-type sessions. And, yeah, in general, I try and have like a little gap in between them. But often what I'll do for that is I'll stagger the start of the next meeting to be rather than on the hour or the half-hour, I start it on the 15th minute. And so then it's sort of I now have these little 15-minute gaps in my workflow, which is enough time to do one or two small things or to go get a drink or whatever it is or if things do run over. Like, again, I feel what you're saying of like, I don't necessarily want to constrain a meeting. Or I also don't necessarily want to go into the habit of often over-running. I think it's good to be intentional. Start meetings on time, end meetings on time. If there's a great conversation that's happening, maybe there's another follow-up meeting that should happen or something like that. But for as nonsensical of a human as I believe myself to be, I am rather rigid about meetings. I try very hard to be on time. I try very hard to wrap them up on time to make sure I go to the next one. And so with that, the 15-minute staggering is what I've found works for me. STEPH: Yeah, that makes sense. One-on-ones feels special to me because I wholeheartedly agree with being very diligent about like, hey, this is our meeting time. Let's do a time check. Someone says that at the end, and then that way, everybody can move on. But one on ones are, there's more open discussion space, and I hate cutting people off, especially because it might not be until the last 15 minutes that you really got into the meat of the conversation. Or you really got somewhere that's a little bit more personal or things that you want to talk about. So if someone's like, "Yeah, let me tell you about my life goals," and you're like, "Oh, no, wait, sorry. We're out of time." That feels terrible and tragic to do. So I struggle with that part of it. CHRIS: I will say actually, on that note, I'm now thinking through, but I believe this to be true. Everyone that reports to me I have a 45-minute one-on-one with, and then my CEO I set up the one-on-one. So I also made that one a 45-minute one-on-one. And that has worked out really well. Typically, I try and structure it and reiterate this from time to time of, like, hey, this is your space, not mine. So let's have whatever conversation fits in here. And it's fine if we don't need to use the whole time, but I want to make sure that we have it and that we protect it. Because I often find much like retro, I don't know; I think everything's fine. And then suddenly the conversation starts, and you're like, you know what? Actually, I'm really concerned now that you mentioned it. And you need that sort of empty space that then the reality sort of pop up into. And so with one on one, I try and make sure that there is that space, but I'm fine with being like, we can cut this short. We can move on from one-on-one topics to more of status updates; let's talk about the work. But I want to make sure that we lead with is there anything deeper, any concerns, anything you want to talk through? And sort of having the space and time for that. STEPH: I like that. And I also think it speaks more directly to the problem I'm having because I'm saying that we keep running over a couple of minutes, and so someone else is waiting. So rather than shorten it, which is where I'm already feeling some pain...although I still think that's a good idea to have a default of 25-minute meetings so then that way, there is a break versus the full 30. So if people want to have back-to-back meetings, they still have a little bit of time in between. But for one on ones specifically, upping it to 45 minutes feels nice because then you've got that 15-minute buffer likely. I mean, maybe you schedule a meeting, but, I don't know, that's funky. But likely, you've got a 15-minute buffer until your next one. And then that's also an area that I feel comfortable in sharing with folks and saying, "Hey, I've booked this whole 45 minutes. But if we don't need the whole time, that's fine." I'm comfortable saying, "Hey, we can end early, and you can get more of your time back to focus on some other areas." It's more the cutting someone off when they're talking because I have to hop to the next thing. I absolutely hate that feeling. So thanks, I think I'll give that a go. I think I'll try actually bumping it up to 45 minutes, presuming that other people like that strategy too, since they're opting in [laughs] to the 45 minutes structure. But that sounds like a nice solution. CHRIS: Well yeah, happy to share it. Actually, one interesting thing that I'm realizing, having been a manager at thoughtbot and then now being a manager within Sagewell, the nature of the interactions are very different. With thoughtbot, I was often on other projects. I was not working with my team day to day in any real capacity. So it was once every two weeks, I would have this moment to reconnect with them. And there was some amount of just catching up. Ideally, not like status update, low-level sort of thing, but sort of just like hey, what have you been working on? What have you been struggling with? What have you been enjoying? There was more like I needed bigger space, I would say for that, or it's not surprising to me that you're bumping into 30 minutes not being quite long enough. Whereas regularly, in the one on ones that I have now, we end up cutting them short or shifting out of true one-on-one mode into more general conversation and chatting about Raycast or other tools or whatever it is because we are working together daily. And we're pairing very regularly, and we're all on the same project and all sorts of in sync and know what's going on. And we're having retro together. We have plenty of places to have the conversation. So the one-on-one again, still, I keep the same cadence and the same time structure just because I want to make sure we have the space for any day that we really need that. But in general, we don't. Whereas when I was at thoughtbot, it was all the more necessary. And I think for folks listening; I could imagine if you're in a team lead position and if you're working very closely with folks, then you may be on the one side of things versus if you're a little bit more at a distance from the work that they're doing day to day. That's probably an interesting question to ask, and think about how you want to structure it. STEPH: Yeah, I think that's an excellent point. Because you're right; I don't see these individuals. We may not have really gotten to interact, except for our daily syncs outside of that. So then yeah, there's always like a good first 10 minutes of where we're just chatting about life and catching up on how things are going before then we dive into some other things. So I think that's a really good point. Cool, solving management problems on the mic. I dig it. In slightly different news, I've joined a book club, which I'm excited about. This book club is about Ruby. It's specifically reading the book Ruby Science, which is a book that was written and published by thoughtbot. And it requires zero homework, which is my favorite type of book club. Because I have found I always want to be part of book clubs. I'm always interested in them, but then I'm not great at budgeting the time to make sure I read everything I'm supposed to read. And so then it comes time for folks to get together. And I'm like, well, I didn't do my homework, so I can't join it. But for this one, it's being led by Joël, and the goal is that you don't have to do the homework. And they're just really short sections. So whoever's in charge of leading that particular session of the book club they're going to provide an overview of what's covered in whatever the reading material that we're supposed to read, whatever topic we're covering that day. They're going to provide an overview of it, an example of it, so then we can all talk about it together. So if you read it, that's wonderful. You're a bit ahead and could even join the meeting like five minutes late. Or, if you haven't read it, then you could join and then get that update. So I'm very excited about it. And this was one of those books that I'd forgotten that thoughtbot had written, and it's one that I've never read. And it's public for anybody that's interested in it. So to cover a little bit of details about it, so it talks about code smells, ways to refactor code, and then also common patterns that you can use to solve some issues. So there's a lot of really just great content that's in it. And I'll be sure to include a link in the show notes for anyone else that's interested. CHRIS: And again, to reiterate, this book is free at this point. Previously, in the past, it was available for purchase. But at one point a number of years ago, thoughtbot set all of the books free. And so now that along with a handful of other books like...what's Edward's DNS book? Domain Name Sanity, I believe, is Edward's book name that Edward Loveall wrote when he was not a thoughtboter, [laughs] and then later joined as a thoughtboter, and then we made the book free. But on the specific topic of Ruby Science, that is a book that I will never forget. And the reason I will never forget it is that book was written by the one and only CTO Joe Ferris, who is an incredibly talented developer. And when I was interviewing with thoughtbot, I got down to the final day, which is a pairing session. You do a morning pairing session with one thoughtbot developer, and you do an afternoon pairing session with another thoughtbot developer. So in the morning, I was working with someone on actually a patch to Rails which was pretty cool. I'd never really done that, so that was exciting. And that went fine with the exception that I kept turning on Caps Lock on their keyboard because I was used to Caps Lock being CTRL, and then Vim was going real weird for me. But otherwise, that went really well. But then, in the afternoon, I was paired with the one and only CTO Joe Ferris, who was writing the book Ruby Science at that time. And the nature of the book is like, here's a code sample, and then here's that code sample improved, just a lot of sort of side-by-side comparisons of code. And I forget the exact way that this went, but I just remember being terrified because Joe would put some code up on the screen and be like, "What do you think?" And I was like, oh, is this the good code or the bad code? I feel like I should know. I do not know. I'm not sure. It worked out fine, I guess. I made it through. But I just remember being so terrified at that point. I was just like, oh no, this is how it ends for me. It's been a good run. STEPH: [laughs] CHRIS: I made it this far. I would have loved to work for this nice thoughtbot company, but here we are. But yeah, I made it through. [laughs] STEPH: There are so many layers to that too where it's like, well if I say it's terrible, are you going to be offended? Like, how's this going to go for me if I speak my truths? Or what am I going to miss? Yeah, that seems very interesting (I kind of like it.) but also a terrifying pairing session. CHRIS: I think it went well because I think the code...I'd been following thoughtbot's work, and I knew who Joe was and had heard him on podcasts and things. And I kind of knew roughly where things were, and I was like, that code looks messy. And so I think I mostly got it right, but just the openness of the question of like, what do you think? I was like, oh God. [laughs] So yeah, that book will always be in my memories, is how I would describe it. STEPH: Well, I'm glad it worked out so we could be here today recording a podcast together. [laughs] CHRIS: Recording a podcast together. Now that I say all that, though, it's been a long time since I've read the book. So maybe I'll take a revisit. And definitely interested to hear more about your book club and how that goes. But shifting ever so slightly (I don't have a lot to say on this topic.) but there's a new framework technology thing out there that has caught my attention. And this hasn't happened for a while, so it's kind of novel for me. So I tend to try and keep my eye on where is the sort of trend of web development going? And I found Inertia a while ago, and I've been very, very happy with that as sort of this is the default answer as to how I build websites. To be clear, Inertia is still the answer as to how I build websites. I love Inertia. I love what it represents. But I'm seeing some stuff that's really interesting that is different. Specifically, Remix.run is the thing that I'm seeing. I mentioned it, I think, in the last episode talking about there was some stuff that they were doing with data loading and async versus synchronous, and do you wait on it or? They had built some really nice levers and trade-offs into the framework. And there's a really great talk that Ryan Florence, one of the creators of Remix.run, gave about that and showed what they were building. I've been exploring it a little bit more in-depth now. And there is some really, really interesting stuff in Remix. In particular, it's a meta-framework, I think, is the nonsense phrase that we use to describe it. But it's built on top of React. That won't be true for forever. I think it's actually they would say it's more built on top of React Router. But it is very similar to Next.js for folks that have seen that. But it's got a little bit more thought around data loading. How do we change data? How do we revalidate data after? There's a ton of stuff that, having worked in many React client-side API-heavy apps that there's so much pain, cache invalidation. How do you think about the cache? When do you fetch from the network? How do you avoid showing 19 different loading spinners on the page? And Remix as a framework has some really, I think, robust and well-thought-out answers to a lot of that. So I am super-duper intrigued by what they're doing over there. There's a particular video that I think shows off what Remix represents really well. It's Ryan Florence, that same individual, the creator of Remix, building just a newsletter signup page. But he goes through like, let's start from the bare bones, simplest thing. It's just an input, and a form submits to the server. That's it. And so we're starting from web 2.0, long, long ago, sort of ideas, and then he gradually enhances it with animations and transitions and error states. And even at the end, goes through an accessibility audit using the screen reader to say, "Look, Remix helps you get really close because you're just using web fundamentals." But then goes a couple of steps further and actually makes it work really, really well for a screen reader. And, yeah, overall, I'm just super impressed by the project, really, really intrigued by the work that they're doing. And frankly, I see a couple of different projects that are sort of in this space. So yeah, again, very early but excited. STEPH: On their website...I'm checking it out as you're walking me through it, and on their website, they have "Say goodbye to Spinnageddon." And that's very cute. [laughs] CHRIS: There's some fundamental stuff that I think we've just kind of as a web community, we made some trade-offs that I personally really don't like. And that idea of just spinners everywhere just sending down a ball of application logic and a giant JavaScript file turning it on on someone's computer. And then immediately, it has to fetch back to the server. There are just trade-offs there that are not great. I love that Remix is sort of flipping that around. I will say, just to sort of couch the excitement that I'm expressing right now, that Remix exists in a certain place. It helps with building complex UIs. But it doesn't have anything in the data layer. So you have to bring your own data layer and figure out what that means. We have ActiveRecord within Rails, and it's deeply integrated. And so you would need to bring a Prisma or some other database connection or whatever it is. And it also doesn't have more sort of full-featured framework things. Like with Rails, it's very easy to get started with a background job system. Remix has no answer to that because they're like, no, no, this is what we're doing over here. But similarly, security is probably the one that concerns me the most. There's an open conversation in their discussion portal about CSRF protection and a back and forth of whether or not Remix should have that out of the box or not. And there are trade-offs because there are different adapters that you can use for auth. And each would require their own CSRF mitigation. But to me, that is the sort of thing that I would want a framework to have. Or I'd be interested in a framework that continues to build on top of Remix that adds in background jobs and databases and all that kind of stuff as a complete solution, something more akin to a Rails or a Laravel where it's like, here we go. This is everything. But again, having some of these more advanced concepts and patterns to build really, really delightful UIs without having to change out the fundamental way that you're building things. STEPH: Interesting. Yeah, I think you've answered a couple of questions that I had about it. I am curious as to how it fits into your current tech stack. So you've mentioned that you're excited and that it's helpful. But given that you already have Rails, and Inertia, and Svelte, does it plug and play with the other libraries or the other frameworks that you have? Are you going to have to replace something to then take advantage of Remix? What does that roadmap look like? CHRIS: Oh yeah, I don't expect to be using Remix anytime soon. I'm just keeping an eye on it. I think it would be a pretty fundamental shift because it ends up being the server layer. So it would replace Rails. It would replace the Inertia within the stack that I'm using. This is why as I started, I was like, Inertia is still my answer. Because Inertia integrates really well with Rails and allows me to do the sort of it's not progressive enhancement, but it's like, I want fancy UI, and I don't want to give up on Rails. And so, Inertia is a great answer for that. Remix does not quite fit in the same way. Remix will own all of the request-response lifecycle. And so, if I were to use it, I would need to build out the rest of that myself. So I would need to figure out the data layer. I would need to figure out other things. I wouldn't be using Rails. I'm sure there's a way to shoehorn the technologies together, but I think it sort of architecturally would be misaligned. And so my sense is that folks out there are building...they're sort of piecing together parts of the stack to fill out the rest. And Remix is a really fantastic controller and view from their down experience and routing layer. So it's routing, controller, view I would say Remix has a really great answer to, but it doesn't have as much of the other stuff. Whereas in my case, Inertia and Rails come together and give me a great answer to the whole story. STEPH: Got it. Okay, that's super helpful. CHRIS: But yeah, again, I'm in very much the exploratory phase. I'm super intrigued by a lot of what I've seen of it and also just sort of the mindset, the ethos of the project as it were. That sounds fancy as I say it, but it's what I mean. I think they want to build from web fundamentals and then enhance the experience on top of that, and I think that's a really great way to go. It means that links will work. It means that routing and URLs will work by default. It means that you won't have loading spinner Armageddon, and these are core fundamentals that I believe make for good websites and web applications. So super interested to see where they go with it. But again, for me, I'm still very much in the Rails Inertia camp. Certainly, I mean, I've built Sagewell on top of it, so I'm going to be hanging out with it for a while, but also, it would still be my answer if I were starting something new right now. I'm just really intrigued by there's a new example out there in the world, this Remix thing that's pushing the envelope in a way that I think is really great. But with that, my now…what was that? My second or my third rave? Also called the positive rant, as we call it. But yeah, I think on that note, what do you think? Should we wrap up? STEPH: Let's wrap up. CHRIS: The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review on iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey. STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeeee!!!!!!!!! ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Watch the live stream: Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training Test & Code Podcast Patreon Supporters Brian #1: Polars: Lightning-fast DataFrame library for Rust and Python Suggested by a several listeners “Polars is a blazingly fast DataFrames library implemented in Rust using Apache Arrow Columnar Format as memory model. Lazy | eager execution Multi-threaded SIMD (Single Instruction/Multiple Data) Query optimization Powerful expression API Rust | Python | ...” Python API syntax set up to allow parallel and execution while sidestepping GIL issues, for both lazy and eager use cases. From the docs: Do not kill parallelization The syntax is very functional and pipeline-esque: import polars as pl q = ( pl.scan_csv("iris.csv") .filter(pl.col("sepal_length") > 5) .groupby("species") .agg(pl.all().sum()) ) df = q.collect() Polars User Guide is excellent and looks like it's entirely written with Python examples. Includes a 30 min intro video from PyData Global 2021 Michael #2: PSF Survey is out Have a look, their page summarizes it better than my bullet points will. Brian #3: Gin Config: a lightweight configuration framework for Python Found through Vincent D. Warmerdam's excellent intro videos on gin on calmcode.io Quickly make parts of your code configurable through a configuration file with the @gin.configurable decorator. It's in interesting take on config files. (Example from Vincent) # simulate.py @gin.configurable def simulate(n_samples): ... # config.py simulate.n_samples = 100 You can specify: required settings: def simulate(n_samples=gin.REQUIRED)` blacklisted settings: @gin.configurable(blacklist=["n_samples"]) external configurations (specify values to functions your code is calling) can also references to other functions: dnn.activation_fn = @tf.nn.tanh Documentation suggests that it is especially useful for machine learning. From motivation section: “Modern ML experiments require configuring a dizzying array of hyperparameters, ranging from small details like learning rates or thresholds all the way to parameters affecting the model architecture. Many choices for representing such configuration (proto buffers, tf.HParams, ParameterContainer, ConfigDict) require that model and experiment parameters are duplicated: at least once in the code where they are defined and used, and again when declaring the set of configurable hyperparameters. Gin provides a lightweight dependency injection driven approach to configuring experiments in a reliable and transparent fashion. It allows functions or classes to be annotated as @gin.configurable, which enables setting their parameters via a simple config file using a clear and powerful syntax. This approach reduces configuration maintenance, while making experiment configuration transparent and easily repeatable.” Michael #4: Performance benchmarks for Python 3.11 are amazing via Eduardo Orochena Performance may be the biggest feature of all Python 3.11 has task groups in asyncio fine-grained error locations in tracebacks the self-type to return an instance of their class The "Faster CPython Project" to speed-up the reference implementation. See my interview with Guido and Mark: talkpython.fm/339 Python 3.11 is 10~60% faster than Python 3.10 according to the official figures And a 1.22x speed-up with their standard benchmark suite. Arriving as stable until October Extras Michael: Python 3.10.5 is available (changelog) Raycast (vs Spotlight) e.g. CMD+Space => pypi search: Joke: Why wouldn't you choose a parrot for your next application

MacStories boss Federico Viticci returns to the show to talk about the iPad's apparent stagnation and how the Mac has grown over the last few years. The guys also talk about Raycast, Shortcuts, Apple silicon and more.

MacStories boss Federico Viticci returns to the show to talk about the iPad's apparent stagnation and how the Mac has grown over the last few years. The guys also talk about Raycast, Shortcuts, Apple silicon and more.

Raycast 「個人利用は無料」でチームで使う場合に有料、というのはなかなかに良いアイデア、とか言ってたら、ちょうどこのタイミングで「チームプラン」のベータが始まりました。 ご意見、ご感想はTwitterのハッシュタグ#ごりゅごcastかお便りフォームにお送りください。

@spring-raining が、最近ランチャーアプリ Raycast を使い始めた @potato4d に Raycast の良さや Extension の開発について聞いてみました。

Guest Ricardo Vazquez Panelists Django Skorupa Show Notes Hello and welcome to Sustain Open Source Design! The podcast where we talk about sustaining open source with design. Learn how we, as designers, interface with open source in a sustainable way, how we integrate into different communities, and how we as coders, work with other designers. Django is our panelist today, and joining him as his guest is Ricardo Vazquez, who's the Senior UX Manager at Wealthsimple, bringing UX leadership to trade and invest in crypto product markets. Ricardo tells us what brought him into the world of open source design, how he brings his curiosity and sense of sharing to design, and how he sees open source design as a community. We also find out how he got his start into teaching, he goes in depth about creative storytelling, his passion with design systems, and he shares his ever-recurring career goals. Go ahead and download this episode now to find out more! [00:00:50] Ricardo explains what brought him into the world of open source design, and how he's bringing his curiosity, openness, and sense of sharing to design. [00:02:32] We hear how Ricardo uses Figma for his work. [00:04:32] Ricardo describes how he sees open source design as a community. [00:07:01] We find out more about what Ricardo meant when he mentioned open sourcing creative storytelling, and he talks about the book, The Hero with a Thousand Faces. [00:14:04] Ricardo talks about the onus of open source communities and how we have the power to bring transparency to the process. [00:18:27] We hear how Ricardo got into his teaching career. [00:23:36] Django explains how designing is much like painting. [00:24:17] Ricardo shares with us his passion of working with design systems or thinking in systems, and he mentions a great book to read called, Thinking in Systems. [00:29:41] We find out what Ricardo's ever-recurring career goals are. [00:37:30] Ricardo tells us about a podcast he writes for called, Full Hearts. Quotes [00:00:57] “Honestly, it's curiosity that led me to open source design.” [00:05:12] “The open source community is tight, integrated, curious, intelligent, driven, and passionate to advance the collective.” [00:05:38] “I continue to believe in Mozilla's mission that they have about net neutrality, and turning everyone into creators of the web, not just consumers of the web.” [00:07:36] “The more time I've spent in this industry the more I realize that skills are not what lead you to impact change as much as storytelling.” [00:17:03] “The value of open source is about discovering opportunities.” [00:24:27] “Thinking in systems and design systems also allow you to do something very similar with a goal of understanding first and then being able to execute in a very rigorous way.” [00:26:01] “The purpose of a system is to solve problems and create desirable futures.” Spotlight [00:32:57] Ricardo's spotlight is Raycast and a Things Extension by Loris. [00:35:03] Django's spotlight is Penpot. Links Open Source Design Twitter (https://twitter.com/opensrcdesign) Open Source Design (https://opensourcedesign.net/) Sustain Design & UX working group (https://discourse.sustainoss.org/t/design-ux-working-group/348) SustainOSS (https://sustainoss.org/) SustainOSS Discourse (https://discourse.sustainoss.org/) Sustain Open Source Twitter (https://twitter.com/sustainoss?lang=en) Django Skorupa Twitter (https://twitter.com/DjangoSkorupa) Ricardo Vazquez Twitter (https://mobile.twitter.com/rcrdovazquez) Ricardo Vazquez LinkedIn (https://ca.linkedin.com/in/vazquezricardo) Wealthsimple (https://www.wealthsimple.com/en-ca) Figma (https://www.figma.com/) [The Hero with a Thousand Faces by Joseph Campbell](https://www.amazon.com/Thousand-Faces-Collected-Joseph-Campbell/dp/1577315936/ref=sr11?crid=1WEWDOPK3FX7R&keywords=the+hero+with+a+thousand+faces&qid=1645563913&s=books&sprefix=the+hero+%2Cstripbooks%2C90&sr=1-1) [Thinking in Systems by Donella H. Meadows](https://www.amazon.com/Thinking-Systems-Donella-H-Meadows/dp/1603580557/ref=sr11?crid=1RD4TJQGHLTSU&keywords=thinking+in+systems&qid=1645575296&sprefix=thinking+in+systems%2Caps%2C79&sr=8-1) Raycast (https://www.raycast.com/) Things Extension by Loris (Raycast) (https://www.raycast.com/loris/things) Penpot (https://penpot.app/) Full Hearts podcast (https://fullheartspodcast.com/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Ricardo Vazquez.

Vulkan Tutorial を読んで三角形を描画してみた話、Alfred の代替となり得る Raycast というツールの話をしました。 https://vulkan-tutorial.com/ https://vulkan-tutorial.com/Drawing_a_triangle/Graphics_pipeline_basics/Introduction https://www.raycast.com/ --- Send in a voice message: https://anchor.fm/pod-de-engineer/message

2021年にProduct Huntで2,000以上のupvoteを集めたプロダクトをチェックしました。 ホスト: 山本 大策（ https://twitter.com/daisaku ） 今回のキーワード: 参考: 2020年のProduct Hunt Top10プロダクトをチェック。2021年は自分にとって必要なものを作ろう。 https://www.prototype.fm/79 以下、2021年にProduct Huntで2,000以上のupvoteを集めたプロダクト。 （upvote数は2022年1月9日確認時点のもの） Tango 3,322 upvotes スクリーンショットを使ったハウツーガイドを自動で作成 ドキュメント作成の煩わしさから解放されます。新入社員の採用、顧客の問題解決、製品アップデートの共有が迅速に行えます。 https://www.tango.us/ ワークフローの理想的な進め方を自動で取得し新入社員研修を簡易化するTangoが約6.3億円を調達 https://jp.techcrunch.com/2021/08/26/2021-08-24-tango-dances-in-with-5-7m-to-making-employee-onboarding-easier/ Sprig 3,189 upvotes オールインワン製品調査プラットフォーム Sprig（旧UserLeap）は、プロダクトやユーザージャーニーの中で、一口サイズの質問をすることができるオールインワン・プロダクト・リサーチ・プラットフォームです。ビデオインタビュー、デザインコンセプトのテスト、実際のユーザーへのマイクロサーベイを数分で簡単に実施できます。 https://sprig.com/ RobinWho 2,943 upvotes あなたを泣かせる最初の投資アプリ。 あなたは、株を買って、売ることに慣れていますか？利益を出すことに慣れましたか？この作業は終わりがありません。利益は魅力的で、単なる収入以上のものをもたらし、習慣を形成します。私たちは、それを中毒と考え、株で儲けることを断ち切るアプリをリリースすることにしました。 ロビン・フー！は、利益中毒を克服するために、この恐怖と戦うために開発されました。全ては超簡単です。「利食い」「損切り」の2つのメインボタンから1つを選ぶだけです。そして、取引を停止します。 https://www.qooore.com/robinwho Typedream 2,816 upvotes Notionのように簡単で、Webflowのように美しい、ノーコードサイトビルダー 使い慣れたNotionのようなインターフェースで素早くページを構築し、コンテンツに集中することができます。 どんなウェブサイトでも最小限の努力で見栄えを良くする、美しくモダンなデフォルト設定 高性能な静的ページと最適化された画像は、Vercel 上の NextJS によって実現されています。 https://typedream.com/ Lucky Carrot 2,667 upvotes 従業員の意欲を高め、認め、評価する Lucky Carrotは、オールインワンの従業員エンゲージメント・プラットフォームです。 ◾ 従業員同士がお互いを認め合うことができるようになります。 ◾ 従業員の成果を可視化する。 ◾ アンケートを通じて、社員の声を届ける。 ◾ 従業員エンゲージメントを向上させるための知見を提供します。 https://luckycarrotapp.com/ Contra 2,500 upvotes 新しいタイプのプロフェッショナルネットワーク Contraは、フレキシブルな働き方のための新しいプロフェッショナルネットワークです。私たちは、あなたが望む人生のためにキャリアを成功させるために必要なツールとインフラを、手数料ゼロで提供します。 https://contra.com/ Cal.com 2,415 upvotes すべての人のためのスケジュール管理インフラ Cal.com（旧Calendso）は、Calendlyに代わるオープンソースのCalendlyです。セルフホスト、または私たちがホスティングします。高度なカスタマイズとオープンAPIで、あなたのビジネスにシームレスに統合します。 あなたやあなたの訪問者が楽しく使えるように設計されています。 https://cal.com/ Persona 2,407 upvotes あらゆるユースケースに対応する、0円からの本人確認サービス Personaは、世界中をカバーする完全自動の本人確認コンポーネント群を提供し、あらゆるユースケースに合わせたカスタムフローを作成するための設定やブランディングを行うことができます。スタータープランに登録すると、10分以内に無料で開始できます。 https://withpersona.com/ Ray.so 2,356 upvotes あなたのコードを美しい画像にする あなたのコードを美しく画像化します。構文カラーを選択したり、背景を隠したり、暗いウィンドウと明るいウィンドウを切り替えたりすることができます。キーボードショートカットを使って、処理を高速化しましょう。 Raycastのチームによって開発されました。 https://ray.so/ Podcastle 2,266 upvotes オーディオの作成、編集、強化、オンラインインタビュー。 Podcastleは、音声コンテンツの作成、編集、強化、オンラインインタビュー、テキストから音声への変換、プロダクション品質のサウンドを数秒で実現する、AIを活用したコラボレーション音声コンテンツ作成プラットフォームです。 https://podcastle.ai/ OpenVC 2,243 upvotes 2,200以上のVCファーム。根本的に自由でオープン。 スタートアップに「最適」なVCファンドを瞬時に見つけることができます。OpenVCでは、2,200以上のファンドを投資基準で閲覧することができます。その代わり、VCはスパムを減らし、より質の高いディールフローを受け取ることができます。ベンチャーキャピタルへのオープンな道を築きましょう https://www.openvc.app/ Scribe 2.0 2,213 upvotes ステップバイステップのガイドを数秒で自動作成 あらゆるプロセスのステップバイステップガイドを自動で作成します。記録を押すだけで、Scribe は、あなたの行動に基づいてスクリーンショットを含む詳細なガイドを作成し、同僚、顧客、友人と共有できるようにします。 https://scribehow.com/ tl;dv for Google Meet 2,205 upvotes 分単位で会議をキャッチアップ 会議の議事録は、ビデオ録画とトランスクリプトの正確な瞬間にリンクされます。重要な内容を完全に文脈化して、即座に共有できます。お気に入りの非同期コラボレーションアプリやCRMと連動します。 会議の内容をすぐに確認できます。 https://tldv.io Doodle Ipsum 2,160 upvotes イラストのロレムイップスム Doodle Ipsumは、Blushが提供する開発者向けの無料イラストレーションツールです。古典的なLorem Ipsumに触発され、簡単なコードでプレースホルダーのイラストを自動生成します。 https://doodleipsum.com SavvyCal 2,142 upvotes スケジュールリンクの送信は、変な感じがしないようにする必要があります。 多くのスケジュール管理ツールは、受信者側に負担を強いるものです。SavvyCal は、両者が会うのに最適な時間を瞬時に見つけることを容易にします。 https://savvycal.com Veganzone 2,137 upvotes ビーガンのビーガンによるビーガンとベジタリアンのためのビーガン Veganzoneは、ヴィーガン＆ベジタリアンのライフスタイルを実践する人々が、共通の価値観を共有し、互いに出会い、イベントを介して交流し、ヴィーガン製品を購入できる新しいモバイル・アプリケーションです。 http://jro.net Audiblogs 2,089 upvotes あらゆるウェブ記事をポッドキャストで聴く Audiblogsは、どんなウェブ記事もAudibleのような音声でPodcastプレーヤーで聴くことができます。運動しながら、料理しながら、家事をしながらなど、「ながら読み」に使ってみてください。 https://audiblogs.com/ Zodier 2,061 upvotes 人気メッセンジャーのチャットボットでデート あなたは出会い系アプリのすべてを見たことがあると思っていますか？ ほとんどない！？ Zodierは仲間を探す新しい方法で、すでにあなたのスマホの中に入っています！ Zodierは、あなたの携帯電話の中にあります。 ボットとデートを統合し、出会いとチャットをシンプルにします。 デート + チャットボット = Zodierです。 これがZodierの始まりです! https://zodier.io Mobile Chat Kit 2,027 upvotes アプリ内モバイルチャット構築のためのUIキット＆サンプルアプリ Streamのアプリ内チャット用UI + SDKを使えば、美しくスケーラブルなチャット体験を数時間で構築することができます。FigmaとSketchのための50以上の手作りの画面。Flutter、React Native、Kotlin、SwiftのためのUIコンポーネント。サイドプロジェクトに利用できる無料のメーカーアカウント。 https://getstream.io/chat/ux-kit/ Integrately (Zapier Alternative) 2,023 upvotes 500以上のアプリに対応する800万以上のオートメーションが用意されている Integrately 2.0 は、技術者でなくても 1 クリックでアプリケーションを統合し、プロセスを自動化することができます。これを可能にするため、私たちは 800 万以上の自動化機能を作成しました。そして、常に追加しています。 必要なのは、オートメーションを有効にすることだけです。 https://integrately.com/ Ghost 4.0 2,019 upvotes ニュースレター、メンバーシップ、サブスクリプション - すべてを一元管理 https://ghost.org/ SigmaOS 2,018 upvotes あなたを速くするブラウザ SigmaOSは、あなたの仕事をより速く、より良くするために設計された、初めての仕事用ブラウザです。 ページやウェブアプリを整理するためのワークスペース。 スヌーズページで頭をスッキリさせる プロ並みのマルチタスクを実現するスプリットスクリーン https://sigmaos.com/ Deep Nostalgia™ 2,016 upvotes 家族写真にアニメーションを 家族写真の顔を、驚きの技術でアニメーション化。 https://www.myheritage.jp/deep-nostalgia このポッドキャストへのお問い合わせ、ご感想、ご質問、ご要望は公式サイト( www.prototype.fm )内の、お問い合わせからメッセージしてください。 Twitterの場合は #prototypefm をつけてツイートしてください。 iTunesStoreでのレビューもお願いします。

We each try out the new Pop_OS! and Carl Richell from System76 joins us to get into the details. Plus why we feel Pop might be the new Ubuntu. Special Guest: Carl Richell.

Lindsay and Steve sit down with Andrew Courtice, head of front-end engineering at Fathom, do discuss his global state management library Harlem. They talk about how Andrew got started in programming during university, and his move from building desktop applications to the web, as well as his initial start with Vue before it reached 1.0. They then discuss Harlem: what it is, how it works, and what problems it solves. They also discuss the state of global state management in the Vue ecosystem, and how to get started building your own library for Vue (including devtool integration!) Panel Lindsay WardellSteve Edwards Guest Andrew Courtice Sponsors Top End DevsCoaching | Top End Devs Links HarlemFathomGitHub | developit/microbundleGitHub: Andrew Courtice ( andrewcourtice )Twitter: Andrew Courtice ( @AndrewCourtice ) Picks Andrew- Raycast Lindsay- Timberborn on SteamLindsay- Download Microsoft Edge Web Browser | MicrosoftLindsay- React PodcastSteve- Random Phrase Generator Contact Lindsay: Twitter: Lindsay Wardell ( @lindsaykwardell ) Contact Steve: Twitter: Steve Edwards ( @wonder95 )GitHub: Steve Edwards ( wonder95 )LinkedIn: Steve Edwards Special Guest: Andrew Courtice.

In this Hasty Treat, Scott and Wes talk about the hottest new tech they love! Linode - Sponsor Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with a $100 in free credit for listeners of Syntax. You can find all the details at linode.com/syntax. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/syntax and click on the “Create Free Account” button to get started. Sentry - Sponsor If you want to know what's happening with your code, track errors and monitor performance with Sentry. Sentry's Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up. Show Notes 03:30 - Lucy Language https://lucylang.org/ A concise language for describing Finite State Machines 06:10 - MDSvex https://github.com/pngwn/MDsveX Mdx for Svelte Smartypants options transforms ASCII punctuation into fancy typographic punctuation HTML entities https://github.com/rehypejs/awesome-rehype 09:56 - RECut https://getrecut.com/ 12:26 - Fig https://fig.io/ It's an app you install on your computer, it adds autocomplete to your terminal Works with most popular terminals Autocompletes git commands NPM commands + tons more - npm install ___ works Adds descriptions of what each command does Mac only - again another reason why Mac is best! Themeable Why not use Fish/ZSH? This isn't a replacement for anything, it's just autocomplete on top These fish plugins are to vim, as Fig is to VS Code Better UI is KEY 15:56 - Warp https://www.warp.dev/ Rust-based termnial Very fast Extensions and themes Share commands and sessions Great for remote server dev Share terminal state - with share links 19:33 - Raycast https://www.raycast.com/ App launcher File Finder Workflow runner Everyone is asking why is it better than Alfred better UI Better outputs math Better defaults - currency conversion Fast as hell Better integrations More Flexible 21:26 - Table Plus https://tableplus.com/ Fantastic little DB tool 23:59 - Obsidian Update https://obsidian.md/ Wes: I haven't got into it - find myself still going back to VS Code 26:50 - Descript Update https://www.descript.com/ All-in-one audio and video editing, like a doc Links https://chriscoyier.net/ https://hyper.is/ https://www.alfredapp.com/ https://strapi.io/ https://studio3t.com/ https://www.mindnode.com/ https://remarkable.com/ https://www.notion.so/ https://joplinapp.org/ http://www.telestream.net/screenflow/overview.htm https://shinywhitebox.com/ Tweet us your tasty treats! Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

如果 EmacsTalk 对您有所帮助 欢迎在各大播客平台留言、打分、转发 也欢迎您为本节目进行打赏支持 ❤️ 本期节目请来了一位使用 Emacs 近十年的资深用户陈斌，他是著名文章《一年成为 Emacs 高手》的作者，同时也是一位拥有近二十年软件开发经验的前辈。 抵触 Emacs 近十年后，陈斌用一年时间就成为了 Emacs 高手，他是怎么做到的？是什么样的契机让他打开了 Emacs 这个潘多拉魔盒？ 作为一个拥有众多插件的开源软件维护者，如何处理用户的不满？如何调节生活与维护的压力？陈斌给出了自己的答案。 此外，节目里还聊到了 Emacs 与 VSCode/Vim 等开发理念上的区别，学习这些软知识，非常有助于加深对 Emacs 的理解。近一个半小时的内容，“湿货”十足，不容错过！ 本期人物 主播：西瓜 嘉宾：陈斌 时间轴 00:00:42 嘉宾自我介绍 00:03:34 为什么会去写《一年成本 Emacs 高手》文章 00:08:18 学习 Emacs 多久后，开始写《一年成本 Emacs 高手》文章 00:10:16 Emacs 为什么不那么“开箱即用” 00:12:54 嘉宾是如何探索出学习 Emacs 最佳实践的 00:15:36 嘉宾列举的一些 Emacs 技巧 00:21:30 Emacs 的开放性，与其他编辑器的区别，“乱” VS “自由” 00:26:31 嘉宾学习 ELisp 的经历 00:30:02 嘉宾对维护开源项目的态度 00:39:35 嘉宾对新手的建议 00:43:53 嘉宾现在的 Emacs 工作流 00:54:11 Emacs 在 Windows 上为什么性能差 01:01:58 Emacs 核心开发团队是怎么样的 01:08:13 嘉宾对入行新人的建议 01:13:20 推荐环节 Show Notes 嘉宾介绍 名字：陈斌 19 年工作经验，最早桌面开发，现在以 web 开发为主 知乎专栏：如何提高编程速度 入坑经历 2011 年开始接触 Emacs，当时大概 40 岁 吃了半年苦头后，无意间发现了 Steve Purcell 的配置，才开始真正掌握其要领 Emacs 技巧分享 在项目中查找文件 find-file-in-project ELisp API 多，不同插件之间可以相互调用 Elisp 学习经历 潜移默化，没有特意去学 对待开源的态度 佛系，软件一开始往往都是不完美的，逐渐去完善就好 对新手学习 Emacs 的建议 现在的工作流 js2-mode org-mode 记录心得体会 混用 magit 和 git 命令行 基于 ctags，使用 counsel-etags 来做代码导航，company-ctags 来做代码补全 shell-mode，新写的 shellcop 插件可以根据 shell output 的文本内容，来快速跳转文件 counsel + ivy 收发邮件使用 gnus 使用 dired 管理视频文件，通过 mplayer 进行播放 Emacs 核心开发团队介绍 Emacs 还能活多久 对新入行新人的建议 不要把眼光局限在一小块领域，可以学些人文/艺术等来提高自己的品味 嘉宾的分享 evil 可同时掌握 Emacs 与 Vim，而且还能彻底解决小指痛的问题 abo-abo 大神的 ivy + swiper + counsel 全家桶 vc-msg 显示当前行的 git 信息 evil-matchit 在成对的 tag 间进行跳转 主播的分享 macOS 上的程序启动器 Raycast，类似与 Alfred，但是免费，且支持剪贴板

Gage and Niall sit down with Chris Ray Gun to discuss Snapple, motivation in quarantine, and parking in the handicap spot. Email Us: almostadultspodcast@gmail.com Tweet Us: @almostadultspod Follow Gage: @GageAgnew Follow Niall: @NiallerDefiler Follow Chris: @ChrisRGun Subscribe to Chris: https://www.youtube.com/user/MindfreakCM Support Gage: https://www.patreon.com/gageagnew Artwork by Matt McEwan: @Envelion Edited by Alex Keel: @hashtagkeel Watch Gage: https://www.twitch.tv/gageagnew/ Subscribe to us on YouTube: https://www.youtube.com/channel/UCaOBpruClPvnYN2BigqH2NA Instagram Us: @almostadultspod Check out our website: gageagnew.com Our theme song was performed by Aaron Overton (@iamifbywhiskey) and written by Dodge Williams (@dbw4511)

Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: We have to make sure that if you’re a brand new obsidian user, it feels accessible, it has infinite depth, and you can go as deep and crazy as you want, but that that surface level is intuitive and inviting to most people, and that’s a really hard thing to balance. 00:00:23 - Speaker 2: Hello and welcome to Meta Muse. Us as a tool for deep work on iPad and Mac. This podcast isn’t about me use the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGranaghan. Hey, Adam. I joined today by Stefan Ago of Obsidian. How’s it going? And Stefan, you’ve got some nice recipes up on your website alongside various blog posts about tools for thought and technology. Tell me a little bit about pillowy Swedish cinnamon rolls. 00:00:55 - Speaker 1: Oh, that’s a good one. So I grew up in France. My mom is half American, half Swedish, my dad is 100% French, and my mom is. A teacher, later in life she became a professional baker. She was always cooking and baking throughout my childhood and taught us a lot. And she was also trying to infuse the household with her American culture and her Swedish culture as well, because I lived in France until I was 17. And so, One of those things is a Swedish cinnamon roll. I think in the US, you know, the kind of cinnamon roll that you’re used to is probably derived from that. It’s usually made with, you know, cinnamon or cardamom, and I came across this technique which is common in Asia called tanghong, which is a technique for making bread out of a, it’s almost like a very, I don’t know if anyone knows what a roux is, which is also a French technique, which is a mix of flour and water that you use to make gravy and other types of things. You use basically a very Like a slurry of water and flour that you don’t darken at all, and you put part of that into the dough. And what it does is somehow, I don’t know all of the chemistry of this, but I think what it does is it encapsulates some of the moisture into the flour, and so when you mix that into the main part of the dough. The dough stays really soft and fluffy and pillowy, and it’s just a really amazing texture. And so I discovered this technique and I think, you know, it’s used for like milk buns and different things in Asia, but I thought it would be a good fit for the Swedish cinnamon roll that I always love to make around the holidays, you know, in December, even though I live in Los Angeles now and it’s not so cold, it’s just a kind of a nice memory. And so it turned out to be the perfect fit in an interesting fusion of two things. And so I put this recipe out. I don’t have very many recipes on my website, but it started to become a little bit of a section, and so I decided to post more of these because they’re really fun for me and very iterative. I like to incorporate techniques that I find online and get feedback from people who try it and. Iterate on them, so maybe it will become a more important section of my website. I think there’s only 2 or 3 recipes on there right now. 00:03:28 - Speaker 2: Especially like the I guess cultural mashup aspect of that, obviously drawing from your own heritage but also reaching outside of that. I always find, I guess as a person who’s an immigrant myself and I’m raising my child who has two parents from different countries and is living in a third country, so maybe not too dissimilar from your upbringing. And yeah, I think there’s just a lot of, I don’t know, interesting, you know, if we say everything is a remix now, you know, this kind of remix of fundamental cultures, I just think there’s a lot there. 00:04:02 - Speaker 1: Yeah, being able to pick and choose techniques, ideas from different cultures and like bring them together is really fun. That’s how I grew up, and so it just comes naturally to me. 00:04:13 - Speaker 2: And tell us a little bit about your background in the professional world. 00:04:18 - Speaker 1: Well, so today I’m the CEO of Obsidian. Obsidian is an app probably a lot of your listeners will know about in the tools for thought kind of space. Before that, I’ve been an entrepreneur my whole life. I’ve run lots of companies, probably the most well known of them is called Lumi. We built a platform that helps entrepreneurs and Teams collaborate with manufacturers, particularly in the packaging space, so it’s a really interesting problem of There’s so much manufacturing capability in the world. Like there’s all these factories that are out there that can make things, but I find that the interface to access that capacity is Very confusing and difficult, and the idea behind the company was what if we could make it as easy to interface with factories as it is to interface with cloud computing. And so that was a really fun adventure. We worked on that for about 8 years, sold the company, and then I found myself having a little bit more free time to think about things. I have been using. A variety of different journaling and wiki type of software for a while and Obsidian came along, founded by Shia Lee and Erica Shu back in 2020. I started using it pretty much right away. It slotted into what I was doing perfectly and. I was using other tools before that and kind of had mashed up a few different things together. And Obsidian just sort of did exactly what I was trying to do by scotch taping all these different solutions together. And so I just fit like a glove right away, started using it, became close with the founders and started working on community contributions to the app. And Eventually, once I was leaving Lumi, they brought me on as the CEO and it’s a very small team. We’re only, you know, 6 people full time. So that title probably like yours, Adam, holds maybe a different meaning within our group, but it’s been really fun and I’ve been on it full time now for about 5 or 6 months, which has been really great. 00:06:32 - Speaker 2: And it must be quite a dramatic experience to come. You’ve obviously started your own company and scaled that up and been the leader there, but coming into a tool that’s already established itself, at least within a particular niche, already has a big audience of fans, already has an existing team, plenty of culture and values and all that sort of thing. Obviously you We’re already resonant with that culture and values coming in, but to suddenly be on the inside and particularly to have this vested authority, all of a sudden, did you find that disorienting? How did that challenge compared to the challenge of starting something totally from scratch and sort of building every piece of it versus needing to like, I don’t know, bootstrap all the context or build the moral authority within the team? 00:07:15 - Speaker 1: Well, I’ve never worked at a company that I didn’t start until now, so it was surprisingly natural because I Had developed this relationship to the founders over a long period of time, very gradually, very organically just through chatting with them and reporting various bugs with the app and, you know, building some community contributions and things like that. So it was surprisingly easy and very natural. It was just really like, instead of spending, you know, a few hours here and there working on obsidian every week. What if I was just doing that full time, and I do think it’s a At least in my mind. When I was thinking about what’s next after Lumia, my default would have been to start another company, but I couldn’t think of anything that I Thought was more exciting than obsidian. And so that to me, at least in my own head, it says a lot. I don’t know if it says a lot to other people, but it does say a lot that I would rather kind of go and help build this thing, which I think is is such an amazing app and community than try to start another thing from scratch right now. 00:08:28 - Speaker 2: Yeah, that makes a lot of sense. And I think that entrepreneurship, you shouldn’t start with, I want to start a company. You should start with, I want to solve a problem or have an impact on the world or go to a place where I can contribute the most. Really starting a company should be your last resort. If there’s really no other way to accomplish, I agree, 00:08:47 - Speaker 2: that’s what you want to do, then you say, well, damn it, I guess I have to start a company. 00:08:51 - Speaker 1: Oh well, I have so many people come to me for entrepreneurship advice and my first advice is don’t do it. Most of the time. I’m constantly like trying to convince them not to start a company. And part of it is just me kind of probing to see how much they actually care about whatever they’re doing that, you know, they can deal with that because that’s pretty much what you’re going to get from the world, like 99% of the time is like, why does this exist? or why are you doing this? But I kind of took my own advice here and I think a lot of times it’s better to go, you know, put more wood behind fewer arrows. 00:09:26 - Speaker 2: Yeah, I think it’s also a really unique opportunity because getting the chance to, for example, I hired a CEO at Hiroku after we’ve been in business for a few years, and that was a really great opportunity to work with someone much more experienced and with knowledge about the spaces we wanted to move into. For me, that was a new experience, yeah, always being an entrepreneur and then kind of Leading or being a co-leader in it until I’m done or don’t have anything else to say and then I just sort of leave. It’s really tricky to bring in a new leader, but it can also be an injection of new expertise, new perspective, new direction, new vision, especially because very often the kinds of people that like to start something are not the same. People or don’t have the same skill set or just passions to want to scale it up, to want to see it grow wider, address, be available to more people, or just the natural kind of management responsibilities that go with managing a team, and existing product, a big base of customers who just seem to have an endless list of bugs and feature requests. It can take a different personality type. So when that can be done well, I think it’s really great to bring in an experienced leader at the right moment. 00:10:34 - Speaker 1: Yeah, and I was so impressed with Erica and Shea. People might know them as Silver and Leak out, which is their name online, but they’re a little bit younger than I am and have such a mature point of view on how they want to build the business of Obsidian from the start, they Made the decision not to go down the VC path, and I’ve, in my own businesses over the years have literally tried every different method of funding any business. I’ve bootstrapped companies. I’ve gone the VC route. Did Shark Tank, did Kickstarter did every different thing you can imagine, loans like if I type your name into YouTube with Shark Tank right now, will I get a 00:11:12 - Speaker 1: clip? You’re gonna find my co-founder Jessie. I was not brave enough to go on there myself, but she’s great, and you should watch that episode. But I think they took a very mature path really thinking about the long term, which is aligned with kind of what the app is trying to do, and having the experience of going through all of those different ways of building a business. I realized it is really hard to run a bootstrapped company and try to grow it kind of on your own. And I think that the approach that we’re taking with Obsidian is definitely hard mode in a way. It seems surprising that you could just easily get millions of dollars, but if you have a good enough idea, there’s investors like banging at your door trying to give you money and it actually takes a lot of Fortitude to say, no, I don’t want millions of dollars. We’re going to just do it, you know, ourselves, we’re gonna grow very carefully and organically and in an almost like selfish way, because I’m such a fan of obsidian first and foremost and a user of it, you know, pretty much every day, have it open in the background of my computer if I’m not using it actively. I almost selfishly wanted to just kind of help ensure that obsidian continues on that independent path and continues to build kind of in a very thoughtful way. And what could I bring from a business standpoint to the table to create the structure that would enable that to continue being a priority. 00:12:45 - Speaker 2: And it’s going to lead to this later, but since we’re sort of on the topic now of the kind of the mechanics, which includes, yeah, financing, team size, but business model, obviously, it’s what I would call a prosumer model. There’s the free product you can download and use, and then there’s the sort of services, subscription services like Sync that you can sort of add on to that once you’re getting value from the product. So I feel like prosumer is something that has like a longer ramp up, but you need to kind of like do that upfront investment, but it also doesn’t have a very good shape for venture because it doesn’t necessarily have that big kind of unicorn in 10 years shape to the graph that say like a B2BAS company might. And then the middle ground there often ends up that companies like this basically finance it through just doing a bunch of consulting projects in the early days. I think maybe like yeah, the 37 signals folks is one example. I’ve done that with multiple businesses to the point you’re willing to reveal how does obsidian strike that balance? Have you been successful enough that you’re just able to finance on customer revenue or that early upfront investment feels like it’s got to come from somewhere? 00:13:50 - Speaker 1: And when you say prosumer, I think in my head, at least I think of prosumer as a market as a user type, but From a business model standpoint, I would say freemium is more the term that I’ve come to. Is that what you mean when you say prosumer, do you mean freemium? 00:14:06 - Speaker 2: No, because you can have a freemium B2B and you can have freemium B2C. So music is one of the main areas like yeah, podcasters and DJs and whatever. This is actually you’ve got people who are often hobbyists or aspiring professionals though realistically. Maybe many of them are never going to make a living from it, but they are willing to spend hundreds or even thousands of dollars on gear on software, etc. So classically B2C, you can’t get anyone to pay for anything. You just monetize with ads or whatever, and then B2B, you know, you get those big sort of company contracts where they’re paying thousands or tens of thousands a month. And so I think of prosumer as being that kind of in between state of like Dropbox is a classic example, like pay $10 a month. Yeah, you get access to like, yeah, again, audio and video stuff, etc. I don’t know, maybe you don’t think of yourself that way, but that’s how I would slot it. 00:14:54 - Speaker 1: Well, I don’t, but I’m trying to kind of come around to your way of thinking of it like in that world, definitely, you know, Apple Notes and OneNote or some of these kind of apps that come shipped with the OS would probably be the consumer one like everyone just has it by default and it’s free, it’s bundled in. Obsidian has a Freeman model so you can totally use Obsidian for free and for personal use, but it is a little more advanced, it has more complexity to it than an Apple notes. It’s trying to, you know, give you a little bit more power user type of features, I suppose, and maybe that’s where the prosumer angle comes in. I think for us in terms of what the kind of broader. Goals of what we’re trying to do are we’re really trying to democratize these tools like we’re trying to make it easily accessible for people to think using these tools and so we don’t feature anything behind a price, so it’s not like There’s a pro version that you pay $10 a month for. The capabilities are behind a license type. So if you are using obsidian for your business, then you need to buy a commercial license. So that’s a little bit of a unique point of view and it has to do with kind of the values that we have around really trying to democratize access to these tools. The capabilities like sync and publish are paid add-ons, but There’s tons of free alternatives that are out there that may even be better for whatever use case you have. And so in a sense we’re competing with a bunch of free alternatives to our own services and we’re OK with that. A lot of the people who upgrade into some of those additional services, they’re doing it because they want to support Obsidian as a company as well. 00:16:51 - Speaker 2: Interesting, the commercial use kind of concept. I assume it’s to some extent is a honor system is quite the right word for it, but yeah, no, it’s an honor system, 00:17:02 - Speaker 2: right? Hard to tell if someone’s truly using something professionally and I think a lot of software again creator type software, if you think of like image editors or something like that, they might have things like water. Marks or something like that, that maybe an individual who’s just screwing around to make a meme, they’re OK with that, but a company would never put up with that. 00:17:19 - Speaker 1: So of course they’re gonna, but we don’t do any of that. Well, hopefully we don’t have to resort to any of those weird tactics. Like I don’t want to do that. That it’s surprising how well the honor system works actually. I think that most companies, we have a lot of great organizations using obsidian that really care about privacy and so they tend to go down the obsidian path more so than some of the other like cloud-based providers that are out there and not encrypted. And so I think that if you’re one of these organizations. You actually do care about reading the license, a lot of the software that you use, and if it says you need to pay $50 a user per year, we don’t get into that much friction, to be honest, when it comes to that. And the only friction that would come up would be everyone who’s in between who are like small, you know, couple people startups who from an honor system standpoint, they’re just probably using obsidian for free and it’s not a big deal. 00:18:21 - Speaker 2: Yeah, well, and classically, it’s been said that Fremium is almost an update of the old system which was used piracy as your sort of free version, so you pirate in Photoshop when you’re, you know, a university student that can’t afford anything and then later you have a real job at a real company and they want to be legit, so they buy you a license. 00:18:39 - Speaker 1: Exactly. Yeah, I mean, that was me. If I didn’t pirate Photoshop when I was, you know, 14 years old, I probably wouldn’t be doing the job that I’m doing now. But, you know, now today in 2023, I think it’s probably a better From a top of the funnel standpoint, piracy is not a great like method of trying to gain users. You might as well just give your app for free and then, you know, try to convince the people who can pay to come and join that tier. 00:19:10 - Speaker 2: Another example I’ve always liked that’s kind of a variation maybe on the the watermark sublime text, where when you buy a license, the only thing it does is remove the unlicensed text that’s in all caps from your title bar, which you probably don’t even notice that much in regular use. If someone’s looking over your shoulder or you’re pair programming on a screen share, it just, yeah, it looks like you’re kind of not serious about your tools and not investing or maybe just remind you of like, hey, this is a tool you rely on, it makes sense to support the creator or creators of it. 00:19:41 - Speaker 1: Yeah, so blind text is a huge inspiration to us. It’s great. 00:19:45 - Speaker 3: That reminds me sometimes you see these YouTube videos where people have the please license your windows sticker on their desktop. 00:19:52 - Speaker 1: Oh my gosh, that’s hilarious. 00:19:57 - Speaker 2: Well, I’d love to hear a little bit about how you think of obsidians fitting into, you know, we’ve talked about the tools a bit, but we self-identify, that is to say the Muse team and to some degree could switch as being part of the tools for thought community scene, whatever you want to call that, you know, your website, you call yourself a second brain. There’s obviously the concept of note taking. You’ve already mentioned Apple Notes, for example, although you know you could argue the degree to which a very simple notes app like Apple Notes is even in the same category as a knowledge graph or a wiki. When you think of that sort of category of software, how do you think of obsidian’s place within it? 00:20:31 - Speaker 1: Yeah, I mean, I think that. What most people are familiar with when I try to explain obsidian to someone who’s never really thought about using a tool like this, I go back to Wikipedia as the touchstone because I think everyone’s been on Wikipedia. People understand that most file systems, most structural systems are hierarchical or chronological, and so they’re linear in one of those ways, but they understand. Even if it’s just sort of intuitively or emotionally that Wikipedia is not organized like that. I mean there are some hierarchies in there, but it’s a web of links that you can click through and everything is related to something else. And I think that is really what I mean, even the term when you say personal wiki, it’s jargon, but if you say it’s like Wikipedia, then it becomes not jargon anymore and it’s like creating your own Wikipedia is oftentimes what I use as a description for obsidian to, you know, non nerds basically. And I think that’s a powerful analogy that, you know, somehow hasn’t permeated into tools like Apple Notes though, you know, I heard recently they’re making a new journaling app, but we’ll be curious to see what they come up with there. Um, but it is like one extra level of friction that maybe those like really basic tools are not looking to do. And once you start to link ideas together, what can you do with that? What new structural concepts does it open up? And it sounds so simple, but at least For me and my thinking, it totally changes the way that I organize my thoughts. There’s some people out there who are geniuses who can do this purely in their mind, but I don’t know. I just don’t have the like RAM in my brain to be able to maintain lots of different ideas at the same time. And so having this tool where I can kind of break down a problem into smaller chunks and then Remix those little chunks, however I want inside of a note is a really powerful and very basic concept. And then everything is layered up on top of that. So graph views, canvas views, you know, backlinks, like all of these different add-ons and things that can enable some new kinds of workflows, databases, like you can kind of go ad infinitum on top of that basic concept, but it comes down to. Links between notes and this kind of bottom up organizational model. 00:23:07 - Speaker 2: I think you actually perfectly teed up our topic today, which is Evergreen notes, and partially I like this term for a lot of reasons comes up, but it’s also a back reference to one of our first guests we ever had on the podcast, Andy Match. We’ll link that in the show notes, but you have a great blog post titled Evergreen Notes Turn Ideas into Objects you can manipulate. 00:23:29 - Speaker 1: Yeah, Evergreen, I think that Andy’s notes about that that he’s published are really great, and what I like about my definition is just turning an idea into a memorable chunk of text, but memorable to you, like a meme that is a meme inside of your own thinking. How can you take An idea that you had or read and turn it into a memorable chunk. Like sometimes I think what we love about good quotes from like famous people or from books is that they are in a way an every green note because they take a feeling or a concept and turn it into this like memorable little chunk of text. And at least in the way that I write for my own personal thinking, having that little chunk of text, like you said, everything is a remix. That’s an evergreen note in my system. And I can use that in the context of a sentence that might start with, because everything is a remix, you know, this thing that I found is interesting for that reason, and I use everything as a remix as a link in that sentence. And it becomes a very natural way to compose ideas together, but I want to try to make it kind of more relatable to People who haven’t thought this way in the past, and that was the purpose of that blog post was try to explain that if you can externalize ideas and you can create your own little memes inside of your system, then you can touch those ideas, you can rotate them, you can. Manipulate them in a way that personally, I find that my brain doesn’t work that way. I don’t have the capability to just do that purely inside of my head. I have to externalize it in order to be able to manipulate it. 00:25:17 - Speaker 3: Yeah, that’s been my experience too. Or at least I think you can fool yourself into thinking that you can manipulate these things in your head, because you can hold what, 7 things in your head? It’s like, oh, look, I have 7 things in my head and I can even combine them in different ways. But it’s sort of false because once you write down 20 or 30 things and have them as discrete objects, that’s when you have the Ability to rapidly play with new combinations. It’s one of those things that works unreasonably well, just writing it down, because it takes it out of your head and it frees up one of those 7 slots to put something in and it makes it possible for you to quickly pick up new objects to put in those 7 slots from your written down items. 00:25:56 - Speaker 1: Yeah, and if you can break your ideas down into smaller and smaller pieces, you can also build up more complex ideas that you feel have a stable foundation. Like you can build ideas on top of each other into thinking more complex thoughts than you could otherwise think, which I think is exciting. That’s really fun. Yeah. 00:26:18 - Speaker 3: This idea of being able to build up more complex thoughts because you’ve written them down, it reminds me of this idea of automation and programming, where sometimes it feels like you don’t really need to automate it because it’s basically going fine when you do it manually, which again, is true as far as it goes. But really what happens is you have some capacity to do stuff manually. So if you automate it. You can add your manual stuff on top of that, so you basically open up the ceiling to be able to do more stuff as a computer user. It kind of has the same feeling to me as this idea of writing stuff down to free up more mental space. 00:26:51 - Speaker 1: Maybe I should give an example so that people who are listening can understand what I’m talking about. I was reading this book by Murakami, I think it’s called What I Talk About When I Talk About Running or something like that. And he likes to run marathons and write books. And so he, you know, kind of compares the two, and he has this phrase that is a very memorable phrase in the book, which is pain is inevitable, but suffering is optional. He says, basically, when you sign up for a marathon, you’re basically signing up for pain. But it’s your choice to decide whether you want to suffer that pain or not. I was going through a very painful time at the time and so it kind of resonated with me. And then an evergreen note that I wrote in obsidian was pain is information and my thought about pain as information was I think children learn this at an early age. If you touch a hot stove, you know, that’s information that don’t touch hot things, you know, you’ll burn yourself. But in general, like pain is a signal from your body. It could be a physical pain, it could be emotional pain that gives you information. And then, There’s this phrase like knowledge is power. So, you know, if you gain enough information through pain, can you build knowledge off of that? By the transit of property is pain power? Like that that was a question that I was asking like if you are able to understand pain and synthesize pain, is it a path to power? It has a lot of connotations, but can you become more powerful by having more painful experiences? So this was kind of just like a train of thought, but like each nugget is an evergreen note. So pain is inevitable, but suffering is optional, pain is information, you know, knowledge is power, pain is power. Like you can kind of try to explore these ideas. You don’t necessarily need to agree with them. Like there’s tons of evergreen notes in my obsidian that I don’t agree with, but I’m trying to turn them into a little meme for myself that I can come back to. And maybe I’m still trying to figure out my opinion about that thought, and I’m trying to use that little fragment of text in a sentence where I’m agreeing with it or I’m disagreeing with it. I’m trying to weigh the pros and cons of it. I’m trying to mix it with another idea. Maybe this idea is not as strong as this other variation of the idea. And I just find it a very useful, you know, way to kind of think about these things and hopefully that example makes sense. 00:29:27 - Speaker 2: The self memes, including accessing maybe yeah, books you’ve read, quotations, yeah, everything is a remix, the running book, I think of ones that I referenced with some frequency like the man in the arena quote, these serve not only to, if we do think of ideas as these little notes, which are essentially objects that we can break apart and then use to do almost like Arithmetic or something like that and explore in ways that are more complex and interesting than the ideas would be on their own, but also can build up that pyramid and then encapsulate actually a lot of kind of sub items under one so everything is a remix or across the chasm or something like that actually contains a lot to it and you could read a whole book in many cases or whole section or think many deep thoughts on that, but eventually if you bubble it up into that meme, it almost reminds me of like a scientific citation where if I’m writing a paper about a complex topic and I need to reference another complex topic, I don’t need to go and restate that whole complex topic. I just referenced the paper and for a very small number of tokens I get essentially all of that brought in if you already know the paper or you know the meme or you know the quote. That basically can just serve as a reference to all that. If you don’t know that well, then you can go and explore, go down the rabbit trail there, which again, I guess does bring us back to that kind of Wikipedia linked knowledge, knowledge graphs, scientific papers as citations like, yeah, these are things that exist in other forms, but this version of it for the personal environment, the personal notes tool, personal knowledge base that has this highly manipulable component, I guess that’s what it feels like is truly new with tools. Likesidian. 00:31:09 - Speaker 1: And maybe the difference there between what you’re talking about and Wikipedia itself is that Wikipedia will reference specific books and places and, you know, concepts or terms, but it doesn’t really have like memes inside of Wikipedia because those are very personal kind of interpretations of an idea. One school of thought could have many different like sub ideas within it and those ideas don’t really tend to make their way. Into Wikipedia in that same way, but the concept of being able to kind of like manipulate them is similar. Am I making sense? Like Wikipedia doesn’t really contain interpretations of an idea, because it’s not trying to do that, it’s trying to be an encyclopedia, so it’s trying to be objective and not subjective, but these evergreen notes are intentionally subjective. 00:32:00 - Speaker 3: The evergreen note examples that we’ve been talking about have been very granular, aphorisms of a few words. Do you also have evergreen notes that are huge sprawling pages in which you’re creating stuff over time, or do you really prefer the granular style? 00:32:16 - Speaker 1: Um, I like really granular, I mean this is just me personally, you know, I’m not dogmatic about this. People can do whatever they want. I tend to have small fragments that I can compose into bigger fragments, so. Yeah, I can’t really think of, you know, really huge evergreen notes that I have. What those turn into is journal entries or stream of consciousness type of things where it’s like playing with Lego blocks. It’s like I’ve got these Lego blocks which are my evergreen notes, and then I have a session where I’m going to think about these like 10 different evergreen notes and combine them together. But that thing is not an evergreen note. It’s just a stream of consciousness, a thought process in my system, it lives as a date stamp with a name, and it’s just like on this day, I had these thoughts about these evergreen notes, but the evergreen notes are not time stamped, they hopefully have longevity. 00:33:19 - Speaker 2: Now longevity, I also feel like it’s an interesting fork to explore here. Some Mark and I have talked about as some of the listeners will know and talking about software longevity and sort of digital preservation and the challenge of bit ros and how quickly files and applications and whole systems sort of cease to be accessible. He talking about kind of your own personal knowledge systems and obviously I know that this is a big part of what. built on, which is just a folder full of mark down files and that’s plain text and now marked down as an extension of that is something that has really stood the test of time in a way that almost any other format you can think of hasn’t. How do you think about evergreen notes, durability, and especially in the context of your personal notes and how long those need to last. 00:34:08 - Speaker 1: It’s a very high priority. I would say that we are kind of plain text maximalists, like even more so than markdown. Markdown is definitely kind of this system that seems to have permeated enough and has lasted long enough that, you know, we feel comfortable using it as the kind of default markup in obsidian, but I think that we’re in this era that’s a very Unusual time because Digital files have only been around for 70 or 80 years. And that’s not very long relative to time. People have been writing things down for thousands of years and so we’ve started generating a huge amount of digital data. How much of that digital data is going to still exist 1000 years from now? It seems like on the one hand, we’re able to capture a lot more than we ever have been able to, but how much will be retained is the question. And my framework for this is just the Lindi effect. I just want to think about what has existed for a long time and can we use that as a proxy for, you know, hopefully something that will last a long time. And my gut feeling is that if computers are still around in 1000 years, plain text will probably still work, you know, maybe some other dramatic thing will happen where computers are not still around, but we’re trying to make decisions within the context that we know about right now. And so that’s also why sometimes I say like files are much more important than apps. We care about the file that you create in Obsidian much more so than the app. The app is ephemeral. Like the app is not gonna last forever. I think it’s a fallacy to think that you’re gonna design a tool that’s gonna last forever. Maybe like a chisel can last forever or something like that, but a software app is probably. not operating systems change, users change, things are changing so quickly. I don’t really care what kind of chisel someone used to, you know, inscribe hieroglyphics on a pyramid or something like that, but they were able to communicate some information that has stood the test of time. And so that’s why Obsidian is writing to plain text files that for now in terms of what we have for digital information is the you could open. An obsidian file on a computer from the 60s, which means that hopefully it will also work for a computer from, you know, 200 years from now. 00:36:38 - Speaker 2: Yeah, I love that and it touches on a few things of very much of interest to me. I mean, one is, I think that from a user perspective, putting aside how long of a duration you expect or want or would be desirable in your data, your work, the things you’ve created, ultimately, I think, especially here talking about creators, people using tools or productivity software to make. Things you really care about your work, not the tool, and obviously people can get excited about the hot new tool and they do, and that’s a lot of fun, but ultimately I care about when I’m using a piece of video editing software to edit a video or I’m using a word processor to write my PhD dissertation. I care about what I’m creating way, way more than the tool itself. As software creators, as tool makers, it’s very easy to have a certain kind of egocentrism, which is the tool is the important part, or maybe this even just comes from programmers where we think, well, the program is a complicated, interesting, important part and all of those bits we write to disk on behalf of the user, that’s kind of a secondary thing, but I think the user perspective is really the inverse of that. 00:37:40 - Speaker 1: Yeah, and I think That’s why the term tools for thought kind of rubs me the wrong way sometimes because it’s putting the tool at a higher level of importance than the thought in a weird way. And I think that the question that I’m wondering about is like, what are we doing on a civilizational level when I say we, like everyone who’s involved in Making and using tools for thought right now. What’s happening right now? Because it does feel like there’s something brewing, there’s like something that’s happening right now in this area that hasn’t, for some reason it wasn’t happening 10 years ago or 20 years ago. It seems to be happening right now. And I do think we’re inventing some interesting new tools, and we’re making some interesting decisions about society or humanity in some way. And I feel like the things that We’ve been kind of talking about in this conversation are the things that we’re doing. We’re trying to unlock a way that people can have thoughts that they haven’t had before. Like maybe some of these tools can open up ideas and allow people to think more complex thoughts or accelerate their progress towards some sort of creative output that they wouldn’t have otherwise been able to get to without these tools. So that seems kind of cool and important. And then the other part is How did those ideas or creations or whatever you made the outputs of the tool last for a long time, hopefully. I mean, maybe you make something very ephemeral and it’s not meant to last for a long time and that’s fine, but if you want them to be able to, they should. And I think that we’re at a turning point, like the printing press or something where we have the opportunity to kind of design these tools to hopefully pursue at least one or both of those goals. 00:39:27 - Speaker 2: Part of what I find so interesting about this, yeah, tools for thought scene, whatever you wanna call it, is just caring about the ability to Use software and computers first of all, as a thinking tool, which I think has only very rarely been something that’s on people’s minds. We’re usually thinking much more pragmatically. Here’s a calendar, here’s email, here’s a to do list, something of that nature. And I’m not sure that all the things that these different tools are trying, whether it’s sort of canvas-based tools, more tech orient. tools, things using space repetition, all that sort of thing, that those things were impossible to do with computers 10 or 15 or 20 years ago, but for some reason, people just got really interested in it right now and there’s some excitement around it and some sexiness around it and maybe some commercial opportunity around it as well, and that just has a bunch of people thinking about it. And regardless of the specifics of any individual product or project, I just love that there’s so many people thinking about the problem from that perspective. How can we use computers to help us all think thoughts we didn’t have before, like you said, be able to do more with our thoughts, be able to do more with our productive philosophical and creative efforts. 00:40:41 - Speaker 1: Yeah, and I think what’s new about computers in this respect is that every paper-based physical based system for thinking was kind of bound by the limitations of physics and physical objects, making it more linear, like a book, you know, is linear in nature. I’m always amazed when people get into the settle cast and like slip box concept that this guy literally did what I’m talking about with Evergreen notes, but just like have these little pieces of paper that were cross referencing itself. It’s a nightmare. It’s so cool that someone tried to do that, but literally, you know, one person did that because it was that complicated. And so we have the opportunity now to do things like canvas or graphs or things that have infinite levels of depth and nonlinear, non-hierarchical structures because we’re not bound by the three dimensional space when we’re, you know, working with these digital files and so that’s a really cool thing. How does the output of whatever you came up with. Like, it’s a means to an end still, like the canvas view, for example, in Obsidian or Muse, like, to me it’s in service of creating something at the other side of that, that is probably not a canvas in itself, like the canvas is not the output, the canvas is the kind of playground to arrive at an output. 00:42:11 - Speaker 2: Yeah, and that has been, I think a challenge in just marketing a product to a wider audience that is fundamentally for thinking, which is the output is the epiphany. The output is the the idea that you wouldn’t have had, as you said, and there may be pragmatic. something where again you’re working on your PhD dissertation or your grand idea or your software product or whatever it is, and the thinking tools help you to achieve that and maybe you’re copy pasting some things out of it, but in a way to me it’s almost a feature that Whatever it is that plain text file that canvas or whatever form the thinking space is taking, or even going to the physical world, right, the whiteboard or the sketchbook, it’s sort of a feature that my sketchbook I can’t turn that into the finished artifact because the sketchbook is the place to have loose thoughts. In a way that’s open ended, that’s safe and private, that is just messy and combinatorial, and then when I feel like, OK, I’ve had the aha moment, this is the thing I need to say or do, now I’m going to move to those more kind of production tools, but that can seem confusing, I think in some cases because it sort of seems like you’re doing extra work and why. And I think of it as you’re doing the work you’re already doing in your head, but you’re doing it through this externalized form, as you said earlier, and that that is a help, even though it may in the sense of like what it looks like to an external person, look like I’m doing more work, but you have to do the thinking either way with or without the help, with or without the aid. And then there’s also that, how do you turn this into like a more Production thing for consumption by other people or execute that idea and that should just be a separate set of tools. 00:43:48 - Speaker 1: It is hard to be messy in a digital form, and I think that’s kind of we’re trying to make that gradient between messy to finished smoother in a way, at least with the obsidian, it’s kind of a Implicit goal of trying to bridge those two things in a way that feels like continuous. 00:44:09 - Speaker 2: Yeah, I know this is something you’ve you’ve touched on with some regularity mark is the idea of like not having there be too discreet of a transition from, OK, now I need to take something that’s kind of transcribe it or take it from my sketchbook and move it to, for example, a digital form. And what’s in there, I’m taking it somewhere else. I think the reality is most production pipelines, if you want to call it that, do have multiple steps, right? I write a script for my movie and the script is in a different tool in a completely different format from shooting on film and then editing that down and then how I’m actually going to distribute that to my end audience is also, you know, uses a different tool, but making those steps less jarring is, I think, very desirable. 00:44:52 - Speaker 3: Yeah, I think you correctly point out that in practice, you’re almost certainly gonna have separate discrete tools, and now that I’m thinking about it in terms of explaining the products and marketing can be quite difficult because, OK, in the ideal case, you have one Uber tool that like magically morphs from a messy idea sandbox into a finalized, you know, edited movie or something. OK, sure. We know that in practice you’re gonna have to have a discrete step there where you say, Develop an outline and use, for example, and that eventually goes into the film production process. That is kind of explainable, like you do need to introduce this extra step that people often skip, unfortunately, but it’s in fact even harder than that because in many cases, what you’re doing with something like muse or obsidian, in my opinion, is you’re basically rewiring your brain, you’re introducing new thoughts into your head and you can actually throw away that artifacts, but it’s what’s in your head. So now you gotta explain to someone, oh, you know, it’s actually just that your neural net weights have been updated. And then furthermore, it’s often the case that these are not in your waking conscious mind. You’re updating the weights in your unconscious mind and explaining that is very, very difficult, you know, source, trust me, bro. 00:45:58 - Speaker 2: Now I’m curious, you mentioned trying to make that process of starting from the raw and unfinished and messy and moving to the more sorted out and organized, smoother, what sorts of things in practice has that looked like for your product? 00:46:13 - Speaker 1: I think for us it’s being nonprescriptive about how the tool works and really working on the primitives. So, Obsidian has a point of view on malleability and extensibility that I think is pretty unique. We try to get the basic things right like text entry, just like even that problem is actually really, really hard just actually making an editor that feels fast and responsive. I think a lot of people get frustrated with other tools that just don’t give them the feeling of they can type as fast as they want anytime and that basic problem is one that we Retain as like one of the most important things about obsidian. And so there’s a handful of these things that are kind of like the primitives like we think links are really important and being able to quickly link between files is really important. We added a new primitive with Canvas, which is like spatial relationships. But all of these different aspects of obsidian, you know, the next priority is extensibility. So the first priority is like let’s get the basic thing. The basic experience as good as possible for 90% of the use cases, but then everything else is a really long tail that is quite unpredictable and very different from person to person depending on how they think, depending on the kind of work that they do. Are they academic, are they creative? Are they using PDFs all day long? Like what are they doing in their actual workflow and how does the tool adapt to that? And so. We just accept that we’re not going to be able to, you know, put all those features into the app and instead what we’re gonna do is just make it really, really extensible so that people can build those things on top of Obsidian and take them in all the different directions that they want and assume that basically there’s going to be very little overlap between which specific plugins any given person is going to be using. I think that I personally have an inclination towards making, you know, these really well designed, opinionated tools that have like a way to use them. Like that’s what I’ve done a lot of my life. But obsidian has challenged me to really think the opposite way and say like, what is core, what is something that everyone needs, and then what is everything else? And recently, like AI has also been this kind of big interesting topic that I think a lot of us have been playing around with these different tools for chat GBT and so on to kind of use them inside of our tools. Like right now there’s probably like 15 different AI plug-ins for Obsidian, and they each have their own like little different take, whereas if you look at some of the other products in the tools for Though space. They’re each implementing it kind of as a first party thing into their app with an opinionated point of view. We don’t have an AI like first party AI integration right now partially because it kind of conflicts with our privacy and values, but if you want to use one of those tools, you can use any of the 15 different open AI integrations that exist. And actually one of the things that I’ve been enjoying is using Chad GPT to make plugins. So the other day I had an idea for a plug-in inspired by someone on Twitter had created this really nifty kind of prototype demo of a stream of consciousness writing experience where the words fade out as you’re typing them, and it just like is very immersive way of writing just like basically one word at a time. And I thought that was so cool. I thought it would be an interesting experiment to ask Chat GBT to make me an obsidian plugin that does this, and it’s not perfect, but I was able to get to something that basically replicated that, you know, within an hour. And so that really speaks to the malleability of the software. Like, can you take this thing and shape it to, you know, what you need as a tool for your process, knowing that maybe your process is even going to change over time, like over the next 5 to 10 years as you evolve as a person. 00:50:14 - Speaker 3: Yeah, it’s been really cool to observe the obsidian community with the plugins. There’s so much cool stuff that people have been trying. I’d be curious, is it your vision for plug-ins that they’re mostly kind of content oriented versus behavior oriented? So for content, I think of, you know, rendering basically and the MySpace backgrounds and that sort of customization, whereas workflow behavior, I could imagine something like every day you take all the Check items from your to do list that haven’t been done and move into a new document that you create with today’s date. Do you see both those as being in play for plug-ins? 00:50:48 - Speaker 1: Oh yeah, for sure. I mean, there’s literally 1000, I think we just crossed 1000 plugins for obsidian, and they do everything under the sun. If they don’t do something, if they’re trying to do something that we like don’t have an API for, that’s something that we should add an API for. Um, so I would say most plug-in, at least half of the plugins do what you’re describing. They’re workflow oriented, they allow. You know, syncing from other systems, they allow, you know, pushing out to other things to do lists like different view modalities for like Kanban or dates or like all kinds of different things. So we try to make it as open ended as possible as far as what plug-ins can do. 00:51:31 - Speaker 2: Yeah, and malleability is a big topic for the researchers at I and Switch, and certainly something I know from a lot of that research is that you do always have this trade-off as an extensible as possible system like you’re describing. If there isn’t an API for something, you should make it, but inevitably that does mean that people are gonna try and do everything to the point that the more extensible it is, the more easy it is to end up either completely shooting yourself in the foot. But perhaps a little less dramatically than that, deleting your data or something like that is more like just this conflict between you install these 5 different plug-ins, the whole interface gets really weird and janky. Now they’re writing in with bug reports about like this button doesn’t work right, but it’s because they installed some plug-in that messed with it in some unexpected way, right? Famously, this is like the difference between like Apple and Android, right? The iOS world is very locked down. You want to customize it, we’ll let you change the background or something, but that’s kind of it, so that they can make sure that experience is really curated and always kind of, you know, just works, so to speak, and then there’s the Android world which is more open-ended, but then is more famous for being basically a little bit janky. How do you think about that trade-off? 00:52:43 - Speaker 1: It’s definitely a trade-off. It definitely has its downsides, but I think that There are for the most part too few tools like obsidian in other spaces that give you that kind of freedom. So I think it’s also a reaction to what most tools that people are used to don’t have that malleability to begin with. So we’re OK with carving out this section of the market where people can have a little bit more freedom at the cost of, yes, you can shoot yourself in the foot for sure. The only thing that we can do is kind of provide the guide rails like what we try to do, for example, we just recently completely revamped the developer documentation. I mean, there’s basic things like how do you capitalize the text on a button, you know, like because we’re open-ended to plugins, like there’s different guidelines on Apple OS, the interface guidelines say that you should always title case your buttons, whereas on the Google interface guidelines it says it should be sentence case, and those are. Just two different opinions that these two different valid and viable and large platforms are choosing. So if you’re a plug-in developer, which one do you use? Like there’s all these like basic decisions you wouldn’t think about, but they make the app feel less cohesive overall when you’re using it if people are capitalizing their buttons in different ways. And so, There’s an effort that we need to make, which is to kind of help developers have really good defaults when they’re kind of building on top of obsidian and guide them towards things that are going to feel intuitive and cohesive to obsidian users while not limiting their freedom. Similarly, we have to also make sure that if you’re a brand new obsidian user and you’ve never used it before, that the kind of like. Top level, it feels accessible that you can understand how this app works, even, you know, with no plug-ins, it makes sense to you, but then it has infinite depth and you can go as deep and crazy as you want, but that that surface level is intuitive and inviting and accessible to most people, and that’s a really, really hard thing to balance. 00:54:59 - Speaker 3: Yeah, I think this is such a rich area, like plug-ins, extensibility, programmability, cause there’s so many variables that you’re dealing with, and at least with our current technology, there’s no way to satisfy fully all deerra at the same time. So you gotta explore the trade-off space and do the best you can and try to push out the frontier. So yeah, I’m very excited to see that you all are giving that a shot. 00:55:21 - Speaker 2: Yeah, I definitely like the idea of the core app that’s sort of very cohesively designed and it has more of a top, top down’s quite the right word for it, but it’s designed by one organization that can, you know, for example, use the standard capitalization on its buttons, but then there is a wider world or a deeper world that you can go out to, but you kind of know when you’re crossing from the relative safety into a bit more of the frontier. We talked about this a little bit with. The creators of Raycast and their plugin system and a lot of what they do is because there are so many of their users and certainly obviously the developers are developers and they can kind of work with them on the pull request and their review process is less, telling them what they can and can’t do and more saying, well, look, it’d be a bit more idiomatic or it fit in better or I think our users would appreciate it more if you made these changes, even potentially working with them on the code. And then of course, obviously you’ve got something like Apple that has this, you know, very heavy-handed and opaque review process, maybe there’s something like the browser vendors with their browser extension reviews are a little bit looser, but how do you think about that curation of that official List that you can submit your lugging into, is there really kind of strict guidelines? Is it more of a, you know, just what you feel is best for the community or you really just trying to filter out true malicious actors and it’s fine if it’s kind of heterogeneous in terms of the style and approach. 00:56:45 - Speaker 1: Yes, so we do have some strict guidelines that have to do with like security, for example, we will obviously like take plugins out of the directory if they have malicious code or anything like that. And so those guidelines are part of the submission process. So we do check for that before we Include a plug-in in the directory. All of the plugins for obsidian 99.99% are open source. And so there’s a little bit of kind of community validation around that as well. There’s certain principles that are important to obsidian, for example, around privacy, so we don’t allow plugins to collect any telemetry data within the app because we think that that is just part of the kind of Set of values that we care about, you know, a different platform may not care as much about that while still carrying a lot of extensibility, but to feel native to Obsidian, it really needs to work offline and have some of these principles built in. So those are the things that we don’t compromise on where we’re saying no, you know, your plug-in cannot be part of that directory. Actually, it’s almost never that we encounter bad actors. I mean, maybe it’s just because we’re small or the community that we’ve built is friendly and so on, but we don’t really encounter that many plug-ins that really stray outside of those guidelines. The next level is like more of a, I guess, of an editorial question which is what stuff bubbles up to the surface if you’re someone who’s brand new and is kind of asking the question, what can I do with obsidian? That’s where things, I think we could do a much better job and those are things that I’d like to work on over the next few years is. How do we surface the realm of possibilities that is there and right now, you know, the most like simple heuristic is just looking at the number of downloads, like you can see that some plug-ins have been downloaded way more than others and that gives you some sort of filter on which ones are better than others. But I think over time, we probably will get involved in curating a little bit more from an editorial standpoint, not from a who’s allowed in, but rather what do we promote, what do we want to showcase some of the interesting things that people have built and the stories behind them and how they connect to other different parts of the app. So I’m not sure if I’m answering your question, but I think that that’s kind of like trying to find that happy medium. 00:59:12 - Speaker 2: Yeah, well, certainly being relatively niche, having a relatively tight knit and friendly community is just a benefit of if you’re either early on or just a, you know, an independent software company that isn’t necessarily going for the mass market, you know, now, nevertheless, I do think that those values like for example, being able to work offline, that is something that is, you know, fairly unique in this industry right now where cloud software is the norm. And presumably someone doesn’t want to get in there and write a plugin for a piece of software if they don’t have some, you know, vibe with the core principles there, but I could still easily imagine as you grow, having people come in and just say, well, yeah, of course I’m going to access this. Cloud service because I can make a useful plug-in with that and then you come back and say, well, actually this isn’t consistent with our values. 00:59:59 - Speaker 1: Well, by the way, that’s not a requirement. There’s lots of plugins like the open AI plugins, like there’s maps plugins, there’s all kinds of plugins that communicate with cloud providers like so we don’t prevent that, but we do prevent telemetry data and we do require plugins to disclose when they’re using network data and for what purpose. And so, The guidelines are fairly open ended. Like people can really build things that heavily modify obsidian, and we’re OK with that, but we do get involved in, you know, making suggestions on the code when we review a plugin or developers will often ask in our Discord channel, what’s the right way of implementing something and you know, if it’s not already in our developer documentation, we’ll work with them or try to improve the documentation. And then there’s kind of a more subtle question that I think we want to work towards, which is what feels obsidian, like what is going to make a plug-in intuitive to a user? It partially is the interface, partially their expectations coming into what obsidian is like as a platform as an ecosystem, and we definitely want to encourage. You know, some developers, for example, are amazing at writing back end software or dealing with like really complex data problems, but they might not be as used to doing the front end part. And so when they go about implementing the GUI part of their plugin, they just need a little bit of extra help with the CSS or something, or what is the right kind of approach to designing this UI for this plug-in. So, Those are things that, I mean, we’re still early on, I would say, and how do we kind of strive towards like making things cohesive um while still giving plugin developers as much freedom as possible, but we definitely skew more towards the freedom than the cohesiveness. 01:01:51 - Speaker 2: I’d love also to ask you about a feature you launched pretty recently called Obsidian Canvas. Obviously this one caught our attention since Canvas is a kind of fundamental docume

Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: We can do the basics that Spotlight can do, but also much better. We invested a lot in the speed to make it faster to launch. We invested in file search to search files in a more predictable way. And then when you have those basics, then there’s the question, what else can you bring to this so you can start navigating and controlling your computer in a new way. 00:00:26 - Speaker 2: Hello and welcome to Meta Muse. Used as a tool for deep work on iPad and Mac, but this podcast isn’t about amuse the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGranaghan. Hey, Adam. Joined today by Thomas Paulman of Raycast. 00:00:43 - Speaker 1: Hey there, happy to be here. 00:00:46 - Speaker 2: And Thomas, I understand you have some travel coming up for you and your team. 00:00:50 - Speaker 1: Yeah, that’s correct. So yeah, we had Raikas, a fully distributed company, but once a year we get together with the whole team and it’s gonna happen soon. So next week, we’re gonna go all to Greece, having a good time there. And we really enjoyed it. It’s the second time we do it. The first one we did was a huge success. It was especially the moment when the pandemic came a little bit to an end as well. So it was really good for everybody getting there. It just makes a huge difference as a remote company seeing each other in person. 00:01:19 - Speaker 2: Yeah, that’s been sort of a secret weapon for us, or maybe not so secret, which is those in-person summits fill quite a lot of what you do get out of being in an office together and gets coupled with getting to go to nice destinations and so forth. 00:01:33 - Speaker 1: It’s also cool because last year we had a few people joining us before they actually worked at Rayos, which was also the perfect onboarding for those kind of people, because, yeah, in a remote company you usually don’t see everybody always in person, but it’s made a huge difference for them. 00:01:50 - Speaker 2: And tell us a little about Raycast. 00:01:52 - Speaker 1: Sure, yeah. So for the ones who don’t know about Rayos, we often describe it as a general productivity tool, mostly targeted towards developers, but also designers and other people who really work on a computer use it. For Mac users, the easiest to describe it is actually A spotlight on steroids. So everybody works on a Mac. No spotlight. The basics are to launch an app, search files, do a few calculations. But with Breakers, we put another level on top of that. So we’re connecting to third party apps like GitHub, Linar, Figma, and have like a public store where people can build extensions for, but other people can experience. So you can think of it a little bit like an app store. So people can build something, share it with others, others can immediately install it. So it makes your work more productive, faster to do. It’s all driven by keyboard shortcuts. It came out of an idea from me and my co-founder. We, like, hugely obsessed with productivity, and we’re a little bit frustrated that nowadays on a computer, oftentimes there’s a lot of friction in the small and little tasks that pile up. And we thought we can do better and basically build it right cause there’s this layer on top of all the other apps that you can use them in a frick. And less way. And so far that seems to be working very well. A lot of people enjoy that. Building extensions with us together. We have a huge community behind us that’s helping us building those experiences. And sometimes they’re ranging also to more fun things like a gift search that you can put in a request, a nice gift, and those kind of things. 00:03:24 - Speaker 2: And we’d love to hear a little about your background, what brought you to this venture. 00:03:28 - Speaker 1: Yeah. So I’m a software engineer and my career started in mobile development. So I worked in iOS and Android. For me, the passion there was I could build something that I can immediately experience. And that basically, since then, I enjoyed doing, like building something that I can experience and share with others. Before Aos, I worked at Facebook on a desktop application, also on the Mac, which was called Spark AR. What I often described as a Photoshop for augmented reality. So for the ones who don’t know it, it looks a little bit like Photoshop. You have a few port in the middle. You can track in 3D objects, and then you can, for example, attach it to your nose and it sticks to your nose with the augmented reality efforts that were there. What was really interesting there, it was also community driven. So it was a tool to create something and then you can share it with others on Instagram and Facebook, and they can use those effects. And this community aspect is really something that I fell in love with, because if you build a tool that other people can produce something with, it’s really interesting to see what they’re gonna produce with. And so with Rayos early on, what we did there is we wanted to make our work flows faster, right? So we build up the stuff for us. And then after a while, we realized there were so many things out there or tools that we may never heard of that like a platform where people can build extensions for and share it with others is actually the way to go. So now we have an API. People who are familiar with React can use the API very seamlessly, and then they can get into creative ways, building those extensions and share it with others. So now it, you have pretty much for every service you know of, you can find one of those extensions, can install it immediately, and can basically gain little productivity boosts throughout the day. Which then oftentimes cut away entire friction points by interacting with slower tools, and that’s what brought us initially to rate us, right? We wanted to make. Little things faster that then have this compound effect that you just enjoy you work more, and that to this day is still our mission which we operating on to every day. 00:05:34 - Speaker 2: And we’ll link the Raycast store in the show notes. I can certainly see the connection between the Spark AR and, you know, that’s a creative tool, certainly you’re helping other people create things, and then the joy one gets from seeing someone make something with a tool you have created that does seem to be a common theme across people that are drawn to building tools as opposed to sort of end user experiences. I’d be curious to hear a little bit about the technical stack. So it is a native Mac app, but I noticed when I just briefly poked at trying to build an extension for Raycast that the hello world is very much like a React component, feels very web technology-ish. How do you do that? Is it ultimately kind of all a pretty fancy electron app or is it just the extensions are kind of like using web technologies, but you use classic native development for the core app? 00:06:24 - Speaker 1: Yeah. It’s actually a question which we get asked quite often. So the app itself is 100% native. It’s written in SWIFT and doesn’t involve any HTML or CSS. So everything is rendered through Apple’s A kit. Actually, we don’t use Swift UI yet. So that was an early decision because we felt like we’re building this app which sits on top of the system and we want to make it really part of the system with the look and feel, but also What you can integrate it with. So early on, we thought like, hey, Swift is the way to go. Also, like, we worked on iOS and Mac OS before, so we knew the tech stack really good, which helped us initially to just bootstrap the app really, really quickly. But then when it comes to building an extension platform, you have a different problem to solve, right? So they actually want to extract the system away and rather want to make it accessible to as many developers as possible. And we went there a little bit on the journey to really figure out how we should build those extensions and especially the API for the extensions. So initially, we started with like more of a version where you have basically finding a chasing schema that you give the app, and then the app renders basically what you describe in this chasing file. But then this brought a lot of like issues when you want to build something more complex, like think about networking requests and then depending networking requests, maybe some optimistic updates to make it snappy. So what we then saw is like, OK, there are already really good UI frameworks out there, and React is one of the most known ones. So why not using React to build extensions and What we did is basically, you can almost describe it as a lightweight react native. So what we do is you literally write react, but instead of rendering HTML, we’re actually rendering swift components. So we’re exposing components like a list and a form, and then you can use those elements to build your extension. And then we just render that with our native engine in, in the application. And it has two benefits, like one, Every developer who knows React can immediately write a Rayo extension without learning anything new. And 2, we keep it very consistent across extensions because we expose these high-level components like a list, and then a list has list items with a leading icon and a title and a subtitle. So all of the extensions look and feel very similar, which was very important to us. But we also have basically the flexibility of React where you can write something really, really complex. So you see now extensions like Gitlab is a good one. It integrates with everything from Gitlab and is nowadays quite complex. It involves all else and optimistic updates, caching, and makes it really, really fast. So it’s a nice abstraction away. And it’s funny now when you have built those things initially natively, and now look at our extensions API. You actually can build those things oftentimes much faster with the extensions API now than what we have done initially natively. 00:09:24 - Speaker 2: It’s a pretty clever way to slice it because for sure, something like a quick launcher of this sort, first of all needs to be really fast, and second, absolutely has to be integrated to the operating system in a way, I think that would be hard with one of these web technology shims, but on the other hand, extensions are something that are pretty naturally. Yeah, using some variation of web technologies fits naturally with that one because I think so many developers know it, and then maybe there’s other benefits as well in terms of, I don’t know what sandboxing or something like that, but yeah, you’re using each technology for the thing that it best suits for and then sort of bridge that gap through your system. 00:10:03 - Speaker 1: Yeah, exactly. I think it also is just a nice separation of concerns, right? So you have natively where you can make this pixel perfect UI components, and then you expose a very high level API that extension developers can use. We’re working at the moment on a file picker, for example. It’s entirely built natively because, well, you need to interact with the operating system to pick files, right? You need to open the finder and so on. And then on the UI side or on the extension side, you can just make it a lot easier, but just say, I want to pick this file or this directory and show me hidden files as well if you want to. So you’re abstracting like a lot of stuff away that an extension developer just doesn’t need to care about anymore. 00:10:47 - Speaker 3: Yeah, I was so interested when I saw the extensions angle on Raycast, because it connects to this idea that we’ve been thinking about for years in the lab, and it’s still a background for us in Muse. It’s like end user programming, extensibility, and so on. Yeah, and the holy grail that I’ve been after is how do you get the very high performance of a low level language like C or objective C with the security or something like a high level language and the end user approachability or something like JavaScript and React. And I think fortunately, in your case, it’s constrained enough that the performance, for example, of extensions isn’t as big of a deal in the sense that like it’s like you’re doing wild computations in the extension itself, right? So that’s kind of a degree of freedom that you have. But the end game that I’ve long imagined is being able to write extensions that are no compromises, and that can eventually be promoted all the way up into the app and even the system, so that you don’t have the like extension world in the app world, in the OS world. It’s more like a continuum where you move back and forth according to your degree of certainty and trust. So I’m always interested to find out how people are tackling this problem because As much as I want that thing, that thing doesn’t exist, you know, it’s an open research problem determine if even can be made. So I’m always curious to see how people are tackling it. 00:12:05 - Speaker 1: Yeah, it’s a super tough problem, right? You want to have flexibility, but on the same side, you want to constrain a little bit that it fits still in the system. So one thing which we did initially when we build the first extensions, we just build them natively to figure out essentially what we need to build and to understand DUI and the UX of something. And then we quickly came up with a paradigm. It’s like, OK, everything you do in Rao is launching a command and that command is basically a standalone thing. That can operate on its own. And then this is basically a constraint you’re giving to a developer. Hey, as soon as this thing is launched, you can do what you want to do, but you need to launch it, right? It cannot run just randomly. That adds certain constraints. And then when we then came to basically the, the extension world, that was really nicely applicable because we then can say, OK, you build commands, they get executed when you launch them run within Ray cost. And then we had enough of this primitives like lists and forms that we can expose, that they can use. They’re very high performance, and then look and feel like the system. So it plurs this line of like, what is actually part of Rayos versus what is an extension to it. Like, a lot of people nowadays don’t longer know that, right? Initially, there was what we had, like core extensions and then some third party ones, but nowadays it’s like just a blurred line because all of them look and behave very similarly. And one missing ingredient that I haven’t mentioned before is like we also have all of the extensions open source and refill them. So to submit an extension that goes into the store, you essentially open a pull request with your extension. So that helps us to also keep the UX and the UI and all the behaviors very similar across extensions because I think that’s, especially for Ray cars, um, which is a tool that you use, basically about muscle memory at some point, it’s very important that the things behave very, very similar. And then from the performance aspect of things, so one thing which we did is we run Node as our JavaScript run time. So with Node, it’s actually very performant for the little operations we do. You have also the benefit if it becomes performance and issue, you could get native modules going as well to integrate them, to get performance out of it. And then React is also for the sizes of extensions to build fast enough to produce DUI. And then we are not constrained and rendering the UI because that again we do natively. And then one thing which I think is very interesting when you integrate something in your main app, you want to make sure there is a certain boundary between main and extension. So if an extension crashes, the app should stay alive, right? So what we do is we run all of that extension code out of process. So it has a separate process. So if there is something corrupt going on in the extension that doesn’t block the main app, it stays responsive, can go back. And I think that’s just a good user experience, right? Because we all know as developers, they’re gonna be bugs, unpredictable things, networkers fails, you maybe don’t handle it properly. So you want to make sure that the app itself behaves correctly, especially with an app like Rayos, which I use hundreds of times a day. You can’t really afford that this thing is gonna crash when there is something wrong by a third-party developer. 00:15:21 - Speaker 3: Yeah, I feel like we could do a whole podcast on this area. I think we sometimes caught it on the show the platform problem. How do you navigate the performance, security, sandboxing, isolation, consistency, developer experience. I also suspect that Adam, you want to talk about the space of wrong. 00:15:40 - Speaker 2: Indeed, as you were talking there, Thomas, I was flashing back to our platforms episode with Joe Webkin, where we talked about maybe not some of the OS level stuff you’re referencing there, Mark, but definitely some kind of store slash plug-in directory and a review process, as well as the constraints that are created for the extension developers you mentioned, for example, you know, these lists and You know, an icon next to an entry is kind of a standard thing to get back as a result of one of your extensions, and that’s potentially desirable. When Joe talked about building a slack app, he said, this is really nice. We don’t need to do much design because there’s so many constraints, like it’s just an icon and some text. It’s only kind of so many ways to do it and in a way that is nice because you have fewer decisions to make and you can just focus on getting the thing built. 00:16:27 - Speaker 1: Yeah, I think what’s also interesting with constraints comes creativity. I mean, that’s a common phrase that you probably hear a lot in those tools that allow people to create something. But it’s actually really true. Like, yes, we provide just lists, but then if you look around with lists, you can actually build a lot of stuff, right? And then with forms, you can do a lot of data inputs. And then we have things like grits, which you can do a little bit more visual style, like showing images. But you will be surprised what people come up with. Like one thing which I remember is just, we can render markdown and we have this detail for you where you can rend the markdown, and somebody just came up with playing snake and just rendering markdown. So it’s obviously a huge constraint if you just have markdown, but developers are creative, right? And so you can build an entire game with just markdown rendering. So it’s always inspiring, and that’s what I mentioned initially with communities. You have like certain ideas what you can build with it, right? When you decide an API, you think like, oh, there are just certain use cases and you maybe prototype, but then when you put it out, the minute you put it out, people interpret it differently and come up with something new. And that’s super exciting about wait and see other use cases that you haven’t thought of before. And I think that’s always the interesting bit was Pretty much every platform that is built out there. It was initially with the iOS App Store as well. There were fun apps initially and then people figured out what are good apps. And then it shaped this whole ecosystem, which we now nowadays live in. But I bet at the beginning, there wasn’t really a plan where this leads, and it’s this iterative process. You put it out and see what works, what doesn’t work, and iterate on it. And a lot of people are involved in this process. By sometimes not even knowing about it, right, because they’re just building for the platform and coming up with something that pushes the boundaries. 00:18:23 - Speaker 2: So our topic today is launchers and a closely related element, which is command palettes. Now for me, launchers is usually the term I use or the category to describe, you mentioned Spotlight earlier there, Thomas, that’s the Mac OS built in. There’s a similar one for iOS and iPad OS if you swipe down on your home screen on your phone or your tablet, you get a kind of search bar slash launcher thing. There’s quite a long history of this stuff. One of my first introductions to it was actually the KDE Linux desktop system, and I think somewhere in, I don’t know what it was like, 2002-ish, they introduced a feature, I think it’s called KRunner, but you essentially you would press a hot key Al FF2 and you’d get this little Mini command line where you could just run a program or do some very basic things, but it was an absolute revelation because before there was always this trade-off of you’re in the terminal, the command line’s great for a lot of things, but of course it also is, can’t do many things from the GUIY world or you then you’re in the GUIY world and everything’s about clicking on menus or the occasional hot key. So that was my introduction to it, but I feel like there’s a pretty rich history of this, and I’d love to hear. You probably are one of the most knowledgeable people on it, so I’d love to hear you walk through that a little bit. 00:19:38 - Speaker 1: Yeah, I mean, we’re working in this space, right, and looked in a lot of those things. And as I say, it has a long history. I think, actually, I would almost take a step back and like, you touched on the terminal, right? I think that’s kind of where all of this sparked. I mean, it was the first interaction we had with computers where you can just interact with it by text input. And I think this is for the launchers and command pallets that dimensions. It’s still the thing today, right? You navigate this without a mouse by text input and keyboard shortcuts. I think the true roots come from the terminal and also what I mentioned in Rayo, you run commands, which you have in a terminal. And we also have arguments for those commands that you can give it arguments to do different things. And when I look back into the history, I mean, after the terminal, the GUI came, right, where we made functionality available with, with elements you can click, which obviously made it a lot more user friendly. But it also came with a little bit of a downside. What you have there is you just have limited real estate, right? So you have buttons and you can only place that many buttons on a screen. And I think that at some point, you run into the limitations of that, and there are these clutter to your eyes. I think one of them. It’s quite known for its Photoshop, which has just a ton of menus, which you’re losing yourself, and there are tutorials on how to use it. But I think it just came out of the need of like software growth and functionality and you’re adding more and more, but the display stays the same, right? Uh, the real estate you have to put those things stay the same, and it comes at some point very cluttered. 00:21:14 - Speaker 2: A metaphor I used to use when explaining to people why I used the terminal. This was, I don’t know, decades ago and I think Folks once, for example, Windows came along and made GUI’s pretty mainstream and they would see me using this computer, what they saw as a more archaic way, and I would usually describe it as, OK, well, menus are like going into a restaurant and ordering from a menu where you’re pointing to pictures on the menu, but like, exactly, you can’t have a lot of nuance. You can point to this picture or that picture, but that’s kind of it. Whereas if you want to have a more in-depth conversation with the chef about all the fine flavors that are in it and how you’re going to tweak it and that sort of thing, like, then you need the power of full language. And that’s to me what a command line is more like having a conversation with the computer. 00:22:03 - Speaker 1: Yeah, I think that describes it actually very nicely because it’s oftentimes even a back and forth, right, where you give the computer one command, it gives you back an answer. You use this answer to pipe it to a different command and do something with it. And this is just very hard to replicate in GUI, right? If not even impossible. But I think in GUI, but then at some point, people realize that there is too much and they try to put in a search for those functionality. And one of the first ones that I remember was in Mac the help menu. So if you click on Help, you have this search field, you can put something in and you search all the menus that you have there, and then you can click that. And that was actually quite nice to use the software you have there. And so it made it more accessible, can find those things. But it was a rather hidden feature, right? Like, it was behind the help button, and usually you don’t like to click help, right? It feels like you can’t use the software. You need to press the help button. So it’s really not. What do you want to click that often? 00:23:02 - Speaker 2: Yeah, I use the help Mac OS search as a quick launcher all the time for, yeah, functions I don’t use all that often, maybe like spell check and sublime text. The way I invoke it is I click help and I type SPE and then I click, you know, basically the first result, and probably there’s a similar thing with, yes, so my video editing software where there’s just so many functions in it. And yeah, I guess that one thing, there is some key command I could memorize, but I just don’t use it quite enough, but I know what to search for and it’s very quick to type it in, so I just do that. 00:23:34 - Speaker 1: Yeah, and it’s quick enough, right? And the other thing is like what the help menu, I think struggles with is it’s just constrained to one application at a time. So you couldn’t use it in your video editor to search something completely unrelated to the video editor and do an action outside of it, like launching a link or another app, right? So it wasn’t possible back then. But then other apps also picked up this behavior. I think one of the first ones that I know that had kind of like a built-in command palette. It was for me sublime. I think initially it was just the file search, but it was extremely efficient. It just popped up the keyboard shortcut, you search for it. And that’s how I learned navigating around files. I lost then basically the sidebar wasn’t really relevant for me anymore, right? It was really just the opening it up, search for the file, continue where you want to program, and then again, opening it. And then they added also functionality in a similar menu. It had a different keyboard shortcut. But you can then search the actions that you can do. This were just menu items I think initially and then even more functionality which wasn’t available in the menu item. And I think a big difference there was it was just front and center. You press this one keyboard shortcut, and you know, you can do everything with it. So for me, that was the point when I almost stopped using keyboard shortcuts that heavily because I knew there was a lot of functionality in there that I don’t use that regularly, but I know how to find it and it’s reliable. And I think that’s, for me, was one of the first experiences where I felt like, this is really good. User interface, it’s still has a very clean UI. It’s not distracting, but you have this full power available via the keyboard without touching a mouse or navigating around in the menu, which is quite cumbersome. 00:25:22 - Speaker 3: Yeah, I actually find it helpful to think of all these UI inputs holistically as follows. So imagine you have a huge grid and the rows in the grid are all the operations you can do in your app. It’s like jump to file, increase text size, indent here, collapse code block, and the columns are the different ways to send inputs to the UI. So you have the menus. You have keyboard shortcuts, you have maybe the command bar, maybe you have Siri, and you have the help menu, and I think the best systems have a few properties. One is they actually use all those inputs. They’re systematically connected. The example of the help menu was a good one where you go to the Help menu and it like literally shines a light on the menu where the command is. And likewise, in the best systems, all of the operations are available in as many of the columns as possible and ideally the user has agency over managing those mappings, so they can change the key binding. And that might be reflected in the menu, you know, a little gray icon that shows what the chorca key is next to it changes as well. 00:26:32 - Speaker 1: Yeah, I think that’s interesting like to basically expose the functionality in different ways. What’s interesting about that one is also you talk to different users, right? So I think not everybody want to use a command palette. It’s on the one end inside a simple system, but it might also be more for advanced users that really rely on the keyboard all day, but you can expose the core functionality also a very good SUI, right? It’s still very useful to have those buttons because they also tell. A story, what is an important action you want to do at the moment. It can highlight something like you have on Zoom calls, the leave button, it’s, it’s red on the end button, right? So it says to you, like, hey, there is a button. If you press that one, it’s red, so be careful about that. But it teaches the user certain interactions that are in the context very important. But then as you mentioned, there is like probably too many of those actions that you can take at any given moment that then the other utilarian things like a menu and a command pallet can shine to give you access to those actions in a more concise way. 00:27:36 - Speaker 2: Yeah, they’re much more discoverable and approachable. 00:27:39 - Speaker 3: Yeah, and in fact, a key benefit of often it’s the menu and the command palette is a complete enumeration of the options. One of the most annoying things for me about software is when I can’t discover the full set of things that are possible, it’s like hidden and there’s no way to enumerate them. But typically, if you open up a command pile and then don’t type anything, you can just press down arrow a bunch and find out all the cool and obscure stuff the app can do. 00:28:03 - Speaker 1: Yeah, definitely. It’s a good way to explore the functionality of applications, especially like the more hidden ones as you mentioned that are maybe further down. 00:28:11 - Speaker 3: And while we’re talking about the properties of these systems in general, I just want to make two kind of theoretical comments. One is, we call them different things like launchers and command bars. I think there’s a bit of a dichotomy in here. So there’s what I would call launchers, which is like you type an app name and it launches the app. There’s search, which is you type like plain text and it finds documents that have that text in them, just like look up where you know the name of your document and you type that and it opens the document for you. There’s commands like calc, you get a calculator. And then there’s hybrid systems that do a mix of all of these, and I don’t think any of those are better or worse. I just think it’s useful to understand there’s quite a spectrum, and that often it’s pretty useful to just combine them all into one thing as Raycast does. The other point I wanted to make, and you knew this was coming, was the importance of speed and performance in these systems, and it’s subtle cause it’s not just that. The system responds quickly to input, although they usually do, and that’s often a benefit of these things, is that you often don’t need any branches at all. So if I want to increase tech size by going through a menu, I have to look at my screen, find the place I want to go, move the mouse there, visually confirm that I’m over the menu, click, confirm that it comes down, move the mouse down. To confirm, each of those visual confirmations is a branch and anytime you’re round tripping through your whole sensory system and making a conscious decision to click or not click, like you’re kind of already hosed, it’s already hundreds of milliseconds. Whereas, like another example, if I want to open the sublime map, I just hit command space SUB enter, and I don’t need to look at my keyboard. I don’t need to think. I don’t need to check any branches. I can do that all basically in one string, and a little bit later, the app will pop up. That’s a huge benefit of these systems and other kind of keyboard input systems in general. 00:29:52 - Speaker 1: Yeah, I totally agree. Speed is like a fundamental thing to this. And it’s not only speed, it’s also the predictability because you described, you type in SUV for sublime, hit enter, right? At some point, it becomes just muscle memory. So you don’t really think about it anymore. You know, you need to go to sublime, you do the sequence that you described, command space, SUV, enter, and then you dare. So the system also needs to be predictable in a way. And that’s also sometimes a challenge, right? Being fast. Predictable, sometimes conflicts. You can’t do many things in parallel because then it becomes unpredictable what finished first, or you need to sequence it somehow. So there’s a huge technical implications there. And then also, what’s very interesting with that you can optimize as well, because it becomes a very fundamental part on how you navigate your computer. And you do a lot of interactions through it, so it becomes smarter as you type in there. So if you type SUB all the time, it recognized that maybe even earlier, if you just type SU, it already uprk because it knows, well, you’re gonna type sublime and make sure that you hit that even faster. And that’s also an interesting angle, which you can’t really have with the UI that you described in the menu where you need to do the steps yourself, and it’s just a lot slower than what the system is capable of doing. 00:31:12 - Speaker 2: Predictability is a huge one for me, and this is a place where, unfortunately, the default system ones for me fall a little short, Spotlight on Mac OS, for example, I use the file lookup aspect quite often. Or you talked about the launching applications, looking up files, searching, and for me those first two are the most important. But yeah, Spotlight will kind of maybe like it updates its cache, sort of lazily, which is fine, but what happens is you type something in. You think you see the result, you hit enter and then it changes the moment before your finger comes down. Which is to me it’s just a no go. Similarly, on the phone and on the iPad, I do use the home screen search quite a bit, often for launching applications, but sometimes for looking up documents. And if you tune it to turn off a bunch of junk, mainly the Siri suggestions that basically go out to the web, but that just takes time, especially if your network connection is not ideal, and so you tend to get this thing where it just changes underneath your finger, and to me that’s just a total no go. 00:32:13 - Speaker 3: Yeah, I feel like I’ve seen this on my Windows machine, which I don’t use very often, but occasionally I’m on it, and it’s like, you open up that whatever it is now. When I was a kid it was the start menu or whatever that is now, and it like starts searching for news stories, and like it’s looking at online help articles, it’s like, I’m looking for to do that TXT on my computer, calm down. 00:32:30 - Speaker 1: Yeah. That’s one thing which we deliberately did in Rayo. So if you open that, it’s very predictable. We basically make sure that it’s a fast algorithm that matches all your entries, but it doesn’t do async operations like going to the network, trying to fetch something, which just ruins the predictability, or it makes it just a lot slower. So there is a lot of engineering work went into The initial version and we did recently an iteration on top of that to make basically that as fast and predictable as possible. And then functionality that needs to go to the network, for example, to search your linear issues. They are in a separate command. So you launch this command and then you’re in the command, and then they can perform an async operation, but even there, We basically build it in a way that there is always cash available, that it is fast by default, and if you need additional data, it’s getting updated in the background. But yeah, like, I think this is sometimes undervalued. Um, making something predictable and keeping it predictably fast is sometimes tricky, but it’s hugely important for such user interfaces. 00:33:40 - Speaker 3: Yeah, and now that I’m thinking about it more, I’m realizing that the moment you stray from totally deterministic predictable, user controlled search, or basically an algorithm for that, that’s totally within the user’s control, it just becomes overwhelmingly tempting for the platform to do nefarious stuff. The example I’m thinking of is Twitter, where Twitter, like every few days, will try to opt you into their algorithmic timeline, but you can go in there and say, no, just show me the tweets of the people that I’ve explicitly followed in the order that they posted them. And the reason I do that, like, you know, a lot of times Twitter has interesting suggestions, but they kind of can’t help themselves but suggest clickbait. And I feel like you kind of get the same dynamic whenever you have algorithmic lists. And so this is a little bastion of user control that I’m trying to maintain in my computing environments, both Twitter and the launchers. 00:34:28 - Speaker 1: Yeah. It’s interesting. One thing we did, we made it configurable how sensitive you want to have to search because the search is very personal. People search for things differently. There’s obviously a huge overlap, but certain groups search differently. So we had initially just, um, searching for prefixes and we switched recently to Fuzzy search where you basically can search for letters that are not directly followed by each other. And that opens up just a lot more search results. So you need to rank them differently and cut them differently off. So what we did is we basically added a preference, and we very not keen on preferences because we feel like we should ship really good defaults. And then here and there, you maybe need a few preferences. This was one of the ones which we went for, because like, we test everything with our team and we’ve already realized there, there are different styles of searching for it. So we went for a preference and made it a, a nice slider, which you basically can Configure the sensitivity of how you wanna have those mats appear in the route search and ray cost. 00:35:29 - Speaker 2: And we had started a little bit on the history of this stuff and the discussion of fuzzy search also reminds me of the first time I saw that, which was in Textmate, I think it was the command T as kind of a different way to quickly pull up files, and it felt like a an amalgamation of search and the command line, which maybe is is in the same realm as all the stuff we’re talking about here. And we started to talk about the history a little bit. I’d be curious to hear where you think this stuff went mainstream, Thomas, because clearly, yeah, this is built into Mac OS, iPad, iOS, whether or not you like the system, default or not, it’s acknowledged by the platform maker that this is something that should be available to everyone. Windows indeed. Has it also, again, I don’t know if start menu is the right term for it these days, but I know when you use a Windows computer these days, you hit the Windows key and your cursor focuses on a field that is pretty simple, but still like kind of one of the launchers. So clearly all the platforms have said this is a core feature, but that wasn’t always that way. They were third party apps at the beginning and it’s interesting also in the case of Raycast, you’re kind of coming full circle and saying, well, actually we could do a lot better than what the core operating system is. 00:36:41 - Speaker 1: Yeah, definitely. I think in the early 2000s, it was the time when you look back, where a bunch of those third party launchers appeared, and Mark touched based on launchers that are basically things to launch as applications. But I think also one critical thing for launchers is that they, globally on your system. So they don’t live in an app. They’re an app themselves, which basically sits on top of everything else. And the first ones were, I think, launched by Quicksilver, both of them. 00:37:10 - Speaker 2: I have great memories of Quicksilver, yeah. 00:37:11 - Speaker 1: Yeah, Quicksilver got a lot of love back in the days. And yeah, basically, they started, I think, with launching applications, but then also thinking a step further, what is it, what you else do? You have files were big in the early 2000s, right? And you need to do something with this files. You may be opening in specific tools, you may want to send it via an email. So there were more this. I think verb, noun input, like you find something and then you do something with it. Initially, on the Mac, at least, this was, um, located on the top right. I think they’re done also the spotlight position that was initially there on the top right where you had this little search symbol, the magnifier glass. You clicked on it and there was a search feed popping up. So it was highly inspired from the help menu that we chatted before, but it was just globally, right? So you clicked on it, you could search an app. And then you launch the app or you can search for files, and it launched the file. And it was the very early days of this. And then later in the 2000s, this became more of a redesign. When Spotlight became, I think, very mainstream was when they did in Yosemite, the redesigned to make it a front and center bar, that when you have the hot key command space, it pops up, and then you have this one big search field to input something. And then it finds results and you can execute on that. I think that was, for me, the tipping point when it became really mainstream because it was a really big feature in Mac. It was basically how you launch your apps, how you find your files. It was a core part of the system by then. And then a few years later, also this became basically part of iOS and basically having the same experience as you described that them to search apps and launch that as well. 00:38:58 - Speaker 3: Yeah, this history overview is quite the trip down memory lane, because this is where you start your computing when you sit down, that’s sort of like a series of pictures of all the living rooms of all the houses you’ve ever lived in. It’s pretty wild. 00:39:09 - Speaker 1: Yeah, good memories also for old operating systems to see how those evolve over time. 00:39:16 - Speaker 2: It is always vaguely shocking to see screenshots of even relatively recent past, you know, 10 years ago, Mac OS or really any operating system, certainly a, a phone screen, which of course will be massively lower resolution than what we have today, and therefore tiny when rendered 1 to 1, and yeah, it’s, you know. Technology moves fast, both in the sense of what computers can do, but also the fashion of it, I think the stylistic elements or something that are constantly evolving for good or for ill. 00:39:48 - Speaker 1: Yeah, definitely. And I think after then, Spotlight became this main thing and other third party apps built like similar feature sets out. I think another tipping point that I saw is like this just a few years ago when we chatted about text editors like Sublime or text made before and VS Code is a modern version of those as well, who has this command palettes inside. But there were other apps outside of developer tooling coming up with command pallets integrated. There were Superhuman, which is an email client, which is very focused on keyboard shortcuts and had this command pallet to make all the actions on emails accessible. There’s linear and issue tracker, similarly, where you can Navigate through it with a command panel that is built in into the tool. And then also other apps like Notion, which oftentimes focus only on search, but even that, they follow a similar interface right where you have this keyboard shortcut, oftentimes it’s either way command K or command P, which seems to be the primary keyboard shortcut that those apps select. But I think that was something which made this even more mainstream because then It got out of this more niche developer space where people experience in, in those other applications or sometimes websites, and even it goes so far that companies nowadays advertise with it, right? So you see on homepage like, oh, we have this fast user interface which is totally accessible by command pallets and that’s just super fascinating to see when such a user interface change happens, right, which we Haven’t really had that many in the past. We started with buttons, we’re still with buttons. A lot of the things are still the same primitives. I think that’s one of the primitives, at least that I remember, that just popped up rather recently in modern UI development. 00:41:42 - Speaker 2: Yeah absolutely. Also, give a shout out to one of the friends of the podcast, which is the Arc browser, and they quite cleverly took, I think it almost feels like a natural extension of the fact that you have a URL bar in browsers, and people know you go there to type in the website you want to visit. At some point, Chrome merged that with search, so right there, that almost mark covers two of the three you were talking about. You’ve got search and the sort of look up by name. The kind of the web version of that, and then arc take it a step further, which is now when you press that same keyboard shortcut that you would normally press to make a new tab or to activate the URL bar, that’s command to or command L, you get something that is indeed can be used as a search or URL entry, but basically is a command palette quick launcher. So I thought that was quite a nice evolution or it feels like this gradual enhancement of what was originally just a place you typed in a web address. 00:42:38 - Speaker 1: Yeah, that’s true. Yeah. I think even with just what you mentioned with Chrome is interesting, right? Initially, you just type in an address, then it became Search for history, then it became just search with the suggestions. It’s just a nice evolution of what seems to be a simple text input can actually be quite powerful and saving again a bunch of clicks or network navigations that you need to do if you don’t have that. 00:43:04 - Speaker 2: And how do you think about the fact that given that this is a built-in platform feature essentially everywhere now and you’re building, presumably what is a better version of that? I mean, I’m a recast user, so I can definitely say it is better than the built-in spotlight, but do you see that as like a challenging, I don’t know, marketing problem or sales problem to pitch the value prop of we’ll install this extra app, it does what you already have, but more or something. 00:43:31 - Speaker 1: Yeah, it’s definitely a problem we’re thinking about. I mean, one thing, Adam, that you mentioned before is people are sometimes frustrated with the buildings due to like the nonpredictable results. So often sometimes people come with those frustrations to us. One thing that we always say is like, you will always have one of those global launchers or command pallets installed, right? Because You have this one keyboard shortcut that you remember and then you’re gonna use that. So at some point, there is a situation where you go from the building and spotlight one to recast and hopefully replace it with the keyboard shortcut that you had before to keep your muscle memory. And so one of the things that we did very early on is basically said, hey, there is this moment when you switch. So what we need to make sure is that we can do the basics that Spotlight can do. But also much better. So that’s where we invested a lot in the speed to make it faster to launch those things. We invested in file search to search files in a more predictable way. And then when you have those basics, and there’s the question, what else can you bring to this, right? And that’s when we decided on the platform aspect, because then you can integrate with pretty much anything else that is on your computer, so you can start really navigating and controlling your computer in a new way. And that goes often that far that people use third party services like Chia exclusively in Rayo because the daily operations they have is, oh, I need to create issues, or I need to see what is assigned to me. And then when I see my assigned issues and Rayo, you also can modify that and update your status. So there is nowadays, a really full flexibility and functionality in there that is not longer just like searching and launching. We rather think about what is actually the workflow you want to do. For example, I want to create a bug report. I’m writing my editor, but I don’t want to jump to the browser, navigate to Chia, open the link, open the create issue form. I would rather just press my global hot key for Raycast, search for the command, type in what I want to have for the bug report, create it, continue where I left off. So we’re really on the path of like covering full workflows instead of like just finding and opening because we believe that’s obviously some part of it, but it’s much better when you can close the loop entirely. And that’s what we kind of said with Rayos, that it really removes the friction that you usually have in a bunch of other things as well. 00:46:03 - Speaker 2: Also occurs to me you’ve gone a little bit full circle in terms of being a platform provider. So, if you started your career as building mobile apps, that meant you were dealing with the often frustrating process of going through app review. So now you’re in the position of reviewing people’s extensions, and I think the way I understand it is you can run your own local extensions as much as you want, that doesn’t need to go through a review, but if you want to put it in your store to make it really easy to share with other people, now you have to, yeah, review that pull request, right? 00:46:35 - Speaker 1: Yes, that’s correct. So you can start developing and use the extensions happily yourself. But then when we share it, we want to make sure that other people have a really good experience. And the motivation from that actually came from a different angle that Mark mentioned. We want to blur the lines, what is built in, and what is third party contributed to Ray cost. And for that, we really want to make sure that every extension is as high quality as possible and follow certain guidelines to make this seamless experience. So the only way we really thought about it is one, we need to have a good API that restricts so much that you can’t really break too much out of the system. But you also need to have a little bit of a refill to make sure that the UI pattern are followed properly. So that led us to making refills, um, which on iOS and went through Apple refills can be sometimes a little bit frustrating, especially if you work on something which pushes the boundaries here and there a little bit. So what we decided to do is being very transparent about that. So we thought about a lot how we do refills and we work with developers directly, right? It’s not that there’s like some marketing department in between. We work really directly with developers together. So when we think about development, there is one review process that all of us know, and it’s the pull request review process, right? We do that every day in our companies. So we thought like, why not do the same. So for our platform, we decided having one big repository where all the extensions are in. And if you want to put an extension into the store, you just open a pull request with your extension, and then as soon as it’s merged, it’s getting pushed in our store, and then other people can install it right from Rayo. So that it’s I think a really good transparency because on the pull request, we discussed with the answer or, hey, how about you do this, give a few hints here, help them, which maybe making the code here and there a little bit better, and then it gets merged. And so far we haven’t had any pushback here because it is so transparent. I think that makes it just A no brainer for a developer, right? You just open a request and not really questions asked. There is one downside to it that we experience nowadays. Like, we have, I think, more than 600 extensions by now in the repository, but this becomes quite a big repository. So the collaboration is a little bit harder. But on the flip side, if you now build the new extension, you have 600 other extensions to look at how you do something. So it’s a huge source of inspiration. It’s a huge sort of templates, essentially, because a lot of the commands are similar. So you can copy other things, or you can also contribute to it, right? That’s also very often happening right now, where people use an extension and think, Hey, actually, I would like to have this functionality, and then they can just go to the source code, modify it, spin out a pull request, and then the author can look over it, and then we can merge it together. 00:49:34 - Speaker 2: I like that a lot, and maybe it also works well because the scale you’re at, or the fact that you are sort of, these are largely kind of developer or developer-ish people, certainly power users who have some level of programming capability solving their own problems and wanting to share that with others, so maybe it doesn’t quite have the huge scale problem the iOS app store does. Now, have you been in a position where you’ve needed to, I don’t know, reject something or reject isn’t quite the right word, I guess, say we’re not ready to accept this because you’re not complying with these things are maybe almost more subjective, you could say obviously flat out like it breaks or it’s, you know, abusive or. Tries to do something nefarious with the system. I think that’s an obvious case. But if it’s something that’s a little bit more of a judgment call, this doesn’t quite comply with RUI and as you said, someone thinks, well, yeah, but I’m pushing the boundaries in an interesting way. Essentially, you disagree and it becomes contentious. Has that happened yet? And if so, have you found a good way to sort it out. 00:50:30 - Speaker 1: Thankfully, not that often. We had a few situations where there were a few discussions, but then you usually find a way to compromise on a few angles from all sides and then we push this thing through. Also, oftentimes you’re very proactive and just help people. Hey, this is how you could do it. Here are examples. Maybe sometimes we even push to the same branch, um, and help them modifying it in the right direction, because it’s also sometimes we aware of that people oftentime build those extensions in their free time, and we want to also make sure to respect that. But so far we’ve been lucky. Like, we didn’t have that many outliers there. And I think it’s interesting when you work with developers together. It’s obviously a specific audience, right? I know they handcraft very well, but they also like usually in our community, very friendly and very collaborative. And at the end of the day, everybody wants to build something which purposes other people as well. And I think now that we have this big amount of extensions. It probably became a little bit easier for us because there are so many examples that you can just follow. So it became more of like, hey, there is a standard you should follow. And if you’re a Ray cost user, you see basically what is a good extension UI. So you experience it yourself. So when you didn’t build it, you’re just following the same patterns. Initially, we had to form that, right? The first step, we had to form it ourselves and then we had it to bring to the community. And then, Nowadays, I think that’s easier because we just having more people in the community, helping with that as well, and having other people who build at the 3rd or 4th extension, and I just now already know what is a good extension. And we also wrote a little bit of guidelines around that. But, well, documentation is sometimes not that everybody reads it, right, as we all know, but at least we have a reference to point people to words, and then when they read it once, they know it for the next time. 00:52:25 - Speaker 2: Yeah, I can see how the element of, let’s collaborate on making this extension you’ve made fit into our ecosystem in a way that meets our standards or will be good for everybody, that that will feel quite different from the distant reviewer who only has 10 seconds to look at your thing and issue some kind of judgment that often is even hard to understand what they’re complaining about and, you know, gestures vaguely at a rule. From this long set of guidelines that you feel like maybe doesn’t even apply. And again, that’s partially a scale thing, but I do think that that’s certainly very powerful, being able to come back and suggest a modification in the branch of like, well, actually, you know, you do it this way, and then it’s like we’re building it together, even though, you know, they’re basically doing most of the work, but you’re working together to make this thing. 00:53:14 - Speaker 1: Yeah, we’re relying there basically on open source, right? And because it’s also open source, I think also people. I want to be presented that well and also this way collaborative. I think that’s also benefit of that and just the transparency with those modes are just much higher and nicer for everybody who is involved. 00:53:36 - Speaker 2: So as we’ve mapped out this transition over the history of computing, right, going from the terminal command line, which itself, I think was a step forward from the punch cards, the very long feedback loop, and the terminal is something that evolves into something that feels like having a conversation with the computer, going to the GUI, which obviously has its pros and cons, and then perhaps some of the merging of those two together and launchers and command pallets and so forth. Something that certainly comes to mind for me is audio interfaces, which are maybe less of a hot thing right at this moment than they were a couple years ago, but I do feel like Siri and Amazon’s Alexa are something that could potentially fit into this story, right? We talked about how terminals like having a conversation with a computer, while these voice interfaces are actually having a conversation with the computer. How do you see those as fitting into the story, or is that different because natural language is just fundamentally kind of a different branch in the user interface history of computing. 00:54:38 - Speaker 1: Yeah, I think, as you mentioned, they became quite prominent over the last couple of years on various devices, where they were the standalone devices like the Amazon Echo, but then you also have things like Siri building to iOS initially, and nowadays also on the Mac. It’s certainly a new way to interact with your computer via voice, which is interesting, but it’s also, I think, very challenging. I think they come from a similar pattern, especially when we look back to the terminal, right? As you say, you really have a conversation. There might be a little bit more forgiving in a way that you don’t need to specify directly a command. You can rather talk about prompts or intents, like, oh, I want to buy something or tell me something about this. That is, I think, a big step forward to make it more forgiving. The hard part about it is that I see is the feedback loop that you have. So, You say something, but you don’t really know exactly what you’re getting back. And it’s very hard to learn that, where you’re then falling back properly into certain patterns and try to figure out how you really need to communicate with the computer that they understand you, which I think is the tricky bit, which almost reminds me a bit of the terminal where you also need to figure out how to talk to this computer. Because there is not that much help. We now have things like autocompletion there, but it’s still like a little bit bumpy to use a terminal. I think similar is on an audio, versus when I compare it to launches and command pallets, you have a really quick feedback loop because you enter something, you get suggestions that you’re essentially filtering down to what you’re looking for, and then you execute that. So it’s very, well, predictable, as you mentioned before. But it’s also very intuitive, whereas the audio is much more abstract and you don’t really have a good grasp on what the computer can do for you, how does that recognize what you’re saying, which I think is the main downside of it. On the flip side, you use cadence for it. I think things in the car, where you basically have your hands and your concentration on something else. I think the input mechanism of voice is just super interesting for those kinds of things. But I find it hard to believe that this is how we’re gonna work if professionally with computers because it’s so different to what we used to, but I might be a little bit old school here. 00:57:02 - Speaker 3: Yeah, this is a very interesting prompt. So I’ll be honest that I was not, and I’m not a fan of the original black box audio interfaces, so Siri and Amazon Echo, and it was for two reasons. One is they were totally black boxed and cloud connected and I felt like you were just putting an always on microphone in your home, which was always extremely suspicious to me, but also, They were black box in the sense of you kind of didn’t know what they could do or what they were thinking, but now I’m thinking back to our big grid, and it would be amazing if we made audio, just one more column, like keyboard shortcuts and command palace, and if you had the same level of agency and visibility. So imagine if you opened up Your launcher app, and you started saying things, and it started narrowing down the commands and highlighting more brightly those that sounded closer to what you were actually talking about. That would be a great way to get feedback and to be able to understand the full palette of options, if you will, for the command interface. And now going back to our discussion about performance, it’s interesting to think a little bit theoretically about the speed, if you will, of these different input methods. So typing is quite fast because it’s very precise as well as having a high number of hits per second. Each key you hit is, I don’t know, it’s probably a couple bytes, and you can do a lot in quick succession. And voice, if you think about where it might be most useful, it’s probably cases where you have a relatively high number of bits to input, and you can have a relatively high degree of confidence that you’re gonna get the right answer, because as you were alluding to before, the feedback and follow up is a bit of a mess