Family of text editors
POPULARITY
25 episodes with Emacs
10 episodes with Emacs
9 episodes with Emacs
20 episodes with Emacs
6 episodes with Emacs
8 episodes with Emacs
11 episodes with Emacs
4 episodes with Emacs
4 episodes with Emacs
3 episodes with Emacs
8 episodes with Emacs
5 episodes with Emacs
3 episodes with Emacs
4 episodes with Emacs
3 episodes with Emacs
6 episodes with Emacs
3 episodes with Emacs
2 episodes with Emacs
4 episodes with Emacs
2 episodes with Emacs
2 episodes with Emacs
6 episodes with Emacs
2 episodes with Emacs
8 episodes with Emacs
2 episodes with Emacs
2 episodes with Emacs
2 episodes with Emacs
We spent the week learning keybindings, installing dependencies, and cramming for bonus points. Today, we score up and see how we did in the TUI Challenge.Sponsored By:Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices! 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:
Our terminal apps are loaded, the goals are set, but we're already hitting a few snags. The TUI Challenge begins...Sponsored By:Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices! 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:
This week, we discuss Zenoss finally getting acquired, Databricks buying Neon, and the debut of WizOS. Plus, updates on OpenAI, Google, Apple—and hot takes on Marmite, Vegemite, and Emacs. Watch the YouTube Live Recording of Episode (https://www.youtube.com/live/gtm8WopIaOM?si=NsjyGL8As3sTLg7P) 519 (https://www.youtube.com/live/gtm8WopIaOM?si=NsjyGL8As3sTLg7P) Runner-up Titles Vegemite is still bad You're probably eating it It's a bold statement This episode's all about us Pendantic is my jam They tell you they're making “calculated bets” Rupert SlackGPT No one knows anything, do everything Rundown Marmite Rice Cakes (https://groceries.morrisons.com/products/marmite-rice-cakes/109658607) M&A Virtana Acquires Zenoss to Deliver the Industry's Deepest and Broadest Observability Platform (https://www.virtana.com/press-release/virtana-acquires-zenoss-to-deliver-the-industrys-deepest-and-broadest-observability-platform/) Databricks Agrees to Acquire Neon to Deliver Serverless Postgres for Developers + AI Agents - Databricks (https://www.databricks.com/company/newsroom/press-releases/databricks-agrees-acquire-neon-help-developers-deliver-ai-systems) Introducing WizOS: Securing Wiz from the ground up with hardened, near-zero-CVE container base images. (https://www.wiz.io/blog/introducing-wizos-hardened-near-zero-cve-base-images) Checking on OpenAI Evolving OpenAI's structure (https://openai.com/index/evolving-our-structure/) OpenAI caves to pressure, keeps nonprofit in charge (https://www.theregister.com/2025/05/05/openai_keep_nonprofit_in_charge/) OpenAI Hires Instacart C.E.O. to Run Business and Operations (https://www.nytimes.com/2025/05/08/technology/openai-fidji-simo.html) OpenAI Reaches Agreement to Buy Startup Windsurf for $3 Billion (https://www.bloomberg.com/news/articles/2025-05-06/openai-reaches-agreement-to-buy-startup-windsurf-for-3-billion) Anysphere, which makes Cursor, has reportedly raised $900M at $9B valuation (https://techcrunch.com/2025/05/04/cursor-is-reportedly-raising-funds-at-9-billion-valuation-from-thrive-a16z-and-accel/) Checking in on Google Google Search traffic decline is inevitable, execs say (https://searchengineland.com/google-search-traffic-decline-inevitable-455345) Google tests replacing 'I'm Feeling Lucky' with 'AI Mode' (https://techcrunch.com/2025/05/13/google-tests-replacing-im-feeling-lucky-with-ai-mode/) Checking on Apple Apple To Appeal Judge's Scathing New Ruling In Epic Games Antitrust Case, Says CEO Tim Cook (https://deadline.com/2025/05/apple-to-appeal-ruling-in-epic-games-fortnite-antitrust-case-1236383340/) Eddy Cue is fighting to save Apple's $20 billion paycheck from Google (https://www.theverge.com/policy/662974/google-search-remedies-trial-eddy-cue-apple-deal-ai) PayPal Brings Contactless Payments to German iPhones Under New EU Rule (https://www.macrumors.com/2025/05/13/paypal-contactless-payments-germany/) emacs — Matt Gemmell (https://mattgemmell.scot/emacs/) Relevant to your Interests New Netflix UI (https://about.netflix.com/en/news/unveiling-our-innovative-new-tv-experience) VMware perpetual license holders receive cease-and-desist letters from Broadcom (https://arstechnica.com/gadgets/2025/05/broadcom-sends-cease-and-desist-letters-to-subscription-less-vmware-users/) The EC2 Pricing Form is 284 MB JSON File? (https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/ap-southeast-2/index.json) Has DOGE missed its opportunity? (https://www.nextgov.com/ideas/2025/05/has-doge-missed-its-opportunity/405125/) Thanks to DOGE, Gumroad's founder has a second job with the VA (https://www.fastcompany.com/91330297/doge-sahil-lavignia-gumroad) Microsoft employees are banned from using DeepSeek app, president says (https://techcrunch.com/2025/05/08/microsoft-employees-are-banned-from-using-deepseek-app-president-says/) AI Is Like a Crappy Consultant (https://lukekanies.com/writing/ai-is-like-a-crappy-consultant/) You can now submit your claims for Apple's $95 million Siri spying settlement (https://www.theverge.com/news/663166/apple-siri-audio-recording-lawsuit-payout-applications) Microsoft laying off about 6,000 people, or 3% of its workforce (https://www.cnbc.com/2025/05/13/microsoft-is-cutting-3percent-of-workers-across-the-software-company.html) The Case for Open AI Tooling: Why Developers Need Sovereignty in the AI Era (https://thenewstack.io/the-case-for-open-ai-tooling-why-developers-need-sovereignty-in-the-ai-era/) DeepSeek's ‘Tech Madman' Founder Is Threatening US Dominance in AI Race (https://www.bloomberg.com/news/features/2025-05-13/deepseek-races-after-chatgpt-as-china-s-ai-industry-soars) Microsoft laying off about 6,000 people, or 3% of its workforce (https://www.cnbc.com/2025/05/13/microsoft-is-cutting-3percent-of-workers-across-the-software-company.html) GM unveils new 'groundbreaking' EV battery tech, aims to be first to market (https://www.cnbc.com/2025/05/13/gm-new-ev-battery-tech.html) Exclusive: Slate Auto has already racked up more than 100,000 refundable reservations (https://techcrunch.com/2025/05/12/slate-auto-crosses-100000-refundable-reservations-in-two-weeks) Nonsense Meet Vulcan, the first Amazon robot with a sense of touch (https://www.cnbc.com/video/2025/05/07/meet-vulcan-the-first-amazon-robot-with-a-sense-of-touch.html) Fyre Festival's embattled founder is selling the brand: 'It's time to pass the torch' (https://www.npr.org/2025/04/24/nx-s1-5374909/fyre-festival-for-salrl-billy-mcfarland) Conferences NDC Oslo (https://ndcoslo.com/), May 21st-23th, Coté speaking. POST/CON 25 (https://postcon.postman.com/2025/), June 3-4, Los Angeles, CA, Brandon representing SDT. Register here for free pass (https://fnf.dev/43irTu1) using code BRANDON (https://fnf.dev/43irTu1) (limited to first 20 People) Contract-Driven Development: Unite Your Teams and Accelerate Delivery (https://postcon.postman.com/2025/session/3022520/contract-driven-development-unite-your-teams-and-accelerate-delivery%20%20%20%20%20%208:33) by Chris Chandler SREDay Cologne, June 12th, 2025 (https://sreday.com/2025-cologne-q2/#tickets) - Coté speaking, discount: CLG10, 10% off. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Sinners (https://www.rottentomatoes.com/m/sinners_2025) Matt: Devs (https://www.imdb.com/title/tt8134186/) — first recommended by Brandon on episode 223 (https://www.softwaredefinedtalk.com/223) Photo Credits Header (https://unsplash.com/s/photos/Vegemite?license=free&orientation=landscape)
The cover was for "The Org Mode Reference Manual" for Emacs. But what was inside... was something very different! More from The Lunduke Journal: https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe
Varun Mohan is the co-founder and CEO of Windsurf (formerly Codeium), an AI-powered development environment (IDE) that has been used by over 1 million developers in just four months and has quickly emerged as a leader in transforming how developers build software. Prior to finding success with Windsurf, the company pivoted twice—first from GPU virtualization infrastructure to an IDE plugin, and then to their own standalone IDE.In this conversation, you'll learn:1. Why Windsurf walked away from a profitable GPU infrastructure business and bet the company on helping engineers code2. The surprising UI discovery that tripled adoption rates overnight.3. The secret behind Windsurf's B2B enterprise plan, and why they invested early in an 80-person sales team despite conventional startup wisdom.4. How non-technical staff at Windsurf built their own custom tools instead of purchasing SaaS products, saving them over $500k in software costs5. Why Varun believes 90% of code will be AI-generated, but engineering jobs will actually increase6. How training on millions of incomplete code samples gives Windsurf an edge, and creates a moat long-term7. Why agency is the most undervalued and important skill in the AI era—Brought to you by:• Brex—The banking solution for startups• Productboard—Make products that matter• Coda—The all-in-one collaborative workspace—Where to find Varun Mohan:• X: https://x.com/_mohansolo• LinkedIn: https://www.linkedin.com/in/varunkmohan/—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) Varun's background(03:57) Building and scaling Windsurf(12:58) Windsurf: The new purpose-built IDE to harness magic(17:11) The future of engineering and AI(21:30) Skills worth investing in(23:07) Hiring philosophy and company culture(35:22) Sales strategy and market position(39:37) JetBrains vs. VS Code: extensibility and enterprise adoption(41:20) Live demo: building an Airbnb for dogs with Windsurf(42:46) Tips for using Windsurf effectively(46:38) AI's role in code modification and review(48:56) Empowering non-developers to build custom software(54:03) Training Windsurf(01:00:43) Windsurf's unique team structure and product strategy(01:06:40) The importance of continuous innovation(01:08:57) Final thoughts and advice for aspiring developers—Referenced:• Windsurf: https://windsurf.com/• VS Code: https://code.visualstudio.com/• JetBrains: https://www.jetbrains.com/• Eclipse: https://eclipseide.org/• Visual Studio: https://visualstudio.microsoft.com/• Vim: https://www.vim.org/• Emacs: https://www.gnu.org/software/emacs/• Lessons from a two-time unicorn builder, 50-time startup advisor, and 20-time company board member | Uri Levine (co-founder of Waze): https://www.lennysnewsletter.com/p/lessons-from-uri-levine• IntelliJ: https://www.jetbrains.com/idea/• Julia: https://julialang.org/• Parallel computing: https://en.wikipedia.org/wiki/Parallel_computing• Douglas Chen on LinkedIn: https://www.linkedin.com/in/douglaspchen/• Carlos Delatorre on LinkedIn: https://www.linkedin.com/in/cadelatorre/• MongoDB: https://www.mongodb.com/• Cursor: https://www.cursor.com/• GitHub Copilot: https://github.com/features/copilot• Llama: https://www.llama.com/• Mistral: https://mistral.ai/• Building Lovable: $10M ARR in 60 days with 15 people | Anton Osika (CEO and co-founder): https://www.lennysnewsletter.com/p/building-lovable-anton-osika• Inside Bolt: From near-death to ~$40m ARR in 5 months—one of the fastest-growing products in history | Eric Simons (founder & CEO of StackBlitz): https://www.lennysnewsletter.com/p/inside-bolt-eric-simons• Behind the product: Replit | Amjad Masad (co-founder and CEO): https://www.lennysnewsletter.com/p/behind-the-product-replit-amjad-masad• React: https://react.dev/• Sonnet: https://www.anthropic.com/claude/sonnet• OpenAI: https://openai.com/• FedRamp: https://www.fedramp.gov/• Dario Amodei on LinkedIn: https://www.linkedin.com/in/dario-amodei-3934934/• Amdahl's law: https://en.wikipedia.org/wiki/Amdahl%27s_law• How to win in the AI era: Ship a feature every week, embrace technical debt, ruthlessly cut scope, and create magic your competitors can't copy | Gaurav Misra (CEO and co-founder of Captions): https://www.lennysnewsletter.com/p/how-to-win-in-the-ai-era-gaurav-misra—Recommended book:• Fall in Love with the Problem, Not the Solution: A Handbook for Entrepreneurs: https://www.amazon.com/Fall-Love-Problem-Solution-Entrepreneurs/dp/1637741987—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
【PR】オムロンエキスパートエンジニアリング株式会社▼採用ページはこちらhttps://bit.ly/3PS6kJd▼社員インタビュー記事はこちらhttps://bit.ly/4gi1csA▼実際にエンジニアとして働く3人の座談会動画はこちらhttps://bit.ly/3PTkrOpテキストエディタ戦争について語ります。「商売道具のこだわりから戦争が起きる」「オジサンで分かるvimとEmacs」「戦争の暫定勝者と最近の潮流」など。【目次】00:00【PR】オムロンエキスパートエンジニアリング株式会社2:49 技術界隈の最大の争い6:02 プログラマーの商売道具って？7:29 白熱の商売道具トーク14:54 テキストエディタって何？17:42 テキストエディタにあるもの・ないもの20:16 メモはメモ用のアプリに20:49 これがvimとEmacsだ！24:15 この見た目には理由がある25:42 オジサンで分かるvimとEmacs28:00 テキストエディタを触ってみよう！36:37 vim vs Emacs43:34 エディタ戦争には他の国も参加していた51:25 デフォルトで使えちゃうvim53:05 新興勢力「Cursor」が現れた56:46 こだわりの商売道具話を募集！【参考文献】◯なぜEmacsはviにエディタ戦争で勝利を収めたのかhttps://qiita.com/dairappa/items/448ac8bf83fe606bc317◯BLUE GIANThttps://amzn.to/41M2d79【サポーターコミュニティへの加入はこちらから！】https://yurugengo.com/support【親チャンネル：ゆる言語学ラジオ】https://www.youtube.com/@yurugengo【実店舗プロジェクト：ゆる学徒カフェ】https://www.youtube.com/@yurugakuto【おたよりフォーム】https://forms.gle/BLEZpLcdEPmoZTH4A※皆様からの楽しいおたよりをお待ちしています！【お仕事依頼はこちら！】info@pedantic.jp【堀元見プロフィール】慶應義塾大学理工学部卒。専門は情報工学。WEBにコンテンツを作り散らかすことで生計を立てている。現在の主な収入源は「アカデミックに人の悪口を書くnote有料マガジン」。Twitter→https://twitter.com/kenhori2noteマガジン→https://note.com/kenhori2/m/m125fc4524aca個人YouTube→https://www.youtube.com/@kenHorimoto【水野太貴プロフィール】名古屋大学文学部卒。専門は言語学。某大手出版社で編集者として勤務。言語学の知識が本業に活きてるかと思いきや、そうでもない。Twitter→https://twitter.com/yuru_mizuno
This week we dig into what it takes to get started and involved in Open Source. You can do it in your community, in your city, or in your area. If nothing like that exists in your area, join us at one of the upcoming community conferences! -- During The Show -- 00:51 Polar Vortex Polar vortex collapse Audio bookshelf python code 03:02 Steve's Immich Journey - Stephen Storage templates (https://immich.app/docs/administration/storage-template/) Asset types and storage locations (https://immich.app/docs/administration/storage-template/) Makes sense from programming perspective Not knowing what to look for 10:38 Cheap Card for AI - Joshua Driver issues Quadro performs a little better Stay away from Tesla cards RAM and CUDA cores Stay away from Intel and AMD 16:10 Seafile help? - Tyler Context path Help available in Geeklab 20:25 Church A/V - Emmanuel RJ6 Quad Shielded Cable RESI (https://resi.io/) OBS and Owncast (https://owncast.online/) NDI Camera Aida Camera (https://www.bhphotovideo.com/c/product/1697374-REG/aida_imaging_hd_ndi_cube_full_hd_ndihx.html) Scarlett2i2 Knock Off (https://www.amazon.com/Interface-Recording-Podcasting-Noise-Free-Wrugste/dp/B0DPHSDLG7) 25:38 News Wire Fish Shell 4.0 - fishshell.com (https://fishshell.com/blog/new-in-40/) DBeaver 25.0 - dbeaver.io (https://dbeaver.io/2025/03/02/dbeaver-25-0/) Emacs 30.1 - masteringemacs.org (https://www.masteringemacs.org/article/whats-new-in-emacs-301) KDE Plasma 6.3.2 - kde.org (https://kde.org/announcements/plasma/6/6.3.2/) EA Open-Sourced More - theverge.com (https://www.theverge.com/news/621397/command-conquer-open-source-ea-red-alert-renegade-generals) Nextcloud Hub 10 - nextcloud.com (https://nextcloud.com/blog/nextcloud-hub10/) Nvidia Linux 570 Drivers - nvidia.com (https://www.nvidia.com/en-us/drivers/details/241089/) Open-Source Nuclear-Fusion Plans - wsj.com (https://www.wsj.com/articles/german-startup-publishes-open-source-plans-for-nuclear-fusion-power-plant-7b2b6241) Black Duck OSSRA - securitymagazine.com (https://www.securitymagazine.com/articles/101420-open-source-software-vulnerabilities-found-in-86-of-codebases) Auto-Color Malware - thehackernews.com (https://thehackernews.com/2025/02/new-linux-malware-auto-color-grants.html) OpenSSF Initiative - devops.com (https://devops.com/openssf-defines-baseline-for-securing-open-source-software/) WhisperCat 1.4 - github.com (https://github.com/ddxy/whispercat/releases/tag/v1.4.1) Wan 2.1 - reuters.com (https://www.reuters.com/technology/artificial-intelligence/alibaba-release-open-source-version-video-generating-ai-model-2025-02-25/) 27:52 Getting Involved in Community Steve and resumes Be prepared to talk about what you say you know Better to say "I don't know" than lie or fake it A wall of text does not help Bold important things Demonstrate your skills Blog Code repository Website Be willing to make compromises Don't chase a position Get involved with a local group Non-Profits Church Linux Group Business Group Lead with Generosity Jab Jab Jab Right Hook Be prepared to "un-sexy work" -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/430) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed)
Take the survey here: https://forms.gle/GMQggRfj99v18VicADo Trump voters prefer EMacs or Vi? Who is happier with their life... people who use Tabs or Spaces? Who is more likely to support censorship... Rust Programmers or C Programmers? You know you want to know. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe
This week, we cover the Sonos executive shake-up, AWS CEO Matt Garman's take on AI, and check in on OpenTofu's growth. Plus, some thoughts on broken windows and Emacs no longer being preinstalled on macOS. Watch the YouTube Live Recording of Episode 502 (https://www.youtube.com/watch?v=flerIIV5OW8) Runner-up Titles Anecdote Investigations. The Software Defined Elves are gonna send you a RØDECaster. Well, maybe we should talk about emacs more! I still have a box of cables Buy One, Pay for One If it's fine, it's fine Rundown Sonos' interim CEO hits all the right notes in first letter to employees (https://www.theverge.com/2025/1/13/24342354/sonos-interim-ceo-tom-conrad-employee-letter) Breaking: Sonos CEO Patrick Spence steps down after disastrous app launch (https://www.theverge.com/2025/1/13/24342179/sonos-ceo-patrick-spence-resignation-reason-app) Sonos Chief Product Officer to Leave; Interim CEO to Take Role (https://www.bloomberg.com/news/articles/2025-01-14/sonos-chief-product-officer-to-leave-interim-ceo-to-take-role?utm_medium=email&utm_source=author_alert&utm_term=250114&utm_campaign=author_19842959) AI's payoff will be massive, says AWS CEO Matt Garman (https://www.theverge.com/24338171/aws-ceo-matt-garman-ai-chips-anthropic-cloud-computing-trainium-decoder-podcast-interview) OpenTofu Turns One With OpenTofu 1.9.0 (https://thenewstack.io/opentofu-turns-one-with-opentofu-1-9-0/) macOS No Longer Ships with Emacs (https://batsov.com/articles/2025/01/12/macos-no-longer-ships-with-emacs/) Relevant to your Interests The 8 worst technology failures of 2024 (https://www.technologyreview.com/2024/12/17/1108883/the-8-worst-technology-failures-of-2024/) 41% of companies worldwide plan to reduce workforces by 2030 due to AI | CNN Business (https://www.cnn.com/2025/01/08/business/ai-job-losses-by-2030-intl/index.html) How I Replaced Notion with Reminders, Numbers, and Notes (https://archive.ph/2024.11.16-053045/https://medium.com/westenberg/how-i-replaced-notion-with-reminders-numbers-and-notes-38282543b29b) Automattic cuts WordPress contribution hours, blames WP Engine (https://www.theverge.com/2025/1/10/24340717/automattic-wordpress-contribution-hours-cut-wp-engine) How Fidelity's “chaos buffet” pushed AWS to new Lambda tools (https://www.thestack.technology/fidelity-chaos-buffet-aws-lambda-fis/) Zuckerberg on Rogan: Facebook's censorship was "something out of 1984" (https://www.axios.com/2025/01/10/mark-zuckerberg-joe-rogan-facebook-censorship-biden) Meta Reorientates Itself Around ‘Masculine Energy' – Pixel Envy (https://pxlnv.com/linklog/meta-masculine-energy/) #6907 Kong-ingress-controller 3.4 has high CPU usage when running 2 pods (https://github.com/Kong/kubernetes-ingress-controller/issues/6907) Survey: AI Tools are Increasing Amount of Bad Code Needing to be Fixed (https://devops.com/survey-ai-tools-are-increasing-amount-of-bad-code-needing-to-be-fixed/) Exclusive | Hanging Out at Starbucks? You Now Need to Order Something (https://www.wsj.com/business/hospitality/starbucks-new-cafe-policy-dining-room-e9ab07bf) A new AI-powered security tool is promising to reinvent how companies secure login credentials (https://www.axios.com/2025/01/14/ai-cybersecurity-startup-intel-funding?utm_term=emshare) Anexia moves 12,000 VMs off VMware to homebrew KVM platform (https://www.theregister.com/2025/01/13/anexia_vmware_to_kvm_migration/) Mullenweg's Grip On WordPress Challenged In New Court Filing (https://www.searchenginejournal.com/mullenwegs-grip-on-wordpress-challenged-in-new-court-filing/537416/) Apple's AI feature just can't get it right (https://www.mindstream.news/p/apple-s-ai-feature-just-can-t-get-it-right) Texas Sues Allstate Over Its Collection of Driver Data (https://www.nytimes.com/2025/01/13/technology/texas-allstate-driver-data-lawsuit.html) Mastodon's CEO and creator is handing control to a new nonprofit organization (https://www.theverge.com/2025/1/13/24342603/mastodon-non-profit-ownership-ceo-eugen-rochko) Nonsense DirecTV to offer 'MySports,' a smaller streaming package of 40 channels (https://www.nytimes.com/athletic/6059981/2025/01/14/directv-mysports-small-channel-package/?source=freedailyemail&campaign=601983&userId=56655) Drake Sues His Label, Calling Kendrick Lamar's ‘Not Like Us' Defamatory (https://www.nytimes.com/2025/01/15/arts/music/drake-kendrick-lamar-lawsuit-not-like-us.html) Hanging Out at Starbucks? You Now Need to Order Something (https://www.wsj.com/business/hospitality/starbucks-new-cafe-policy-dining-room-e9ab07bf) Listener Feedback Capture AI's Low-Hanging Fruit with Agents (https://bweagle.medium.com/capture-ais-low-hanging-fruit-with-agents-904b00eb6860) The Ethics of Using AI Tools at Work (https://www.thecloudcast.net/2025/01/the-ethics-of-using-ai-tools-at-work.html) ****## Conferences CfgMgmtCamp (https://cfgmgmtcamp.org/ghent2025/), February 2-5, 2025. Civo Navigate North America (https://www.civo.com/navigate/north-america), San Francisco, Feb 10-11, 2025 DevOpsDayLA (https://www.socallinuxexpo.org/scale/22x/events/devopsday-la) at SCALE22x (https://www.socallinuxexpo.org/scale/22x), March 6-9, 2025, discount code DEVOP SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Capital One Café (https://www.capitalone.com/local/) Matt: The WELL: Bruce Sterling and Jon Lebkowsky: State of the World 2025 (https://people.well.com/conf/inkwell.vue/topics/551/Bruce-Sterling-and-Jon-Lebkowsky-page01.html) Tasmania Parks and Wildlife Service logo (https://3capesgearandgourmet.com.au/wp-content/uploads/2020/09/Parks-Tasmania.gif) Coté: Splatoon (https://splatoon.nintendo.com/) Photo Credits Header (https://unsplash.com/photos/a-room-with-broken-windows-XNiNhOjgezE) Artwork (https://unsplash.com/photos/a-room-with-broken-windows-XNiNhOjgezE)
This show has been flagged as Explicit by the host. table td.shrink { white-space:nowrap } hr.thin { border: 0; height: 0; border-top: 1px solid rgba(0, 0, 0, 0.1); border-bottom: 1px solid rgba(255, 255, 255, 0.3); } New hosts Welcome to our new hosts: Paulj, Jon The Nice Guy. Last Month's Shows Id Day Date Title Host 4261 Mon 2024-12-02 HPR Community News for November 2024 HPR Volunteers 4262 Tue 2024-12-03 DIY C02 operat0r 4263 Wed 2024-12-04 An interview with Adam Matthews about the Disco Pigeon Ken Fallon 4264 Thu 2024-12-05 Mintcast, high crimes and misdemeanors. Some Guy On The Internet 4265 Fri 2024-12-06 Drivecasting: arm sleeves, glasses and more. Some Guy On The Internet 4266 Mon 2024-12-09 What's the weather? Lee 4267 Tue 2024-12-10 Borderlands Movie Review Kevie 4268 Wed 2024-12-11 Book review and an Emacs rabbit-hole enistello 4269 Thu 2024-12-12 What is on My Podcast Player 2024, Part 2 Ahuka 4270 Fri 2024-12-13 Playing Civilization IV, Part 4 Ahuka 4271 Mon 2024-12-16 Beginners guide to Proxmox Al 4272 Tue 2024-12-17 Embed Mastodon Threads hairylarry 4273 Wed 2024-12-18 Improving videography with basic manual settings Trixter 4274 Thu 2024-12-19 The Wreck - I'm alright! Archer72 4275 Fri 2024-12-20 What is on My Podcast Player 2024, Part 3 Ahuka 4276 Mon 2024-12-23 PWNED operat0r 4277 Tue 2024-12-24 Introduction episode by Paul Paulj 4278 Wed 2024-12-25 Pi powered Christmas Tree Kevie 4279 Thu 2024-12-26 What is on My Podcast Player 2024, Part 4 Ahuka 4280 Fri 2024-12-27 Isaac Asimov: The Foundation Ahuka 4281 Mon 2024-12-30 My ridiculously complicated DHCP setup at home Jon The Nice Guy 4282 Tue 2024-12-31 Backup Power for my Gas Furnace Trey Comments this month These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 26 comments in total. Past shows There are 7 comments on 4 previous shows: hpr3531 (2022-02-14) "Barrier: Software KVM" by Windigo. Comment 3: SolusSpider - Peter Paterson on 2024-12-01: "Fellow user of Barrier, and also InputLeap." hpr4070 (2024-03-08) "Civilization III" by Ahuka. Comment 1: Red Orm on 2025-01-01: "hpr4070 :: Civilization III" Comment 2: Kevin O'Brien on 2025-01-02: "Thank you" hpr4258 (2024-11-27) "Introduction and History of Using Computers" by SolusSpider. Comment 5: Spartan Minter on 2024-12-02: "Linux Mint " Comment 6: ClaudioM on 2024-12-03: "Hey Solusspider! Great First Episode!" hpr4260 (2024-11-29) "The Golden Age" by Ahuka. Comment 1: Moss Bliss on 2025-01-01: "Penguicon" Comment 2: Kevin O'Brien on 2025-01-01: "Sorry to hear it" This month's shows There are 19 comments on 10 of this month's shows: hpr4264 (2024-12-05) "Mintcast, high crimes and misdemeanors." by Some Guy On The Internet. Comment 1: Henrik Hemrin on 2024-12-06: "Thunderbird"Comment 2: Majid on 2024-12-07: "Mintcast and Thunderbird"Comment 3: Dave Morriss on 2024-12-14: "Thunderbird and email management" hpr4266 (2024-12-09) "What's the weather?" by Lee. Comment 1: Lee on 2024-10-21: "Errata" hpr4268 (2024-12-11) "Book review and an Emacs rabbit-hole" by enistello. Comment 1: Henrik Hemrin on 2024-12-15: "Thanks for the book tip" hpr4269 (2024-12-12) "What is on My Podcast Player 2024, Part 2" by Ahuka. Comment 1: Random listener on 2024-12-13: "Request for a bit more info in show notes" hpr4272 (2024-12-17) "Embed Mastodon Threads" by hairylarry. Comment 1: Ken Fallon on 2024-11-28: "Wayne Myers ?? Where did I hear that name before ?"Comment 2: Henrik Hemrin on 2024-12-18: "How is the post behaviour on Mastodon reflected on the web site?"Comment 3: Reto on 2024-12-25: "Plain text is not" hpr4274 (2024-12-19) "The Wreck - I'm alright!" by Archer72. Comment 1: SolusSpider - Peter Paterson on 2024-12-19: "I'm Mark's hospital room stalker!"Comment 2: Paulj on 2024-12-30: "Thanks for Sharing!" hpr4276 (2024-12-23) "PWNED" by operat0r. Comment 1: JonTheNiceGuy on 2024-12-28: "Exposed RDP, at least it wasn't VNC (which I did!), and VPN" hpr4277 (2024-12-24) "Introduction episode by Paul" by Paulj. Comment 1: SolusSpider - Peter Paterson on 2024-12-24: "Welcome Paul to HPR"Comment 2: Trey on 2024-12-24: "Welcome"Comment 3: Paul on 2024-12-25: "Thanks Peter"Comment 4: Paulj on 2024-12-26: "Thanks Trey!" hpr4280 (2024-12-27) "Isaac Asimov: The Foundation" by Ahuka. Comment 1: Red Orm on 2025-01-01: "hpr4280 :: Isaac Asimov: The Foundation"Comment 2: Kevin O'Brien on 2025-01-02: "Thank you" hpr4281 (2024-12-30) "My ridiculously complicated DHCP setup at home" by Jon The Nice Guy. Comment 1: Paulj on 2024-12-30: "Welcome, and thanks!" Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mailing List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://lists.hackerpublicradio.com/pipermail/hpr/2024-December/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Any other business Thanks to all 59 HPR contributors in 2024! Ahuka, Al, Andrew Conway, Archer72, Beeza, Beto, Bob, Brian in Ohio. Cedric De Vroey, Celeste, Claudio Miranda, Clinton Roy, Cov, crvs, Daniel Persson, Dave Hingley. Dave Morriss, Deltaray, dnt, dodddummy, enistello, Fred Black, gemlog, geospart. hairylarry, Henrik Hemrin, hobs, Honkeymagoo, HPR Volunteers, Jeroen Baten, Jon The Nice Guy, Ken Fallon. Kevie, Kinghezy, knightwise, Lee, Lochyboy, mnw, Moss Bliss, Mr. Young. MrX, Ne01sfree, Noodlez, norrist, operat0r, Paulj, Quvmoh, Rho`n. SolusSpider, Some Guy On The Internet, Stache_AF, Swift110, Thaj Sara, thelovebug, thompsgj, Trey. Trixter, Trollercoaster, Windigo. Provide feedback on this episode.
Daisuke Murase さんをゲストに迎えて、レイオフ、MacBook Pro, Bluesky, ゲームなどについて話しました。 Show Notes レイオフされてまじで大変でした - unknownplace.org Show | Hacker News Lobsters Short-term health insurance in Oregon Reeder Openvibe Diablo IV Path of Exile 2 AIが画面を見ながらサポートしてくれるマイクラ実況
This show has been flagged as Clean by the host. https://www.masteringemacs.org/ https://www.gnu.org/software/emacs/ Provide feedback on this episode.
Genervt von dreisten Kleinanzeigen-Nachrichten ("Was letzte Preis, Kusseng holt ab") flüchtet Christian in den Fediverse-Flohmarkt. Moritz taucht in ein tiefes Rabbit-Hole und klärt einmalig die Frage, welcher Texteditor der Beste ist.
Fredrik talks to Evan Czaplicki, creator of Elm about figuring out a good path for yourself. What do you do when you have a job which seems like it would be your dream job, but it turns out to be the wrong thing for you? And how do you escape from that? You can’t put the success of something you build before your own personal and mental health, no matter how right the decision may be for the thing you build. Is there ever a reproducible path? Aren’t most or all successful things in large part a result of their circumstances? Platform languages and productivity languages - which do you prefer? Thoughts on the tradeoffs of when and how to roll things out and when to present ideas. Evan’s development mindset and environment, and the ways it has affected Elm’s design - all the way down to the error messages. Finally, of course, the benefits of country life - out of the radiation of San Francisco. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Evan Elm Prezi Guido van Rossum Brendan Eich Bjarne Stroustrup Hindley–Milner type inference Gary Bernhardt Talks by Gary SIMD Standard ML Ocaml Haskell Lambda calculus Algebraic data types Type inference Virtual DOM Webbhuset Dart Safari’s no performance regressions rule Sublime text GHC Nano Emacs Titles The personal aspects A culture clash I wasn’t supposed to be here This numb feeling I’ve never really been to the real world Is this even real? The path that Guido did This is you This isn’t for me, and it’s your fault Valuing my own health Reckless indifference A dispute between colleagues A nice solution will come out if you’re patient enough Here’s your error message: good luck Farmer’s disposition These are good years Getting paid in chickens for web development Finding a place
You may have heard of a text editor called Emacs, which has been around for a long time. This is your chance to hear how Matt has used it to create a GTD list manager. He talks about how he got into GTD, and goes into plenty of detail about the system he has developed, through many iterations, using Emacs. You can listen to the entire conversation from December 2023 at GTD Connect®. -- This audio is one of many available at GTD Connect, a learning space and community hub for all things GTD. Join GTD practitioners from around the world in learning, sharing, and developing the skills for stress-free productivity. Sign up for a free guest pass Learn about membership options Knowing how to get the right things done is a key to success. It's easy to get distracted and overwhelmed. Stay focused and increase productivity with GTD Connect—a subscription-based online learning center from the David Allen Company. GTD Connect gives you access to a wealth of multimedia content designed to help you stay on track and deepen your awareness of principles you can also learn in GTD courses, coaching, and by reading the Getting Things Done book. You'll also get the support and encouragement of a thriving global community of people you won't find anywhere else. If you already know you'd like to join, click here to choose from monthly or annual options. If you'd like to try GTD Connect free for 14 days, read on for what's included and how to get your free trial. During your 14-day free trial, you will have access to: Recorded webinars with David Allen & the certified coaches and trainers on a wide range of productivity topics GTD Getting Started & Refresher Series to reinforce the fundamentals you may have learned in a GTD course, coaching, or book Extensive audio, video, and document library Slice of GTD Life series to see how others are making GTD stick David Allen's exclusive interviews with people in his network all over the world Lively members-only discussion forums sharing ideas, tips, and tricks Note: GTD Connect is designed to reinforce your learning, and we also recommend that you take a course, get individual coaching, or read the Getting Things Done book. Ready to start your free trial?
Summary Generative AI promises to accelerate the productivity of human collaborators. Currently the primary way of working with these tools is through a conversational prompt, which is often cumbersome and unwieldy. In order to simplify the integration of AI capabilities into developer workflows Tsavo Knott helped create Pieces, a powerful collection of tools that complements the tools that developers already use. In this episode he explains the data collection and preparation process, the collection of model types and sizes that work together to power the experience, and how to incorporate it into your workflow to act as a second brain. Announcements Hello and welcome to the Data Engineering Podcast, the show about modern data management Dagster offers a new approach to building and running data platforms and data pipelines. It is an open-source, cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability, a declarative programming model, and best-in-class testability. Your team can get up and running in minutes thanks to Dagster Cloud, an enterprise-class hosted solution that offers serverless and hybrid deployments, enhanced security, and on-demand ephemeral test deployments. Go to dataengineeringpodcast.com/dagster (https://www.dataengineeringpodcast.com/dagster) today to get started. Your first 30 days are free! Data lakes are notoriously complex. For data engineers who battle to build and scale high quality data workflows on the data lake, Starburst powers petabyte-scale SQL analytics fast, at a fraction of the cost of traditional methods, so that you can meet all your data needs ranging from AI to data applications to complete analytics. Trusted by teams of all sizes, including Comcast and Doordash, Starburst is a data lake analytics platform that delivers the adaptability and flexibility a lakehouse ecosystem promises. And Starburst does all of this on an open architecture with first-class support for Apache Iceberg, Delta Lake and Hudi, so you always maintain ownership of your data. Want to see Starburst in action? Go to dataengineeringpodcast.com/starburst (https://www.dataengineeringpodcast.com/starburst) and get $500 in credits to try Starburst Galaxy today, the easiest and fastest way to get started using Trino. Your host is Tobias Macey and today I'm interviewing Tsavo Knott about Pieces, a personal AI toolkit to improve the efficiency of developers Interview Introduction How did you get involved in machine learning? Can you describe what Pieces is and the story behind it? The past few months have seen an endless series of personalized AI tools launched. What are the features and focus of Pieces that might encourage someone to use it over the alternatives? model selections architecture of Pieces application local vs. hybrid vs. online models model update/delivery process data preparation/serving for models in context of Pieces app application of AI to developer workflows types of workflows that people are building with pieces What are the most interesting, innovative, or unexpected ways that you have seen Pieces used? What are the most interesting, unexpected, or challenging lessons that you have learned while working on Pieces? When is Pieces the wrong choice? What do you have planned for the future of Pieces? Contact Info LinkedIn (https://www.linkedin.com/in/tsavoknott/) Parting Question From your perspective, what is the biggest barrier to adoption of machine learning today? Closing Announcements Thank you for listening! Don't forget to check out our other shows. Podcast.__init__ (https://www.pythonpodcast.com) covers the Python language, its community, and the innovative ways it is being used. The Machine Learning Podcast (https://www.themachinelearningpodcast.com) helps you go from idea to production with machine learning. Visit the site (https://www.dataengineeringpodcast.com) to subscribe to the show, sign up for the mailing list, and read the show notes. If you've learned something or tried out a project from the show then tell us about it! Email hosts@dataengineeringpodcast.com (mailto:hosts@dataengineeringpodcast.com)) with your story. Links Pieces (https://pieces.app/) NPU == Neural Processing Unit (https://en.wikipedia.org/wiki/AI_accelerator) Tensor Chip (https://en.wikipedia.org/wiki/Google_Tensor) LoRA == Low Rank Adaptation (https://github.com/microsoft/LoRA) Generative Adversarial Networks (https://en.wikipedia.org/wiki/Generative_adversarial_network) Mistral (https://mistral.ai/) Emacs (https://www.gnu.org/software/emacs/) Vim (https://www.vim.org/) NeoVim (https://neovim.io/) Dart (https://dart.dev/) Flutter (https://flutter.dev/) Typescript (https://www.typescriptlang.org/) Lua (https://www.lua.org/) Retrieval Augmented Generation (https://github.blog/2024-04-04-what-is-retrieval-augmented-generation-and-what-does-it-do-for-generative-ai/) ONNX (https://onnx.ai/) LSTM == Long Short-Term Memory (https://en.wikipedia.org/wiki/Long_short-term_memory) LLama 2 (https://llama.meta.com/llama2/) GitHub Copilot (https://github.com/features/copilot) Tabnine (https://www.tabnine.com/) Podcast Episode (https://www.themachinelearningpodcast.com/tabnine-generative-ai-developer-assistant-episode-24) The intro and outro music is from Hitman's Lovesong feat. Paola Graziano (https://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/Tales_Of_A_Dead_Fish/Hitmans_Lovesong/) by The Freak Fandango Orchestra (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/)/CC BY-SA 3.0 (https://creativecommons.org/licenses/by-sa/3.0/)
This is a recap of the top 10 posts on Hacker News on April 15th, 2024.This podcast was generated by wondercraft.ai(00:32): Embezzlers Are Nice People (2017)Original post: https://news.ycombinator.com/item?id=40042616&utm_source=wondercraft_ai(02:18): T-Mobile employees across the country receive cash offers to illegally swap SIMsOriginal post: https://news.ycombinator.com/item?id=40045093&utm_source=wondercraft_ai(04:03): PuTTY vulnerability vuln-p521-biasOriginal post: https://news.ycombinator.com/item?id=40044665&utm_source=wondercraft_ai(05:57): Neon Serverless Postgres is generally availableOriginal post: https://news.ycombinator.com/item?id=40040593&utm_source=wondercraft_ai(07:45): A tiny ultrabright laser that can melt steelOriginal post: https://news.ycombinator.com/item?id=40038251&utm_source=wondercraft_ai(09:54): An FDA approved device offers a new treatment for tinnitusOriginal post: https://news.ycombinator.com/item?id=40041430&utm_source=wondercraft_ai(11:29): We are moving to General AvailabilityOriginal post: https://news.ycombinator.com/item?id=40039191&utm_source=wondercraft_ai(13:12): Tesla to lay off more than 10% of its staffOriginal post: https://news.ycombinator.com/item?id=40038549&utm_source=wondercraft_ai(15:10): Beautifying Org Mode in Emacs (2018)Original post: https://news.ycombinator.com/item?id=40037844&utm_source=wondercraft_ai(17:00): A shrub in Nepal supplies the raw material for the bank notes used in JapanOriginal post: https://news.ycombinator.com/item?id=40037396&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
An audio blog of sorts, where I focus on one thing that’s not directly related to fiction but important for me. This episode I’m covering Zettelkasten. Here are some supporting links: Zettelkasten on Wikipedia Zettelkasten.de FYI I’m using Vim with Vimwiki and Vim-zettel. I’ve also tried Emacs with Org-Roam, but I didn’t care for it…Read more F/log_1: Zettelkasten
What's the best way to roll central authentication? What's the best Google replacement suite? This week Noah and Steve dig into hosting questions, as always your calls go to the front of the line! -- During The Show -- 01:36 PHP, Kanban etc - Joe Nextcloud Deck Our Note Organizer (https://github.com/JoeMrCoffee/OurNoteOrganizer) 03:40 NIX Feedback - Alexander People time rank/prioritize "What problem does it solve" is a framework Effective evangelizing Making something "sticky" No bad questions 13:22 Caller Tony from Toronto Central Authentication? FreeIPA (https://www.freeipa.org/page/Main_Page) Samaba4 Distros Zentyal (https://zentyal.com/) 20:48 Grimnir from Mumble Volumio (https://volumio.com/) Locking it down SSH Samaba Home Assistant (https://www.home-assistant.io/) Adding music Separate Volumio from the PI 25:00 Nextcloud? - Craig Nextcloud (https://nextcloud.com/) is challenging on iOS Head Scale (https://headscale.net/) SpiderOak Immich (https://immich.app/) SeaFile (https://www.seafile.com/en/home/) Encrypt locally, then upload to "cloud" Fastmail (https://www.fastmail.com/) 36:20 Vivaldi & Hosting questions - Ben Hugo (https://gohugo.io/) Altispeed Hosting Vivaldi 41:25 Database Questions - Anton Argument against DIY OpenEMR (https://www.open-emr.org/) Open Source No lock in Form editor CPT/ICD10 codes WikiJS (https://js.wiki/) Weasis (https://weasis.org/en/getting-started/download-dicom-viewer/) 47:26 News Wire OSI Election Results - opensource.org (https://opensource.org/blog/results-of-2024-elections-of-osi-board-of-directors) Red Hat Nova - lore.kernel.org (https://lore.kernel.org/dri-devel/Zfsj0_tb-0-tNrJy@cassiopeiae/) Linux 6.9 RC - lkml.iu.edu (https://lkml.iu.edu/hypermail/linux/kernel/2403.3/00300.html) Regata OS 24 - betanews.com (https://betanews.com/2024/03/19/regata-os-24-arctic-fox-linux/) Wine 9.5 - gitlab.winehq.org (https://gitlab.winehq.org/wine/wine/-/releases/wine-9.5) Kafka UI 1.0 - GitHub (https://github.com/kafbat/kafka-ui) Firefox 124 - Mozilla (https://www.mozilla.org/en-US/firefox/124.0/releasenotes/) Gnome 45.5 - Gnome (https://discourse.gnome.org/t/gnome-45-5-released/20043) Gnome 46 - Gnome (https://release.gnome.org/46/) Emacs 29.3 - Gnu.org (https://lists.gnu.org/archive/html/emacs-devel/2024-03/msg00611.html) Cmake 3.29 - Cmake.org (https://cmake.org/cmake/help/latest/release/3.29.html) OpenVPN - OpenVPN (https://openvpn.net/community-downloads/) SysVInit 3.09 - Phoronix (https://www.phoronix.com/news/SysVinit-3.09) Docker 26 - Docker (https://docs.docker.com/engine/release-notes/26.0/) Lemur Pro - System76 (https://blog.system76.com/post/lemur-pro-ultraportable-laptops) Devika - Market Tech Post (https://www.marktechpost.com/2024/03/25/meet-devika-an-open-source-ai-software-engineer-that-aims-to-be-a-competitive-alternative-to-devin-by-cognition-ai/) GitHub (https://github.com/stitionai/devika) Ubuntu LTS 12 Year Support - How To Geek (https://www.howtogeek.com/ubuntu-linux-legacy-support-program/) 49:05 Shufflecake Shufflecake (https://shufflecake.net/) Linux encryption tool Makes hidden volumes Spiritual successor to TrueCrypt and VeriCrypt GPG encryption -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/382) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed)
Andrew Bosworth—or Boz, as most people know him—is the chief technology officer at Meta and head of Reality Labs, the company's augmented reality/virtual reality (AR/VR) organization, which he created in 2017. Boz joined Facebook in 2006 as their approximately 10th engineer, and in his 18-year tenure he built the original News Feed, Messenger, and Groups, as well as many early anti-abuse and infrastructure systems. At various times he has been the engineering director overseeing Events, Places, Photos, Videos, Timeline, Privacy, and more. Before Reality Labs, he ran the Ads and Business Platform product group, where he led engineering, product, research, analytics, and design, taking annual revenue from $4 billion to $40 billion in five years. Andrew currently leads Meta's efforts in AR, VR, AI, and consumer hardware across Quest, Ray-Ban Meta glasses, and more. In our conversation, we discuss:• Stories from the early days of Facebook• Lessons from Meta's downturn and recent turnaround• Meta's culture of transparency• Boz's thoughts on the Apple Vision Pro• Why communication is the job• Why you should regularly seek help from your manager• Lessons in setting incentives and avoiding their misuse• Why you should optimize for a variety in experience in your career• The importance of trusting your own expertise and not being swayed by external opinions• Stories of failures and personal growth—Brought to you by:• Vanta—Automate compliance. Simplify security.• Eppo—Run reliable, impactful experiments• Explo—Embed customer-facing analytics in your product—Find the full transcript at: https://www.lennyspodcast.com/making-meta-andrew-boz-bosworth-cto/—Where to find Andrew Bosworth:• Facebook: https://www.facebook.com/boz/• Instagram: https://www.instagram.com/boztank/• X: https://twitter.com/boztank• LinkedIn: https://www.linkedin.com/in/andrew-bosworth-8247a01/• Website: https://boz.com/• Photography website: https://wardenshortbow.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) Boz's background(04:48) Fun facts about him(07:20) Early days at Facebook(11:11) Advice for founders(13:22) Leveraging leaders(19:27) Tips for communicating with managers(22:10) Transparency at Meta(27:01) The importance of clear guidelines(29:11) Involvement in the details(33:15) Building the News Feed(37:28) Passion and career growth(40:25) Exploring new opportunities(42:02) The value of variety in experience(45:01) Giving and receiving feedback(47:38) Boz's tattoos(51:30) Communication is the job(01:00:47) Comparing VR headsets: Meta Quest 3 and Apple Vision Pro(01:10:41) Meta's downturn and turnaround(01:16:10) Navigating org changes(01:20:43) Lessons from failure(01:26:33) Closing thoughts(01:29:57) Lightning round—Referenced:• Reality Labs: https://about.meta.com/realitylabs/• Quest: https://www.meta.com/quest/• Ray-Ban Meta smart glasses: https://www.ray-ban.com/usa/ray-ban-meta-smart-glasses• Taekwondo: https://en.wikipedia.org/wiki/Taekwondo• 4-H: https://4-h.org/• David Copperfield's website: https://www.davidcopperfield.com/html/• MC Hammer on Instagram: https://www.instagram.com/mchammer/• George W. Bush: https://www.whitehouse.gov/about-the-white-house/presidents/george-w-bush/• Fry's Electronics: https://en.wikipedia.org/wiki/Fry%27s_Electronics• Association for Computing Machinery: https://www.acm.org• Get It Done: https://boz.com/articles/get-it-done• Patrick Stewart on X: https://twitter.com/sirpatstew• The FB Exec Practice That Changed the Way I Lead (about HPMs): https://livingos.substack.com/p/fb-exec-hpm• Mark Zuckerberg on Facebook: https://www.facebook.com/zuck• Chris Cox on LinkedIn: https://www.linkedin.com/in/chris-cox-2896b841/• Javier Olivan on LinkedIn: https://www.linkedin.com/in/javierolivan/• Brian Chesky's new playbook: https://www.lennyspodcast.com/brian-cheskys-new-playbook/• Eye of Sauron: https://lotr.fandom.com/wiki/Eye_of_Sauron• Ruchi Sanghvi on LinkedIn: https://www.linkedin.com/in/rsanghvi/• Eric Schmidt on LinkedIn: https://www.linkedin.com/in/eric-e-schmidt/• Sheryl Sandberg on LinkedIn: https://www.linkedin.com/in/sheryl-sandberg-5126652/• Best Advice Sheryl Sandberg Received: If Offered a Seat on Rocket Ship, Get On: https://news.yahoo.com/blogs/newsmakers/best-advice-sheryl-sandberg-received-don-t-idiot-161459450.html• Veritas: https://en.wikipedia.org/wiki/Veritas• Communication is The Job: https://boz.com/articles/communication-is-the-job• Repetition does not spoil the prayer: https://www.linkedin.com/pulse/repetition-does-spoil-prayer-constantine-constantinides-m-d-ph-d--1f/• Janet Lansbury's website: https://www.janetlansbury.com/• Dr. Becky on Instagram: https://www.instagram.com/drbeckyatgoodinside• Boz to the Future Episode 18: The Future According to Matthew Ball: https://www.meta.com/blog/quest/boz-to-the-future-episode-18-matthew-ball-metaverse-epyllion/• Apple Vision Pro: https://www.apple.com/apple-vision-pro• Quest 3 headset: https://www.meta.com/quest/quest-3/• Virtual desktop: https://www.meta.com/experiences/2017050365004772/• Meta Horizon Workrooms: https://www.meta.com/experiences/2514011888645651/ • After trying the Vision Pro, Mark Zuckerberg says Quest 3 ‘is the better product, period': https://www.theverge.com/2024/2/13/24072413/mark-zuckerberg-apple-vision-pro-review-quest-3• Lou Holtz on X: https://twitter.com/CoachLouHoltz88• Gell-Mann amnesia effect: https://en.wiktionary.org/wiki/Gell-Mann_Amnesia_effect• “Wet streets cause rain”: https://news.ycombinator.com/item?id=19026568• Michael Crichton on X: https://twitter.com/CrichtonBooks• AI research at Meta: https://ai.meta.com/research/• Llama 2: https://llama.meta.com/• Warren Buffett quote: https://www.brainyquote.com/quotes/warren_buffett_383933• Mark Slee on LinkedIn: https://www.linkedin.com/in/mcslee/• Dave Fetterman on LinkedIn: https://www.linkedin.com/in/davefetterman/• Emacs and Vim: https://dev.to/george_udonte/emacs-and-vim-an-overview-for-beginners-2e65• Ami Vora on LinkedIn: https://www.linkedin.com/in/amvora/• The Dream Machine: https://www.amazon.com/Dream-Machine-M-Mitchell-Waldrop/dp/1732265119• Alan Turing: https://en.wikipedia.org/wiki/Alan_Turing• Good Inside: A Guide to Becoming the Parent You Want to Be: https://www.amazon.com/Good-Inside-Guide-Becoming-Parent/dp/B09Y4WG7RJ• Dr. Becky's website: https://www.goodinside.com/• The Mandalorian on Disney+: https://www.disneyplus.com/series/the-mandalorian/3jLIGMDYINqD• Scott Trowbridge on LinkedIn: https://www.linkedin.com/in/scott-trowbridge-b70866/• Dave Filoni on X: https://twitter.com/dave_filoni• Jon Favreau on X: https://twitter.com/jon_favreau• Mercedes-Benz AMG EQS Sedan: https://www.mbusa.com/en/vehicles/model/eqs/sedan/amgeqsv4• Tracey Emin “Trust Yourself”: https://www.artsy.net/artwork/tracey-emin-trust-yourself• Tracey Emin on Instagram: https://www.instagram.com/traceyeminstudio• Rick Rubin: Protocols to Access Creative Energy and Process | Huberman Lab Podcast: https://www.youtube.com/watch?v=GpgqXCkRO-w• Ansel Adams: https://en.wikipedia.org/wiki/Ansel_Adams—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
This is a recap of the top 10 posts on Hacker News on January 30th, 2023.This podcast was generated by wondercraft.ai(00:31): Researchers have found a faster way to do integer linear programmingOriginal post: https://news.ycombinator.com/item?id=39185198&utm_source=wondercraft_ai(02:51): Senator Wyden Letter Confirms NSA Is Buying US Persons' Data from Data BrokersOriginal post: https://news.ycombinator.com/item?id=39189481&utm_source=wondercraft_ai(05:25): How to deal with receiving a cease-and-desist letter from Big TechOriginal post: https://news.ycombinator.com/item?id=39190791&utm_source=wondercraft_ai(08:15): Quickemu: Quickly run optimised Windows, macOS and Linux virtual machinesOriginal post: https://news.ycombinator.com/item?id=39188432&utm_source=wondercraft_ai(10:17): I just wanted Emacs to look nice – Using 24-bit color in terminalsOriginal post: https://news.ycombinator.com/item?id=39189881&utm_source=wondercraft_ai(12:42): Apple Vision Pro review: magic, until it's notOriginal post: https://news.ycombinator.com/item?id=39190506&utm_source=wondercraft_ai(14:59): CEOs Are Using Return to Office Mandates to Mask Poor ManagementOriginal post: https://news.ycombinator.com/item?id=39191696&utm_source=wondercraft_ai(17:18): Everyone hates the electronic medical recordOriginal post: https://news.ycombinator.com/item?id=39186252&utm_source=wondercraft_ai(19:38): Why flying insects gather at artificial lightOriginal post: https://news.ycombinator.com/item?id=39192807&utm_source=wondercraft_ai(21:28): There's So Much Data Even Spies Are Struggling to Find SecretsOriginal post: https://news.ycombinator.com/item?id=39187069&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
Como últimamente hay tanta algarabía en el grupo de Telegram de atareao con Linux, en referencia a la supuesta eterna batalla, entre Emacs y Vi, he querido poner un poco de sal en nuestras vidas, con este título tan llamativo. No, nunca he utilizado Emacs, y por el momento no lo voy a utilizar. Ahora mismo tengo demasiados frentes abiertos como para abrir un nuevo frente, sabiendo que ese nuevo frente es todo un agujero negro capaz de absorber hasta la luz. Entonces, ¿a que me refiero cuando digo que abandono Emacs por Vi?. Básicamente me refiero a la línea de comandos. Si, así es, ¿no lo sabías? En la línea de comandos tienes la posibilidad de utilizar el funcionamiento de Vi o el de Emacs. Y digo funcionamiento, y no atajos de teclado, porque en el caso de Vi, puedes utilizar los distintos modos de Vi. Así que vamos a mis razonamientos. Más información, enlaces y notas en https://atareao.es/podcast/563
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book ""A History of Fake Things on the Internet"" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Jeff Jarvis, Paris Martineau, and Jason Howell Guest: Alex Stamos Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book ""A History of Fake Things on the Internet"" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Jeff Jarvis, Paris Martineau, and Jason Howell Guest: Alex Stamos Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book ""A History of Fake Things on the Internet"" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Jeff Jarvis, Paris Martineau, and Jason Howell Guest: Alex Stamos Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book ""A History of Fake Things on the Internet"" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Jeff Jarvis, Paris Martineau, and Jason Howell Guest: Alex Stamos Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book "A History of Fake Things on the Internet" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Paris Martineau, and Jason Howell Guest: Alex Stamos Download or subscribe to this show at https://twit.tv/shows/this-week-in-google. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book "A History of Fake Things on the Internet" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Paris Martineau, and Jason Howell Guest: Alex Stamos Download or subscribe to this show at https://twit.tv/shows/this-week-in-google. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book "A History of Fake Things on the Internet" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Paris Martineau, and Jason Howell Guest: Alex Stamos Download or subscribe to this show at https://twit.tv/shows/this-week-in-google. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
Discussion of upcoming Black Friday sales on Google Pixel phones and tablets Concerns with the Pixel tablet including laggy performance, inability to use independently from dock, and high pricing Leo shares his epiphany on the usefulness of AI for expert systems and personalized agents Demonstration of Leo's custom AI assistants for Lisp and Emacs programming languages Talk of Elon Musk's reputation decline after acquiring Twitter Discussion of studies showing people perceive AI-generated faces as more human than real faces Overview of lawsuit allowing school districts to sue social media companies for youth addiction Interview with Alex Stamos, former Facebook CSO and current Stanford professor Alex's perspective on risks of deepfakes in elections vs for individual harassment Thoughts on moral panic around social media and youth mental health Alex recounts attending a closed-door Senate AI hearing led by Senator Schumer Discussion of social media companies loosening policies on election misinformation Concerns about TikTok as a news source and possible propaganda risks Talk of new book "A History of Fake Things on the Internet" by Walter Shirer Alex's suggestion for comprehensive federal privacy regulations Revelation during Google antitrust trial of Apple's cut of Google search revenue Hosts: Leo Laporte, Paris Martineau, and Jason Howell Guest: Alex Stamos Download or subscribe to this show at https://twit.tv/shows/this-week-in-google. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT hid.link/twig wix.com/studio?utm_campaign=pa_podcast_studio_10/ 23_TWiT%5Esponsors_cta
The Elixir community has a new OpenSource CMS thanks to DockYard and Leandro Pereira! We talk with Leandro to better understand what the Beacon project is and what it can do. It's built using Phoenix LiveView and can be deployed standalone or as part of an existing Elixir Phoenix application. The Admin features include the ability for non-developers to edit content and immediately deploy changes without re-deploying the app. We talk about how BeaconCMS is positioned against Wordpress and static sites and where the greatest benefits are. A feature in development is the HEEx template editor which promises to be a very exciting tool for non-developers. Learn along with us! Show Notes online - http://podcast.thinkingelixir.com/174 (http://podcast.thinkingelixir.com/174) Elixir Community News - https://twitter.com/chris_mccord/status/1713894354962534808 (https://twitter.com/chris_mccord/status/1713894354962534808?utm_source=thinkingelixir&utm_medium=shownotes) – LiveView optimized DOM patching announced, resulting in significant speed improvements in browser's DOM patching time. - https://twitter.com/basilenouvellet/status/1713981828028133847 (https://twitter.com/basilenouvellet/status/1713981828028133847?utm_source=thinkingelixir&utm_medium=shownotes) – Real world test results demonstrating faster speeds due to LiveView's optimized DOM patching. - https://dashbit.co/blog/latency-rendering-liveview (https://dashbit.co/blog/latency-rendering-liveview?utm_source=thinkingelixir&utm_medium=shownotes) – New post on performance optimization in Phoenix LiveView by José Valim. - https://youtu.be/Ckgl9KO4E4M?si=UNf5sNShzl1oTZQS&t=1731 (https://youtu.be/Ckgl9KO4E4M?si=UNf5sNShzl1oTZQS&t=1731?utm_source=thinkingelixir&utm_medium=shownotes) – Chris McCord's ElixirConf keynote demo on LiveView's new dev tool features. Time signature for dev tools example - https://twitter.com/josevalim/status/1711756969814426066 (https://twitter.com/josevalim/status/1711756969814426066?utm_source=thinkingelixir&utm_medium=shownotes) – José Valim's explanation on LiveView's unreleased feature. - https://github.com/elixir-saas/clicktocomponent (https://github.com/elixir-saas/click_to_component?utm_source=thinkingelixir&utm_medium=shownotes) – An external library called "clicktocomponent" to support the Cmd+Click functionality in LiveView. - https://news.livebook.dev/remote-execution-smart-cell---launch-week-2---day-1-m3dv2 (https://news.livebook.dev/remote-execution-smart-cell---launch-week-2---day-1-m3dv2?utm_source=thinkingelixir&utm_medium=shownotes) – Announcement of Livebook's new feature - Remote execution Smart cell. - https://news.livebook.dev/speech-to-text-with-whisper-timestamping-streaming-and-parallelism-oh-my---launch-week-2---day-2-36osSY (https://news.livebook.dev/speech-to-text-with-whisper-timestamping-streaming-and-parallelism-oh-my---launch-week-2---day-2-36osSY?utm_source=thinkingelixir&utm_medium=shownotes) – Livebook's new features in their Whisper integration for improved speech-to-text performance. - https://news.livebook.dev/introducing-file-integration---launch-week-2---day-3-2HoFfa (https://news.livebook.dev/introducing-file-integration---launch-week-2---day-3-2HoFfa?utm_source=thinkingelixir&utm_medium=shownotes) – Livebook's introduction to File Integration. - https://news.livebook.dev/integration-with-snowflake-and-microsoft-sql-server---launch-week-2---day-4-2o4z9C (https://news.livebook.dev/integration-with-snowflake-and-microsoft-sql-server---launch-week-2---day-4-2o4z9C?utm_source=thinkingelixir&utm_medium=shownotes) – Livebook adds support for Snowflake and SQL Server. - https://news.livebook.dev/vim-and-emacs-key-bindings---launch-week-2---day- (https://news.livebook.dev/vim-and-emacs-key-bindings---launch-week-2---day-?utm_source=thinkingelixir&utm_medium=shownotes) – Livebook support for VIM & Emacs key bindings. - https://hexdocs.pm/ash_sqlite/get-started-with-sqlite.html (https://hexdocs.pm/ash_sqlite/get-started-with-sqlite.html?utm_source=thinkingelixir&utm_medium=shownotes) – Ash Framework's new AshSqlite library release. - https://oban.pro/releases/web/v2.10 (https://oban.pro/releases/web/v2.10?utm_source=thinkingelixir&utm_medium=shownotes) – Release of Oban Web 2.10.0. - https://github.com/emmanueltouzery/elixir-extras.nvim (https://github.com/emmanueltouzery/elixir-extras.nvim?utm_source=thinkingelixir&utm_medium=shownotes) – Release of a new Neovim Elixir plugin called elixir-extras.nvim. - https://twitter.com/samokhvalov/status/1714153676212949355 (https://twitter.com/samokhvalov/status/1714153676212949355?utm_source=thinkingelixir&utm_medium=shownotes) – PostgreSQL tip for setting a human-readable label for a connection session. - https://github.com/pgbouncer/pgbouncer/releases/tag/pgbouncer121_0 (https://github.com/pgbouncer/pgbouncer/releases/tag/pgbouncer_1_21_0?utm_source=thinkingelixir&utm_medium=shownotes) – Upcoming PgBouncer 1.21 release with support for prepared statements. - https://twitter.com/ElixirConfEU/status/1713929804062273663 (https://twitter.com/ElixirConfEU/status/1713929804062273663?utm_source=thinkingelixir&utm_medium=shownotes) – Announcement for call for talks for ElixirConf Europe 2024. - https://www.elixirconf.eu/ (https://www.elixirconf.eu/?utm_source=thinkingelixir&utm_medium=shownotes) – ElixirConf Europe 2024 conference details. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://github.com/BeaconCMS/beacon (https://github.com/BeaconCMS/beacon?utm_source=thinkingelixir&utm_medium=shownotes) – The main Beacon CMS project - https://github.com/BeaconCMS/beacon_demo (https://github.com/BeaconCMS/beacon_demo?utm_source=thinkingelixir&utm_medium=shownotes) – Beacon CMS demo project - https://github.com/BeaconCMS/beaconliveadmin (https://github.com/BeaconCMS/beacon_live_admin?utm_source=thinkingelixir&utm_medium=shownotes) – Beacon CMS admin project - https://beaconcms.org/ (https://beaconcms.org/?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.youtube.com/watch?v=5jk0fIJOFuc&list=PLqj39LCvnOWbHaZldxw_g02RaTQ4vQ1eY&index=16 (https://www.youtube.com/watch?v=5jk0fIJOFuc&list=PLqj39LCvnOWbHaZldxw_g02RaTQ4vQ1eY&index=16?utm_source=thinkingelixir&utm_medium=shownotes) – ElixirConf 2023 - Beacon - The next generation of CMS in Phoenix LiveView - https://mdxjs.com/ (https://mdxjs.com/?utm_source=thinkingelixir&utm_medium=shownotes) - https://hex.pm/packages/earmark (https://hex.pm/packages/earmark?utm_source=thinkingelixir&utm_medium=shownotes) - https://github.com/leandrocp/mdex (https://github.com/leandrocp/mdex?utm_source=thinkingelixir&utm_medium=shownotes) - https://github.com/BeaconCMS/livemonacoeditor (https://github.com/BeaconCMS/live_monaco_editor?utm_source=thinkingelixir&utm_medium=shownotes) – The code editor, based on the Livebook editor - https://github.com/leandrocp/mdex (https://github.com/leandrocp/mdex?utm_source=thinkingelixir&utm_medium=shownotes) – Markdown parser and formatter - https://github.com/leandrocp/autumn (https://github.com/leandrocp/autumn?utm_source=thinkingelixir&utm_medium=shownotes) – Syntax highlighter for code blocks - https://github.com/TheFirstAvenger/safe_code (https://github.com/TheFirstAvenger/safe_code?utm_source=thinkingelixir&utm_medium=shownotes) – Inspect HEEx for unsafe code - https://github.com/BeaconCMS/beacon/milestone/1 (https://github.com/BeaconCMS/beacon/milestone/1?utm_source=thinkingelixir&utm_medium=shownotes) – Beacon v0.1 release milestone - https://github.com/BeaconCMS/beaconliveadmin/milestone/1 (https://github.com/BeaconCMS/beacon_live_admin/milestone/1?utm_source=thinkingelixir&utm_medium=shownotes) Guest Information - https://twitter.com/leandrocesquini (https://twitter.com/leandrocesquini?utm_source=thinkingelixir&utm_medium=shownotes) – on Twitter - https://github.com/leandrocp/ (https://github.com/leandrocp/?utm_source=thinkingelixir&utm_medium=shownotes) – on Github - hhttps://leandrocp.com.br (hhttps://leandrocp.com.br?utm_source=thinkingelixir&utm_medium=shownotes) – Blog - https://github.com/leandrocp/mdex (https://github.com/leandrocp/mdex?utm_source=thinkingelixir&utm_medium=shownotes) – Other project MDEx - A fast 100% CommonMark-compatible GitHub Flavored Markdown parser and formatter for Elixir. Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern) - Cade Ward - @cadebward (https://twitter.com/cadebward) - Cade Ward on Fediverse - @cadebward@genserver.social (https://genserver.social/cadebward)
Karl Voit describes himself as “a life hacker trying to make deliberate decisions on every aspect of life.” Among these are the tools he uses to manage his personal information. In particular, Karl is an avid user of Org Mode in Emacs, which is the focus of this conversation.Show notespublic voit - Homepage of Karl VoitKarl Voit on Mastodon (@publicvoit@graz.social)Filofax - WikipediaFranklin Planner - WikipediaLaTeX - A document preparation systemEmacs - WikipediaEmacs Lisp - WikipediaOrg-mode - WikipediaDaring Fireball: MarkdownGitHubOrgzly - Notes & To-Do ListsSyncthingabo-abo/hydra: make Emacs bindings that stick aroundpublic voit — How to Use This Blog Efficientlynovoid/lazyblorg: Blogging with Org-mode for very lazy peopleShow notes include Amazon affiliate links. We get a small commission for purchases made through these links.If you're enjoying the show, please rate or review us in Apple's podcast directory:https://podcasts.apple.com/us/podcast/the-informed-life/id1450117117?itsct=podcast_box&itscg=30200
Name one other podcast where you can hear about heavy 3D-printed drones, DIY semiconductors, and using licorice to block laser beams. Throw in homebrew relays, a better mouse trap, and logic analyzers, and you'll certainly be talking about Elliot Williams and Al Williams on Hackaday Podcast 235. There's also contest news, thermoforming, and something that looks a little like 3D-printed Velcro. Elliot and Al also have their semi-annual argument about Vi vs. Emacs. Spoiler alert: they decided they both suck. Missed any of their picks? Check out the links on Hackaday, and as always, tell us what you think about this episode in the comments!
We've all run "mix phx.new", but have you ever thought to customize what that does? We talk with Victor Björklund who explains how we can create customized Phoenix project generators and why we might want to. We also discuss customizing the phoenix generators for our already generated projects. We explore the idea of supporting 3rd-party maintained generators and what that might look like. A fun discussion sure to “generate” ideas for your project! Show Notes online - http://podcast.thinkingelixir.com/167 (http://podcast.thinkingelixir.com/167) Elixir Community News - https://github.com/elixir-lang/elixir/releases/tag/v1.15.5 (https://github.com/elixir-lang/elixir/releases/tag/v1.15.5?utm_source=thinkingelixir&utm_medium=shownotes) – Elixir 1.15.5 bug fix release - https://pdx.social/@kenichi/110934002380304132 (https://pdx.social/@kenichi/110934002380304132?utm_source=thinkingelixir&utm_medium=shownotes) – Livebook code cells getting Vim and Emacs support - https://pragprog.com/titles/tvmelixir/adopting-elixir/ (https://pragprog.com/titles/tvmelixir/adopting-elixir/?utm_source=thinkingelixir&utm_medium=shownotes) – Good quote from the “Adopting Elixir” book (published 5 years ago) - https://twitter.com/paraxialio/status/1694832429087728005 (https://twitter.com/paraxialio/status/1694832429087728005?utm_source=thinkingelixir&utm_medium=shownotes) - https://elixirforum.com/t/elixir-saves-pinterest-2-million-year-other-marketing-examples/57909/14 (https://elixirforum.com/t/elixir-saves-pinterest-2-million-year-other-marketing-examples/57909/14?utm_source=thinkingelixir&utm_medium=shownotes) – Elixir Saves Pinterest $2 million/year - https://twitter.com/davydog187/status/1694768741467165147 (https://twitter.com/davydog187/status/1694768741467165147?utm_source=thinkingelixir&utm_medium=shownotes) – Tweet by Dave Lucia about what people can accomplish with Elixir and Phoenix in a short amount of time. - https://twitter.com/geolessel/status/1695467313477173313 (https://twitter.com/geolessel/status/1695467313477173313?utm_source=thinkingelixir&utm_medium=shownotes) – Geoffrey Lessel shared observation that the timing page used by the World Cube Association is a Phoenix LiveView page. - https://github.com/thewca/wca-live (https://github.com/thewca/wca-live?utm_source=thinkingelixir&utm_medium=shownotes) – Platform for running WCA competitions and sharing live results with the world created by Jonatan Kłosko - https://twitter.com/AshFramework/status/1696257451857707295 (https://twitter.com/AshFramework/status/1696257451857707295?utm_source=thinkingelixir&utm_medium=shownotes) – Ash Framework experiments with adding a new “atomics” feature. - https://github.com/ash-project/ash/blob/main/documentation/topics/atomics.md (https://github.com/ash-project/ash/blob/main/documentation/topics/atomics.md?utm_source=thinkingelixir&utm_medium=shownotes) – Atomics documentation and design - https://twitter.com/ac_alejos/status/1695562511787983164 (https://twitter.com/ac_alejos/status/1695562511787983164?utm_source=thinkingelixir&utm_medium=shownotes) – Elixir gets a new Reinforcement Learning library named "Rein" for Nx. - https://github.com/DockYard/rein (https://github.com/DockYard/rein?utm_source=thinkingelixir&utm_medium=shownotes) – Rein project on Github - https://fly.io/phoenix-files/star-cross-live-view-processes/ (https://fly.io/phoenix-files/star-cross-live-view-processes/?utm_source=thinkingelixir&utm_medium=shownotes) – Star-Crossed LiveView Processes about linking processes to solve UI design Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://victorbjorklund.com/guide-to-custom-phoenix-phx-new-generator-mix-task (https://victorbjorklund.com/guide-to-custom-phoenix-phx-new-generator-mix-task?utm_source=thinkingelixir&utm_medium=shownotes) - https://jawdropping.io/ (https://jawdropping.io/?utm_source=thinkingelixir&utm_medium=shownotes) - https://github.com/phoenixframework/phoenix/tree/main/installer (https://github.com/phoenixframework/phoenix/tree/main/installer?utm_source=thinkingelixir&utm_medium=shownotes) - https://hex.pm/packages/oban (https://hex.pm/packages/oban?utm_source=thinkingelixir&utm_medium=shownotes) Guest Information - https://twitter.com/BjorklundVictor (https://twitter.com/BjorklundVictor?utm_source=thinkingelixir&utm_medium=shownotes) – on Twitter - https://github.com/victorbjorklund/ (https://github.com/victorbjorklund/?utm_source=thinkingelixir&utm_medium=shownotes) – on Github - https://genserver.social/victorbjorklund (https://genserver.social/victorbjorklund?utm_source=thinkingelixir&utm_medium=shownotes) – on Fediverse - https://victorbjorklund.com/ (https://victorbjorklund.com/?utm_source=thinkingelixir&utm_medium=shownotes) – Blog Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern) - Cade Ward - @cadebward (https://twitter.com/cadebward) - Cade Ward on Fediverse - @cadebward@genserver.social (https://genserver.social/cadebward)
What is it like to use the Dvorak keyboard layout? Is it better for programming than the standard Qwerty layout? Join Evan and Thomas as they discuss keyboard layouts along with potential advantages of different keyboard types when it comes to dealing with RSI. The discussion then turns to editors and how they relate to each other including Emacs, Neovim, and VSCode. And then finishing with a discussion on Rust/programming safety and a brief overview of design-by-contract and literate programming.https://twitter.com/_evanwalter_thereactshow.com/supportJoin The Reactors! thereactshow.com/the-reactors-communityJoin our Discord! https://discord.gg/zXYggKUBC2My book: Foundations of High-Performance React https://www.thereactshow.com/bookConsulting: https://thomashintz.orgMusic by DRKST DWN: https://soundcloud.com/drkstdwnSupport the show
We discuss the packages installed in the second of three files that make up my emacs config. Since recording, I pulled in some EXWM (the Emacs X Window Manager, that's right), even though I'm not actually using it, I'm still using stumpWM. I have also added pass, the password manager, khardel, an emacs package for the khard CLI address book application. I also moved (server-start) to this file, so that it'll only happen when I'm on linux. ;;; init-extra.el --- Extra init stuff ;;; Commentary: ;;; Stuff just for my personal laptop, not for my work laptop or termux, for example. ;;; Code: ;;;;;;;;;;;;;;;; ;;; org-roam ;;; ;;;;;;;;;;;;;;;; (use-package org-roam :demand t :straight (:host github :repo "org-roam/org-roam" :files (:defaults "extensions/*")) :custom (org-roam-mode-sections (list #'org-roam-backlinks-section #'org-roam-reflinks-section #'org-roam-unlinked-references-section)) :init (setq org-roam-directory "~/org/roam/" org-roam-capture-templates '(("o" "outline" plain "%?" :if-new (file+head "${slug}.org" "#+title: ${title}n#+filetags: :outline:n") :immediate-finish t :unnarrowed t) ("r" "reference" plain "%?" :if-new (file+head "${slug}.org" "#+title: ${title}n") :immediate-finish t :unnarrowed t) ("m" "memo" entry "* ${title}n%?" :if-new (file "memos.org") :immediate-finish t :unnarrowed t))) :bind (("C-c n l" . org-roam-buffer-toggle) ("C-c n f" . org-roam-node-find) ("C-c n g" . org-roam-graph) ("C-c n i" . org-roam-node-insert) ("C-c n c" . org-roam-capture) ;; Dailies ("C-c n j" . org-roam-dailies-capture-today)) :config ;; If you're using a vertical completion framework, you might want a more informative completion interface (setq org-roam-node-display-template (concat "${title:*} " (propertize "${tags:10}" 'face 'org-tag))) (org-roam-db-autosync-mode) ;; If using org-roam-protocol (require 'org-roam-protocol)) ;; citations (use-package citar :after org-roam :custom (org-cite-insert-processor 'citar) (org-cite-follow-processor 'citar) (org-cite-activate-processor 'citar) (citar-bibliography '("~/org/biblio.bib")) (citar-notes-paths '("~/org/roam")) (citar-file-note-extensions '("org")) :hook (LaTeX-mode . citar-capf-setup) (org-mode . citar-capf-setup) :bind (("C-c n b" . #'citar-open-notes) :map org-mode-map :package org ("C-c b" . #'org-cite-insert))) ;; view your org-roam notes on a map (use-package org-roam-ui :after org-roam :custom (org-roam-ui-sync-theme t) (org-roam-ui-follow t) (org-roam-ui-update-on-save t) (org-roam-ui-open-on-start t)) ;; archive web pages in org attachments (use-package org-board :after org :custom (org-board-default-browser #'browse-url) (org-board-property "ROAM_REFS") :bind (:map org-mode-map ("C-c B a" . org-board-archive) ("C-c B o" . org-board-open) ("C-c B D" . org-board-delete-all))) ;;;;;;;;;;;;;;; ;;; Writing ;;; ;;;;;;;;;;;;;;; ; something like grammarly, but open source (use-package langtool) ;; better than docview, for pdf (use-package pdf-tools) ;; annotating docs in org files (use-package org-noter) ;; epub (use-package nov :mode (".epub$" . nov-mode)) ;;; Invoke quick emacs windows to edit anything anywhere. ;;; bind a key in xorg to ~emacsclient -c (emacs-everywhere)~ (use-package emacs-everywhere) ;;;;;;;;;;;;;; ;;; Auctex ;;; ;;;;;;;;;;;;;; (straight-use-package '( auctex :host nil :repo "https://git.savannah.gnu.org/git/auctex.git" :pre-build (("./autogen.sh") ("./configure" "--without-texmf-dir" "--with-lispdir=.") ("make")))) (setq TeX-data-directory (expand-file-name "straight/repos/auctex" user-emacs-directory) TeX-lisp-directory TeX-data-directory) (eval-after-load 'info '(add-to-list 'Info-additional-directory-list (expand-file-name "straight/repos/auctex/doc" user-emacs-directory))) (load (expand-file-name "straight/repos/auctex/auctex.el" user-emacs-directory) nil t t) (load (expand-file-name "straight/repos/auctex/preview-latex.el" user-emacs-directory) nil t t) (use-package evil-tex) (use-package latex-preview-pane :custom (latex-preview-pane-use-frame t)) (use-package adaptive-wrap) ;;; END AUCTEX ;;; ;;;;;;;;;;;;;;;;;;; ;;; Programming ;;; ;;;;;;;;;;;;;;;;;;; ;; downloading and viewing Dash documentation files (use-package dash-docs :init (defun elisp-doc () (setq-local consult-dash-docsets '("Emacs Lisp"))) (add-hook 'emacs-lisp-mode-hook 'elisp-doc) :custom (dash-docs-docsets-path (expand-file-name "docsets" user-emacs-directory)) (dash-docs-browse-func 'eww)) (use-package consult-dash :straight (:host codeberg :repo "rahguzar/consult-dash") :bind (("M-s d" . consult-dash)) :after consult :config ;; Use the symbol at point as initial search term (consult-customize consult-dash :initial (thing-at-point 'symbol))) ;;;;;;;;;;;;; ;;; Email ;;; ;;;;;;;;;;;;; (use-package notmuch :commands notmuch :config (defun notmuch-show-view-html () "Open the text/html part of the current message using `notmuch-show-view-part'. From https://emacs.stackexchange.com/a/63457" (interactive) (save-excursion (goto-char (prop-match-beginning (text-property-search-forward :notmuch-part "text/html" (lambda (value notmuch-part) (equal (plist-get notmuch-part :content-type) value))))) (notmuch-show-view-part))) ;; Enable link to message via org-store-link (load-file (expand-file-name "org-notmuch.el" user-emacs-directory)) (require 'org-notmuch) :bind (:map notmuch-show-mode-map (". v" . notmuch-show-view-html)) :custom (notmuch-draft-folder "local/drafts") (notmuch-search-oldest-first nil) (notmuch-fcc-dirs "fastmail/sent") (notmuch-tagging-keys '(("r" ("+receipt" "-inbox") "Receipt"))) (sendmail-program (executable-find "msmtp")) (message-sendmail-f-is-evil t) (message-sendmail-extra-arguments '("--read-envelope-from"))) (use-package khardel :after notmuch :bind (:map notmuch-message-mode-map ("C-c M-k" . khardel-insert-email))) ;;;;;;;;;;;; ;;; PASS ;;; ;;;;;;;;;;;; (use-package pass) ;;;;;;;;;;;; ;;; EXWM ;;; ;;;;;;;;;;;; (use-package xelb :disabled t :straight (:host github :repo "ch11ng/xelb")) (use-package exwm :disabled t :straight (:host github :repo "ch11ng/exwm") :defer t :config (require 'exwm-systemtray) (require 'exwm-randr) (setq xcb:connection-timeout 20) (exwm-systemtray-enable) (add-hook 'exwm-update-class-hook (lambda () (exwm-workspace-rename-buffer exwm-class-name))) (add-hook 'exwm-randr-screen-change-hook (lambda () (start-process-shell-command "autorandr" nil "autorandr -c"))) (defun exwm-randr-mobile() "Load a xrandr profile to use only the laptop screen." (interactive) (start-process-shell-command "xrandr" nil "xrandr --output eDP-1 --auto --output DP-1 --off")) (defun exwm-randr-docked() "Load a xrandr profile to use only the connected external screen DP-1." (interactive) (start-process-shell-command "xrandr" nil "xrandr --output eDP-1 --off --output DP-1 --auto")) (defun exwm-randr-chair() "Load a xrandr profile to use both the laptop screen and the connected screen." (interactive) (start-process-shell-command "xrandr" nil "xrandr --output HDMI-1 --auto --scale 1.3 --output eDP-1 --off")) (defun exwm-randr-all() "Load a xrandr profile to use both the laptop screen and the connected screen." (interactive) (start-process-shell-command "xrandr" nil "xrandr --output eDP-1 --primary --output DP-1 --above eDP-1") (setq exwm-randr-workspace-output-plist '(0 "eDP-1" 1 "DP-1")) ) (exwm-randr-enable) :custom (exwm-input-global-keys `((,(kbd "s-r") . exwm-reset) (,(kbd "s-w") . exwm-workspace-switch) (,(kbd "s-a") . exwm-randr-all) (,(kbd "s-c") . exwm-randr-chair) (,(kbd "s-d") . exwm-randr-docked) (,(kbd "s-m") . exwm-randr-mobile) (,(kbd "s-k") . exwm-input-release-keyboard) (,(kbd "s-f") . exwm-layout-toggle-fullscreen) (,(kbd "s-p") . pass) (,(kbd "s-t") . exwm-workspace-switch-to-buffer) (,(kbd "s-&") . (lambda (command) (interactive (list (read-shell-command "$ "))) (start-process-shell-command command nil command))) ,@(mapcar (lambda (i) `(,(kbd (format "s-%d" i)) . (lambda () (interactive) (exwm-workspace-switch-create ,i)))) (number-sequence 0 9)) )) ) ;; start emacs server (server-start) ;;; END ;;; (provide 'init-extra) ;;; init-extra.el ends here
table td.shrink { white-space:nowrap } hr.thin { border: 0; height: 0; border-top: 1px solid rgba(0, 0, 0, 0.1); border-bottom: 1px solid rgba(255, 255, 255, 0.3); } New hosts Welcome to our new hosts: HopperMCS, Reto. Last Month's Shows Id Day Date Title Host 3891 Mon 2023-07-03 HPR Community News for June 2023 HPR Volunteers 3892 Tue 2023-07-04 Emacs package curation, part 1 dnt 3893 Wed 2023-07-05 Game card design resources Klaatu 3894 Thu 2023-07-06 The Page 42 Show: Ugly News Week, Show's Epoch! HopperMCS 3895 Fri 2023-07-07 What's in my backpack Stache_AF 3896 Mon 2023-07-10 The Brochs of Glenelg Andrew Conway 3897 Tue 2023-07-11 HPR AudioBook Club 22 - Murder at Avedon Hill HPR_AudioBookClub 3898 Wed 2023-07-12 The Oh No! News. Some Guy On The Internet 3899 Thu 2023-07-13 Repair corrupt video files for free with untruc Paul Quirk 3900 Fri 2023-07-14 Preparing Podcasts for Listening Ahuka 3901 Mon 2023-07-17 Time Managment operat0r 3902 Tue 2023-07-18 Introduction to a new series on FFMPEG Mr. Young 3903 Wed 2023-07-19 Why I don't love systemd (yet) deepgeek 3904 Thu 2023-07-20 How to make friends Klaatu 3905 Fri 2023-07-21 Presenting Fred Black folky 3906 Mon 2023-07-24 The Oh No! News. Some Guy On The Internet 3907 Tue 2023-07-25 My introduction show Reto 3908 Wed 2023-07-26 Emacs package curation, part 2 dnt 3909 Thu 2023-07-27 Permission tickets. one_of_spoons 3910 Fri 2023-07-28 Playing Civilization II Ahuka 3911 Mon 2023-07-31 An overview of the 'ack' command Dave Morriss Comments this month These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 20 comments in total. Past shows There are 4 comments on 3 previous shows: hpr3876 (2023-06-12) "Recording An Episode For Hacker Public Radio" by Ryuno-Ki. Comment 1: Reto on 2023-07-01: "Good information about recording" hpr3883 (2023-06-21) "Emergency Show: How to demonstrate the power of condensing steam" by Mike Ray. Comment 1: dnt on 2023-07-15: "Clap!" hpr3889 (2023-06-29) "comm - compare two sorted files line by line" by Ken Fallon. Comment 1: Reto on 2023-07-08: "KDirStat is dead, long live QDirStat!" Comment 2: Ken Fallon on 2023-07-12: "QDirstat is nice but I meant kdiff3" This month's shows There are 16 comments on 11 of this month's shows: hpr3891 (2023-07-03) "HPR Community News for June 2023" by HPR Volunteers. Comment 1: norrist on 2023-07-03: "solocast updates"Comment 2: Kevin O'Brien on 2023-07-04: "My truck" hpr3892 (2023-07-04) "Emacs package curation, part 1" by dnt. Comment 1: Klaatu on 2023-07-05: "I love this topic"Comment 2: dnt on 2023-07-11: "Do it!" hpr3894 (2023-07-06) "The Page 42 Show: Ugly News Week, Show's Epoch!" by HopperMCS. Comment 1: Kevin O'Brien on 2023-07-08: "I loved the show" hpr3896 (2023-07-10) "The Brochs of Glenelg" by Andrew Conway. Comment 1: dnt on 2023-07-29: "Ruins" hpr3900 (2023-07-14) "Preparing Podcasts for Listening" by Ahuka. Comment 1: Hipstre on 2023-07-14: "Limiter/GPodder"Comment 2: Eugene on 2023-07-16: "No need for podcast preprocessing"Comment 3: Kevin O'Brien on 2023-07-17: "Sansa Clip+" hpr3901 (2023-07-17) "Time Managment" by operat0r. Comment 1: Reto on 2023-07-18: "aCalendar on Android" hpr3902 (2023-07-18) "Introduction to a new series on FFMPEG" by Mr. Young. Comment 1: dnt on 2023-07-29: "ffmpeg" hpr3903 (2023-07-19) "Why I don't love systemd (yet)" by deepgeek. Comment 1: dnt on 2023-07-29: "systemd" hpr3904 (2023-07-20) "How to make friends" by Klaatu. Comment 1: dnt on 2023-07-29: "Friends"Comment 2: Beeza on 2023-08-02: "Frienships" hpr3909 (2023-07-27) "Permission tickets. " by one_of_spoons. Comment 1: dnt on 2023-07-29: "Great show, keep em coming!" hpr3910 (2023-07-28) "Playing Civilization II" by Ahuka. Comment 1: dnt on 2023-07-29: "Game mechanics" Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mail List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://lists.hackerpublicradio.com/pipermail/hpr/2023-July/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Any other business The HPR Static Site As mentioned in the last Community News episode, the HPR database and website was moved to a new server, and the static site generator written by Rho`n was used to generated the non-interactive part of the website. Since then, there has been a process of adapting the software to the new configuration. Unfortunately Rho`n has not been available during this process, but we are gradually learning our way around his excellent software and making changes to suit our needs. If you spot any problems or have ideas for new features, please raise issues on the Gitea repository at: https://repo.anhonesthost.net/rho_n/hpr_generator/issues. Reserve Queue A policy change is required in the use of the reserve queue. When there are unfilled slots between 5 and 7 days in the future, episodes in this queue will be used to fill them. This extra time is required because of the time it can take to process a show and load it to the Internet Archive. Bram Moolenaar, author of Vim dies There was an announcement from Bram's family today (2023-08-05) that he died on August 3rd 2023 from a medical problem that worsened recently. Bram Moolenar's page on Wikipedia
This is a recap of the top 10 posts on Hacker News on July 30th, 2023.This podcast was generated by wondercraft.ai(00:39): Ffmprovisr – Making FFmpeg EasierOriginal post: https://news.ycombinator.com/item?id=36929499&utm_source=wondercraft_ai(02:33): Emacs 29.1Original post: https://news.ycombinator.com/item?id=36929514&utm_source=wondercraft_ai(04:20): Scientists may have found mechanism behind cognitive decline in agingOriginal post: https://news.ycombinator.com/item?id=36929090&utm_source=wondercraft_ai(06:11): I feel hopeless, rejected, and a burden – One week of empathy training (2019)Original post: https://news.ycombinator.com/item?id=36932524&utm_source=wondercraft_ai(08:06): How the Rich Reap Huge Tax Breaks From Private NonprofitsOriginal post: https://news.ycombinator.com/item?id=36929335&utm_source=wondercraft_ai(09:52): Welcome to WikifunctionsOriginal post: https://news.ycombinator.com/item?id=36927695&utm_source=wondercraft_ai(11:22): The Long History of Nobody Wants to Work AnymoreOriginal post: https://news.ycombinator.com/item?id=36931129&utm_source=wondercraft_ai(13:09): Linux Air Combat: free, lightweight and open-source combat flight simulatorOriginal post: https://news.ycombinator.com/item?id=36934029&utm_source=wondercraft_ai(15:05): Chicago95 – Windows 95 Theme for LinuxOriginal post: https://news.ycombinator.com/item?id=36929096&utm_source=wondercraft_ai(16:56): What's up, Python? The GIL removed, a new compiler, optparse deprecatedOriginal post: https://news.ycombinator.com/item?id=36935041&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
Richard Matthew Stallman leads the Free Software Movement, which shows how the usual non-free software subjects users to the unjust power of its developers, plus their spying and manipulation, and campaigns to replace it with free (freedom-respecting) software. Born in 1953, Stallman graduated Harvard in 1974 in physics. He worked at the MIT Artificial Intelligence Lab from 1971 to 1984, developing system software including the first extensible text editor Emacs (1976), plus the AI technique of dependency-directed backtracking, also known as truth maintenance (1975). In 1983 Stallman launched the Free Software Movement by announcing the project to develop the GNU operating system, planned to consist entirely of free software. Stallman began working on GNU on January 5, 1984, resigning from MIT employment in order to do so. In October 1985 he established the Free Software Foundation. Stallman invented the concept of copyleft, "Change it and redistribute it but don't strip off this freedom," and wrote (with lawyers) the GNU General Public License, which implements copyleft. This inspired Creative Commons. Stallman personally developed a number of widely used software components of the GNU system: the GNU Compiler Collection, the GNU symbolic debugger (gdb), GNU Emacs, and various others. The GNU/Linux system, which is a variant of GNU that also contains the kernel Linux developed by Linus Torvalds, is used in tens or hundreds of millions of computers. Alas, people often call the system "Linux", giving the GNU Project none of the credit. Their versions of GNU/Linux often disregard the ideas of freedom which make free software important, and even include nonfree software in those systems. Nowadays, Stallman focuses on political advocacy for free software and its ethical ideas. He spends most of the year travelling to speak on topics such as "Free Software And Your Freedom" and "Copyright vs Community in the Age of the Computer Networks". Another topic is "A Free Digital Society", which treats several different threats to the freedom of computer users today. In 1999, Stallman called for development of a free on-line encyclopedia through inviting the public to contribute articles. This idea helped inspire Wikipedia. Stallman was a Visiting Scientist at MIT from 1991 (approximately) to 2019. Free Software, Free Society is Stallman's book of essays. His semiautobiography, Free as in Freedom, provides further biographical information. Original video here Full Wikipedia entry here Richard Stallman's books here --- Support this podcast: https://podcasters.spotify.com/pod/show/theunadulteratedintellect/support
We discuss the packages installed in the second of three files that make up my emacs config. ;;; init-base.el --- The basics ;;; Commentary: ;;; Packages for my personal and work laptop, but not termux. ;;; Code: ;;;;;;;;;;;;;;; ;;; Writing ;;; ;;;;;;;;;;;;;;; ;; Focused writing mode (use-package olivetti :hook (olivetti-mode . typewriter-mode-toggle) :bind ("C-x C-w" . olivetti-mode) :custom (olivetti-body-width 64) :config (defvar-local typewriter-mode nil "Typewriter mode, automatically scroll down to keep cursor in the middle of the screen. Setting this variable explicitly will not do anything, use typewriter-mode-on, typewriter-mode-off and typewriter-mode-toggle instead.") (defun typewriter-mode-on() "Automatically scroll down to keep cursor in the middle of screen." (interactive) (setq-local typewriter-mode t) (centered-cursor-mode +1)) (defun typewriter-mode-off() "Automatically scroll down to keep cursor in the middle of screen." (interactive) (kill-local-variable 'typewriter-mode) (centered-cursor-mode -1)) (defun typewriter-mode-toggle() "Toggle typewriter scrolling mode on and off." (interactive) (if typewriter-mode (typewriter-mode-off) (typewriter-mode-on)))) (use-package centered-cursor-mode) ;; Check for weasel words and some other simple rules (use-package writegood-mode :bind ("C-c g" . writegood-mode)) ;; spellchecking (use-package flyspell-correct :after flyspell :bind (:map flyspell-mode-map ("C-;" . flyspell-correct-wrapper))) ;; show correction options in a popup instead of the minibuffer (use-package flyspell-correct-popup :after (flyspell-correct)) ;online thesaurus service from powerthesaurus.org (use-package powerthesaurus) ;; WordNet Thesaurus replacement (use-package synosaurus :custom (synosaurus-choose-method 'default) :config (when window-system (if (string= (x-server-vendor) "Microsoft Corp.") (setq synosaurus-wordnet--command "C:Program Files (x86)WordNet2.1binwn.exe")))) ;; WordNet search and view (use-package wordnut :bind ("C-c s" . wordnut-search) :config (when window-system (if (string= (x-server-vendor) "Microsoft Corp.") (setq wordnut-cmd "C:Program Files (x86)WordNet2.1binwn.exe")))) ;; fill and unfill with the same key (use-package unfill :bind ("M-q" . unfill-toggle)) ;; Markdown... (use-package markdown-mode) ;;;;;;;;;;;;;; ;;; Coding ;;; ;;;;;;;;;;;;;; ;; Syntax checking (use-package flycheck :diminish :init (global-flycheck-mode)) (use-package flycheck-popup-tip :after (flycheck) :hook (flycheck-mode-hook . flycheck-popup-tip-mode)) ;; Web design (use-package emmet-mode :hook (sgml-mode . emmet-mode) ;; Auto-start on any markup modes (css-mode . emmet-mode)) ;; enable Emmet's css abbreviation. (use-package sass-mode) (use-package web-mode) ;; Python (use-package python :mode (".py'" . python-mode) :interpreter ("python" . python-mode)) ;; highlight todo items everywhere (use-package hl-todo :straight (:host github :repo "tarsius/hl-todo") :custom (hl-todo-keyword-faces `(("FIXME" error bold) ("STUB" error bold) ("REPLACETHIS" error bold) ("REVISIT" error bold))) (hl-todo-exclude-modes nil) :config (add-to-list 'hl-todo-include-modes 'org-mode) :init (global-hl-todo-mode)) ;; git (use-package magit) (use-package git-timemachine) ;; rest APIs via org source block (use-package ob-restclient) ;;; END ;;; (provide 'init-base) ;;; init-base.el ends here
Not really every single one, because straight.el installs dependencies automatically. Here's the file I went through during this recording. Some things may have changed slightly since the time of recording. Save this file in ~/.emacs.d/init.el to reproduce my exact Emacs configuration that I use at home and at work. ;;; init.el --- This is Tiago's init.el file ;;; Commentary: ;;; Thanks to everyone that curates Emacs packages. ;;; Code: ;; BEGIN Straight.el bootstrap (defvar bootstrap-version) (let ((bootstrap-file (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory)) (bootstrap-version 6)) (unless (file-exists-p bootstrap-file) (with-current-buffer (url-retrieve-synchronously "https://raw.githubusercontent.com/radian-software/straight.el/develop/install.el" 'silent 'inhibit-cookies) (goto-char (point-max)) (eval-print-last-sexp))) (load bootstrap-file nil 'nomessage)) ;; END Straight.el bootstrap (straight-use-package 'use-package) (setq straight-use-package-by-default t) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; > ;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Get minor modes off the modeline (use-package diminish) (use-package evil :init (setq evil-want-keybinding nil) :config (evil-mode) :custom (evil-undo-system 'undo-redo) :bind ("C-u" . evil-scroll-up)) (use-package evil-collection :diminish evil-collection-unimpaired-mode :after evil :config (evil-collection-init)) (use-package evil-surround :after evil :config (global-evil-surround-mode 1)) ;; In-Buffer Completion (use-package company :diminish :config (global-company-mode)) ;; completion with extra info box (use-package company-box :diminish :hook (company-mode . company-box-mode)) ;; Show key bindings as you go (use-package which-key :diminish :config (which-key-mode)) ;; search query feedback in the buffer (use-package anzu :diminish :config (global-anzu-mode +1)) (use-package evil-anzu) ;; Completion in the minibuffer (snippet from vertico) (use-package vertico :init (vertico-mode) ;; Different scroll margin ;; (setq vertico-scroll-margin 0) ;; Show more candidates ;; (setq vertico-count 20) ;; Grow and shrink the Vertico minibuffer ;; (setq vertico-resize t) ;; Optionally enable cycling for `vertico-next' and `vertico-previous'. ;; (setq vertico-cycle t) ) ;; Persist history over Emacs restarts. Vertico sorts by history position. ;; (use-package savehist ;; :init ;; (savehist-mode)) ;; A few more useful configurations... (use-package emacs :init ;; Add prompt indicator to `completing-read-multiple'. ;; We display [CRM], e.g., [CRM,] if the separator is a comma. (defun crm-indicator (args) (cons (format "[CRM%s] %s" (replace-regexp-in-string "`[.*?]*|[.*?]*'" "" crm-separator) (car args)) (cdr args))) (advice-add #'completing-read-multiple :filter-args #'crm-indicator) ;; Do not allow the cursor in the minibuffer prompt (setq minibuffer-prompt-properties '(read-only t cursor-intangible t face minibuffer-prompt)) (add-hook 'minibuffer-setup-hook #'cursor-intangible-mode) ;; Emacs 28: Hide commands in M-x which do not work in the current mode. ;; Vertico commands are hidden in normal buffers. ;; (setq read-extended-command-predicate ;; #'command-completion-default-include-p) ;; Enable recursive minibuffers (setq enable-recursive-minibuffers t)) ;; Optionally use the `orderless' completion style. ;; Get completion even if you type substrings that don't match in the ;; same order you typed them in. (use-package orderless :init ;; Configure a custom style dispatcher (see the Consult wiki) ;; (setq orderless-style-dispatchers '(+orderless-consult-dispatch orderless-affix-dispatch) ;; orderless-component-separator #'orderless-escapable-split-on-space) (setq completion-styles '(orderless basic) completion-category-defaults nil completion-category-overrides '((file (styles partial-completion))))) ;; Enable rich annotations in the completion (use-package marginalia ;; Either bind `marginalia-cycle' globally or only in the minibuffer :bind (("M-A" . marginalia-cycle) :map minibuffer-local-map ("M-A" . marginalia-cycle)) ;; The :init configuration is always executed (Not lazy!) :init ;; Must be in the :init section of use-package such that the mode gets ;; enabled right away. Note that this forces loading the package. (marginalia-mode)) ;; Searching commands and lots of other stuff ;; This is a snippet taken from consult (use-package consult ;; Replace bindings. Lazily loaded due by `use-package'. :bind (;; C-c bindings in `mode-specific-map' ("C-c M-x" . consult-mode-command) ("C-c h" . consult-history) ("C-c k" . consult-kmacro) ("C-c m" . consult-man) ("C-c i" . consult-info) ([remap Info-search] . consult-info) ;; C-x bindings in `ctl-x-map' ("C-x M-:" . consult-complex-command) ;; orig. repeat-complex-command ("C-x b" . consult-buffer) ;; orig. switch-to-buffer ("C-x 4 b" . consult-buffer-other-window) ;; orig. switch-to-buffer-other-window ("C-x 5 b" . consult-buffer-other-frame) ;; orig. switch-to-buffer-other-frame ("C-x r b" . consult-bookmark) ;; orig. bookmark-jump ("C-x p b" . consult-project-buffer) ;; orig. project-switch-to-buffer ;; Custom M-# bindings for fast register access ("M-#" . consult-register-load) ("M-'" . consult-register-store) ;; orig. abbrev-prefix-mark (unrelated) ("C-M-#" . consult-register) ;; Other custom bindings ("M-y" . consult-yank-pop) ;; orig. yank-pop ;; M-g bindings in `goto-map' ("M-g e" . consult-compile-error) ("M-g f" . consult-flymake) ;; Alternative: consult-flycheck ("M-g g" . consult-goto-line) ;; orig. goto-line ("M-g M-g" . consult-goto-line) ;; orig. goto-line ("M-g o" . consult-outline) ;; Alternative: consult-org-heading ("M-g m" . consult-mark) ("M-g k" . consult-global-mark) ("M-g i" . consult-imenu) ("M-g I" . consult-imenu-multi) ;; M-s bindings in `search-map' ("M-s d" . consult-find) ("M-s D" . consult-locate) ("M-s g" . consult-grep) ("M-s G" . consult-git-grep) ("M-s r" . consult-ripgrep) ("M-s l" . consult-line) ("M-s L" . consult-line-multi) ("M-s k" . consult-keep-lines) ("M-s u" . consult-focus-lines) ;; Isearch integration ("M-s e" . consult-isearch-history) :map isearch-mode-map ("M-e" . consult-isearch-history) ;; orig. isearch-edit-string ("M-s e" . consult-isearch-history) ;; orig. isearch-edit-string ("M-s l" . consult-line) ;; needed by consult-line to detect isearch ("M-s L" . consult-line-multi) ;; needed by consult-line to detect isearch ;; Minibuffer history :map minibuffer-local-map ("M-s" . consult-history) ;; orig. next-matching-history-element ("M-r" . consult-history)) ;; orig. previous-matching-history-element ;; Enable automatic preview at point in the *Completions* buffer. This is ;; relevant when you use the default completion UI. :hook (completion-list-mode . consult-preview-at-point-mode) ;; The :init configuration is always executed (Not lazy) :init ;; Optionally configure the register formatting. This improves the register ;; preview for `consult-register', `consult-register-load', ;; `consult-register-store' and the Emacs built-ins. (setq register-preview-delay 0.5 register-preview-function #'consult-register-format) ;; Optionally tweak the register preview window. ;; This adds thin lines, sorting and hides the mode line of the window. (advice-add #'register-preview :override #'consult-register-window) ;; Use Consult to select xref locations with preview (setq xref-show-xrefs-function #'consult-xref xref-show-definitions-function #'consult-xref) ;; Configure other variables and modes in the :config section, ;; after lazily loading the package. :config ;; Optionally configure preview. The default value ;; is 'any, such that any key triggers the preview. ;; (setq consult-preview-key 'any) ;; (setq consult-preview-key "M-.") ;; (setq consult-preview-key '("S-" "S-")) ;; For some commands and buffer sources it is useful to configure the ;; :preview-key on a per-command basis using the `consult-customize' macro. (consult-customize consult-theme :preview-key '(:debounce 0.2 any) consult-ripgrep consult-git-grep consult-grep consult-bookmark consult-recent-file consult-xref consult--source-bookmark consult--source-file-register consult--source-recent-file consult--source-project-recent-file ;; :preview-key "M-." :preview-key '(:debounce 0.4 any)) ;; Optionally configure the narrowing key. ;; Both < and C-+ work reasonably well. (setq consult-narrow-key "
Avi Freedman, CEO at Kentik, joins Corey on Screaming in the Cloud to discuss the fun of solving for observability. Corey and Avi discuss how great simplicity can be deceiving, and Avi points out that with great simplicity comes great complexity. Avi discusses examples of this that he sees in Kentik customer environments, as well as the differences he sees in cloud environments from traditional data center environments. Avi also reveals his predictions for the future and how enterprise M&A will affect the way companies view data centers and VPCs. About AviAvi Freedman is the co-founder and CEO of network observability company Kentik. He has decades of experience as a networking technologist and executive. As a network pioneer in 1992, Freedman started Philadelphia's first ISP, known as netaxs. He went on to run network operations at Akamai for over a decade as VP of network infrastructure and then as chief network scientist. He also ran the network at AboveNet and was the CTO of ServerCentral.Links Referenced: Kentik: https://kentik.com Email: avi@kentik.com Twitter: https://twitter.com/avifreedman LinkedIn: https://www.linkedin.com/in/avifreedman TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Most Companies find out way too late that they've been breached. Thinkst Canary changes this. Deploy Canaries and Canarytokens in minutes and then forget about them. Attackers tip their hand by touching 'em giving you the one alert, when it matters. With 0 admin overhead and almost no false-positives, Canaries are deployed (and loved) on all 7 continents. Check out what people are saying at canary.love today!Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. This promoted guest episode is brought to us by our friends at Kentik. And into my social grist mill, they have thrown Avi Freedman, their CEO. Avi, thank you for joining me.Avi: Thank you for having me, Corey. I've been a big fan for some time, I have never actually fallen off my seat laughing, but I've come close a couple times on some of your threads.Corey: You must have a great chair.Avi: I should probably upgrade it [laugh].Corey: [laugh]. I have been looking forward to this conversation for a while because you are one of those rare creatures who comes from a similar world to what I did where we were grumpy and old before our time because we worked on physical infrastructure in data centers, we basically wrangled servers into doing the things that we wanted them to do when hardware reliability was an aspiration rather than a reality. And we also moved on from that, in many ways. We are not blind to the modern order of how computers work. But you still run a lot of what you do in data centers, but many of your customers are in cloud. You speak both languages very fluently because of the unifying thread between all of this, which is, of course, the network. How did you wind up in, I guess we'll call it network hell.Avi: [laugh]. I mean, network hell was truly… in the '90s, when the internet was—I mean, the internet is sort of like the human body: the more you study it, the more amazing it is that it ever worked in the first place, not that it breaks sometimes—was the bugs, and trying to put together the technology back then, you know, that we had the life is pretty good nowadays, other than the [laugh] immense complexity that has been unleashed on us by everyone taking the same technology and then writing it in their own software and giving it their own marketing names. And thus, you have multi-cloud networking. So, got into it because it's a problem that needs to be solved, right? There's no ESP that connects the applications together; the network still needs to make it work. And now people own some of it, and then more of it, they don't own, but they're still responsible for it. So, it's a fun problem to solve.Corey: The timing of this episode is apt because I've used Kentik myself for a few things over the years. And to be fair, using it for any of my personal networking problems is a bit like noticing, “Oh, I have a loose thread here on my shirt. Pass me the chainsaw.” It's, my environment is tiny and it's over-scoped. But I just earlier this week wound up having to analyze a day's worth of Flow Logs from one of my clients, and to do this, I had to spin up an EC2 instance with 128 gigs of RAM and then load the Flow Logs for that day into RAM, and then—not kidding—I ran into OOM Killer because I ran out of RAM on this thing.Avi: [laugh].Corey: It is, like, yeah, that's right. The network is chatty, the logs are immense, and it's easy to forget. Because the reason I was doing this was just to figure out what are the things that are talking to each other in this environment to drive up some aspects of data transfer costs. But that is an esoteric use case for this; it's not why most people tend to think about network observability. So, I'm going to ask you the blunt question up front here because it might be a really short episode. Do we have to care about networking in the least now that cloud is the default in most locations? It is just an API call away, isn't it?Avi: With great simplicity comes great complexity. So, to the people running infrastructure, to developers or architects, turning it all on, it looks like just API calls. But did you set the policies right? Can the things talk to each other? Are they talking in patterns that are causing you wild data transfer costs?All these things ultimately come back to some team that actually has to make it go. And can be pretty hard to figure that out, right, because it's not just the VPC Flow Logs. It's, what's the policy? It's, what are they talking to that maybe isn't in that cloud, that's maybe in another cloud? So, how do you bring it all together? Like, you could have—and maybe you should have—used Athena, right? You can put VPC Flow Logs in S3 buckets and use Athena and run SQL queries if all you want is your top talker.Corey: Oh, I did. That's how I started, but Athena is, uh… it has some challenges. Let's just put it that way and leave it there. DuckDB is what I was using and I'm much happier with it for a variety of excellent reasons.Avi: Okay. Well, I'll tease you another time about, you know—I lost this battle at Kentik. We actually don't use swap, but I'm a big fan of having swap and monitoring it so the OOM Killer only does what you want or doesn't fire at all. But that's a separate religious debate.Corey: There's a counterargument of running an in-memory data store. And then oh, we're going to use it as swap though, so it's like, hang on, this just feels like running a normal database with extra steps.Avi: Computers allow you to do amazing things and only occasionally slap you nowadays with it. It's pretty amazing. But back to the question. APIs make it easy to turn on, but not so easy to run. The observability that you get within a given cloud is typically very limited.Google actually has the best. They show some topology and other things. I mean, a lot of what we do involves scraping API calls in the cloud to figure out what does this all mean, then convolving it with the VPC Flow Logs and making it look like a network, and what are the gateways, and what are the rules being applied and what can't talk to itself? If you just look at VPC Flow Logs like it's Syslog, good luck trying to figure out what VPCs are talking to each other. It's exactly the problem that you were describing.So, the ease of turning it on is exactly inversely proportional to the ease of running it. And, you know, as a vendor, we think it's an awesome [laugh] problem, but we feel for our customers. And you know, occasionally it's a pain to get the IAM roles set up to scrape things and help them, but that's you know, that's just part of the job.Corey: It's fascinating to me, just looking from an AWS perspective, just how much work clearly has to be done to translate their Byzantine and very strange networking environment and concepts into things that customers see. Because in many cases, the things that the virtual machines that we've run on top of EC2, let alone anything higher level, is being lied to the entire time about what the actual topology of the environment is. It was most notable, for me at least, at re:Invent 2022, the most recent one, where they announced they have a TCP replacement, scalable, reliable data grammar SRD. It's a new protocol entirely. It's, “Oh, wow, can we use it?” “No.” “Okay.” Like, I get that it's a lot of work, I get you're excited about it. Are you going to talk to us about how it actually works? “Oh, absolutely not.” So… okay, good for you, I guess.Avi: Doesn't Amazon have to write a press release before they build anything, and doesn't the press release have to say, like, why people give a shit, why people care?Corey: Yep. And their story on this was oh, it enables us to be a lot faster at letting EBS volumes talk to some of our beefier instances.Avi: [laugh].Corey: And that's all well and good, don't get me wrong, but it's also, “Yay, it's more reliable,” is a difficult message to send. I mean, it's hard enough when—and it's necessary because you've got to tacitly admit that reliability and performance haven't been all they could be. But when it's no longer an issue for most folks, now you're making them wonder, like, wait, how bad was it? It's just a strange message.Avi: Yeah. One of my projects for this weekend is, I actually got a gaming PC and I'm going to try compression offload to the CUDA cores because right now, we do compress and decompress with Intel cores. And like, if I'm successful there and we can get 30% faster subqueries—which doesn't really matter, you know, on the kind of massive queries we run—and 20% more use out of the computers that we actually run, I'm probably not going to do a press release about it. But good to see the pattern.But you know, what you said is pretty interesting. As people like Kentik, we have to put together, well, on Azure, you can have VPCs that cross regions, right? And in other places, you can't. And in Google, you have performance metrics that come out and you can get it very frequently, and in Amazon and Azure, you can't. Like, how do you take these kinds of telemetry that are all the same stuff underneath, but packaged up differently in different quantos and different things and make it all look the same is actually pretty fun and interesting.And it's pretty—you know, if you give some cloud engineers who focus on the infrastructure layer enough beers or alcohol or just room to talk, you can hear some funny stories. And it all made sense to somebody in the first place, but unpacking it and actually running it as a common infrastructure can be quite fun.Corey: One of the things that I have found notable about your perspective, as particularly, you're running all of the network ingest, to my understanding, in your data center environment. Because we talked about this when you were kind enough to invite me to your company all-hands offsite, presumably I assume when people do that, it's so they can beat me up in the alley, but that only happened twice. I was very pleasantly surprised.Avi: [And you 00:09:23] made fun of us only three times, so you know, you beat us—Corey: Exactly.Avi: —but it was all enjoyed.Corey: But always with love. Now, what I found fascinating was you and I sat down for a while and you talked about your data center architecture. And you asked me—since I don't have anything to sell you—is there an economical way that I could see running your environment on top of AWS? And the answer was sure, if by economical you mean an absolute minimum of six times what you're currently paying a year, sure you can get there. But it just does not make sense for any realistic approach to doing this.And the reason I bring this up is that you're in a data center not because of religious beliefs, “Of, well, this is good enough for my grandpappy, so it's good enough for me.” It's because it solves the problem you have in a way that the cloud providers clearly cannot. But you also are not anti-cloud. So, many folks who are all-in on data centers seem to be doing it out of pure self-interest where, well, if everyone goes all-in on cloud, then we have nothing left to sell them. I've used AWS VPC Flow Logs. They have nothing that could even remotely be termed network observability. Your future is assured as long as people understand what it is that you're providing them and what are you that adds. So yeah, people keep going in a cloud direction, you're happy as houses.Avi: We'll use the best tools for building our infrastructure that we can, right? We use cloud. In fact, we're just buying some reserved instances, which always, you know, I give it the hairy eyeball, but you know, we're probably always going to have our CI/CD bursty stuff in the cloud. We have performance testing regions on all the major clouds so that we can tell people what performance is to and from cloud. Like, that we have to use cloud for.And if there's an always-on model, which starts making sense in the cloud, then I try not to be the first to use anything, but [laugh] we'll be one of the first to use it. But every year, we talk to, you know, the major clouds because we're customers of all them, for as I said, our testing infrastructure if nothing else, and you know, some of them for some other parts, you know, for example, proxying VPC Flow Logs, we run infrastructure on Kubernetes in all—in the three biggest to proxy VPC Flow Logs, you know, and so that's part of our bill. But if something's always on, you know, one of our storage servers, it's a $15,000 machine that, you know, realistically runs five years, but even if you assume it runs three years, we get financing for it, cost a couple $100 a month to host, and that's inclusive of our ops team that runs, sort of, everything, you just do the math. That same machine would be, you know, even not including data transfer would be maybe 3500 a month on cloud. The economics just don't quite make sense.For burst, for things like CI/CD, test, seasonality, I think it's great. And if we have patterns like that, you know, we're the first to use it. So, it's just a question of using what's best. And a lot of our customers are in that realm, too. I would say some of them are a little over-rotated, you know, they've had big mandates to go one way or the other and don't have the right, you know, sort of nuanced view, but I think over time, that's going to fix itself. And yeah, as you were saying, like, the more people use cloud, the better we do, so it's just really a question of what's the best for us at our infrastructure and at any given time.Corey: I think that that is something that is not fully appreciated or well understood is that I work with cloud technologies because for what I do, it makes an awful lot of sense. But I've been lately doing a significant build-out in my home network on the perspective of yeah, this makes sense for what I do. And I now have increased number of workloads that I'm running here and I got to say, it feels a little strange, on some level, not to be paying AWS on something metered by the second whenever I'm running a job here. That always feels a little on the weird side. But I'm not suggesting I filled my house with servers either.Avi: [unintelligible 00:13:18] going to report you to the House on Cloudian Activities Committee [laugh] for—Corey: [laugh].Avi: To straighten you out about your infrastructure use and beliefs. I do have to ask you, and I do have some foreknowledge of this, where is the controller for your network running? Is it running in your house or—Corey: Oh, the WiFi controller lives in Ohio with all the other unpleasant things. I mean, even data transfer between Ohio and Virginia—if you're on AWS—is half-price because data wants to get out of Ohio just as much as the people do. And that's fine, but it can also fail out of band. I can chill that thing for a while and I'm not able to provision new equipment, I can't spin up new SSIDs, but—Avi: Right. It's the same as [kale scale 00:14:00], which is, like, sufficiently indistinguishable from magic, but it's nice there's [head scale 00:14:05] in case something happened to them. But yeah, you know, you just can't set up new stuff without your SSHing old way while it's down. So.Corey: And worst case, it goes away irretrievably, I can spin a new one up, I can pair everything locally, do it by repointing DNS locally, and life will go on. It's one of those areas where, like, I would not have this in Ohio if latency was a concern if it was routing every packet out halfway across the country before it hit the general internet. That would be a challenge for me. But that's not what I'm doing.Avi: Yeah, yeah. No, that makes sense. And I think also—Corey: And I certainly pay AWS by the second for that thing. That's—I have a three-year savings plan for that thing, and if nothing else, it was useful for me just to figure out what the living hell was going on with the savings plan purchase project one year. That was just, it was challenged to get that straightened out in some ways. Turns out that the high watermark of the console is a hundred-and-some-odd-thirty-million dollars you can add to cart and click the buy button. Have fun.Avi: My goodness. Okay, well.Corey: The API goes up to $26.2 billion. Try that in a free tier account, preferably someone else's.Avi: I would love to have such problems. Right now, that is not one of them. We don't spend that much on infrastructure.Corey: Oh, that is more than Amazon's—AWS's at least—quarterly revenue. So, if you wind up doing a $26.2 billion, it's like—it's that old saw. You owe Amazon a million dollars, you have a problem. If you owe Amazon $26 billion, Amazon has a problem. Yeah, that's when Andy Jassy calls you 20 minutes after you make that purchase, and at least to me, he yells at me with a, “Listen here, asshole,” and it sort of devolves from there.Avi: Well, I do live in Seattle, so you know, they send the posse out, I'm pretty sure.Corey: [laugh] I will be keynoting DevOpsDays Seattle on August 1st with a talk that might very well resonate with your perspective, “The Modern Devops: A Million Ways to Die in Production.”Avi: That is very cool. I mean, ultimately, I think that's what cloud comes back to. When cloud was being formed, it's just other people's computers, storage, and network. I don't know if you'd argue that there's a politics, control plane, or a—Corey: Oh, I would say, “Cloud? There's no cloud; just someone else's cost center.”Avi: Exactly. And so, how do you configure it? And back to the question of, should everything be on-prem or does cloud abstract at all, it's all the same stuff that we've been doing for decades and decades, just with other people's software and names, which you help decode. And then it's the question we've always had: what's the best thing to do? Do you like [Wellfleet 00:16:33] or [Protion 00:16:35]? Now, do you like Azure [laugh] or Google or Amazon or somebody else or running your own?Corey: It's almost this generation's equivalent of Vi versus Emacs.Avi: Yes. I guess there could be a crowd equivalent. I use VI, but only because I'm a lisp addict and I don't want to get stuck refining Eliza macros and connecting to the ChatGPT in Emacs. So, you know. Someone just did a Emacs as PID 0. So basically, no init, just, you know, the kernel boots into Emacs, and then someone of course had to do a VI as PID 0. And I have to admit, Emacs would be a lot more useful as a PID 0, even though I use VI.Corey: I would say that—I mean, you wind up in writing in Emacs and writing lisp in it, then I've got to say every third thing you say becomes a parenthetical.Avi: Exactly. Ha.Corey: But I want to say that there's also a definite moving of data going on there that I think is a scale that, for those of us working mostly in home labs and whatnot, can be hard to imagine. And I see that just in terms of the volume of Flow Logs, which to be clear, are smaller than the data transfer they are representing in almost every case.Avi: Almost every.Corey: You see so much of the telemetry that comes out of there and what customers are seeing and what their problems are, in different ways. It's not just Flow Logs, you ingest a whole bunch of different telemetry through a variety of modern and ancient and everything in between variety of protocols to support, you know, the horror that is network equipment interoperability. And just, I can't—I feel like I can't do a terrific job of doing justice to describing just how comprehensive Kentik is, once you get it set up as a product. What is on the wire has always been for me the arbiter of truth because computers will lie to you, but it's very tricky to get them to lie and get the network story to cover for it.Avi: Right. I mean, ultimately, that's one of the sources of truth. There's routing, there's performance testing, there's a whole lot of different things, and as you were saying, in any one of these slices of your, let's just pick the network. There's many different things that all mean the same, but look different that you need to put together. You could—the nerd term would be, you know, normalizing. You need to take all this stuff and normalize it.But traffic, we agree, that's where we started with. We call it the what if what is. What's actually happening on the infrastructure and that's the ancient stuff like IPFIX and NetFlow and sFlow. Some people that would argue that, you know, the [IATF 00:19:04] would say, “Oh, we're still innovating and it's still current,” but you know, it's certainly on-prem only. The major cloud vendors would say, “Oh, well, you can run the router—cloud routers—or you could run cloud versions of the big routers,” but we don't really see that as a super common pattern today.But what's really the difference between NetFlow and the VPC Flow Log? Well, some VPC Flow Logs have permit deny because they're really firewall logs, but ultimately, it's something went from here to there. There might not be a TCP flag, but there might be something else in cloud. And, you know, maybe there's rum data, which is also another kind of traffic. And ultimately, all together, we try to take that and then the business metadata to say, whether it's NetBox in the old world or Kubernetes in the new world, or some other [unintelligible 00:19:49], what application is this? What user is this?So, you can ask questions about why am I blowing up between these cloud regions? What applications are doing it, right? VPC Flow Logs by themselves don't know that, so you need to add that kind of metadata in. And then there's performance testing, which is sort of the what is. Something we do, Thousand Eyes does, some other people do.It's not the actual source of truth, but for example, if you're having a performance problem getting between, you know, us-east and Azure in the east, well, there's three other ways you can get there. If your actual traffic isn't getting there that way, then how do you know which one to use? Well, let's fire up some tests. There's all the metrics on what all of the devices are reporting, just like you get metrics from your machines and from your applications, and then there's stuff even up at the routing layer, which God help you, hopefully you don't need to actually get in and debug, but sometimes you do. And sometimes, you know, your neighbor tells the mailman that that mail is for me and not for you and they believe them and then you have a big problem when your bills don't get paid.The same thing happens in the cloud, the same thing happens on the internet [unintelligible 00:20:52] at the routing. So, the goal is, take all the different sources of it, make it the same within each type, and then pull it all together so you can look at a single place, you can look at a map, you can look at everything, whether it's the cloud, whether it's your own data centers, your own WAN, into the internet and in between in a coherent way that understands your application. So, it's a small task that we've bit off, but you know, we have fun solving it.Corey: Do you find that when you look at customer environments, that they are, and I don't mean to be disparaging here, truly I don't, but if you were to ask me to design something today, I would probably not even be using VPCs if I'm doing this completely greenfield. I would be a lot more cloud-first, et cetera, et cetera. Whereas in many cases, that is not the right path, especially if you know, customers have the temerity to not be founded within the last 18 months before AWS existed in some ways. Do you find that the majority of what they're doing looks like they're treating the cloud like data centers or do you find that they are leveraging cloud in ways that surprise you and would not be possible in traditional data centers? Because I can't shake the feeling that the network has a source of truth for figuring out what's really going on [is very hard to beat 00:22:05].Avi: Yes, for the most part, to both your assertion at the end and sort of the question. So, in terms of the question, for the most part, people think of VPCs as… you know, they could just equivalent be VLANs and [unintelligible 00:22:21], right? I've got policies, and I have these things that are talking to each other, and everything else is not local. And I've got—you know, it's not a perfect mapping to physical interfaces in VLANs but it's the equivalent of that.And that is sort of how people think about it. In the data center, you'd call it micro-segmentation, in the cloud, you call it clouding, but you know, just applying all the same policies and saying this stuff can talk to each other and not. Which is always sort of interesting, if you don't actually know what is talking [laugh] to each other to apply those policies. Which is a lot of what you know, Kentik gets brought in for first. I think where we see the cloud-native thinking, which is overlaid on top of that—you could call it overlay, I guess—which is service mesh.Now, putting aside the question of what's going to be a service mesh, what's going to be a network mesh, where there's something like [unintelligible 00:23:13] sit, the idea that there's a way that you look at traffic above the packets at, you know, layers three to more layer seven, that can do things like load balancing, do things like telemetry, do things like policy enforcement, that is a layer that we see very commonly that a lot of the old school folks have—you know, they want their lsu F5s and they want their F5 script. And they're like, “Why can't I have this in the cloud?”—which I guess you could buy it from F5 if you really want—but that's pretty common. Now, not everything's a sidecar anymore and there's still debates about what's going on there, but that's pretty common, even where the underlying cloud just looks like it could just be a data center.And that seems to be state of the art, I would say, our traditional enterprise customers, for sure. Our web company customers, and you know, service providers use cloud more for their OTT and some other things. As we work with them, they're a little bit more likely to be on-prem, you know, historic. But remember, in the enterprise, there's still a lot of M&A going on, I think that's even going to pick up in the next couple of years and a lot of what they're doing is lift-and-shift of [laugh] actual data centers. And my theory is, it's got to be easier to just make it look like VPCs than completely redo it.Corey: I'd say that there's reasons that things are the way that they are. Like, ignoring that this is the better approach from a technical perspective entirely because that's often not the only answer, it's we have assurances we made as part of audit compliance regimes, of our SOC 2, of how we handle certain things and what those controls are. And yeah, it's not hard for even a junior employee, most of the time, to design a reasonable architecture on a whiteboard. The problem is, how do you take something pre-existing and get it to a state that closely resembles that while not turning it off for a long time?Avi: Right. And I think we're starting to see some things that probably shouldn't exist, like, people trying to do VXLAN as overlays into and between VPCs because that was how their data s—you know, they're more modern on the data center side and trying to do that. But generally, I think people have an understanding they need to be designing architecture for greenfield things that aren't too far bleeding edge, unless it's like a pure developer shop, and also can map to the least common denominator kinds of infrastructure that people have. Now, sometimes that may be serverless, which means, you know, more CDN use and abstracted layers in front, but for, you know, running your own components, we see a lot of differences but also a lot of commonality. It's differences at the micro but commonality the macro. And I don't know what you see in your practice. So.Corey: I will say that what I see in practice is that there's a dichotomy where you have born-in-the-cloud companies where 80% of their spend is on a single workload and you can do a whole bunch of deep optimizations. And then you see the conglomerate approach where it's giant spend, but it's all very diffuse across 1500 different applications. And different philosophies, different processes, different cultures give rise to a lot of these things. I will say that if I had a magic wand, I would—and again, the fact that you sponsor and promote this episode is deeply appreciated. Thank you—Avi: You're welcome.Corey: —but it does not mean that you get to compromise my authenticity and objectivity. You can't buy my opinion, just my attention. But I will say this, that I would love it if my customers used Kentik because it is one of the best things I've ever seen to describe what is talking to what that scale and in volume without going super deep into the weeds. Now, obviously, I'm not allowed to start rolling out random things into customer environments. That's how I get sued to death. But, ugh, I wish it was there.Avi: You probably shouldn't set up IAM rules without asking them, yes. That wouldn't be bad.Corey: There's a reason that the only writable stuff that I have access to is generating reports in Cost Explorer.Avi: [laugh]. Okay.Corey: Everything else is read-only. All we do is to have conversations with folks. It sets context for those conversations. I used to think that we'd be doing this as a software offering. I no longer believe that actually solves the in-depth problems that people have.Avi: Well, I appreciate the praise. I even take some of the backhanded praise slash critique at the beginning because we think a lot about, you know, we did design for these complex and often hybrid infrastructures and it's true, we didn't design it for the two or four router, you know, infrastructure. If we had bootstrapped longer, if we'd done some other things, we might have done it that way. We don't want to be exclusionary. It's just sort of how we focus.But in the kind of customers that you have, these are things that we're thinking about what can we do to make it easier to onboard because people have these massive challenges seeing the traffic and understanding it and the cost and security and the performance, but to do more with the VPC Flow Logs, we need to get some of those metrics. We think about should we make an open-source thing. I don't know how much you've seen the concern that people have universally across cloud providers that they turn on something like Kentik, and they're going to hit their API rate limiter. Which is like, really, you can't build a cache for that at the scale that these guys run at, the large cloud providers. I don't really understand that. But it is what it is.We spent a lot of time thinking about that because of security policy, and getting the kind of metrics that we need. You know, if we open-source some of that, would it make it easier, plug it into people's observability infrastructure, we'd like to get that onboarding time down, even for those more complex infrastructures. But you know, the payoff is there, you know? It only takes a day of elapsed time and one hour or so. It's just you got to get a lot of approvals to get the kind of telemetry that you need to make sense of this in some environments.Corey: Oh, yes. And that's part of the problem, too, is like, you could talk about one of those big environments where you have 1500 apps all talking to each other. You can't make sense of any of it without talking to people and having contacts and occasionally get a little bit of [unintelligible 00:29:07] just what these things are named. But at that point, you're just speculating wildly. And, you know, it's an engineering trap, where I'm just going to guess rather than asking someone who knows the answer because I don't want to look foolish. It's… you just three weeks chasing your own tail. Who's the foolish one?Avi: We're not in a competitive business to yours—Corey: [laugh].Avi: But I do often ask when we're starting off, “So, can you point us at the source of truth that describes what all your applications are?” And usually, they're, like, “[laugh]. No.” But you know, at the same time to make sense of this stuff, you also need that metadata and that's something that we designed to be able to take.Now, Kubernetes has some of that. You may have some of it in ServiceNow, a lot of people use. You may have it in your own text file, CSV somewhere. It may be in NetBox, which we've seen people actually use for the cloud, more on the web company and service provider side, but even some traditional enterprise is starting to use it. So, a lot of what we have to do as a vendor is put all that together because yeah, when you're running across multiple environments and thousands of applications, ultimately scrying at IP addresses and VPC IDs is not going to be sufficient.So, the good news is, almost everybody has those sources and we just tried to drag it out of them and pull it back together. And for now, we refuse to actually try to get into that business because it's not a—seems sort of like, you know, SAP where you're going to be sending consultants forever, and not as interesting as the problems we're trying to solve.Corey: I really want to thank you, not just for supporting the show of course, but also for coming here to suffer my slings and arrows. If people want to learn more, where's the best place for them to find you? And please don't respond with an IP address.Avi: 127.0.0.1. You're welcome at my home at any time.Corey: There's no place like localhost.Avi: There's no place like localhost. Indeed. So, the company is kentik.com, K-E-N-T-I-K. I am avi@kentik.com. I am@avifriedman on Twitter and LinkedIn and some other things. And happy to chat with nerds, infrastructure nerds, cloud nerds, network nerds, software nerds, debate, maybe not VI versus Emacs, but should you swap space or not, and what should your cloud architecture look like?Corey: And we will, of course, put links to that in the [show notes 00:31:20].Avi: Thank you.Corey: Thank you so much for being so generous with your time. I really appreciate it.Avi: Thank you for having this forum. And I will let you know when I am down in San Francisco with some time.Corey: I would be offended if you didn't take the time to at least say hello. Avi Friedman, CEO at Kentik. I'm Cloud Economist Corey Quinn, and this has been a promoted guest episode of Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a all five-star review on your podcast platform of choice, along with an angry comment saying how everything, start to finish, is somehow because of the network.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.
Kenneth Rose, CTO at OpsLevel, joins Corey on Screaming in the Cloud to discuss how OpsLevel is helping developer teams to scale effectively. Kenneth reveals what a developer portal is, how he thinks about the functionality of a developer portal, and the problems a developer portal solves for large developer teams. Corey and Kenneth discuss how to drive adoption of a developer portal, and Kenneth explains why it's so necessary to have executive buy-in throughout that process. Kenneth also discusses how using their own portal internally along with seeking out customer feedback has allowed OpsLevel to make impactful innovations. About KenKenneth (Ken) Rose is the CTO and Co-Founder of OpsLevel. Ken has spent over 15 years scaling engineering teams as an early engineer at PagerDuty and Shopify. Having in-the-trenches experience has allowed Ken a unique perspective on how some of the best teams are built and scaled and lends this viewpoint to building products for OpsLevel, a service ownership platform built to turn chaos into consistency for engineering leaders.Links Referenced: OpsLevel: https://www.opslevel.com/ LinkedIn: https://www.linkedin.com/company/opslevel/ Twitter: https://twitter.com/OpsLevelHQ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn, about, oh I don't know, two years ago and change, I wound up writing a blog post titled, “Developer Portals are An Anti Pattern,” and I haven't really spent a lot of time thinking about them since. This promoted guest episode is brought to us by our friends at OpsLevel, and they have sent their CTO and co-founder Ken Rose, presumably in an attempt to change my perspective on these things. Let's find out. Ken, thank you for agreeing to, well, run the gauntlet, for lack of a better term.Ken: Hey, Corey. Thanks again for having me. And I've heard, you know, heard and listened to your show a bunch, and really excited to be here today.Corey: Let's begin with defining our terms. I'm curious to know what a developer portal is. ‘What would you say a developer portal means to you?' Like it's a college entrance essay.Ken: Right? Definitely. You know, so really, a developer portal is this consolidated place for developers to come to, especially in large organizations to be able to get their jobs done more easily, right? A large challenge that developers have in large organizations, there's just a lot to do and a lot to take care of. So, a developer portal is a place for developers to be able to better own, manage, and run the services, they're responsible for that run in production, and they can do that through access, easy access to self-service tooling.Corey: I guess, on some level, this turns into one of those alignment charts of, like, what is a database and, like, how prescriptive you want to be. It's like, well is a senior engineer a database because you can query them and they have information? Would you consider, for example, Kubernetes be a developer platform, and/or would the AWS console?Ken: Yeah, that's actually an interesting question, right? So, I think there's actually two—we're going to get really niggly here—there's developer platform and developer portal, right? And the word portal for me is something that sits above a developer platform. I don't know if you remember, like, the late-90s, early-2000s, like, portals were all the rage.Like, Yahoo and AltaVistas were like search portals, they were trying to, at the time, consolidate all this information on a much smaller internet to make it easy to access. A developer portal is sort of the same thing, but custom-built for developers and trying to consolidate a lot of the tooling that exists. Now, in terms of the AWS console? Yeah, maybe. Like, it has a suite of tools and suite of offerings. It doesn't do a lot on the well, how do I quickly find out what's running in production and who is responsible for it? I don't know, unless AWS shipped, like, their, you know, three-hundredth new offering in the last week that I haven't, you know, kept on top of.But you know, there's definitely some spectrum in terms of what goes into a developer portal. For me, there's kind of three main things you need. You do need some kind of a catalog, like, what's out there who owns it; you need some kind of a way to measure, like, how good are those services, like, how well built are they; and then you need some access to self-service tooling. And that last part is where, like, the Kubernetes or AWS could be, you know, sort of a dev portal as well.Corey: My experience with developer portals—there was a time when I loved it. RightScale was what I used—at some depth—back in I want to say 2010, 2011 because the EC2 console was clearly not built or designed by anyone who had not built EC2 themselves with their bare hands and sweat of their brow. And in time, the EC2 console got better where it wasn't written in hieroglyphics, as best we could tell, and it became ‘click button to launch instance.' And RightScale really didn't have a second act and they wound up getting acquired by our friends over at Flexera years later. And I haven't seen their developer portal in at least eight years as a direct result of this.So, the problem, at least when I was viewing it purely in the context of AWS services, it feels like you are competing against AWS iterating forward on developer experience, which they iterate slowly, sometimes, and unevenly across their breadth of services, but it does feel like at some level by building an internal portal, you are, first, trying to out-innovate AWS, in some ways, and two, you are inherently making the trade-off of not using recent features and enhancements that have not themselves been incorporated into the portal. That's where the, I guess the start, the genesis of my opposition to the developer portal approach comes from. Is that philosophy valid these days? Not as much. Because I can see an argument for it shifting.Ken: Yeah, I think it's slightly different. I think of a developer portal as again, it's something that sort of sits on top of AWS or Google Cloud or whatever cloud provider use, right? You give an example for example with RightScale and EC2. So, provisioning instances is one part of the activity you have to do as a developer. Now, in most modern organizations, you have, like, your product developers that ship features. They don't actually care about provisioning instance themselves. There are another group called the platform engineers or platform group that are responsible for building automation and tooling to help spin up instances and create CI/CD pipelines and get everything you need set up.And they might use AWS under the covers to do that, but the automation built on top and making that accessible to developers, that's really what a developer portal can provide. In addition, it also provides links to operational tooling that you need, technical documentation, it's everything you need as a developer to do your job, in one place. And though AWs bills itself is that, I think of them as more, they have a lot of platform offerings, right, they have a lot of infra-offerings, but they still haven't been able to, I think, customize that, unless you're an organization that builds—that has kind of gone in-all on AWS and doesn't build any of your own tooling, that's where a developer portal helps. It really helps by consolidating all that information in one place, by making that information discoverable for every developer so they have less… less cognitive load, right? We've asked developers to kind of do too much that we don't… we've asked to shift left and well, how do we make that information more accessible?Regarding the point of, you know, AWS adds new features or new capabilities all the time and, like, well you have this dev portal, that's sort of your interface for how to get things done. Like, how will you use those? Dev portal doesn't stop you from doing that, right? So, my mental model is, if I'm a developer, and I want to spin up a new service, I can just press a button inside of my dev portal in my company and do that. And I have a service that is built according to the latest standards, it has a CI/CD pipeline, it already has a—you know, it's registered in PagerDuty, it's registered in Datadog, it has all the various bits.And then there's something else that I want to do that isn't really on the golden path because maybe this is some new service or some experiment, nothing stops us from doing that. Like, you still can use all those tools from AWS, you know, kind of raw. And if those prove to be valuable for the rest of the organization, great. They can make their way into the dev portal; they can actually become a source of leverage. But if they're not, then they can also just sit there on the vine. Like, not everything that eight of us ever produces will be used by every company.Corey: Many years ago, I got a Cisco pair of certifications because recession was hitting and I needed to be better at networking. And taking those certifications, in those days before Cisco became the sad corporate dragon with no friends we all know today, they were highly germane and relevant. But I distinctly remember, even now, 15 years later, that there was this entire philosophy of pretend that the entire world is Cisco only, which in networking is absolutely never true. It feels like a lot of the AWS designs and patterns tend to assume, oh yeah, you're going to use AWS services for everything. I have never yet found that to be true, other than when I'm just trying to be obstinate.And hell is interoperability between a bunch of different things. Yes, I may want to spin up an EC2 instance and an AWS load balancer and some S3 storage or whatnot, but I'm also going to want to monitor it with PagerDuty, I'm going to want to have a CDN that isn't CloudFront because most CDN these days don't hate you in quite the same economic ways and are simpler to work with, et cetera, et cetera, et cetera. So, there's definitely a story wherein I've found that there's an—the interoperability of tying these things together is helpful. How do you avoid falling down the trap of oh, everyone should be multi-cloud, single pane of glass at cetera, et cetera? In practice that always seems to turn to custard.Ken: Yeah, I think multi-cloud and single pane of glass are actually two different things. So multi-cloud, like, I agree with you to some sense. Like, pick a cloud and go with it, like, unless you have really good business reasons to go for multi-cloud. And sometimes you do, like, years ago, I worked at PagerDuty, they were multi-cloud for a reliability reason, that hey, if one cloud provider goes down, you don't want [crosstalk 00:08:40]—Corey: They were an example I used all the time for that story—Ken: Right.Corey: —specifically the thing woke you up was homed in a bunch of different places, whereas the marketing site, the onboarding flow, the periphery stuff around it was not because it didn't need to be.Ken: Exactly.Corey: Like, the core business need of wake you up was very much multi-cloud because once upon a time, it wasn't and it went down with the rest of us-east-1 and people weren't woken up to be told their site was on fire.Ken: A hundred percent. And on the kind of like application side where, even then, pick a cloud and go with it, unless there's a really compelling business reason for your business to go multi-cloud. Maybe there's something credits or compliance or availability, right? There might be reasons, but you have to be articulate about whether they're right for you.Now, single pane of glass, I think that's different, right? I do think that's something that, ultimately, is a net boon for developers. In any large organization, there is a myriad of internal tools that have been built. And it's like, well, how do I provision a new topic in the Kafka cluster? How do I actually get access to the AWS console? How do I spin up a new service, right? How do I kind of do these things?And if I'm a developer, I just want to ship features. Like, that's what I'm incented to do, that's what I'm optimizing for. And all this other stuff I have to do as part of my job, but I don't want to have to become, like, a Kubernetes guru to be able to do it, right? So, what a developer portal is trying to do is be that single pane of glass, bringing all these common set of tools and responsibilities that you have as a developer in one place. They're easy to search for, they're easy to find, they're easy to query, they're easy to use.Corey: I should probably have asked this earlier on, but let's disambiguate for a little bit here. Because when I'm setting up to use a new service or product and kick the tires on it, no two explorations really look the same. Whereas at most responsible mature companies that are building products that are—services that are going to production use, they've standardized around a number of different approaches. What does your target customer look like? Is there a certain point of scale, a certain level of complexity, a certain maturity of process?Ken: Absolutely. So, a tool like OpsLevel or a developer portal really only makes sense when you hit some critical mass in terms of the number of services you have running in production, or the number of developers that you have. So, when you hit 20, 30, 50 developers or 20, 30, 50 services, an important part of a developer portal is this catalog of what's out there. Once you kind of hit the Dunbar number of services, like, when you have more than you keep in your head, that's when you start to need tooling like this. If you look at our customer base, they're all you know, kind of medium to large-sized companies. If you're a startup with, like, ten people, OpsLevel is probably not right for you. We use all playable internally at OpsLevel, and you know, like, we're still a small company. It's like, we make it work for us because we know how to get the most out of it, but like, it's not the perfect fit because it's not really meant for, you know, smaller companies.Corey: Oh, I hear you. I think I'm probably… I have a better AWS bill analytic system running internally here at The Duckbill Group than some banks do. So, I hear you on that front.Ken: I believe it.Corey: But also implies to me that there's no OpsLevel prospect or customer deployment that has ever been greenfield. It's always you're building existing things, there's already infrastructure in place, vendors have been selected across the board. You aren't—don't to want to starting a company day one, they're going to all right, time to spin up our AWS account and we're also going to wind up signing up for OpsLevel, from the sound of it.Ken: Correct—Corey: Accurate? Inaccurate?Ken: I think that's actually accurate. Like, a lot of the problems, we solve other problems that come as you start to scale both your product and your engineering team. And it's the problems of complexity.Corey: What do those painful problems look like? In other words, what is someone sitting at home right now listening to this, or driving to work debating whether want to ram a bridge abutment or go into the office depending on their mental state today, what painful problem did they have that OpsLevel is designed to fix?Ken: Yeah, for sure. So, let's help people self-select. So, here's my mental model for any [unintelligible 00:12:25]. There are product developers, platform developers, and engineering leaders. Product developers, if you're asking questions like, “I just got paged for the service. I don't know what this does.” Or, “It's upstream from here. Where do I find the technical documentation?” Or, “I think I have to do something with the payment service. Where do I find the API for that?”You know, when you get to that scale, a developer portal can help you. If you're a platform engineer and you have questions like, “Okay, we got to migrate. We're migrating, I don't know, from Datadog to Honeycomb, right? We got to get these fifty or a hundred or thousands of services and all these different owners to, like, switch to some new tool.” Or, “Hey, we've done all this work to ship the golden path. Like, how to actually measure the adoption of all this work that we're doing and if it's actually valuable?” Right?Like, we want everybody to be on a certain set of CI tooling or a certain minimum version of some library or framework. How do we do that? How do we measure that? OpsLevel is for you, right? We have a whole bunch of stuff around maturity.And if you're engineering leader, ultimately, questions you care about, like, “How fast are my developers working? I have this massive team, we've made this massive investment in hiring all these humans to write software and bring value for our customers. How can we be more efficient as a business in terms of that value delivery?” And that's where OpsLevel can help as well.Corey: Guardrails, whether they be economic, regulatory, or otherwise, have to make it easier than doing things incorrectly because one of the miracle aspects of cloud also turns into a bit of a problem, which is shadow IT is only ever a corporate credit card away. Make it too difficult to comply with corporate policies and people won't. And they're good actors; they're trying to get work done. They're not trying to make people's lives harder, but they don't want to spend six weeks provisioning an EC2 cluster. So, there's always that weird trade-off.Now, it feels—and please correct me if I'm wrong—once someone has rolled out OpsLevel at their organization, where it really shines is spinning up a new service where okay, great, you're going to spin up the automatic observability portion of it, you're going to spin up the underlying infrastructure in certain ways that comply with our policies, it's going to build the CI/CD pipelines around it, you're going to wind up having the various cost instrumentation rolled out to it. But for services that are already excellent within the environment, is there an OpsLevel story for them?Ken: Oh, absolutely. So, I look at it as, like, the first problem OpsLevel helps solve is the catalog and what's out there and who owns it. So, not even getting developers to spin up new services that are kind of on the golden path, but just understanding the taxonomy of what are the services we have? How do those services compose into higher-level things like systems or domains? What's the whole set of infrastructure we have?Like, I have 50 AWS accounts, maybe a handful of GCP ones, also, some Azure. I have all this infrastructure that, like, how do I start to get a handle on, like, what's out there in prod and who's responsible for it. And that helps you get in front of compliance risks, security risks. That's really the starting point for OpsLevel building that catalog. And we have a bunch of integrations that kind of slurp all this data to automatically assemble that catalog, or YAML as well if that's your thing. But that's the starting point is building that catalog and figuring out this assignment of, like, okay, this service and this human, or this—sorry—team, like, they're paired together.Corey: A number of offerings in this space, which honestly, my exposure to it is bounded simultaneously to things that are ten years old and no one uses anymore, or a bunch of things I found on GitHub. And the challenge that both of those products tend to have is that they assume certain things to be true about a given environment: that they're using Terraform to manage everything, or they're always going to be using CloudFormation, or everyone there knows Python or something else like that. What are the prerequisites to get started with OpsLevel?Ken: Yeah, so we worked pretty hard to build just a ton of integrations. I would say integrations is are just continuing thing we have going on in the background. Like, when we started, like, we only supported a GitHub. Now, we support all the gits, you know, like GitHub, GitLab, Bitbucket, Azure DevOps, like, we're building [unintelligible 00:16:19]. There's just a whole, like, long tail of integrations.The same with APM tooling. The same with vulnerability management tooling, right? And the reason we do that is because there's just this huge vendor footprint, and people, you know, want OpsLevel to work for them. Now, the other thing we try to do is we also build APIs. So, anything we have as, like, a core integration, we also have kind of like an underlying API for, so that there's, no matter what you have an escape hatch. If like, you're using some tool that we don't support or you have some homegrown thing, there's always a way to try to be able to integrate that into OpsLevel.Corey: When people think about developer portals, the most common one that pops to mind is Backstage, which Spotify wound up building, internally, championing, open-sourcing, and I believe, on some level, turned into a product because if there's one thing people want, it's to have their podcast music company become a SaaS vendor, which is weird to me. But the criticisms that I've seen about and across the board have rung relatively true, including from people internal at Spotify who have used the thing, which is, well first is underestimating the amount of effort that is necessary to maintain Backstage itself, that the build versus buy discussion is always harder to bu—engineers love to build, but they shouldn't be building things outside of their core competency half the time, and the other is driving adoption within the org where you can have the most amazing developer portal in the known universe, but if people don't use it, it may as well not exist and doing the carrot and stick approach often doesn't work. I think you have a pretty good answer that I need not even ask you to elaborate on, “Well, how do we avoid having to maintain this ourselves,” since you have a company that does this, but how do you find companies are driving adoption successfully once they have deployed OpsLevel?Ken: Yeah, that's a great question. So, absolutely. Like, I think the biggest thing you need first, is kind of cultural buy-in and that this is a tool that we want to invest in, right? I think one of the reasons Spotify was successful with Backstage and I think it was System Z before that was that they had this kind of flywheel of, like, they saw that their developers were getting, you know better faster, working happier, by using this type of tooling, by reducing the cognitive load. The way that we approach it is sort of similar, right?We want to make sure that there is executive buy-in that, like, everybody agrees this is, like, a problem that's worth solving. The first step we do is trying to build out that catalog again and helping assign ownership. And that helps people understand, like, hey, these are the services I'm responsible for. Oh, look, and now here's this other context that I didn't have before. And then helping organizations, you know, what—it depends on the problem we're trying to solve, but whether it's rolling out self-serve automation to help developers, like, reduce what was before a ton of cognitive load or if it's helping platform teams define what good looks like so they can start to level up the overall health of what's running in production, we kind of work on different problems, but it's picking one problem and then you know, kind of working with the customers and driving it forward.Corey: On some level, I think that this is going to be looked down upon inherently just by automatic reflex of folks with infrastructure engineering backgrounds. It's taken me some time to learn to overcome my own negative reaction to it. Because it's, I'm here to build things and I want to build things out in such a way that it's portable and reusable without having to be tied to a particular vendor and move on. And it took me a long time to realize that what that instinct was whispering in my ear was in fact, no, you should be your own cloud provider. If that's really what I want to do, I probably should just brush up on you know, computer science trivia from 20 years ago and then go see if I can pass Google's SRE interview.I'm not here to build the things that just provision infrastructure from scratch every company I wind up landing at. It feels like there's more important, impactful work that I can do. And let's be clear, people are never going to follow guardrails themselves when they have to do a bunch of manual steps. It has to be something that is done for them. And I don't know how you necessarily get there without having some form of blueprint or something like that, provided for them with something that is self-service because otherwise, it's not going to work.Ken: I a hundred percent agree, by the way, Corey. Like, the take that, like, automation is the only way to drive a lot of this forward is true, right? If for every single thing you're trying—like, we have a concept called a rubric and it's basically how you measure the service health. And you can—it's very customizable, you have different dimensions. But if, for any check that's on your rubric, it requires manual effort from all your developers, that is going to be harder than something you can just automate away.So, vulnerability management is a great example. If you tell developers, “Hey, you have to go upgrade this library,” okay, some percentage [unintelligible 00:20:47], if you give developers, “Here's a pull request that's already been done and has a test passing and now you just need to merge it,” you're going to have a much better adoption rate with that. Similarly with, like, applying templates being able to [up-level 00:20:57], you know, kind of apply the latest version of a template to an existing service, those types of capabilities, anything where you can automate what the fixes are, absolutely you're going to get better adoption.Corey: As you take a look at your existing reference customers—which is something I always look for on vendor websites because, like, oh, we have many customers who will absolutely not admit to being customers, it's like, that sounds like something that's easy to say—you have actual names tied to these things. Not just companies, but also individuals. If you were to sit down and ask your existing customer base, “So, why did you wind up implementing OpsLevel and what has the value that's delivered to you been since that implementation?” What do they say?Ken: Definitely. I actually had to check our website because we, you know, land new customers and put new logos on it. I was like, “Oh, I wonder what the current set is out right now?”Corey: I have the exact same challenge. Like oh, we have some mutual customers. And it's okay. I don't know if I can mention them by name because I haven't checked our own list of testimonials [unintelligible 00:21:51] lately because say the wrong thing and that's how you wind up being sued and not having a company anymore.Ken: Yeah. So, I don't—I definitely, you know, want to stay [on side 00:22:00] on that part, but in terms of, like, kind of sample reference customer, a lot of the folks that we initially worked with are the platform teams, right? They're the teams that care about what's out there, and they need to know who's responsible for it because they're trying to drive some kind of cross-cutting change across the entire, you know, production footprint. And so, the first thing that generally people will say is—and I love this quote. This came—I won't name them, but like, it's in one of our case studies.It was like, “I had, like, 50 different attempts at making a spreadsheet and they're all, like, in the graveyard, like, to be able to capture what's out there and who's responsible for it.” And just OpsLevel helping automate that has been one of the biggest values that they've gotten. The second point, then is now be able to drive maturity and be able to measure how well those services are being built. And again, it's sort of this interesting thing where we start with the platform teams. And then sometime later security teams find out about OpsLevel, and they're like, “Oh, this is a tool I can use to, like, get developers to do stuff? Like, I've been trying to get developers to do stuff for the longest time.”And they—I file Jira tickets and they just sit there and nothing gets done. But when it becomes part of this, like, overall health score that you're trying to increase a part of the across the board, yeah, it's just a way to kind of drive action.Corey: I think that there's a dichotomy of companies that emerge. And I tend to see the world through a lens of AWS bills, so let's go down that path. I feel like there are some companies presumably like OpsLevel, whereas if I—assuming you're running on top of AWS—if I were to pull your AWS bill, I would see upwards of 80% of your spend is going to be on this application called OpsLevel, the service that you provide to people. As opposed to the other side of the world, which is large enterprises, where they're spending hundreds of millions of dollars a year, but the largest application they have is a million-and-a-half a year in spend because just, they have thousands of these things scattered everywhere. That latter case is where I tend to see more platform teams, where I start to see a lot of managing a whole bunch of relatively small workloads. And developer platforms really seem to be where a lot of solutions lead, whereas 80% of our workload is one application, we don't feel the need for that as much. Is that accurate? Am I misunderstanding some aspect of it?Ken: No, a hundred percent you'd hit the nail on the head. Like, okay, think about the typical, like, microservices adoption journey. Like, you started with, you know, some small company—like us—you started with a monolith. Ah, maybe you built out a second app—Corey: Then you read on Hacker News and realize, “Oh, if we want to hire people, we've got to be doing what all the cool kids are up to.”Ken: Right. We got a microservice all the thing—but that's actually you know, microservices should come later, right, as a response to you needing scale your org and scale your—Corey: As someone who started building some application with microservices, I could not agree more.Ken: A hundred percent. So, it's as you're starting to take steps to having just more moving parts in your production infrastructure, right? If you have one moving part, unless it's like a really large moving part that you can internally break down, like, kind of this majestic monolith where you do have kind of like individual domains that are owned by different teams, but really the problem we're trying to solve, it's more about, like, who owns what. Now, if that's a single atomic unit, great, but can you decompose that? But if you just have, like, one small application, kind of like the whole team is owning everything, again, a developer portal is probably not the right tool for you. It really is a tool that you need as you start to scale your engineer work and as you start to scale the number of moving parts in your production infrastructure.Corey: I tended to use to think of that in terms of boring companies versus innovative ones and I don't think that's accurate. I think it is the question of maturity and where companies lead to. On some level, of OpsLevel starts growing and becomes larger and larger in different ways and starts doing acquisitions and launching into other areas, at some point, you don't have just one product offering, you have a multitude of them. At which point having something like that is going to be critical. But I have to ask, given that you are sort of not exactly your target customer profile, what are the sharp edges been on using it for your use case?Ken: Yeah. So, we actually have an internal Slack channel, we call OpsLevel on OpsLevel. And finding those sharp edges actually has been really useful for us. You know, all the good stuff, dogfooding and it makes your own product better. Okay, so we have our main app, we also do have a bunch of smaller things and it's like, oh yeah, you know, we have, like, I don't know, various Hackaday things that go on, it's important we kind of wind those down for, you know, compliance, we have our marketing site, we have, like, our Terraform.Like, so there's, like, stuff. It's not, like, hundreds or thousands of things, but there's more than just the main app. The second though, is it's really on the maturity piece that we really try to get a lot of value out of our own product, right? Helping—we have our own platform team. They're also trying to drive certain initiatives with our product developers.There is that usual tension of our, like, our own product developers are like, “I want to ship features.” What's this security thing I have to go take care of right now? But OpsLevel itself, like, helps reflect that. We had an operational review today and it was like, “Oh, this one service is actually now”—we have platinum as a level. It's in gold instead of platinum. It's like, “Why?” “Oh, there's this thing that came up. We got to go fix that.” “Great. Let's go actually go fix that so we're back into platinum.”Corey: Do you find that there's often a choice you have to make internally, where you could make the product more effective for your specific use case, but that also diverges from where your typical customer needs or wants the product to go?Ken: No, I think a lot of the things we find for our use case are, like, they're more small paper cuts, right? They're just as we're using it, it's like, “Hey, like, as I'm using this, I want to see the report for this particular check. Why do I have to click six times to get?” You know, like, “Wouldn't it be great if we had a button?” Right?And so, it's those type of, like, small innovations that kind of come up. And those ultimately lead to, you know, a better product for our customers. We also work really closely with our customers and developers are not shy about telling you what they don't like about your product. And I say this with love, like, a lot of our customers give us phenomenal feedback just on how our product can be better and we try to internalize that and you know, roll that feedback into the product.Corey: You have a number of integrations of different SaaS providers, infrastructure providers, et cetera, that you wind up working with. I imagine that given your scale and scope and whatnot, those offerings are dictated by what customers say, “Hey, we're using this thing. Are you going to support that or are you not going to maintain our business?” Which is a great way to wind up financing a lot of product development and figuring out what matters to people. My question for you is, if you look across the totality of your user base, what are the most popularly used integrations, if you can say?Ken: Yeah, for sure. I think right now—I could actually dive in to pull the numbers—GitHub and GitLab—or… I think GitHub, like, has slightly more adoption across our customer base. At least with our customers, almost nobody uses Bitbucket. I mean, we have, like, a small number, but, like, it's… I think, single-digit percentage. A lot of people use PagerDuty, which you know, hey, I'm an ex-PagerDuty person [crosstalk 00:28:24] and I'm glad to see that.Corey: I have a free tier PagerDuty account that will automatically page me for my home automation stuff. Specifically, if you know, the fire alarm goes off. Like, yeah, okay, there are certain things I want to be woken up for, but it's a very short list.Ken: Yeah, it's funny, the running default message when we use a test PagerDuty was, “The server is on fire.” [unintelligible 00:28:44] be like, “The house is on fire.” Like you know, go get that taken care of. There's one other tool so that's used a lot. Datadog actually is used a ton by just across our entire customer base, despite its… we're also Data—we're a Datadog partner, we're a Datadog customer, you know? It's not cheap, but it's a good product for, you know, monitoring and logs and there are [crosstalk 00:29:01]—Corey: No other than cloud infrastructure providers, I get the number one most common source of inquiries is Datadog optimization. It has now risen to a board-level concern in many cases because observability is expensive. That's a sign of success, on some level. Meanwhile, I'm sitting here, like, Date-a-dog? Oh, my God, that's disgusting. It's like Tinder for Pets. Which it turns out is not at all what they do.Ken: Nice.Corey: Yeah.[audio break 00:29:23]—optimizing their Slack integrations, their GitHub integration, et cetera. Or are they starting with the spinning up the servers piece of it?Ken: A lot of the time—and again, that first problem they're trying to solve is just get me a handle on everything we have running in production. You know, if you have multiple AWS accounts, multiple Kubernetes clusters, dozens or even hundreds of teams, God help you if you're going to try to, like, build a list manually to consolidate all that information. That's really the first part is, like, integrate Kubernetes, integrate your CI/CD pipelines, integrate Git, integrate your Cloud account, like, will integrate with everything and will try to build that map of, like, here's everything that's out there, and start to try to assign it to, like, and here's people that we think might be responsible in terms of owning the software. That's generally the starting point.Corey: Which makes an awesome amount of sense. I think going at it from the infrastructure first perspective is where I've seen most developer platforms founder. And to be fair, the job is easier now than it was years ago because it used to be that you were being out-innovated by AWS constantly. Innovation has slow down there. And you know that because of how much they say the pace of innovation has only sped up.And whenever AWS says something in a marketing context, they're insecure about it. I've learned this through the fullness of time observing that company. And these days, most customers do not use the majority of features available for any given service. They have solidified to a point where you can responsibly build on top of these things. Now, it seems that the problem is all the ‘yes, and' stuff that gets built on top of it.Ken: Yeah. Do you have an example, actually, like, one of the kinds of, like, ‘yes, and' tools that you're thinking about?Corey: Oh, absolutely. We have a bunch of AWS environment stuff so we should configure CloudWatch to look at all these things from an observability perspective. No, you should not. You should set up Datadog. And the first time someone does that by hand, they enable all have the observability and the rest and suddenly get charged approximately the GDP of Guam.And okay, maybe we shouldn't do that because then you have the downstream impact of that on your CloudWatch bill. So okay, how do we optimize this for the observability piece directly tied to that? How do we make sure that we get woken up when the site is down or preferably before that, but not every time basically, a EBS volume starts to get a little bit toasty? You have to start dialing this stuff in. And once you've found a lot of those aspects, being able to templatize that and roll that out on an ongoing basis and having the integrations all work together feels like it's the right problem to be solving.Ken: Yeah, absolutely. And the group that I think is responsible for that kind of—because it's a set of problems you described—is really, like, platform teams. Sometimes service owners for like, how should we get paged, but really, what you're describing are these kind of cross-cutting engineering concerns that platform teams are uniquely poised to help solve in an [unintelligible 00:32:03] organization, right? I was thinking what you said earlier. Like, nobody just wants to rebuild the same info over and over, but it's sort of like, it's not just building an [unintelligible 00:32:09]; it's kind of like solving this, like, how do we ship? Can we actually run stuff in prod? And not just run it but get observability and ensure that we're woken up for it and, like, what's that total end-to-end look like from, like, developers writing code to running software in production that's serving traffic? And solving all the problems [unintelligible 00:32:24], that's what I think of was platform engineering.Corey: So, my last question before we wind up wrapping this episode comes down to, I am very adept at two different programming languages, and those are brute force and enthusiasm. What implementation language is most of what you find yourself working with? And why is it in invariably going to be YAML?Ken: Yeah, that's a great question. So, I think there's, in terms of implementing OpsLevel and implementing a service catalog, we support YAML. Like, you know, there's this very common workflow, you just drop a YAML spec, basically, in your repo, if you're a service owner. And that, we can support that. I don't think that's a great take, though.Like, we have other integrations. Again, if the problem you're trying to solve is I want to build a catalog of everything that's out there, asking each of your developers hey, can you please all write YAML files that, like, describe the services you own and drop them into this repo? You've inverted this, like, database that essentially you're trying to build, like, what's out there and stored it in Git, potentially across several hundreds or thousands of repos. You put a lot of toil now on individual product developers to go write and maintain these files. And if you ever had to, like, make a blanket update to these files, there's no atomic way to kind of do that, right?So, I look at YAML as, like, I get it, you know? Like, we use the YAML for all the things in DevOps, so why not their service catalog as well, but I think it's toil. Like, there are easier ways to build a catalog. By, kind of, just integrate. Like, hook up AWS, hook up GitHub, hook up Kubernetes, hook up your CI/CD pipeline, hook up all these different sources that have information about what's running in prod, and let the software, let the tool, automatically infer what's actually running as opposed to requiring humans to manually enter data.Corey: I find that there are remarkably few technical holy wars that I cannot unify both sides on by nominating something far worse. Like, the VI versus Emacs stuff, the tabs versus spaces, and of course, the JSON versus YAML folks. My JSON versus YAML answer is XML: God's language. I find that as soon as you suggest that, people care a hell of a lot less about the differences between JSON and YAML because their job is to now kill the apostate, which is me.Ken: Right. Yeah. I remember XML, like, oh, man, 2002. SOAP. I remember SOAP as a protocol. That was a thing.Corey: Some of the earliest S3 API calls were done in SOAP, and I think they finally just used it to wash their mouths out when all was said and done.Ken: Nice. Yeah.Corey: I really want to thank you for taking the time to do your level best to attempt to convert me, and I would argue in many respects, you have succeeded. I'm thinking about this differently than I did half an hour ago. If people want to learn more, where's the best place for them to find you?Ken: Absolutely. So, you can always check out our website, opslevel.com. We're also fairly active on LinkedIn. If Twitter hasn't imploded by the time this episode becomes launched, then they can also check us out at twitter.com/OpsLevelHQ. We're always posting, just different content on, like, how to be successful with service maturity, DevOps, developer productivity, so that you know, ultimately, that you can ship out to customers faster.Corey: And we will, of course, put links to that in the [show notes 00:35:23]. Thank you so much for taking the time, not just to speak with me, but also for sponsoring this episode. It is appreciated.Ken: Cheers.Corey: Ken Rose, CTO and co-founder at OpsLevel. I'm Cloud Economist Corey Quinn and this has been a promoted guest episode of Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment which, upon further reflection, you could have posted to all of the podcast platforms if only you had the right developer platform to pull it off.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.
FreeBSD Foundation Welcomes New Team Members, OpenZFS the Ideal Storage Solution for University Environments, SCaLE20X Conference Report, 916 days of Emacs, XTerm: It's Better Than You Thought, NetBSD Annual General Meeting 2023, and more NOTES** This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines FreeBSD Foundation Welcomes New Team Members (https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-team-members/) What Makes OpenZFS the Ideal Storage Solution for University Environments (https://klarasystems.com/articles/openzfs-what-makes-openzfs-the-ideal-storage-solution-for-university-environments//) News Roundup SCaLE20X Conference Report (https://freebsdfoundation.org/blog/scale20x-conference-report/) 916 days of Emacs (https://sqrtminusone.xyz/posts/2023-04-13-emacs/) XTerm: It's Better Than You Thought (https://aduros.com/blog/xterm-its-better-than-you-thought/) NetBSD AGM2023: Annual General Meeting, May 13, 21:00 UTC (https://mail-index.netbsd.org/netbsd-announce/2023/05/05/msg000348.html) Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Adrian - Tilde (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/508/feedback/Adrian%20-%20Tilde.md) Dan - Root Shell (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/508/feedback/Dan%20-%20Root%20Shell.md) Florian - Salt Extension (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/508/feedback/Florian%20-%20Salt%20Extension.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***
Mike Brevoort, Chief Product Officer at Gitpod, joins Corey on Screaming in the Cloud to discuss all the intricacies of remote development and how Gitpod is simplifying the process. Mike explains why he feels the infinite resources cloud provides can be overlooked when discussing remote versus local development environments, and how simplifying build abstractions is a fantastic goal, but that focusing on the tools you use in a build abstraction in the meantime can be valuable. Corey and Mike also dive into the security concerns that come with remote development, and Mike reveals the upcoming plans for Gitpod's local conference environment, CDE Universe. About MikeMike has a passion for empowering people to be creative and work together more effectively. He is the Chief Product Officer at Gitpod striving to remove the friction and drudgery from software development through Cloud Developer Environments. He spent the previous four years at Slack where he created Workflow Builder and “Platform 2.0” after his company Missions was acquired by Slack in 2018. Mike lives in Denver, Colorado and enjoys cycling, hiking and being outdoors.Links Referenced: Gitpod: https://www.gitpod.io/ CDE Universe: https://cdeuniverse.com/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: It's easy to **BEEP** up on AWS. Especially when you're managing your cloud environment on your own!Mission Cloud un **BEEP**s your apps and servers. Whatever you need in AWS, we can do it. Head to missioncloud.com for the AWS expertise you need. Corey: Have you listened to the new season of Traceroute yet? Traceroute is a tech podcast that peels back the layers of the stack to tell the real, human stories about how the inner workings of our digital world affect our lives in ways you may have never thought of before. Listen and follow Traceroute on your favorite platform, or learn more about Traceroute at origins.dev. My thanks to them for sponsoring this ridiculous podcast. Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. I have had loud, angry, and admittedly at times uninformed opinions about so many things over the past few years, but something that predates that a lot is my impression on the idea of using remote systems for development work as opposed to doing local dev, and that extends to build and the rest. And my guest today here to argue with me about some of it—or agree; we'll find out—is Mike Brevoort, Chief Product Officer at Gitpod, which I will henceforth be mispronouncing as JIT-pod because that is the type of jerk I am. Mike, thank you for joining me.Mike: Thank you for insulting my company. I appreciate it.Corey: No, by all means, it's what we do here.Mike: [laugh].Corey: So, you clearly have opinions on the idea of remote versus local development that—I am using the word remote development; I know you folks like to use the word cloud, in place of remote, but I'm curious to figure out is, is that just the zeitgeist that has shifted? Do you have a belief that it should be in particular places, done in certain ways, et cetera? Where do your opinion on this start and stop?Mike: I think that—I mean, remote is accurate, an accurate description. I don't like to emphasize the word remote because I don't think it's important that it's remote or local. I think that the term cloud connotes different values around the elasticity of environments and the resources that are more than what you might have on your local machine versus a remote machine. It's not so much whether the one machine is local or remote as much of it is that there are infinite numbers of resources that you can develop across in the cloud. That's why we tend to prefer our cloud development environments.Corey: From my perspective, I've been spending too many years now living in basically hotels and airports. And when I was doing that, for a long time, the only computer I bring with me has been my iPad Pro. That used to be a little bit on the challenging side and these days, that's gotten capable enough where it's no longer interesting in isolation. But there's no local development environment that is worth basically anything on that. So, I've been SSHing into things and using VI as my development environment for many years.When I started off as a grumpy Unix sysadmin, there was something reassuring about the latest state of whatever it is I'm working on lives in a data center somewhere rather than on a laptop, I'm about to leave behind a coffee shop because I'm careless. So, there's a definite value and sense that I am doing something virtuous, historically. But it didn't occur to me till I started talking to people about this, just how contentious the idea was. People would love to ask all kinds of fun objections to this where it was, “Oh, well, what about when you're on a plane and need to do work?” It's, well, I spend an awful lot of time on planes and that is not a limiting factor in me writing the terrible nonsense that I will charitably called code, in my case. I just don't find that that idea holds up anywhere. The world has become so increasingly interconnected that that seems unlikely. But I do live in San Francisco, so here, every internet is generally pretty decent; not every place is. What are your thoughts?Mike: I agree. I mean, I think one thing is, I would just like not to think about it, whether I can or can't develop because I'm connected or not. And I think that we tend to be in a world where that is moreso the case. And I think a lot of times when you're not connected, you become reconnected soon, like if your connection is not reliable or if you're going in and out of connectivity issues. And when you're trying to work on a local laptop and you're connecting and disconnecting, it's not like we develop these days, and everything is just isolated on our local laptop, especially we talk about cloud a lot on this podcast and a lot of apps now go way beyond just I'm running a process on my machine and I'm connecting to data on my machine.There are local emulators you could use for some of these services, but most of them are inferior. And if you're using SQS or using any other, like, cloud-based service, you're usually, as a developer, connecting to some version of that and if you're disconnected anyway, you're not productive either. And so, I find that it's just like an irrelevant conversation in this new world. And that the way we've developed traditionally has not followed along with this view of I need to pile everything in on my laptop, to be able to develop and be productive has not, like, followed along with the trend that moved into the cloud.Corey: Right. The big problem for a long time has been, how do I make this Mac or Windows laptop look a lot like Linux EC2 instance? And there have been a bunch of challenges and incompatibility issues and the rest, and from my perspective, I like to develop in an environment that at least vaguely resembles the production environment it's going to run in, which in AWS's case, of course, comes down to expensive. Bu-dum-tss.Mike: Yeah, it's a really big challenge. It's been a challenge, right? When you've worked with coworkers that were on a Windows machine and you were on a Mac machine, and you had the one person on their Linux machine forever, and we all struggled with trying to mimic these development environments that were representative, ultimately, of what we would run in production. And if you're counting costs, we can count the cost of those cloud resources, we can count the cost of those laptops, but we also need to count the cost of the people who are using those laptops and how inefficient and how much churn they have, and how… I don't know, there was for years of my career, someone would show up every morning to the stand-up meeting and say, it's like, “Well, I wasted all afternoon yesterday trying to work out my, you know, issues with my development environment.” And it's, like, “I hope I get that sorted out later today and I hope someone can help me.”And so, I think cost is one thing. I think that there's a lot of inconsistencies that lead to a lot of inefficiencies and churn. And I think that, regardless of where you're developing, the more that you can make your environments more consistent and sound, not for you, but for your own team and have those be more representative of what you are running in production, the better.Corey: We should disambiguate here because I fear this is one of the areas where my use case tends to veer off into the trees, which is I tend to operate largely in isolation, from a development point of view. I build small, micro things that wind up doing one thing, poorly. And that is, like, what I do is a proof of concept, or to be funny, or to kick the tires on a new technology. I'll also run a bunch of random things I find off of JIF-ub—yes, that's how I pronounce GitHub. And that's great, but it also feels like I'm learning as a result, every stack, and every language, in every various version that it has, and very few of the cloud development environments that I've seen, really seems to cater to the idea that simultaneously, I want to have certain affordances in my shell environment set up the way that I want them, tab complete this particular suite of tools generically across the board, but then reset to that baseline and go in a bunch of different directions of, today, it's Python in this version and tomorrow, it's Node in this other version, and three, what is a Typescript anyway, and so on and so forth.It feels like it's either, in most cases, you either get this generic, one-size-fits-everyone in this company, for this project, approach, or it's, here's a very baseline untuned thing that does not have any of your dependencies installed. Start from scratch every time. And it's like, feels like there are two paths, and they both suck. Where are you folks at these days on that spectrum?Mike: Yeah, I think that, you know, one, if you do all of that development across all these different libraries and technology stacks and you're downloading all these repos from JIF-hub—I say it right—and you're experimenting, you tend to have a lot of just collision of things. Like if you're using Python, it's, like, really a pain to maintain isolation across projects and not have—like, your environment is, like, one big bucket of things on your laptop and it's very easy to get that into a state where things aren't working, and then you're struggling. There's no big reset on your laptop. I mean, there is but it takes—it's a full reset of everything that you have.And I think the thing that's interesting to me about cloud development environments is I could spin one of these up, I could trash it to all hell and just throw it away and get another one. And I could get another one of those at a base of which has been tuned for whatever project or technology I'm working on. So, I could take—you know, do the effort to pre-setup environments, one that is set up with all of my, like, Python tooling, and another one that's set up with all my, like, Go or Rust tooling, or our front-end development, even as a base repo for what I tend to do or might tend to experiment with. What we find is that, whether you're working alone or you're working with coworkers, that setting up a project and all the resources and the modules and the libraries and the dependencies that you have, like, someone has to do that work to wire that up together and the fact that you could just get an environment and get another one and another one, we use this analogy of, like, tissue boxes where, like, you should just be able to pull a new dev environment out of a tissue box and use it and throw it away and pull as many tissues out of the box as you want. And they should be, like, cheap and ephemeral because—and they shouldn't be long-lived because they shouldn't be able to drift.And whether you're working alone or you're working in a team, it's the same value. The fact that, like, I could pull on these out, I have it. I'm confident in it of what I got. Like for example, ideally, you would just start a dev environment, it's available instantly, and you're ready to code. You're in this project with—and maybe it's a project you've never developed on. Maybe it's an open-source project.This is where I think it really improves the sort of equitability of being able to develop, whether it's in open-source, whether it's inner-source in companies, being able to approach any project with a click of a button and get the same environment that the tech lead on the project who started it five years ago has, and then I don't need to worry about that and I get the same environment. And I think that's the value. And so, whether you're individual or you're on a team, you want to be able to experiment and thrash and do things and be able to throw it away and start over again, and not have to—like for example, maybe you're doing that on your machine and you're working on this thing and then you actually have to do some real work, and then now that you've done something that conflicts with the thing that you're working on and you're just kind of caught in this tangled mess, where it's like, you should just be able to leave that experiment there and just go work on the thing you need to work on. And why can't you have multiples of these things at any given time?Corey: Right. One of the things I loved about EC2 dev environments has been that I can just spin stuff up and okay, great, it's time for a new project. Spin up another one and turn it off when I'm done using it—which is the lie we always tell ourselves in cloud and get charged for things we forget to turn off. But then, okay, I need an Intel box one day. Done. Great, awesome. I don't have any of those lying around here anymore but clickety, clickety, and now I do.It's nice being able to have that flexibility, but it's also sometimes disconcerting when I'm trying to figure out what machine I was on when I was building things and the rest, and having unified stories around this becomes super helpful. I'm also finding that my overpowered desktop is far more cost-efficient when I need to compile something challenging, as opposed to finding a big, beefy, EC2 box for that thing as well. So, much of the time, what my remote system is doing is sitting there bored. Even when I'm developing on it, it doesn't take a lot of modern computer resources to basically handle a text editor. Unless it's Emacs, in which case, that's neither here nor there.Mike: [laugh]. I think that the thing that becomes costly, especially when using cloud development environments, is when you have to continue to run them even when you're not using them for the sake of convenience because you're not done with it, you're in the middle of doing some work and it still has to run or you forget to shut it off. If you are going to just spin up a really beefy EC2 instance for an hour to do that big compile and it costs you 78 cents. That's one thing. I mean, I guess that adds up over time and yes, if you've already bought that Mac Studio that's sitting under your desk, humming, it's going to be more cost-efficient to use that thing.But there's, like, an element of convenience here that, like, what if I haven't bought the Mac Studio, but I still need to do that big beefy compilation? And maybe it's not on a project I work on every single day; maybe it's the one that I'm just trying to help out with or just starting to contribute to. And so, I think that we need to get better about, and something that we're very focused on at JIT-pod, is—Gitpod—is—Corey: [laugh]. I'm going to get you in trouble at this rate.Mike: —[laugh]—is really to optimize that underlying runtime environment so that we can optimize the resources that you're using only when you're using it, but also provide a great user experience. Which is, for me, as someone who's responsible for the product at Gitpod, the thing I want to get to is that you never have to think about a machine. You're not thinking about this dev environment as something that lives somewhere, that you're paying for, that there's a meter spinning that if you forget it, that you're like, ah, it's going to cost me a lot of money, that I have to worry about ever losing it. And really, I just want to be able to get a new environment, have one, use it, come back to it when I need it, have it not cost me a lot of money, and be able to have five or ten of those at a time because I'm not as worried about what it's going to cost me. And I'm sure it'll cost something, but the convenience factor of being able to get one instantly and have it and not have to worry about it ultimately saves me a lot of time and aggravation and improves my ability to focus and get work done.And right now, we're still in this mode where we're still thinking about, is it on my laptop? Is it remote? Is it on this EC2 instance or that EC2 instance? Or is this thing started or stopped? And I think we need to move beyond that and be able to just think of these things as development environments that I use and need and they're there when I want to, when I need to work on them, and I don't have to tend to them like cattle.Corey: Speaking of tending large things in herds—I guess that's sort of for the most tortured analogy slash segway I've come up with recently—you folks have a conference coming up soon in San Francisco. What's the deal with that? And I'll point out, it's all on-site, locally, not in the cloud. So, hmm…Mike: Yeah, so we have a local conference environment, a local conference that we're hosting in San Francisco called CDE Universe on June 1st and 2nd, and we are assembling all the thought leaders in the industry who want to get together and talk about where not just cloud development is going, but really where development is going. And so, there's us, there's a lot of companies that have done this themselves. Like, before I joined Gitpod, I was at Slack for four years and I got to see the transition of a, sort of, remote development hosted on EC2 instances transition and how that really empowered our team of hundreds of engineers to be able to contribute and like work together better, more efficiently, to run this giant app that you can't run just alone on your laptop. And so, Slack is going to be there, they're going to be talking about their transition to cloud development. The Uber team is going to be there, there's going to be some other companies.So, Nathan who's building Zed, he was the one that originally built Adam at GitHub is now building Zed, which is a new IDE, is going to be there. And I can't mention all the speakers, but there's going to be a lot of people that are really looking at how do we drive forward development and development environments. And that experience can get a lot better. So, if you're interested in that, if you're going to be in San Francisco on June 1st and 2nd and want to talk to these people, learn from them, and help us drive this vision forward for just a better development experience, come hang out with us.Corey: I'm a big fan of collaborating with folks and figuring out what tricks and tips they've picked up along the way. And this is coming from the perspective of someone who acts as a solo developer in many cases. But it always drove me a little nuts when you see people spending weeks of their lives configuring their text editor—VIM in my case because I'm no better than these people; I am one of them—and getting it all setup and dialed in. It's, how much productivity you gaining versus how much time are you spending getting there?And then when all was said and done a few years ago, I found myself switching to VS Code for most of what I do, and—because it's great—and suddenly the world's shifting on its axis again. At some point, you want to get away from focusing on productivity on an individualized basis. Now, the rules change when you're talking about large teams where everyone needs a copy of this running locally or in their dev environment, wherever happens to be, and you're right, often the first two weeks of a new software engineering job are, you're now responsible for updating the onboarding docs because it's been ten minutes since the last time someone went through it. And oh, the versions bumped again of what we would have [unintelligible 00:16:44] brew install on a Mac and suddenly everything's broken. Yay. I don't miss those days.Mike: Yeah, the new, like, ARM-based Macs came out and then you were—now all of a sudden, all your builds are broken. We hear that a lot.Corey: Oh, what I love now is that, in many cases, I'm still in a process of, okay, I'm developing locally on an ARM-based Mac and I'm deploying it to a Graviton2-based Lambda or instance, but the CI/CD builder is going to run on Intel, so it's one of those, what is going on here? Like, there's a toolchain lag of round embracing ARM as an architecture. That's mostly been taken care of as things have evolved, but it's gotten pretty amusing at some point, just as quickly that baseline architecture has shifted for some workloads. And for some companies.Mike: Yeah, and things just seem to be getting more [laugh] and more complicated not less complicated, and so I think the more that we can—Corey: Oh, you noticed?Mike: Try to simplify build abstractions [laugh], you know, the better. But I think in those cases where, I think it's actually good for people to struggle with setting up their environment sometime, with caring about the tools that they use and their experience developing. I think there has to be some ROI with that. If it's like a chronic thing that you have to continue to try to fix and make better, it's one thing, but if you spend a whole day improving the tools that you use to make you a better developer later, I think there's a ton of value in that. I think we should care a lot about the tools we use.However, that's not something we want to do every day. I mean, ultimately, I know I don't build software for the sake of building software. I want to create something. I want to create some value, some change in the world. There's some product ultimately that I'm trying to build.And, you know, early on, I've done a lot of work in my career on, like, workflow-type builders and visual builders and I had this incorrect assumption somewhere along the way—and this came around, like, sort of the maker movement, when everybody was talking about everybody should learn how to code, and I made this assumption that everybody really wants to create; everybody wants to be a creator, and if given the opportunity, they will. And I think what I finally learned is that, actually most people don't like to create. A lot of people just want to be served; like, they just want to consume and they don't want the hassle of it. Some people do, if they have the opportunity and the skillsets, too, but it's also similar to, like, if I'm a professional developer, I need to get my work done. I'm not measured on how well my local tooling is set up; I'm sort of measured on my output and the impact that I have in the organization.I tend to think about, like, chefs. If I'm a chef and I work 60 hours in a restaurant, 70 hours in a restaurant, the last thing I want to do is come home and cook myself a meal. And most of the chefs I know actually don't have really nice kitchens at home. They, like, tend to, they want other people to cook for them. And so, I think, like, there's a place in professional setting where you just need to get the work done and you don't want to worry about all the meta things and the time that you could waste on it.And so, I feel like there's a happy medium there. I think it's good for people to care about the tools that they use the environment that they develop in, to really care for that and to curate it and make it better, but there's got to be some ROI and it's got to have value to you. You have to enjoy that. Otherwise, you know, what's the point of it in the first place?Corey: One thing that I used to think about was that if you're working in regulated industries, as I tended to a fair bit, there's something very nice about not having any of the data or IP or anything like that locally. Your laptop effectively just becomes a thin client to something that's already controlled by the existing security and compliance apparatus. That's very nice, where suddenly it's all someone steals my iPad, or I drop it into the bay, it's locked, it's encrypted. Cool, I go to the store, get myself a new one, restore a backup from iCloud, and I'm up and running again in a very short period of time as if nothing had ever changed. Whereas when I was doing a lot of local development and had bad hard drive issues in the earlier part of my career, well, there goes that month.Mike: Yeah, it's a really good point. I think that we're all walking around with these laptops with really sensitive IP on it and that those are in bars and restaurants. And maybe your drives are encrypted, but there's a lot of additional risks, including, you know, everything that is going over the network, whether I'm on a local coffee shop, and you know, the latest vulnerability that, an update I have to do on my Mac if I'm behind. And there's actually a lot of risk and having all that just sort of thrown to the wind and spread across the world and there's a lot of value in having that in a very safe place. And what we've even found that, at Gitpod now, like, the latest product we're working on is one that we called Gitpod Dedicated, which gives you the ability to run inside your own cloud perimeter. And we're doing that on AWS first, and so we can set up and manage an installation of Gitpod inside your own AWS account.And the reason that became important to us is that a lot of companies, a lot of our customers, treat their source code as their most sensitive intellectual property. And they won't allow it to leave their perimeter, like, they may run in AWS, but they have this concept of, sort of like, our perimeter and you're either inside of that and outside of it. And I think this speaks a little bit to a blog post that you wrote a few months ago about the lagging adoption of remote development environments. I think one of those aspects is, sort of, convenience and the user experience, but the other is that you can't use them very well with your stack and all the tools and resources that you need to use if they're not running, sort of, close within your perimeter. And so, you know, we're finding that companies have this need to be able to have greater control, and now with the, sort of, trends around, like, coding assistance and generative AI and it's even the perfect storm of not only am I like sending my source code from my editor out into some [LM 00:22:36], but I also have the risk of an LM that might be compromised, that's injecting code and I'm committing on my behalf that may be introducing vulnerabilities. And so, I think, like, getting that off to a secure space that is consistent and sound and can be monitored, to be kept up-to-date, I think it has the ability to, sort of, greatly increase a customer's security posture.Corey: While we're here kicking the beehive, for lack of a better term, your support for multiple editors in Gitpod the product, I assumed that most people would go with VS Code because I tend to see it everywhere, and I couldn't help but notice that neither VI nor Emacs is one of the options, the last time I checked. What are you seeing as far as popularity contests go? And that might be a dangerous question because I'm not suggesting you alienate many of the other vendors who are available, but in the world I live in, it's pretty clear where the zeitgeist of my subculture is going.Mike: Yeah, I mean, VS Code is definitely the most popular IDE. The majority of people that use Gitpod—and especially we have a, like, a pretty heavy free usage tier—uses it in the browser, just for the convenience of having that in the browser and having many environments in the browser. We tend to find more professional developers use VS Code desktop or the JetBrains suite of IDEs.Corey: Yeah, JetBrains I'm seeing a fair bit of in a bunch of different ways and I think that's actually most of what your other options are. I feel like people have either gone down the JetBrains path or they haven't and it seems like it's very, people who are into it are really into it and people who are not are just, never touch it.Mike: Yeah, and we want to provide the options for people to use the tools that they want to use and feel comfortable on. And we also want to provide a platform for the next generation of IDEs to be able to build on and support and to be able to support this concept of cloud or remote development more natively. So, like I mentioned, Nathan Sobo at Zed, I met up with him last week—I'm in Denver; he's in Boulder—and we were talking about this and he's interested in Zed working in the browser, and he's talked about this publicly. And for us, it's really interesting because, like, IDEs working in the browser is, like, a really great convenience. It's not the perfect way to work, necessarily, in all circumstances.There's some challenges with, like, all this tab sprawl and stuff, but it gives us the opportunity, if we can make Zed work really well in for Gitpod—or anybody else building an IDE—for that to work in the browser. Ultimately what we want is that if you want to use a terminal, we want to create a great experience for you for that. And so, we're working on this ability in Gitpod to be able to effectively, like, bring your own IDE, if you're building on that, and to be able to offer it and distribute on Gitpod, to be able to create a new developer tool and make it so that anybody in their Gitpod workspace can launch that as part of their workspace, part of their tool. And we want to see developer tools and IDEs flourish on top of this platform that is cloud development because we want to give people choice. Like, at Gitpod, we're not building our own IDE anymore.The team started to. They created Theia, which was one of the original cloud, sort of, web-based IDEs that now has been handed over to the Eclipse Foundation. But we moved to VS Code because we found that that's where the ecosystem were. That's where our users were, and our customers, and what they wanted to use. But we want to expand beyond that and give people the ability to choose, not only the options that are available today but the options that should be available in the future. And we think that choice is really important.Corey: When you see people kicking the tires on Gitpod for the first time, where does the bulk of their hesitancy come from? Like, what is it where—people, in my experience, don't love to embrace change. So, it's always this thing, “This thing sucks,” is sort of the default response to anything that requires them to change their philosophy on something. So okay, great. That is a thing that happens. We'll see what people say or do. But are they basing it on anything beyond just familiarity and comfort with the old way of doing things or are there certain areas that you're finding the new customers are having a hard time wrapping their head around?Mike: There's a couple of things. I think one thing is just habit. People have habits and preferences, which are really valuable because it's the way that they've learned to be successful in their careers and the way that they expect things. Sometimes people have these preferences that are fairly well ingrained that maybe are irrational or rational. And so, one thing is just people's force of habit.And then getting used to this idea that if it's not on my laptop, it means—like what you mentioned before, it's always what-ifs of, like, “What if I'm on a plane?” Or like, “What if I'm at the airport in a hurricane?” “What if I'm on a train with a spotty internet connection?” And so, there's all these sort of what-if situations. And once people get past that and they start actually using Gitpod and trying to set their projects up, the other limiting factor we have is just connectivity.And that's, like, connectivity to the other resources that you use to develop. So, whether that's, you know, package or module repositories or that some internal services or a database that might be running behind a firewall, it's like getting connectivity to those things. And that's where the dedicated deployment model that I talked about, running inside of your perimeter on our network, they have control over, kind of helps, and that's why we're trying to overcome that. Or if you're using our SaaS product, using something like Tailscale or a more modern VPN that way. But those are the two main things.It's like familiarity, this comfort for how to work, sort of, in this new world and not having this level of comfort of, like, it's running on this thing I can hold, as well as connectivity. And then there is some cost associated with people now paying for this infrastructure they didn't have to pay for before. And I think it's a, you know, it's a mistake to say that we're going to offset the cost of laptops. Like, that shouldn't be how you justify a cloud development environment. Like—Corey: Yeah, I feel like people are not requesting under-specced laptops much these days anymore.Mike: It's just like, I want to use a good laptop; I want to use a really nice laptop with good hardware and that shouldn't be the cost. The proposition shouldn't be, it's like, “Save a thousand dollars on every developer's laptop by moving this off to the cloud.” It's really the time savings. It's the focus. It's the, you know, removing all of that drift and creating these consistent environments that are more secure, and effectively, like, automating your development environment that's the same for everybody.But that's the—I think habits are the big thing. And there is, you know, I talked about a little bit that element of, like, we still have this concept of, like, I have this environment and I start it and it's there, and I pay for it while it's there and I have to clean it up or I have to make sure it stopped. I think that still exists and it creates a lot of sort of cognitive overhead of things that I have to manage that I didn't have to manage before. And I think that we have to—Gitpod needs to be better there and so does everybody else in the industry—about removing that completely. Like, there's one of the things that I really love that I learned from, like, Stewart Butterfield when I was at Slack was, he always brought up this concept called the convenience threshold.And it was just the idea that when a certain threshold of convenience is met, people's behavior suddenly changes. And as we thought about products and, like, the availability of features, that it really drove how we thought about even how to think about you know, adoption or, like, what is the threshold, what would it take? And, like, a good example of this is even, like, the way we just use credit cards now or debit cards to pay for things all the time, where we're used to carry cash. And in the beginning, when it was kind of novel that you could use a credit card to pay for things, like even pay for gas, you always had to have cash because you didn't know if it'd be accepted. And so, you still had to have cash, you still had to have it on hand, you still had to get it from the ATM, you still have to worry about, like, what if I get there and they don't accept my cards and how much money is it going to be, so I need to make sure I have enough of it.But the convenience of having this card where I don't have to carry cash is I don't have to worry about that anymore, as long as they have money in my bank account. And it wasn't until those cards were accepted more broadly that I could actually rely on having that card and not having the cash. It's similar when it comes to cloud development environments. It needs to be more convenient than my local development environment. It needs to be—it's kind of like early—I remember when laptops became more common, I was used to developing on a desktop, and people were like, nobody's ever going to develop on a laptop, it's not powerful enough, the battery runs out, I have to you know, when I close the lid, when you open the lid, it used to take, like, five minutes before, like, it would resume an unhibernate and stuff, and it was amazing where you could just close it and open it and get back to where you were.But like, that's the case where, like, laptops weren't convenient as desktops were because they were always plugged in, powered on, you can leave them and you can effectively just come back and sit down and pick up where you left off. And so, I think that this is another moment where we need to make these cloud development environments more convenient to be able to use and ultimately better. And part of that convenience is to make it so that you don't have to think about all these parts of them of whether they're running, not running, how much they cost, whether you're going to be there [unintelligible 00:31:35] or lose their data. Like, that should be the value of it that I don't have to think about any of that stuff.Corey: So, my last question for you is, when you take a look at people who have migrated to using Gitpod, specifically from the corporate perspective, what are their realizations after the fact—I mean, assuming they still take your phone calls because that's sort of feedback of a different sort—but what have they realized has worked well? What keeps them happy and coming back and taking your calls?Mike: Yeah, our customers could focus on their business instead of focusing on all the issues that they have with configuring development environments, everything that could go wrong. And so, a good example of this is a customer they have, Quizlet, Quizlet saw a 45-point increase in developer satisfaction and a 60% reduction in incidents, and the time that it takes to onboard new engineers went down to ten minutes. So, we have some customers that we talk to that come to us and say, “It takes us 20 days to onboard an engineer because of all the access they need and everything you need to set up and credentials and things, and now we could boil that down to a button click.” And that's the thing that we tend to hear from people is that, like, they just don't have to worry about this anymore and they tend to be able to focus on their business and what the developers are actually trying to do, which is build their product.And in Quizlet's example, it was really cool to see them mention in one of the recent OpenAI announcements around GPT4 and plugins is they were one of the early customers that built GPT4 plugins, or ChatGPT, and they mentioned that they were sharing a lot of Gitpod URLs around when we reached out to congratulate them. And the thing that was great about that, for us is, like, they were talking about their business and what they were developing and how they were being successful. And we'd rather see Gitpod in your development environment just sort of disappear into the background. We'd actually like to not hear from customers because it's just working so well from them. So, that's what we found is that customers are just able to get to this point where they could just focus on their business and focus on what they're trying to develop and focus on making their customers successful and not have to worry about infrastructure for development.Corey: I think that really says it all. On some level, when you have customers who are happy with what's happening and how they're approaching this, that really is the best marketing story I can think of because you can say anything you want about it, but when customers will go out and say, “Yeah, this has made our lives better; please keep doing what you're doing,” it counts for a lot.Mike: Yeah, I agree. And that's what we're trying to do. You know, we're not trying to win, sort of, a tab versus spaces debate here around local or cloud or—I actually just want to enable customers to be able to do their work of their business and develop software better. We want to try to provide a method and a platform that's extensible and customizable and gives them all the power they need to be able to just be ready to code, to get to work as soon as they can.Corey: I really want to thank you for being so generous with your time. If people want to learn more, where's the best place for them to find you, other than at your conference in San Francisco in a few weeks?Mike: [laugh]. Yeah, thank you. I really appreciate the banter back and forth. And I hope to see you there at our conference. You should come. Consider this an invite for June 1st and 2nd in San Francisco at CDE Universe.Corey: Of course. And we will put links to this in the [show notes 00:34:53]. Thank you so much for being so generous with your time. I appreciate it.Mike: Thanks, Corey. That was really fun.Corey: Mike Brevoort, Chief Product Officer at Gitpod. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment detailing exactly why cloud development is not the future, but then lose your content halfway through because your hard drive crashed.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.
The release of Ubuntu 23.04 Lunar Lobster is nigh so we take a look at some of the things the security team has been doing along the way, plus it's our 6000th USN so we look back at the last 19 years of USNs whilst covering security updates for the Linux kernel, Emacs, Irssi, Sudo, Firefox and more.
This just in, egg corner, you won't believe what happens next! Scammers are everywhere, watch out! It's my way or the highway. Wait, who's way? Andrew tells us about a brand new app called Calendar.app and 15 alternatives. And don't forget, ~~One Prime Plus Dot Com~~ Canion Dot Blog Slash Save! Damn Flies 00:00:00 Gnat (https://en.wikipedia.org/wiki/Gnat) :bug Fly (https://en.wikipedia.org/wiki/Fly)
Welcome to Dev Game Club, where this week we continue our series on Dwarf Fortress. We talk about working on a thing for a long time, the refinements of the latest version, and a host of other small issues. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary. Sections played: Several hours of the latest version of the game Issues covered: rendering different glyphs, working on a thing for twenty years, the historical record, preservation, iteration, a game of saying yes, being able to leverage systems to other purposes, adding to the interface, modernizing their UI, experimentation and direction, setting goals, greater clarity, when a dwarf can't do a thing, doing more planning due to exposure to the systems, intuiting where things should go in relation to one another, the presentation of UI, the depth of the emotional state of the dwarves, world generation and fantasy elements, amount of space determining how dwarves will act, hotkeying to views, elevation levels of the world, planning ahead, the responsiveness of the dwarves, increased tick rate and the way it impacts play, communicating state of what the dwarf is up to, how the game might do on Steam, the appeal of life simulation games, emergent stories, a child playing with the trash, adding dialog for trade, giving goals or quests without a quest system, making a thing out of the trade panel, the tradeoff of fidelity and simulation, the benefits of Moore's Law, games we have a hard time playing now, liking problematic things, the sign that a thing is a problem from another's perspective, simple mechanics that work, increasing the fun. Games, people, and influences mentioned or discussed: Monkey Island, Grim Fandango, Halo, World of Warcraft, APEX Legends, Fortnite, SimCity, Lynx, Lexis-Nexis, DOS, Linux/Unix, Emacs, Indiana Jones and the Temple of Doom, Minecraft, Populous, Civilization, RimWorld, The Sims, Will Wright, DOOM (1993), Cities: Skylines, Fallout, Farmville, Skyrim, Flight of the Conchords, Colin Tougas, GTA III, Pokemon Red/Blue, Hideo Kojima, Metal Gear Solid, Dragon's Lair, Tron, Death Stranding, Jarkko Sivula, Rogue, Dark Souls, RPG Maker, Unity, Godot, Uncharted, Mainichi, Mattie Brice, Microsoft Powerpoint, Sierra On-Line, Kirk Hamilton, Aaron Evers, Mark Garcia. Next time: The Steam Version Twitch: brettdouville or timlongojr, instagram:timlongojr, Twitter: @timlongojr and @devgameclub DevGameClub@gmail.com
About GeneGene Kim is a multiple award-winning CTO, researcher and author, and has been studying high-performing technology organizations since 1999. He was founder and CTO of Tripwire for 13 years. He has written six books, including The Unicorn Project (2019), The Phoenix Project (2013), The DevOps Handbook (2016), the Shingo Publication Award winning Accelerate (2018), and The Visible Ops Handbook (2004-2006) series. Since 2014, he has been the founder and organizer of DevOps Enterprise Summit, studying the technology transformations of large, complex organizations.Links: The Phoenix Project: https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/1942788290/ The Unicorn Project: https://www.amazon.com/Unicorn-Project-Developers-Disruption-Thriving/dp/B0812C82T9 The DevOps Enterprise Summit: https://events.itrevolution.com/ @RealGeneKim TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Cloud Economist Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: If you asked me to rank which cloud provider has the best developer experience, I'd be hard-pressed to choose a platform that isn't Google Cloud. Their developer experience is unparalleled and, in the early stages of building something great, that translates directly into velocity. Try it yourself with the Google for Startups Cloud Program over at cloud.google.com/startup. It'll give you up to $100k a year for each of the first two years in Google Cloud credits for companies that range from bootstrapped all the way on up to Series A. Go build something, and then tell me about it. My thanks to Google Cloud for sponsoring this ridiculous podcast.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey Quinn: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by a man who needs no introduction but gets one anyway. Gene Kim, most famously known for writing The Phoenix Project, but now the Wall Street Journal best-selling author of The Unicorn Project, six years later. Gene, welcome to the show.Gene Kim: Corey so great to be on. I was just mentioning before how delightful it is to be on the other side of the podcast. And it's so much smaller in here than I had thought it would be.Corey Quinn: Excellent. It's always nice to wind up finally meeting people whose work was seminal and foundational. Once upon a time, when I was a young, angry Unix systems administrator—because it's not like there's a second type of Unix administrator—[laughing] The Phoenix Project was one of those texts that was transformational, as far as changing the way I tended to view a lot of what I was working on and gave a glimpse into what could have been a realistic outcome for the world, or the company I was at, but somehow was simultaneously uplifting and incredibly depressing all at the same time. Now, The Unicorn Project does that exact same thing only aimed at developers instead of traditional crusty ops folks.Gene Kim: [laughing] Yeah, yeah. Very much so. Yeah, The Phoenix Project was very much aimed at ops leadership. So, Bill Palmer, the protagonist of that book was the VP of Operations at Parts Unlimited, and the protagonist in The Unicorn Project is Maxine Chambers, Senior Architect, and Developer, and I love the fact that it's told in the same timeline as The Phoenix Project, and in the first scene, she is unfairly blamed for causing the payroll outage and is exiled to The Phoenix Project, where she recoils in existential horror and then finds that she can't do anything herself. She can't do a build, she can't run her own tests. She can't, God forbid, do her own deploys. And I just love the opening third of the book where it really does paint that tundra that many developers find themselves in where they're just caught in decades of built-up technical debt, unable to do even the simplest things independently, let alone be able to independently develop tests or create value for customers. So, it was fun, very much fun, to revisit the Parts Unlimited universe.Corey Quinn: What I found that was fun about—there are few things in there I want to unpack. The first is that it really was the, shall we say, retelling of the same story in, quote/unquote, “the same timeframe”, but these books were written six years apart.Gene Kim: Yeah, and by the way, I want to first acknowledge all the help that you gave me during the editing process. Some of your comments are just so spot on with exactly the feedback I needed at the time and led to the most significant lift to jam a whole bunch of changes in it right before it got turned over to production. Yeah, so The Phoenix Project is told, quote, “in the present day,” and in the same way, The Unicorn Project is also told—takes place in the present day. In fact, they even start, plus or minus, on the same day. And there is a little bit of suspension of disbelief needed, just because there are certain things that are in the common vernacular, very much in zeitgeist now, that weren't six years ago, like “digital disruption”, even things like Uber and Lyft that feature prominently in the book that were just never mentioned in The Phoenix Project, but yeah, I think it was the story very much told in the same vein as like Ender's Shadow, where it takes place in the same timeline, but from a different perspective.Corey Quinn: So, something else that—again, I understand it's an allegory, and trying to tell an allegorical story while also working it into the form of a fictional work is incredibly complicated. That's something that I don't think people can really appreciate until they've tried to do something like it. But I still found myself, at various times, reading through the book and wondering, asking myself questions that, I guess, say more about me than they do about anyone else. But it's, “Wow, she's at a company that is pretty much scapegoating her and blaming her for all of us. Why isn't she quitting? Why isn't she screaming at people? Why isn't she punching the boss right in their stupid, condescending face and storming out of the office?” And I'm wondering how much of that is my own challenges as far as how life goes, as well as how much of it is just there for, I guess, narrative devices. It needed to wind up being someone who would not storm out when push came to shove.Gene Kim: But yeah, I think she actually does the last of the third thing that you mentioned where she does slam the sheet of paper down and say, “Man, you said the outage is caused by a technical failure and a human error, and now you're telling me I'm the human error?” And just cannot believe that she's been put in that position. Yeah, so thanks to your feedback and the others, she actually does shop her resume around. And starts putting out feelers, because this is no longer feeling like the great place to work that attracted her, eight years prior. The reality is for most people, is that it's sometimes difficult to get a new job overnight, even if you want to. But I think that Maxine stays because she believes in the mission. She takes a great deal of pride of what she's created over the years, and I think like most great brands, they do create a sense of mission and there's a deep sense of the customers they serve. And, there's something very satisfying about the work to her. And yeah, I think she is very much, for a couple of weeks, very much always thinking about, she won't be here for long, one way or another, but by the time she stumbles into the rebellion, the crazy group of misfits, the ragtag bunch of misfits, who are trying to find better ways of working and willing to break whatever rules it takes to take over the very ancient powerful order, she falls in love with a group. She found a group of kindred spirits who very much, like her, believe that developer productivity is one of the most important things that we can do as an organization. So, by the time that she looks up with that group, I mean, I think she's all thoughts of leaving are gone.Corey Quinn: Right. And the idea of, if you stick around, you can theoretically change things for the better is extraordinarily compelling. The challenge I've seen is that as I navigate the world, I've met a number of very gifted employees who, frankly wind up demonstrating that same level of loyalty and same kind of loyalty to companies that are absolutely not worthy of them. So my question has always been, when do I stick around versus when do I leave? I'm very far on the bailout as early as humanly possible side of that spectrum. It's why I'm a great consultant but an absolutely terrible employee.Gene Kim: [laughing] Well, so we were honored to have you at the DevOps Enterprise Summit. And you've probably seen that The Unicorn Project book is really dedicated to the achievements of the DevOps Enterprise community. It's certainly inspired by and dedicated to their efforts. And I think what was so inspirational to me were all these courageous leaders who are—they know what the mission is. I mean, they viscerally understand what the mission is and understand that the ways of working aren't working so well and are doing whatever they can to create better ways of working that are safer, faster, and happier. And I think what is so magnificent about so many of their journeys is that their organization in response says, “Thank you. That's amazing. Can we put you in a position of even more authority that will allow you to even make a more material, more impactful contribution to the organization?” And so it's been my observation, having run the conference for, now, six years, going on seven years is that this is a population that is being out promoted—has been promoted at a rate far higher than the population at large. And so for me, that's just an incredible story of grit and determination. And so yeah, where does grit and determination becomes sort of blind loyalty? That's ultimately self-punishing? That's a deep question that I've never really studied. But I certainly do understand that there is a time when no amount of perseverance and grit will get from here to there, and that's a fact.Corey Quinn: I think that it's a really interesting narrative, just to see it, how it tends to evolve, but also, I guess, for lack of a better term, and please don't hold this against me, it seems in many ways to speak to a very academic perspective, and I don't mean that as an insult. Now, the real interesting question is why I would think, well—why would accusing someone of being academic ever be considered as an insult, but my academic career was fascinating. It feels like it aligns very well with The Five Ideals, which is something that you have been talking about significantly for a long time. And in an academic setting that seems to make sense, but I don't see it thought of or spoken of in the same way on the ground. So first, can you start off by giving us an intro to what The Five Ideals are, and I guess maybe disambiguate the theory from the practice?Gene Kim: Oh for sure, yeah. So The Five Ideals are— oh, let's go back one step. So The Phoenix Project had The Three Ways, which were the principles for which you can derive all the observed DevOps practices from and The Four Types of Work. And so in The Five Ideals I used the concept of The Five Ideals and they are—the first—Corey Quinn: And the next version of The Nine whatever you call them at that point, I'm sure. It's a geometric progression.Gene Kim: Right or actually, isn't it the pri—oh, no. four isn't, four isn't prime. Yeah, yeah, I don't know. So, The Five Ideals is a nice small number and it was just really meant to verbalize things that I thought were very important, things I just gravitate towards. One is Locality and Simplicity. And briefly, that's just, to what degree can teams do what they need to do independently without having to coordinate, communicate, prioritize, sequence, marshal, deconflict, with scores of other teams. The Second Ideal is what I think the outcomes are when you have that, which is Focus, Flow and Joy. And so, Dr. Mihaly Csikszentmihalyi, he describes flow as a state when we are so engrossed in the work we love that we lose track of time and even sense of self. And that's been very much my experience, coding ever since I learned Clojure, this functional programming language. Third Ideal is Improvement of Daily Work, which shows up in The Phoenix Project to say that improvement daily work is even more important than daily work itself. Fourth Ideal is Psychological Safety, which shows up in the State of DevOps Report, but showed up prominently in Google's Project Oxygen, and even in the Toyota production process where clearly it has to be—in order for someone to pull the andon cord that potentially stops the assembly line, you have to have an environment where it's psychologically safe to do so. And then Fifth Ideal is Customer Focus, really focus on core competencies that create enduring, durable business value that customers are willing to pay for, versus context, which is everything else. And yeah, to answer your question, Where did it come from? Why do I think it is important? Why do I focus on that? For me, it's really coming from the State of DevOps Report, that I did with Dr. Nicole Forsgren and Jez Humble. And so, beyond all the numbers and the metrics and the technical practices and the architectural practices and the cultural norms, for me, what that really tells the story of is of The Five Ideals, as to what one of them is very much a need for architecture that allows teams to work independently, having a higher predictor of even, continuous delivery. I love that. And that from the individual perspective, the ideal being, that allows us to focus on the work we want to do to help achieve the mission with a sense of flow and joy. And then really elevating the notion that greatness isn't free, we need to improve daily work, we have to make it psychologically safe to talk about problems. And then the last one really being, can we really unflinchingly look at the work we do on an everyday basis and ask, what the customers care about it? And if customers don't care about it, can we question whether that work really should be done or not. So that's where for me, it's really meant to speak to some more visceral emotions that were concretized and validated through the State of DevOps Report. But these notions I am just very attracted to.Corey Quinn: I like the idea of it. The question, of course, is always how to put these into daily practice. How do you take these from an idealized—well, let's not call it a textbook, but something very similar to that—and apply it to the I guess, uncontrolled chaos that is the day-to-day life of an awful lot of people in their daily jobs.Gene Kim: Yeah. Right. So, the protagonist is Maxine and her role in the story, in the beginning, is just to recognize what not great looks like. She's lived and created greatness for all of her career. And then she gets exiled to this terrible Phoenix project that chews up developers and spits them out and they leave these husks of people they used to be. And so, she's not doing a lot of problem-solving. Instead, it's this recoiling from the inability for people to do builds or do their own tests or be able to do work without having to open up 20 different tickets or not being able to do their own deploys. She just recoil from this spending five days watching people do code merges, and for me, I'm hoping that what this will do, and after people read the book, will see this all around them, hopefully, will have a similar kind of recoiling reaction where they say, “Oh my gosh, this is terrible. I should feel as bad about this as Maxine does, and then maybe even find my fellow rebels and see if we can create a pocket of greatness that can become like the sublimation event in Dr. Thomas Kuhn's book, The Structure of Scientific Revolutions.” Create that kernel of greatness, of which then greatness then finds itself surrounded by even more greatness.Corey Quinn: What I always found to be fascinating about your work is how you wind up tying so many different concepts together in ways you wouldn't necessarily expect. For example, when I was reviewing one of your manuscripts before this went to print, you did reject one of my suggestions, which was just, retitle the entire thing. Instead of calling it The Unicorn Project. Instead, call it Gene Kim's Love Letter to Functional Programming. So what is up with that?Gene Kim: Yeah, to put that into context, for 25 years or more, I've self-identified as an ops person. The Phoenix Project was really an ops book. And that was despite getting my graduate degree in compiler design and high-speed networking in 1995. And the reason why I gravitated towards ops, because that was my observation, that that's where the saves were made. It was ops who saved the customer from horrendous, terrible developers who just kept on putting things into production that would then blow up and take everyone with it. It was ops protecting us from the bad adversaries who were trying to steal data because security people were so ineffective. But four years ago, I learned a functional programming language called Clojure and, without a doubt, it reintroduced the joy of coding back into my life and now, in a good month, I spend half the time—in the ideal—writing, half the time hanging out with the best in the game, of which I would consider this to be a part of, and then 20% of time coding. And I find for the first time in my career, in over 30 years of coding, I can write something for years on end, without it collapsing in on itself, like a house of cards. And that is an amazing feeling, to say that maybe it wasn't my inability, or my lack of experience, or my lack of sensibilities, but maybe it was just that I was sort of using the wrong tool to think with. That comes from the French philosopher Claude Lévi-Strauss. He said of certain things, “Is it a good tool to think with?” And I just find functional programming is such a better tool to think with, that notions like composability, like immutability, what I find so exciting is that these things aren't just for programming languages. And some other programming languages that follow the same vein are, OCaml, Lisp, ML, Elixir, Haskell. These all languages that are sort of popularizing functional programming, but what I find so exciting is that we see it in infrastructure and operations, too. So Docker is fundamentally immutable. So if you want to change a container, we have to make a new one. Kubernetes composes these containers together at the level of system of systems. Kafka is amazing because it usually reveals the desire to have this immutable data model where you can't change the past. Version control is immutable. So, I think it's no surprise that as our systems get more and more complex and distributed, we're relying on things like immutability, just to make it so that we can reason about them. So, it is something I love addressing in the book, and it's something I decided to double down on after you mentioned it. I'm just saying, all kidding aside is this a book for—Corey Quinn: Oh good, I got to make it worse. Always excited when that happens.Gene Kim: Yeah, I mean, your suggestion really brought to the forefront a very critical decision, which was, is this a book for technology leaders, or even business leaders, or is this a book developers? And, after a lot of soul searching, I decided no, this is a book for developers, because I think the sensibilities that we need to instill and the awareness we need to create these things around are the developers and then you just hope and pray that the book will be good enough that if enough engineers like it, then engineering leaders will like it. And if enough engineering leaders like it, then maybe some business leaders will read it as well. So that's something I'm eagerly seeing what will happen as the weeks, months, and years go by. Corey Quinn: This episode is sponsored in part by DataStax. The NoSQL event of the year is DataStax Accelerate in San Diego this May from the 11th through the 13th. I've given a talk previously called the myth of multi-cloud, and it's time for me to revisit that with... A sequel! Which is funny given that it's a NoSQL conference, but there you have it. To learn more, visit datastax.com that's D-A-T-A-S-T-A-X.com and I hope to see you in San Diego. This May.Corey Quinn: One thing that I always admired about your writing is that you can start off trying to make a point about one particular aspect of things. And along the way you tie in so many different things, and the functional programming is just one aspect of this. At some point, by the end of it, I half expected you to just pick a fight over vi versus Emacs, just for the sheer joy you get in effectively drawing interesting and, I guess, shall we say, the right level of conflict into it, where it seems very clear that what you're talking about is something thing that has the potential to be transformative and by throwing things like that in you're, on some level, roping people in who otherwise wouldn't weigh in at all. But it's really neat to watch once you have people's attention, just almost in spite of what they want, you teach them something. I don't know if that's a fair accusation or not, but it's very much I'm left with the sense that what you're doing has definite impact and reverberations throughout larger industries.Gene Kim: Yeah, I hope so. In fact, just to reveal this kind of insecurity is, there's an author I've read a lot of and she actually read this blog post that she wrote about the worst novel to write, and she called it The Yeomans Tour of the Starship Enterprise. And she says, “The book begins like this: it's a Yeoman on the Starship Enterprise, and all he does is admire the dilithium crystals, and the phaser, and talk about the specifications of the engine room.” And I sometimes worry that that's what I've done in The Unicorn Project, but hopefully—I did want to have that technical detail there and share some things that I love about technology and the things I hate about technology, like YAML files, and integrate that into the narrative because I think it is important. And I would like to think that people reading it appreciate things like our mutual distaste of YAML files, that we've all struggled trying to escape spaces and file names inside of make files. I mean, these are the things that are puzzles we have to solve, but they're so far removed from the business problem we're trying to solve that really, the purpose of that was trying to show the mistake of solving puzzles in our daily work instead of solving real problems.Corey Quinn: One thing that I found was really a one-two punch, for me at least, was first I read and give feedback on the book and then relatively quickly thereafter, I found myself at my first DevOps Enterprise Summit, and I feel like on some level, I may have been misinterpreted when I was doing my live-tweeting/shitposting-with-style during a lot of the opening keynotes, and the rest, where I was focusing on how different of a conference it was. Unlike a typical DevOps Days or big cloud event, it wasn't a whole bunch of relatively recent software startups. There were serious institutions coming out to have conversations. We're talking USAA, we're talking to US Air Force, we're talking large banks, we're talking companies that have a 200-year history, where you don't get to just throw everything away and start over. These are companies that by and large, have, in many ways, felt excluded to some extent, from the modern discussions of, well, we're going to write some stuff late at night, and by the following morning, it's in production. You don't get to do that when you're a 200-year-old insurance company. And I feel like that was on some level interpreted as me making fun of startups for quote/unquote, “not being serious,” which was never my intention. It's just this was a different conversation series for a different audience who has vastly different constraints. And I found it incredibly compelling and I intend to go back.Gene Kim: Well, that's wonderful. And, in fact, we have plans for you, Mr. Quinn.Corey Quinn: Uh-oh.Gene Kim: Yeah. I think when I say I admire the DevOps Enterprise community. I mean that I'm just so many different dimensions. The fact that these, leaders and—it's not leaders just in terms of seniority on the organization chart—these are people who are leading technology efforts to survive and win in the marketplace. In organizations that have been around sometimes for centuries, Barclays Bank was founded in the year 1634. That predates the invention of paper cash. HMRC, the UK version of the IRS was founded in the year 1200. And, so there's probably no code that goes that far back, but there's certainly values and—Corey Quinn: Well, you'd like to hope not. Gene Kim: Yeah, right. You never know. But there are certainly values and traditions and maybe even processes that go back centuries. And so that's what's helped these organizations be successful. And here are a next generation of leaders, trying to make sure that these organizations see another century of greatness. So I think that's, in my mind, deeply admirable.Corey Quinn: Very much so. And my only concern was, I was just hoping that people didn't misinterpret my snark and sarcasm as aimed at, “Oh, look at these crappy—these companies are real companies and all those crappy SAS companies are just flashes in the pan.” No, I don't believe that members of the Fortune 500 are flash in the pan companies, with a couple notable exceptions who I will not name now, because I might want some of them on this podcast someday. The concern that I have is that everyone's work is valuable. Everyone's work is important. And what I'm seeing historically, and something that you've nailed, is a certain lack of stories that apply to some of those organizations that are, for lack of a better term, ossified into their current process model, where they there's no clear path for them to break into, quote/unquote, “doing the DevOps.”Gene Kim: Yeah. And the business frame and the imperative for it is incredible. Tesla is now offering auto insurance bundled into the car. Banks are now having to compete with Apple. I mean, it is just breathtaking to see how competitive the marketplaces and the need to understand the customer and deliver value to them quickly and to be able to experiment and innovate and out-innovate the competition. I don't think there's any business leader on the planet who doesn't understand that software is eating the world and they have to that any level of investment they do involves software at some level. And so the question is, for them, is how do they get educated enough to invest and manage and lead competently? So, to me it really is like the sleeping giant awakening. And it's my genuine belief is that the next 50 years, as much value as the tech giants have created: Facebook, Amazon, Netflix, Google, Microsoft, they've generated trillions of dollars of economic value. When we can get eighteen million developers, as productive as an engineer at a tech giant is, that will generate tens of trillions of dollars of economic value per year. And so, when you generate that much economic activity, all problems become solvable, you look at climate change, you take a look at the disparity between rich and poor. All things can be fixed when you significantly change the economic economy in this way. So, I'm extremely hopeful and I know that the need for things like DevOps are urgent and important.Corey Quinn: I guess that that's probably the best way of framing this. So you wrote one version that was aimed at operators back in 2013, this one was aimed at developers, and effectively retails and clarifies an awful lot of the same points. As a historical ops person, I didn't feel left behind by The Unicorn Project, despite not being its target market. So I guess the question on everyone's mind, are you planning on doing a third iteration, and if so, for what demographic?Gene Kim: Yeah, nothing at this point, but there is one thing that I'm interested in which is the role of business leaders. And Sarah is an interesting villain. One of my favorite pieces of feedback during the review process was, “I didn't think I could ever hate Sarah more. And yet, I did find her even to be more loathsome than before.” She's actually based on a real person, someone that I worked with.Corey Quinn: That's the best part, is these characters are relatable enough that everyone can map people they know onto various aspects of them, but can't ever disclose the entire list in public because that apparently has career consequences.Gene Kim: That's right. Yes, I will not say who the character is based on but there's, in the last scene of the book that went to print, Sarah has an interesting interaction with Maxine, where they meet for lunch. And, I think the line was, “And it wasn't what Maxine had thought, and she's actually looking forward to the next meeting.” I think that leaves room for it. So one of the things I want to do with some friends and colleagues is just understand, why does Sarah act the way she does? I think we've all worked with someone like her. And there are some that are genuinely bad actors, but I think a lot of them are doing something, based on genuine, real motives. And it would be fun, I thought, to do something with Elizabeth Henderson, who we decided to start having a conversation like, what does she read? What is her background? What is she good at? What does her resume look like? And what caused her to—who in technology treated her so badly that she treats technology so badly? And why does she behave the way she does? And so I think she reads a lot of strategy books. I think she is not a great people manager, I think she maybe has come from the mergers and acquisition route that viewed people as fungible. And yeah, I think she is definitely a creature of economics, was lured by an external investor, about how good it can be if you can extract value out of the company, squeeze every bit of—sweat every asset and sell the company for parts. So I would just love to have a better understanding of, when people say they work with someone like a Sarah, is there a commonality to that? And can we better understand Sarah so that we can both work with her and also, compete better against her, in our own organizations?Corey Quinn: I think that's probably a question best left for people to figure out on their own, in a circumstance where I can't possibly be blamed for it.Gene Kim: [laughing].That can be arranged, Mr. Quinn.Corey Quinn: All right. Well, if people want to learn more about your thoughts, ideas, feelings around these things, or of course to buy the book, where can they find you?Gene Kim: If you're interested in the ideas that are in The Unicorn Project, I would point you to all of the freely available videos on YouTube. Just Google DevOps Enterprise Summit and anything that's on the plenary stage are specifically chosen stories that very much informed The Unicorn Project. And the best way to reach me is probably on Twitter. I'm @RealGeneKim on Twitter, and feel free to just @ mention me, or DM me. Happy to be reached out in whatever way you can find me. Corey Quinn: You know where the hate mail goes then. Gene, thank you so much for taking the time to speak with me, I appreciate it.Gene Kim: And Corey, likewise, and again, thank you so much for your unflinching feedback on the book and I hope you see your fingerprints all over it and I'm just so delighted with the way it came out. So thanks to you, Corey. Corey Quinn: As soon as my signed copy shows up, you'll be the first to know.Gene Kim: Consider it done. Corey Quinn: Excellent, excellent. That's the trick, is to ask people for something in a scenario in which they cannot possibly say no. Gene Kim, multiple award-winning CTO, researcher, and author. Pick up his new book, The Wall Street Journal best-selling The Unicorn Project. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on Apple Podcasts. If you hated this podcast, please leave a five-star review on Apple Podcasts and leave a compelling comment.Announcer: This has been this week's episode of Screaming in the Cloud. You can also find more Corey at ScreamingintheCloud.com or wherever fine snark is sold.This has been a HumblePod production. Stay humble.
It's the third annual Unplugged Tuxies; our community votes on the best projects, distros, desktops, and services of 2022.
© 2020-2025 Ivy Podcast Discovery LLC
