Podcasts about Bret Victor

A Rust for Linux developer resigns amidst rising tension in the Linux community, Bret Victor shows off what he's been working on for years, Rachel (by the bay) laments how useless "SRE" has become as a role, Doug Turnbull makes the case for hiring junior devs & Baldur Bjarnason says the LLM honeymoon phase is about to end.

A Rust for Linux developer resigns amidst rising tension in the Linux community, Bret Victor shows off what he's been working on for years, Rachel (by the bay) laments how useless "SRE" has become as a role, Doug Turnbull makes the case for hiring junior devs & Baldur Bjarnason says the LLM honeymoon phase is about to end.

A Rust for Linux developer resigns amidst rising tension in the Linux community, Bret Victor shows off what he's been working on for years, Rachel (by the bay) laments how useless "SRE" has become as a role, Doug Turnbull makes the case for hiring junior devs & Baldur Bjarnason says the LLM honeymoon phase is about to end.

Brought to you by Eppo—Run reliable, impactful experiments | Vanta—Automate compliance. Simplify security | Ezra—The leading full-body cancer screening company—Lane Shackleton is CPO of Coda, where he's been leading the product and design team for over eight years. Lane started his career as an Alaskan climbing guide and then as a manual reviewer of AdWords ads before becoming a product specialist at Google and later a Group PM at YouTube. He also writes a weekly newsletter with insights and rituals for PMs, product teams, and startups. In today's conversation, we discuss:• Principles that set great PMs apart• Rituals of great product teams• The fine line between OKRs and strategy, and why it matters• “Two-way write-up”• The story of how skippable YouTube ads were born and lessons learned• How to gauge personal career growth• “Tim Ferriss Day” and its impact on Coda's history• How Lane bootstrapped his way to CPO from the bottom of the tech ladder—Find the transcript and references at: https://www.lennyspodcast.com/what-sets-great-teams-apart-lane-shackleton-cpo-of-coda/ —Where to find Lane Shackleton:• X: https://twitter.com/lshackleton• LinkedIn: https://www.linkedin.com/in/laneshackleton• Substack: https://lane.substack.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) Lane's background(04:03) Working as a guide in Alaska(07:32) Parallels between guiding and building software(09:12) Why Lane started studying and writing about product teams(12:49) How Lane came up with the career ladder and guiding principles(14:10) The five levels Coda's career ladder(16:30) Principles of great product managers(21:06) The beginner's-mind ritual at Coda(24:05) Two rituals: “cathedrals not bricks” and “proactive not reactive”(27:46) How to develop your own guiding principles(31:17) Learning from your “oh s**t” moments(36:03) Rituals from great product teams: HubSpot's FlashTags(42:15) Rituals from great product teams: Coda's Catalyst(47:01) Implementing rituals from other companies(49:48) How to navigate changing vs. sticking with current rituals(53:02) “Tag up” and why one-on-one meetings are harmful (55:27) Lane's handbook on strategy and rituals(57:10) How skippable ads came about on YouTube   (1:01:46) Lane's path to CPO(1:07:02) Advice for aspiring PMs(1:10:53) Tim Ferriss Day at Coda(1:13:24) Using two-way write-ups (1:19:30) The fine line between OKRs and strategy, and why it matters(1:21:41) Lightning round—Referenced:• Endurance: https://www.amazon.com/Endurance-Shackletons-Incredible-Alfred-Lansing/dp/0465062881• Bret Victor's talk “Inventing on Principle”: https://www.youtube.com/watch?v=EGqwXt90ZqA• Jeremy Britton on LinkedIn: https://www.linkedin.com/in/jeremybritton/• Comedian on Netflix: https://www.netflix.com/title/60024976• The Score Takes Care of Itself: My Philosophy of Leadership: https://www.amazon.com/Score-Takes-Care-Itself-Philosophy/dp/1591843472• The Creative Act: A Way of Being: https://www.amazon.com/Creative-Act-Way-Being/dp/0593652886• AlphaZero: https://en.wikipedia.org/wiki/AlphaZero• Antoine de Saint-Exupéry: https://en.wikipedia.org/wiki/Antoine_de_Saint-Exup%C3%A9ry• Storyworthy: Engage, Teach, Persuade, and Change Your Life through the Power of Storytelling: https://www.amazon.com/Storyworthy-Engage-Persuade-through-Storytelling/dp/1608685489• The Moth: https://themoth.org/events• Seth Godin's website: https://www.sethgodin.com/• The Obstacle Is the Way: The Timeless Art of Turning Trials into Triumph: https://www.amazon.com/Obstacle-Way-Timeless-Turning-Triumph/dp/1591846358• Tony Fadell's TED talk: https://www.youtube.com/watch?v=9uOMectkCCs• FlashTags: A Simple Hack for Conveying Context Without Confusion: https://www.onstartups.com/flashtags-a-simple-hack-for-conveying-context-without-confusion• How Coda builds product: https://www.lennysnewsletter.com/p/how-coda-builds-product• 100-dollar voting ritual: https://coda.io/@lshackleton/100-dollar-voting-exercise• Pixar's Brain Trust: https://pixar.fandom.com/wiki/Brain_Trust• Lane's product handbook: coda.io/producthandbook• The rituals of great teams | Shishir Mehrotra of Coda, YouTube, Microsoft: https://www.lennyspodcast.com/the-rituals-of-great-teams-shishir-mehrotra-coda-youtube-microsoft/• Principle #4: Learn by making, not talking: https://lane.substack.com/p/principle-4-learn-by-making-not-talking• Phil Farhi on LinkedIn: https://www.linkedin.com/in/philfarhi/• How to ask the right questions, project confidence, and win over skeptics | Paige Costello (Asana, Intercom, Intuit): https://www.lennyspodcast.com/how-to-ask-the-right-questions-project-confidence-and-win-over-skeptics-paige-costello-asana-intercom-intuit/• Chip Conley's website: https://chipconley.com/• Jeff Bezos Banned PowerPoint in Meetings. His Replacement Is Brilliant: https://www.inc.com/carmine-gallo/jeff-bezos-bans-powerpoint-in-meetings-his-replacement-is-brilliant.html• Working Backwards: Insights, Stories, and Secrets from Inside Amazon: https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595• Dory and Pulse: https://coda.io/@codatemplates/dory-and-pulse• Turning the Flywheel: A Monograph to Accompany Good to Great: https://www.amazon.com/Turning-Flywheel-Monograph-Accompany-Great/dp/0062933795/• Waking Up: A Guide to Spirituality Without Religion: https://www.amazon.com/Waking-Up-Spirituality-Without-Religion/dp/1451636024• The Inner Game of Tennis: The Classic Guide to the Mental Side of Peak Performance: https://www.amazon.com/Inner-Game-Tennis-Classic-Performance/dp/0679778314• Good Strategy/Bad Strategy: The Difference and Why It Matters: https://www.amazon.com/Good-Strategy-Bad-Difference-Matters/dp/0307886239• The Last Dance on Netflix: https://www.netflix.com/title/80203144• Full Swing on Netflix: https://www.netflix.com/title/81483353• Stephen Curry: Underrated on AppleTV+: https://tv.apple.com/us/movie/stephen-curry-underrated/umc.cmc.23v0wxaiwz60bjy1w4vg7npun• Arrested Development on Netflix: https://www.netflix.com/title/70140358• Shishir's interview question clip on TikTok: https://www.tiktok.com/@lennyrachitsky/video/7160779872296652078• The Ultimate Reference Check Template: https://coda.io/@startup-hiring/reference-checks-template• SwingVision: https://swing.tennis/• Waking Up app: https://www.wakingup.com/—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

Shanea Leven, co-founder and CEO of CodeSee, shared her journey as a tech founder in an episode of the Tech Founder Odyssey podcast series. Despite coming to programming later than many of her peers, Leven always had a creative spark and a passion for making things. She initially pursued fashion design but taught herself programming in college and co-founded a company building custom websites for book authors. This experience eventually led her to a job at Google, where she worked in product development.While at Google, Leven realized the challenge of deciphering legacy code and onboarding developers to it. Inspired by a presentation by Bret Victor, she came up with the idea for CodeSee—a developer platform that helps teams understand and review code bases more effectively. She started working on CodeSee in 2019 as a side project, but it soon received venture capital funding, allowing her to quit her job and focus on the startup full-time.Leven candidly discussed the challenges of juggling a day job and a startup, particularly after receiving funding. She also shared advice on raising money from venture capitalists and building a company culture.Listen to the full episode and check out more installments from The Tech Founder Odyssey.How Teleport's Leader Transitioned from Engineer to CEOHow 2 Founders Sold Their Startup to Aqua Security in a YearHow Solvo's Co-Founder Got the ‘Guts' to Be an Entrepreneur

Smart contracts aren't actually new. Computer scientist, legal scholar, and cryptographer Nick Szabo coined the term in 1994 (possibly earlier, depending on who you ask). Old problems seem to keep coming back. Bret Victor gave a talk in 2013 called “The Future of Programming,” where he talked about problems from 1973 that were still relevant. To learn more about the Agoric blockchain, check out their homepage. If you'd rather shape how the blockchain itself operates, much of Agoric's code is open source. Connect with Dean on Twitter or Telegram

Before the time-travelling talks, the programmable rooms, the ladders and rocket launchers, we had the first real Bret Victor essay: Magic Ink. It set the stage for Bret's later explorations, breaking down the very idea of "software" into a few key pieces and interrogating them with his distinct focus, then clearly demoing a way we could all just do it better. All of Bret's works feel simultaneously like an anguished cry and a call to arms, and this essay is no exception. For the next episode, we're reading Programming as Theory Building as Peter Naur, with a little bit of Gilbert Ryle's The Concept of Mind thrown in for good measure. Links Four Hundred of the most Chart-Topping Thoughts of All Time: Inventing On Principal Stop Drawing Dead Fish Drawing Dynamic Visualizations Dynamicland Paper Programs by JP Posma was inspired by Dynamicland. "Computers aren't the thing. They're the thing that gets us to the thing." from Halt and Catch Fire Charticulator is Microsoft Research's take on a _Drawing Dynamic Visualizations_-esq tool. Jimmy's Fender Jazz bass looks like this, but red, but like a decade older, but like $600 at the time. We could probably post parts of this episode as Boyfriend Roleplay on YouTube. Fitts's Law is but one thing we've learned about the industrial design aspect of building good software. The Witness is a game where communicating ideas through (essentially) graphic design is the whole entire point of the game. If you haven't played it, know that it comes highly recommended by plenty of folks in the community. A "red letter Bible" is a Bible in which the words spoken by Jesus are colored red, to make them easier to identify. Toph Tucker has a pretty cool personal website. It's rare to see these sorts of sites nowadays, and they're always made by adventuresome programmers, trendy design agencies, or their clients. In the Flash era, it felt like everyone had a website like this, for better and for worse. tldraw is a beautiful little browser-based drawing tool by Steve Ruiz. What few things it does, it does exceptionally well. John while Henry had had had had had had had had had been my preference. #devlog-together is the channel on our Future of Coding slack community where members post small, frequent updates about what they're working on. The (Not Boring) apps are arguably a counterpoint to Bret's theses about information apps and harmful interaction, where the interaction and graphic design are balanced against being maximally-informative, toward being silly and superfluous, to great effect. Did you know there's a hobby horse, but also a hobby horse? I didn't! There are a few examples of folks doing FoC work that, in Ivan's view, align well with the values Bret outlines in Magic Ink: Szymon Kaliski's projects for Ink & Switch, summarized in his Strange Loop talk, Programmable Ink. Mock Mechanics is an environment for building mechanisms by Felipe Reigosa. PANE by Josh Horowitz inverts the usual node-wire programming pattern by putting data in the nodes and data transformation in the wires. Robot Odyssey was a 1984 game for the Apple II (and some other, lesser systems) in which players would go inside various robots to reprogram them. Music featured in this episode: Wash Machine, from the unfinished 2014 album Sneaky Dances Shaun's Amaj Rebirth, created in November 2022 for a friend named — you guessed it — Shaun. Hey! Send us questions we can answer on the show. Like, "How do you keep bread warm?" Or, "What's so great about concatenative languages?" We'll answer them. Send them here: Jimmy Ivan Or just DM one of us in the FoC Slack. futureofcoding.org/episodes/060See omnystudio.com/listener for privacy information.

[00:01:01] Andrew explains how he had to make a complex data table.[00:03:27] Chris talks about an entry at Rails Hackathon called “Con[text]” for learning Spanish and English.[00:05:07] We learn about some of the cool improvements with the new Turbo release.[00:11:08] Chris tells us everything that went on at Rails Hackathon, and he tells us the winner of the Judges' Favorite which was Typefighters by Team Rubades.[00:13:42] Find out more about the Best Solo/Community Favorite award given to Jim Jones' Checkpoint Rails, and Chris brings up a talk Bret Victor did in 2012 called, “Inventing on Principle.”[00:19:38] We hear more about the killer submission, Airtable clone by HotTable, which won the “Most Phlex-ible” award.[00:22:22] The last award Chris explains is the “Kent Believe He Finished” award.[00:23:20] Andrew asks Chris if he saw any usage of Turbo that he was surprised about and never would have thought to do that.[00:26:29] Chris explains the support they had for Rails Hackathon and what he wants for the next one. [00:29:29] Chris tells us how he wants to do Rails Hackathons a couple times a year and things they could do to keep it fun. [00:34:21] Andrew mentions to Chris for the next Hackathon they should think about adding some categories so when they judge they can do some comparing. [00:35:25] Without leaking too much info, Andrew announces he started pairing with Nate Hopkins on the weekends again.Panelists:Chris OliverAndrew MasonSponsor:HoneybadgerLinks:Jason Charnes TwitterChris Oliver TwitterAndrew Mason TwitterRails Hackathon 2022 Winnerscheckpoint-rails 0.1.2Bret Victor-Inventing on Principle (YouTube)Destroy All Software (Gary Bernhardt)Ruby Radar NewsletterRuby Radar Twitter

Dobrodošli na Zalet — podkast o dizajnu digitalnih proizvoda! Imamo prvog gosta! Veliko nam je zadovoljstvo što smo imali priliku da ugostimo Milovana Jovičića Miku. Milovan je dizajner, konsultant, organizator mitapa i violinista. Pričali smo o konsaltingu, zajednicama, etici u dizajnu i biciklama za um.Poglavlja

The Circles- product (incl integrations)- docs- content- community- UGCTALK ABOUT SVELTE SOCIETY STORYDimensions of the Circles- negative engineering? or dev exceptions- onboarding -> production -> prod-dev -> billing -?Other definitions of devx- single command do a lot -> until too magic- does what it says you would do- making some cycles faster -> esbuild 100x faster - bret victor inventing on principleFuture of Devx? integrate forward, or backward- content creation meta - video. shortgame + longgame.- backward -> going into docs, productListen to the DevX pod: https://devxpod.buzzsprout.com/1895030/10012425-the-radiating-circles-in-devx-with-swyx-head-of-developer-experience-temporalPauline: 0:00Hi, Shawn! Thank you so much for joining us for a DevX pod today. We're really excited to have you on board. I just wanted to point out this is one of those things where I tweeted about something and then someone was like, I recommend this person. And then I found you, so this is really exciting and we're going to have this awesome conversation about developer experience. Maybe for those who may not have heard of you before, can you give us a bit of an introduction on your story? What you're all about?Shawn: 0:31Yeah. Thanks for inviting me on. I'm Shawn also known as swyx online. I originally am from Singapore and, moved to the U S for college and pretty much the rest of my career and spent my first career in finance before changing careers to tech. And since I joined tech, I've been fairly known for learning in public, for speaking about reacts and serverless. And now I work as Head of Developer Experience at Temporal.Pauline: 0:55I have a follow-up question actually. What does it mean to be head of developer experience at Temporal?Shawn: 1:02It's a role that we basically, I created for myself because when they were reaching out to hire me, they didn't have something like that. And I don't think it's a common role at a startup as well. The bit of a background, which we can get into like how I got started into developer experience. I previously worked at Netlify where I originally joined as a developer advocate type person, but then when Sarah Drasner came along and started leading us as a VP she restructured the whole thing to make it more of a developer experience engineer. So I'm turning developer relations into something where you actually do a bit more engineering and are responsible for parts of the developer experience rather than talking about it. Then I continued that into AWS, whereas also a driver advocate for AWS Amplify. Well, I think for me, the role that I really thought would make the most sense to borrow was something that spans across docs and developer advocacy as well as community. And then I was also a product manager for our recent tax group STK. When you're in a smaller startup, you kind of have to wear many hats. And so, uh, this developer experience umbrella felt that the most descriptiveMike: 2:14I think you literally just covered the next two questions I wanted to go talk about. I wonder if you have any more details in terms of overall what DevX is to you?Shawn: 2:25Yeah. I've actually written some thoughts about this. I kind of think about it as a radiating circle out from the core product. And so part of this is influenced by me struggling with developer relations at Netlify and at AWS, because often there's a separate team that is responsible for docs. There's a separate team that's responsible for product. It's very hard actually, when you realize. A lot of the things that you do as a developer advocate is very it's downstream of everything else that's above you. And if they're shipped and organized by different teams, then you can get a very disjoint experience. Essentially like your impact as a developer advocate may not be as high because people don't see your stuff as much as they see the docs or the experience about it. So just think about it in terms of like, okay, you start with the core products, make sure that the product design and you get enough feedback. You make sure that API design is really solid. then you radiate out into the docs, which is your sort of first party content on how to use it. I consider docs secondary to products because the best doc's is the docs you don't have to read, right. That is intuitive experience, but still you need docs anyway. And then going out from the docs you need, you go into first party content, which is the role of a developer advocate. And that is anything that's ancillary to docs that explains the why instead of the, what or the how. But you can also dive into the what and the how as well. Like sometimes you just need to pitch the same thing, seven different ways before someone gets it. And then you go from the first party content, which is your blog posts and talks and stuff like that. It's very traditional DevRel fodder into community, which is going from one to many communication to many, to many communication. In other words, having a place where your users talk to other users and help each other out. And then the final tier is enabling third-party content, which is I think about it in terms of users writing blog posts and books, workshops and courses and tutorials about you, even posting jobs with your tool or your technology in the job description on anything like this, where it's very user initiated. I really like encouraging that because that's how you know that you start scaling developer experience beyond the sheer number of people that are working in your company because you have users working for you. But that only happens after you got all the core inner loop stuff right.Mike: 4:48I like the analogy with the radiator being in the middle and starting to do, send the heat out. I wonder, what's your take on in product developer experience, how do you make sure you don't have to ride this doc? Do you know that chapter in the documentation and how do you deal with that? Are you directly involved in the product to make certain changes that you think are more intuitive? Or how does that go?Shawn: 5:13Yeah, I think it depends on the maturity of the company. This role or this job changes very much depending on whether you're a seed stage or series B and maybe you're not a venture funded company, but depending on the maturity of the products, right? If the thing is mostly fully formed, then you have much less impact or possibility of changing things. But for me, I was directly involved in shaping every single part of the API that we shipped for the TypeScript and I wrote almost every single word of the docs. Very extremely involved! Because then after that it can flow from there to my DevRel efforts and community building efforts. So I think it really depends. The second thing it really depends on is how visual you are versus how much of a code base Platform you are. So we are very code based. In other words, we care much more about API design than user experience design or UI design. I think UI design for visual product makes sense. I think Gitpod probably more of a visual products because there's no Gitpod API. I mean, there's a config and there's no Gitpod API that I integrate into my app or anything like that. Netlify where I used to work as well. Yes, there's another Netlify config, but like the rest of the thing is just point and click. So in that sense, yes. The role of UI design, I think is very powerful. The last point I'll mentioned for you as well, is that another principle or API design principle that applies regardless of whether you're doing visual or programmatic SDK work, is that you want to try to enhance the power of a single command. So for us it was Netlify deploy or git commit, and that would create a whole new deploy preview. And that was a big revolution in front end development. There was other analogies in the CLI that we should, that we shift this well that I was involved in. But I always think about that in terms of like, okay, how do you increase the power of a single action and just pack as much as possible in there? I really liked that idea. I don't know if that is described as good developer experience, but to me, I think that really contributes to a wow moment that where you type a single command and something magical happens, because that would have typically taken many steps to accomplish.Mike: 7:27I think this is a great way to describe it. The other thing I like is when it does what you expect it to do, I think that's another huge one. You could have add whatever, but then, it does only half of the stuff or, yeah there's really good examples out there for sure. Nice.Shawn: 7:42There's a part of a developer experience, which I often talk about which is a developer exceptions. In other words, developer experience often we talk about happy paths. Like, oh, if you ask them, do I like this? Look at how amazing it is. Look at how awesome and how fast and how everything, how amazing everything is. But people in developer experience often don't talk about the, what happens when things go wrong and actually sometimes paying attention to giving you a nice remedial path when something goes wrong is actually also a really good experience that developer experience, which people don't talk. So improving observability, making sure that you don't have pricing mistakes or your pricing is predictable, at least. And doing things like having clear versioning and deprecation support policies, these all kind of boring and less headliner things that you want to ship, but it's actually very key for developer experience.Pauline: 8:35That's a really good point. You said having a wow moment and that I think is a really good explanation of what developer experience is. Why is it important to you that we have that wow moment? Why should we even care about developer experience? Why have that wow moment?Shawn: 8:54I think the wow moment is more of a marketing thing in the sense that there's a lot of developer tools out there and you need to stand out somehow and you need to get to that wow moment as quickly as possible because everyone has other things going on. They may click away if you don't get to that wow moment. so I think that's part of it. The other part, which is also like game design, in the sense that, you need to keep having rushes of endorphins to you, to make your job fun, to have the developers stay in flow and developers that stay in flow and more productive. As to why in general, should we even care about developer experience? I actually, yeah. There's a cynical view. And then there's a more genuine view. The one genuine view is that developer experience helps, developers be more productive, which helps ship more products and makes users happy and blah, blah, blah, develop a tooling companies are worth multiple billions of dollars. And if you can help a developer tools company improve the developer experience in whatever form, then that creates a lot of value for developers. That's the feel good, happy view. My secret problem with developer experiences that I don't think it's that important. Like it's, you're not curing cancer. You're not flying to Mars or anything like that. So I think it's intellectually, interesting and financially very rewarding career. But we should also be a bit humble about. Yeah. Like nobody wakes nobody else outside of developers cares about developing experience. We, they just care about, are you making the thing that helps me make the other thing go faster or ship faster, whatever. And that's it. All these other metrics around, like, I don't know, like number of people visiting your blog posts, like no one cares. So I'm very cynical about that sort of thing. OhMike: 10:45no, my analytics,Pauline: 10:49I was just going to say that's... That's probably the most refreshing take actually. Because I feel like a lot of other people have not mentioned it in that sort of way or describe developer experience in that way you are right.Shawn: 11:02Also, I wasn't interviewing there, I was talking with a very senior person at Cloudflare and, I told him this . And he was, I think he was like considering to hire me or whatever. And it wasn't an interview or anything, but I think I closed that door when I told him this, because he was like, what are you talking about? Developer Experience is everything. I'm like, dude, like, come on. Like, like developers are very pampered. Like we have like unlimited leave ,we have like six figure salaries. We're fine. Like, we don't, you don't have to pretend like this is the highest value thing in the world. But, I mean, it's still very valuable. It's just it's one of many possible things that smart people are. Oh, could you read it one more? Nice thing, which is that I think improving the developer experience for beginners is very important. Enables beginners to get started, to make the career, to, to transition their careers which is I'm a career changer myself. And if I did not have the help of people who focus so much on docs and community and, making things accessible to beginners, then I would not be here. I'm not against it. I'm just saying it's not, you know, there are also many other important things.Pauline: 12:09Absolutely. If you're like a doctor or a surgeon, or solving our pandemic . Yeah. No, thank you for that. A lot of our guests have said accessibility especially to begin as is why people should continue caring about developer experience and improving it and stuff like that. That's a good point.Shawn: 12:25Yes.Mike: 12:29No, no, I, I was, uh, I wanted to move on, but that's a good point. And it does make moving on a bit easier then on the previous note we talked about, so I think we talked about the commands that, you know, do a lot for you. What other kind of like excellent developer experience have you experienced or maybe build yourself or with the team that you can share about?Shawn: 12:49I feel like I should write this down because there's a number of nice develop experiences that stick in my head that I haven't really articulated very well. So in other words, single command doing multiple things that's good until the point that it becomes too magic and then that's bad. We've established that already. Another one that I really like is making some cycles faster, right? If you can make things in order of magnitude faster than you have better developer experience. Something that people bring up a lot is the benchmarks of IES built in the JavaScript ecosystem, comparing to Webpack or a parcel or roll-up. On the ESPP build website, they have a very prominent benchmark that shows that they are a hundred times faster than Webpack. And that is. And when anytime you increase things by orders of magnitude, that you unlock different usage of that tool. And so I think it's a very important thing to try to always look for areas in which you can speed up the feedback cycle because then you unlock opportunities for play. I think one of the best talks on developer experience that everybody has talked about is I think Bret Victor's inventing on principle talk, where he shows like, okay, if instead of jumping back and forth between your editor and your final output, why not just combine them and have your app or your writing be directly interactable so that you can shape it and play with it as you go along and discover new things because of the play. So I really am inspired by that. And there's a simple analogy to the shift left ideology that came out of IBM, which is that a lot of times when people discover bugs, they discover it very late in production, or even after they shifted in production. And if you shift things left, if you reduce the feedback loop of finding bugs, whether through tests or types or a QA or whatever, right? There's a whole bunch of techniques that are all developer tooling and development experience related. If you shift those items left from production back into the development time, then you enable the opportunity to increase the feedback loop in and correct your mistakes before they get too far out, or you build too much. So I really liked that feedback loop reduction, and then another developer experience thing, which I really like is this idea that everything is just there for you. In other words, you don't have to go out and assemble a bunch of different tools yourself, having an all in one package that with blessed the tools that are known to work together, I think is really helpful. One example of this is I'm actually going to venture out to the jobs review system and talk about Anaconda and Python. So Python is a fairly wide and huge community. But Anaconda is a specific distribution of hyphen with preselected pack packages that are all guaranteed to work together because dependency resolution was a huge problem for the Python ecosystem and the data scientists that were using Python, where it's spending so much time, like trying to say, like, does this work at the other thing? No, it doesn't. So I will have to both drop back to like an older version of the common thing, blah, blah, blah. Very common in JavaScript as well, by the way. But Anaconda actually managed to carve out a niche in Python and made Python, the de facto language for machine learning because they made that develop experience so much. And I actually genuinely think that they are, single-handedly responsible for making Python itself that much more popular. I think that's another interesting thing, which is like, where's the all-in-one for the 80% of use cases that don't need that much customization. Of course, if you want to customize sure, go ahead. You have the full power, but most people, they don't, they just have very standard needs. Let's just do this, just pave out the common path. And so that's how I went from using React. Which is the most popular Javascript framework, to Svelte, which Mike knows very well. And so has all the tools and tools included batteries included. And if I need to customize or drop out of it, I can. And I think that is also a really good developer experience in there so that the, all the ones who toolkit it, that doesn't constrain you too much.Mike: 16:57So really the question for 2022 is what's the Anaconda of JavaScript?Shawn: 17:01When Vercel talks about building the SDK for the web, that's what they mean.Mike: 17:04Yeah. Good point.Pauline: 17:05You gave me lots of flashbacks of playing around with Python over the past few years. I haven't really been in that ecosystem in a long time. Actually, Mike will be really proud of me, but I started learning and rebuilding one of my big projects. One of my, well, actually my blog, which is my biggest project, in Svelte, moving away from Nextjs. But, it's taking me quite a long time, longer than I thought, because there's so many. I don't know, there's so many different things that I need to learn how to use this Svelte way of doing things. But yeah, it's really interesting. It's a lot of fun. I understand why Mike and yourself love it so much. I think.Mike: 17:43We will talk offline about that Pauline.Pauline: 17:46So let's, let's do that. Yeah. Lots to, lots of talk about, yeah, it's messy. Yeah. Awesome. Thank you for sharing that.Shawn: 17:55One thing I'll share with you about this Svelte thing. I'm friends with Rich. I had come across Svelte, but actually ignored him for a year until I was like on a trip with him at Barcelona. And then he was like, he's still talking about Svelte. And I was like, okay, I have to try this because you can only be friends with someone so long before you have to try their things. And then I tried it and I was like, oh, okay. I'm an idiot for ignoring this for so long. But the other thing. Notice was that Svelte did not have a very strong community backing behind it. So actually started Svelte society as a part of the next stage of developer experience. So if you think about that reading radiating circle thing, had a very strong product already and it needed and it had pretty good docs. It needed the next level, which is community or DevRel, whatever that is. There is no first party DevRel for Svelte, but I guess Rich's the one had a one man show for that. The community part was the thing that I focused on and that's how Svelte society got started.Pauline: 18:45I was going to say, but this is what is this? Maybe the sixth or seventh episodes that we'll be posting on dev X pod and community has taken the lead every single time. It's always the thing that brings everything together. And it's also very validating because I focused on community at Gitpod so every time I hear it, I'm just like, yeah, that was great. Cool. Awesome. I wanted to move on to our next question, which is, where do you see DevX evolving? Will we be focused on tools or people or community?Shawn: 19:20I think, in line with the model that we've been developing, in this episode, either you integrate forward or integrate backwards, in other words, a typical typically develop experience is very tied to developer relations and a lot of first party content creation. So you integrate forward, meaning that talk a little bit more with community, you take on more community management roles or you encourage more, third party content by holding workshops and stuff like that. Or you integrate backwards, which is you get more involved with products. So I think that's an interesting way to think about this in terms of the radiating circles, but the other way to think about it as well is what's the shift within the content creation meta game, which I think about a lot as well. So for me right now is that I think a lot of people should be shifting towards video. I think that, the amount of time that how much time do you spend. You know, a week or a day I spent roughly an hour or two hours. Yeah,Pauline: 20:14exactly. I was going to say a bigger number than that, so, yeah. I'm glad you said your number first.Shawn: 20:19We all spend, we all spent a lot of time and a lot of times we're never going to spend on developer content because we're just on YouTube to veg out to. But I think people who do video very well are getting disproportionate attention. And I think it's a very scalable format. There are challenges with it, which I think Mike has maybe one up in the past before, which is that video is very expensive to produce and it gets outdated very quickly. There will be new tools that arise to fix that. But otherwise, I think the sheer reach of YouTube is just unparalleled. It is the second biggest search engine in the world. The content that lives on there, if you can get it to be evergreen, it can be extremely valuable. I still get comments on videos that I did two years ago, I always think about the half-life of content. The half-life of a tweet is four hours. The half-life of a blog post is maybe like a year or if it's a good blog post, if it's a normal. blog post that everyone is like treating us nothing special then. Yeah. It's probably a day or so. That will be irrelevant in a non-existent, but for videos. It's definitely very long. So I'm very interested in that. And I almost also interested in this idea of having a short game in the long game. It's kind of like tennis. If you only play long games, if you only stay at the back and you only love the ball and then you get killed on the, on the short game. Likewise. So in other words, do you have a short form game where you can pitch your startup in very short and concise detail? And do you have a long game where if people want to engage with you over very in-depth conversation, you also have ability to go deep and you have the content to offer them. I think having, so this is why I focus on having two minute videos and three hour workshops. you want to go extremes? There's a lot of 30 minute talks and podcasts out there. That's fine. But, I think the areas of relative under development are the short game and the long game.Mike: 22:12I had a conversation with a friend recently where she was asking me like, Hey, why don't we put some educational tech content on TikTok? And it was around the time when, TikTok had took over Google products in terms of like number of visits in 2021. And that was yeah, actually, why not? So I signed up for TikTok and I spent like 10 minutes watching videos. And I'm like, this is crap. Like what the heck? There's just too much stuff I don't care about. So I need a way to filter the stuff I care about. But then I started searching for things like web development, full stack development, and then whatnot. And there's a few things, but I think what you're saying in terms of the two minutes versus longer things, you can take that to an even other extreme of I'm going to take a real cheesy example, but array methods. One video, 15 seconds about each method and put it up there, see if it goes viral and people talk about it. But I think this is another platform that it's going to up and coming and currently not used for it, I think might be a really interesting play.Shawn: 23:11To see if it started watching it. I'm keeping eyes on it as well. The problem is that every, everybody knows array methods and you're not really doing anything for your work by explaining a writing methods. You might grow your own personal following, but that's also not a very valuable following. And let's just be real about that, right? If you get a whole bunch of beginners, then you will be incentivized to create more beginner content and you'll be stuck in beginner tutorial. And then I see a lot of people also get stuck to that because the numbers are only thing that matters to them. So I think, as far as philosophy of consecration goes, I definitely aim for some mix of intellectual curiosity and reach. And if you have only reach, then you may sell out yourself and you may burn out. You may not fall in love with the process. And I think that is the saddest thing in the world for someone to be in such a privileged job as a developer experience person, and to have your own personal intellectual curiosity, thrown by the wayside. I do, and they're doing courage to try to pursue some mix of reach plus first intellectual curiosity. I think the person that really does it best is Scott Hanselman. I don't know if you follow him. To talk as well. He does introductory stuff, but it's always authentic to him. He's not selling out. He's genuinely like, Hey, I think this is really important. And whether or not it happens to be advanced or intermediate or beginner, he's always very much that this is something he genuinely thinks in his.Pauline: 24:34The first thing that's on my mind is the fact that I love how in the past two episodes, actually we've been talking about, we've been bringing to light, content creation in developer experience because I don't think a lot of people think about that. Certainly until the previous episode, I didn't really think of developer experience, including content creation or including things like videos or tech talks, because the only thing I was thinking about was the products, like how can we make the product better? So that engineers on board quickly. So yeah, I really liked this conversation and it's really quite eye opening for me. I don't know. Mike, I wanted to say to your point, TikTok does get better after you train the algorithm. I was like, I don't know why anyone is on this app is just full of gen Z. I was just like, I don't understand this. But then after I started watching content that I actually liked it's really good it's really interesting. And now I've been hooked like at least an hour a day. I've been on it.Mike: 25:33But well, on the bright side, I have a lot of different methods to peel a pineapple now. So I learned aPauline: 25:43lot of, and the how to use an air fryer in all these different ways, how to cook all these different recipes. Oh, yeah, it's really cool. I just find it really interesting that content creation is included, but it really validates where my thoughts are in terms of content creation and develop experience as a whole.Shawn: 26:01This job, this industry is still very nascent, so it's not well-defined. So I don't think you should feel weird about it at all. I think for me, I came at it from my background, which is that we called this DevRel function, this content creation function at Netlify, we called it developer experience engineer. And so that's part of what we do. I should also mention that. Yeah, we were responsible for third-party integrations as well. So I guess.Pauline: 26:33Exactly.Shawn: 26:35But no, I think, at the end of the day, people wants to develop the tools. Companies want people to discover them and the best ways to, through content marketing. And that's why they hire people who are smart at that. And getting them down through that top of the funnel is very useful to them. I think probably where that we need to do better is that yes, I can pull a lot of people at the top of funnel, but if the product doesn't align with what they expect, then it's going to be a very leaky bucket. A lot of people going to come in, they're going to kick the tires and then they're going to leave. So how can we get a higher qualified audience or how can we get a product that is more intuitive or that retains people better? My own personal journey has been very much backward integrating into.Mike: 27:21Nice. Yeah, I feel like every episode we recorders, I always go away with it and I'm like, okay, let me think about all that again. And then I started researching and digging deeper and I'm like, there's a lot of interesting stuff. And we're really just getting started and five years from now, if we had another episode and talked about what is DevRel going? We would have a very interesting conversation, probably very different to today. Definitely looking forward to it. Cool. So one thing we tried to do is use kind of at the end of the podcast to wrap up with a fun thing that you recently came across with, or somebody you want to give a shout out to, that really made your day in the last couple of weeks or so? Um, yeah anything top of mind that you want to share?Shawn: 28:01I wasn't prepared for this, but I guess I'll shout out to obsidian. So I think for me, my personal note taking system is very much very important to me in terms of having it as a second brain where I store all the thoughts that I had that are still working progress or data points on some essay that I'm writing, but it's not done yet. And I moved around a lot from simple note to one note to notion. And most recently I made the shift to obsidian and the way I decided on this is that I really wanted to bet on mark down. I think mark down is a format that's going to. Longer than any of us. And that I also wanted it to sync, to GitHub and to have a good mobile application and obsidian match all of those things. Plus it has an optional service to publish your notes so I can share what I am thinking as I think it, for people who really care about, finding out before I publish something on my blog. Obsidian is a really good note taking.Pauline: 29:01I was going to say that is really interesting that you shared that for this week because Mike I'll just go next. But the thing that I wanted to share this week is actually LogSeq which is similar to obsidian. I don't know if you've heard of it. I think it's created by the same people or someone had left obsidian team and then built it. I'm not actually sure of the background. But I have been using it for the past two months now. And it's my favorite note taking app, just because, I think in bullet points. And I sometimes feel overwhelmed when I used to use other note taking apps where I would write like a long block of notes and then I try to organize it, but it just all felt overwhelming. Whereas when I have bullet points at the start of when I'm taking notes, it just like sinking things into my head better. I don't know. No, it just makes sense for my workflow. And then every single day, I don't need to worry about organizing my notes. I can just when I open up the app tomorrow, I will have a fresh, clean slate and I can start I'm taking notes of my day. And again, it's become my second brain because then I can just scroll back down and be like, what did they do yesterday again? And then everything is in one place. So yeah, LogSeq is my shout out of the week actually. And it was just really interesting that you brought up obsidian. Cause I think they go hand in hand. Well, but yeah, over to you, Mike, what's your fun thing about.Mike: 30:30Well, you really put me in a tough spot because I feel like I need to talk about my note taking,Pauline: 30:35I genuinely have this prepared in my notes. I was like, this is what I'm going to talk about, which is why I was really interested in,Mike: 30:42oh, I'll take the Liberty to do two things. One is my note taking app, which is Reflect.App. Exactly the same concept. You get a little graph every day. It gives you a new empty note, you take your note, but same idea. Markdown, I guess, for the win. The other thing I did have in my notes though to share is I don't even know if I should share it because I literally just found out about it two days ago when I read the landing page, but I want to dive deeper into it. It's swim.io with double M. And what they're saying is that they sync your talks with your code. So it's more of like a documentation tool for code, it seems well, the screenshot looks interesting. Let's say that. So I'm going to dive into it, but I figured this, is it something that is literally just top of mind, for today's podcast then? Um, I figuredShawn: 31:30out what share that. Yeah, we actually a hand-rolled we had wrote something like this for our own docs. I don't know if it's a startup. I remember this one because, swim, they raised a pretty big series, a 30 million, and also it's coming out of Israel. So it's just like a really it's the market, this big come on. But, uh, Hey, you know, it's a hard problem and it helps developer experience.Pauline: 31:53We'll link everything that we mentioned from this episode in the show notes, but we have reached the end of the podcast. Oh my gosh time has flown by. Thank you so much, Shawn, for joining us today, I'm excited to share this episode with everyone. So many things to think about, and Mike said earlier, I actually edit these podcasts, so I listen to them, quite a few times over. Every time I listened to them, I'm like, wow, there's so many ideas here that we can take on for Gitpod, for community or whatever it is. I'm really excited to re-listen to this multiple times, take the best bits and then share it with everyone. So yeah. Just want to say thank you again.Shawn: 32:30Well, thanks for having me pleasure. I'm really excited that you guys are doing this because people are dying for more DevX content. Every time I post something about it. You know, how I feel about that mix now? And so every time I posted about it, I always feel like a bit of a mix of like, okay, like, this is interesting, but also I don't want it to define who I am, but I think it, yeah, it's definitely very valuable and people are very interested.Pauline: 32:51Yes, absolutely. Absolutely. I'm sure it's going to be an interesting lesson to a lot of people!

This podcast was one of the best experiences I've been gifted. Hope you enjoy a few hours with a guy who needs no introduction, Vlad Magdalin. Find Guest: Vlad Magdalin Twitter: https://twitter.com/callmevlad?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor Website: www.webflow.com Contact Host: Emily Giordano Email: emily@greatdesignlead.com Website: www.greatdesignlead.com YouTube: https://www.youtube.com/channel/UCQfSnsyrx3kGp92-s0Jj91w LinkedIn: https://www.linkedin.com/in/emily-giordano/ Instagram: @greatdesignlead - https://www.instagram.com/greatdesignlead/ Resources: The Infinite Game Book by Simon Sinek Inventing on Principle by Bret Victor - https://youtu.be/PUv66718DII Magic Ink by Bret Victor - http://worrydream.com/MagicInk/ Bret Victor - http://worrydream.com/ --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

Ian Johnson is a former Google UX engineer and data visualization engineer with ObservableHQ building data visualizations with JavaScript. He works on both the tools and the visualizations built with D3 on the web. He discusses how to use tools like D3 to tell a story using your data. Panel Dan ShappirSteve Edwards Guest Ian Johnson Sponsors Shortcut (formerly Clubhouse.io)Raygun | Click here to get started on your free 14-day trialDev Influencers Accelerator Links ObservableDrawing with DataScales / Observable PlotTwitter: Ian Johnson ( @enjalot ) Picks Dan- Apple's Browser Engine Ban Is Holding Back Web App Innovation – The New StackIan- Bret Victor, beast of burdenIan- For ExampleIan- Bret Victor - Inventing on Principle - YouTubeSteve- Dad Jokes on InstagramSteve- Dad Jokes by Pubity Contact Dan: GitHub: Dan Shappir ( DanShappir )LinkedIn: Dan ShappirTwitter: Dan Shappir ( @DanShappir ) Contact Steve: Twitter: Steve Edwards ( @wonder95 )GitHub: Steve Edwards ( wonder95 )LinkedIn: Steve Edwards Special Guest: Ian Johnson.

Ian Johnson is a former Google UX engineer and data visualization engineer with ObservableHQ building data visualizations with JavaScript. He works on both the tools and the visualizations built with D3 on the web. He discusses how to use tools like D3 to tell a story using your data. Panel Dan ShappirSteve Edwards Guest Ian Johnson Sponsors Shortcut (formerly Clubhouse.io)Raygun | Click here to get started on your free 14-day trialDev Influencers Accelerator Links ObservableDrawing with DataScales / Observable PlotTwitter: Ian Johnson ( @enjalot ) Picks Dan- Apple's Browser Engine Ban Is Holding Back Web App Innovation – The New StackIan- Bret Victor, beast of burdenIan- For ExampleIan- Bret Victor - Inventing on Principle - YouTubeSteve- Dad Jokes on InstagramSteve- Dad Jokes by Pubity Contact Dan: GitHub: Dan Shappir ( DanShappir )LinkedIn: Dan ShappirTwitter: Dan Shappir ( @DanShappir ) Contact Steve: Twitter: Steve Edwards ( @wonder95 )GitHub: Steve Edwards ( wonder95 )LinkedIn: Steve Edwards Special Guest: Ian Johnson.

About this episode This week's episode features an interview with Vlad Magdalin, co-founder of Webflow. For those that may not be aware, Webflow (at its core) is a website building platform, but yet it is so much more. Webflow is a platform that has enabled thousands of designers to act as an design and development agency because Webflow allows anyone to design masterfully, and develop online engagements without any need to know how to code. In fact, just a few weeks ago we had Duncan Hamra, cofounder of Memberstack on The Startup Story. In his episode we discovered that Memberstack was built ontop of Webflow. So the reality is that Webflow is not just a website builder but an entire web and software development platform that is democratizing how web design and development is achieved. Vlad is an incredible storyteller and you're going to love his full episode. But for me, one of my favourite aspects of his entrepreneurial journey. Is the fact that both he and his brother (who is also his co-founder) are refugees from Russia and who grew up in the Shadows of Silicon Valley. Having immigrated to the US only days before the collapse of the Soviet Union, Vlad knows quite a bit about starting over from scratch. And aside from overcoming many personal struggles as he adapted his life to try and fit in within the United States. It also took him and his brother four separate tries to get their now two-billion-dollar company up and running. Vlad's story is so incredibly relatable because the startup story for many companies is not one continuous thread, sometimes it has many starts and stops and Vlad was no different. In this episode, you'll hear: Vlad shares how he was born in the USSR and his parents took the massive risk to move him and his siblings to America in 1991. He shares what it was like growing up in American from the age of 9 and how he struggled with his identity and he tried to hide that he was from Russia. When Vlad was looking to go to college his parents said he should do a computer course like his brother. He did this for one term then dropped out to go to art school to do 3D animation as he aspired to work at Pixar. While he was at college Vlad had his first entrepreneurial venture. Vlad was using Quickdot to chat with his friends but the app crashed. So picked up a book on programming and started writing a clone of Quickdot but developed it and started ChatterFox. Here he fell in love with programming. Vlad shares how he first came up with the idea for Webflow when he was an intern at a design agency. He accidentally saw how the company was charging their clients hundreds of thousands of dollars while Vlad was getting paid $7 an hour. This sparked his entrepreneurial flair and he wanted to fix the problem he saw and make it better for everyone involved. Vlad shares how he pushed back starting Webflow for 6 years and experienced many ups and downs with this. He almost gave up until one day he randomly receives a trademark certificate for Webflow, that he applied for it over 5 years ago. He took this as a sign to keep going. How he went viral on Hacker News. In less than 24 hours it was the number 1 post and went viral on Twitter. Vlad shares the posting on hacker news drove over 20,000 sign ups. When Webflow launched only 30 people out of the 20,000 paid to use the software. Vlad shares that with those first 30 customers they started a group chat, to hear direct complaints, suggestions and requests they were making. How they think Webflow hasn't even scratched the surface yet of what's to come for the website and with their Series B round completed they are on to developing Webflow. Resources from this episode Join Grindology: https://grindology.com/ ExpressVPN: Get 3 Months Free → https://www.expressvpn.com/startupstory Get Emails: https://app.getemails.com/referrals/newaccount?ref=R18HWW5 The Startup Story Inner Circle: https://www.thestartupstory.co/vip The Startup Story on LinkedIn: https://www.linkedin.com/company/thestartupstory The Startup Story is now on YouTube: https://www.youtube.com/jamesmckinney The Startup Story on Instagram: https://www.instagram.com/thestartupstory Webflow Website: https://webflow.com/ Webflow Instagram: https://www.instagram.com/webflow/ Webflow Twitter: https://twitter.com/webflow Webflow Facebook: https://www.facebook.com/webflow/ Bret Victor, Investing On Principle: https://www.youtube.com/watch?v=PUv66718DII Share the podcast The Startup Story community has been so incredible in sharing our podcast with others, and we thank you! We do have more stories to tell and more people to reach. So please keep sharing!

Overview Programming is not just about creating enterprise-level apps but can be put to work to help people express themselves creatively in many different ways. This is just one of a few profound takeaways from today’s show, where we got a chance to sit down with Pine Wu, former Visual Studio Code developer at Microsoft who built Vetur, a language server that enhances the Vue editing experience. We talk to Pine about Vetur’s background and functionality, his current nomadic pursuits, and his approach to programming as an art or a means to art more than anything else. On the subject of Vetur, Pine explains the context behind the name, and what led him to build the project in the first place. He speaks about how he built out early versions of Vetur by leveraging open source code from other platforms, how the project blew up overnight, its current abilities, and what the future holds. From there, we move on to discuss Pine’s thoughts about what coding means to him. We touch on ideas about the value of exploring content outside of one's discipline, the line between learning and building, and how the tools we create and use structure the way we think about what we work on as well as what we build. Pine also shares a bunch of cool resources today – creative projects using Vue and other frameworks, as well as key texts and talks that have influenced his ideas about art, perception, tools, and computer science. For a wide-reaching conversation about creativity, learning, and writing software that is useful to the world outside of corporations, be sure to tune in! Key Points From This Episode: The human languages and programming languages Pine is fluent in. Matthew Butterick’s work with Racket and why Pine wants to learn this language next. The line between learning and building; recent projects Pine did and what they taught him. Pine’s approach to learning programming as a means of achieving his creative ends. The added perceptive abilities you get from learning things outside of your field. Why ‘computer science’ is a misnomer, describing an art more than a science; how Pine got into programming. New features in Vue 3 and the changes Pine has to make to Vetur to support them. The online channels that Pine is most active on; where to find him if you’d like to get in touch. All the great picks from our hosts and guest from today’s episode. Tweetables: “I learn while I’m doing so I try to start new projects that help me learn.” — @octref [0:04:04] “I would rather sign up for a course in sociology or philosophy or design rather than sign up for a course in programming. That’s how I learn and try to improve my ways of thinking.” — @octref [0:05:58] “Other than learning to innovate on new ideas, I also want to learn to be able to see certain things that people of other disciplines can’t. That’s one of the reasons I am learning to draw with color.” — @octref [0:08:32] Picks of the week: - Pine's picks: - Media for Thinking the Unthinkable: Designing a new medium for science and engineering, Bret Victor (http://worrydream.com/MediaForThinkingTheUnthinkable) - poolside.fm (https://poolside.fm/) - How to Hack a Painting, Tyler Hobbs (https://tylerxhobbs.com/essays/2020/how-to-hack-a-painting) - Future of Coding (https://futureofcoding.org/) - The New Media Reader, edited by Nick Montfort and Noah Wardrip-Fruin (https://bookshop.org/books/the-new-media-reader-with-cdrom/9780262232272) Tessa's picks: Moft Z 5-in-1 Sit-Stand Desk (https://www.moft.us/products/moft-z-5-in-1-sit-stand-desk) The Dance of Anger (https://bookshop.org/books/the-dance-of-anger-cd-a-woman-s-guide-to-changing-the-pattern-of-intimate-relationships/9780060726508), Harriet Lerner Ph.D., read by Barbara Caruso Chilling outside in cars https://parametric.press/issue-01/unraveling-the-jpeg (https://parametric.press/issue-01/unraveling-the-jpeg/) Pine's photography Ben's picks: Sponsor Pine on GitHub (https://github.com/sponsors/octref) Ari's picks: Renpure Rosemary Mint Cleansing Conditioner (https://www.renpure.com/products/hair/solutions-rosemary-mint-cleansing-conditioner/) Links Mentioned in Today’s Episode: Pine Wu on GitHub (https://github.com/octref) Pine Wu on Twitter (https://twitter.com/octref?lang=en) Pine Wu Blog (https://blog.matsu.io/) Vetur (https://vuejs.github.io/vetur/) Mrmrs (http://mrmrs.cc/) Von, 菅野 よう子 (Kanno Yōko), ft. Arnór Dan Arnarson (https://www.youtube.com/watch?v=lfksYyxGRJw) 残響のテロル (Zankyō no Teroru) / Terror in Resonance (https://www.imdb.com/title/tt3613454/) Tyler Hobbs’s Guide to Simulating Watercolor Paint (https://tylerxhobbs.com/essays/2017/a-generative-approach-to-simulating-watercolor-paints) Inventing on Principle (https://www.youtube.com/watch?v=PUv66718DII) Structure and Interpretation of Computer Programs (https://www.amazon.com/Structure-Interpretation-Computer-Programs-Engineering/dp/0262510871) Pollen (https://docs.racket-lang.org/pollen/) Beautiful Racket (https://beautifulracket.com/) Hackers and Painters (http://www.paulgraham.com/hp.html) Bret Victor (http://worrydream.com/) Enjoy the Vue on Twitter (https://twitter.com/enjoythevuecast?lang=en) Special Guest: Pine Wu.

Key Points From This Episode: - An intro into Pine, his experiences at Microsoft, and the work he does in Visual Studio Code. - What leading a nomadic life means to Pine, and the things he enjoys learning as a freelancer. - Pine’s ideas about not only being a programmer but wanting to study graphic design too. - An intro into Vetur, Pine’s project that provides autocomplete functionality for Vue files. - How Pine has expanded Vetur’s functionality beyond autocomplete and diagnostic errors. - The beginnings of Vetur: Pine’s love of Vue which wasn’t compatible with VS Code. - How Pine developed early Vetur versions by copy-pasting and modifying parts of existing support from other platforms. - The story of Vetur’s huge early success after the creator of Repl tweeted about it. - Humor in Pine’s talks and how his non-sugarcoated approach plays into this. Pine’s rapid prototyping tool and how it fits in with his passion for enabling expressive coding. - Perspectives on the idea that tools shape how we think and what we build. - Pine’s thoughts on future Vetur upgrades: A type renaming tool and more. Tweetables: - “If you are editing a TypeScript or JavaScript file in your Visual Studio Code, you see that after you press a dot you see a lot of autocompletions. Those are powered by what is called a language server and a language server basically analyzes the whole code base, breaks your code into abstract syntax trees, analyzes them, and then gives you autocompletion and diagnostic errors. Vetur basically does that for Vue files.” — @octref [0:07:34] - “As a programmer, my passion is not writing enterprise-level or large scale Vue apps. My interest is more in the expressive side of coding.” — @octref [0:17:01] - “Without a microscope, you are unable to work with bacteria. Without a telescope, you are unable to work with galaxies. It’s only with these tools that you can perceive certain things.” — @octref [0:22:10] Links Mentioned in Today’s Episode: - Pine Wu on GitHub (https://github.com/octref) - Pine Wu on Twitter (https://twitter.com/octref?lang=en) - Pine Wu Blog (https://blog.matsu.io/) - Vetur (https://vuejs.github.io/vetur/) - Mrmrs (http://mrmrs.cc/) - Von, 菅野 よう子 (Kanno Yōko), ft. Arnór Dan Arnarson (https://www.youtube.com/watch?v=lfksYyxGRJw) - 残響のテロル (Zankyō no Teroru) / Terror in Resonance (https://www.imdb.com/title/tt3613454/) - Tyler Hobbs’s Guide to Simulating Watercolor Paint (https://tylerxhobbs.com/essays/2017/a-generative-approach-to-simulating-watercolor-paints) - Inventing on Principle (https://www.youtube.com/watch?v=PUv66718DII) - Structure and Interpretation of Computer Programs (https://www.amazon.com/Structure-Interpretation-Computer-Programs-Engineering/dp/0262510871) - Pollen (https://docs.racket-lang.org/pollen/) - Beautiful Racket (https://beautifulracket.com/) - Hackers and Painters (http://www.paulgraham.com/hp.html) - Bret Victor (http://worrydream.com/) - The New Media Reader (http://www.newmediareader.com/) - Enjoy the Vue on Twitter (https://twitter.com/enjoythevuecast?lang=en) Special Guest: Pine Wu.

Microsoft's Adam Menges—founder at Lobe.ai and a former Apple employee—on helping people build intelligence into their apps by making it simple and understandable, his unconventional education, having death present, regret avoidance, grit, and his daily routine for note-taking, file management, meditation, and much more. Adam is a product designer, entrepreneur, and engineer located in San Francisco who specializes in Artificial Intelligence and visual programming languages. He spent time working for both Apple and SendGrid before starting his own company, Lobe, which was acquired in late 2018. Adam is continuing his work on making machine learning more accessible, and researching applications of the technology for video effects. You can contact Adam to find out more at adammenges.com, and reach out to him at adam@adammenges.com and +17204840285. Favorite quotes "You wake up in the morning, you reach over to the side of your bed, grab your laptop, and then you go until you're tired and have to go to bed." [22:40] "In order to be wildly creative, in order to increase your creative capacity, you need to be able to see the effect of what you're doing in real time." [24:31] "No one can actually context-switch, even if you think you can multitask." "[Lobe] gives you a springboard to understand what's happening behind the scenes and go for the research elsewhere." "If you are reminded five times a day that you're going to die, it makes each day much more meaningful." "All right, I'm never goin to be the smartest person in the room but I'll outwork everyone, and that'll be me." "You can do anything you set your mind to do. Don't hold yourself back." "If it becomes addictive then the technology is not invisible. It's very present." "The mission of Lobe is to make machine learning simple and understandable for those who are not machine learnists—those that don't code." Books Grit by Angela Duckworth The Rise of Superman: Decoding the Science of Ultimate Human Performance by Steven Kotler Einstein: The Life of a Genius by Walter Isaacson Why Zebras Don't Get Ulcers Links AdamMenges.com SendGrid Lobe.ai SmartGeometry CSU University NVIDIA Titan X graphic card Machine learning (concept) ReLU (rectified linear unit) (concept) TensorFlow ResNet ImageNet image database Grasshopper Visual programming (concept) Hacker Paradise Mirrorless cameras Direct manipulation Bear (app) Oak for unguided meditation by Kevin Rose (app) We Croak (app) [34:05] Markdown Love Story Yoga in the mission CrossFit Widget tweet from Adam's countdown Spark AR Instagram filters Shaders (concept) All Birds Statistical death Flow Deliberate practice vvvv (visual programming language) The Future of Programming by Bret Victor (talk) Media Behind the Tech with Kevin Scott The Creative Brain (movie) Abstract: The Art of Design (documentary series) People mentioned Samantha Walker Kevin Scott, Microsoft's CTO Bill Gates Jonathan Ive Markus Beissinger Mike Matas Angela Duckworth Elon Musk Steve Jobs Lindsey Menges Bret Victor Cal Newport Outline Teaser. [0:00] Intro. [1:16] An unconventional education and avoiding context-switching. [2:15] SendGrid. [4:30] Apple. [5:38] The beginnings of Lobe. [6:26] The machine in my apartment. [7:39] A consumer tool. [9:20] The origins of Lobe. [10:13] Projects people built with Lobe. [12:17] Wind tunnel simulation. [12:32] Parents autoplaying audio books. [15:06] Tracking dolphin migration patterns. [15:53] Is Lobe a black box? [16:59] Joining Microsoft: From three remote workers to eighteen employees. [18:53] Early days of Lobe: How it was to start the company. [19:49] What do you miss? Building Lobe while traveling the world. [21:04] Visual programming and immediate feedback. [22:10] Photography. [22:47] Direct manipulation. [23:31] Adam's daily routine. [23:58] Meditation. [25:45] CrossFit and Yoga. [26:20] The goal of meditation and focus. [27:00] Distractions and notifications. [27:33] Screen time. [28:02] Death and regret avoidance. [29:31] Habits to have death present. [31:21] A death countdown. [32:51] A file system to be present. [33:36] How many days do you have left? [34:05] Calculating your statistical death. [34:20] Analog activities. [35:11] Keeping in touch online. [35:43] Grit. [37:01] The Grit Scale: Angela Duckworth's work on grit as an indicator of success. [41:09] Forgetting past fears and struggles. [45:19] Deliberate practice. [46:52] Custom-made clothing. [47:57] Connect with Adam. [51:39] Books. [52:15] Media recommendations. [52:37] A purchase of $100 or less. [53:22] Success. [53:58] Role models. [54:24] A message to the world. [54:42] A healthy relationship with technology. [54:50] Ideas: When and where do you get them? [55:38] Creativity: What makes you more creative? [55:59] Slowing down. [56:21] Simple. [56:34] Intuitive. [56:54] Your mission. [57:13] How will artificial intelligence and machine learning impact our lives? [57:24] Outro. [58:35] Submit your questions and I'll try to answer them in future episodes. I'd love to hear from you. If you enjoy the show, would you please consider leaving a short review on Apple Podcasts/iTunes? It takes less than 60 seconds and really helps. Show notes, transcripts, and past episodes at gettingsimple.com/podcast. Theme song Sleep by Steve Combs under CC BY 4.0. Follow Nono Twitter.com/nonoesp Instagram.com/nonoesp Facebook.com/nonomartinezalonso YouTube.com/nonomartinezalonso

Omar Rizwan (https://rsnous.com) is a researcher at Dynamicland, a research lab in Oakland, California, led by Bret Victor.

Many years in the works, Figure It Out is coming out in May 2020! In this episode, authors Stephen P. Anderson and Karl Fast discuss the complex world of information (think incomprehensible tax policies to confusing medical explanations) we are faced with, and the ways in which information can be transformed into better presentations, better meetings, better software, and better decisions. Stephen also shares a personal anecdote about part of the inspiration for the book. Get your copy: https://rosenfeldmedia.com/books/figure-it-out/ Mentioned in the episode… Stephen’s latest project: The Mighty Minds Club. Learn more and subscribe: https://www.producthunt.com/upcoming/the-mighty-minds-club Karl’s recommended reads: Smarter Than You Think by Clive Thompson https://www.amazon.com/Smarter-Than-You-Think-Technology/dp/1594204454 and Messy: The Power of Disorder to Transform Our Lives by Tim Hartford https://www.amazon.com/Messy-Power-Disorder-Transform-Lives-ebook/dp/B01BD1SU2E/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=1587498076&sr=1-1 Stephen’s interesting people to check out: Nicky Case and her “explorable explanations” https://ncase.me/; Bret Victor and real time feedback loops https://en.wikipedia.org/wiki/Bret_Victor

Mary and Tom Poppendieck on The Modern Agile Show, Daniel Mezick on Agile Uprising, Jennifer Tu, Zee Spencer, Thayer Prime, and Matt Patterson on Tech Done Right, James Colgan on This Is Product Management, and Matt Kaplan on Build by Drift. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting March 18, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. MARY AND TOP POPPENDIECK ON THE MODERN AGILE SHOW The Modern Agile Show podcast featured Mary and Tom Poppendieck with host Joshua Kerievsky. Recorded at the ScanAgile 2018 conference in Helsinki, Mary and Tom talked about their keynote on proxies and permissions. Inspired by Bret Victor’s statement that creators need an immediate connection to what they create, Tom and Mary presented on how the most effective teams are autonomous, asynchronous teams that are free of the proxies and permissions that separate creators from their creations.  This led to a discussion of lean thinking and Mary pointed out that the interesting thing about lean is that fast and safe go together. She gave the example of a construction site where nothing slows things down more than the occurrence of an accident. Mary talked about how Jeff Bezos is a good early example of someone who understood that if you want to get really, really big, you need to have autonomous agents acting independently and thinking for themselves. iTunes link: https://itunes.apple.com/ca/podcast/interview-with-mary-and-tom-poppendieck/id1326918248?i=1000407584120&mt=2 Website link: https://github.com/modernagile/podcast/blob/master/ModernAgileShow_26_Interview_with_Mary_and_Tom_Poppendieck.mp3 DANIEL MEZICK ON AGILE UPRISING The Agile Uprising podcast featured Daniel Mezick with hosts Jay Hrcsko and Brad Stokes. Daniel told the story of how the OpenSpace Agility movement was born from ideas he brought to a Scrum Gathering in Paris in 2013 under the name Open Agile Adoption.  He described Open Space as an invitational, all-hands meeting format in which there is an important issue, no one person has the answer, and there is an urgency to reach a decision. The Open Space format then creates the conditions for high performance through self-organization. Brad brought up that he imagines that OpenSpace Agility can be terrifying to some leaders. Daniel noted that the fear is due to the fact that we have failed the executive leadership of the largest organizations. In the name of “meeting them where they’re at,” we’ve traded away our principles and values and haven’t taught them anything in exchange. Daniel says, “Self-management scales. Not the framework.” This echoes Mary Poppendieck’s comments from the Modern Agile Show on how self-managing, autonomous, asynchronous agents are the only way to scale. Using Scrum as an example, Daniel said that, for the Product Owner to be successful, everyone in the organization must respect his or her decisions. If you do that, he says, you will immediately get culture change because you’ve refactored the authority distribution schema. iTunes link: https://itunes.apple.com/ca/podcast/openspace-agility-with-daniel-mezick/id1163230424?i=1000430511928&mt=2 Website link: https://agileuprising.libsyn.com/podcast/openspace-agility-with-daniel-mezick JENNIFER TU, ZEE SPENCER, THAYER PRIME, AND MATT PATTERSON ON TECH DONE RIGHT FROM TABLE XI The Tech Done Right podcast featured Jennifer Tu, Zee Spencer, Thayer Prime, and Matt Patterson with host Noel Rappin. Noel started by asking the guests what they thought the biggest mistake people make when trying to hire developers is. Thayer said, “One of the biggest mistakes anybody makes in hiring is hiring people they like and that they want to work with because they’re nice as opposed to hiring against a spec of what the worker is supposed to be doing.” This comment matches my own experience because this practice was rampant on previous teams of mine. Jennifer asked Matt how his company attracts candidates and he described using their current employee’s networks. Thayer called this the number one diversity mistake that all companies make.  Noel asked about what to do at the end of the process where you need to go from multiple opinions you need to turn into a single yes/no decision. Jennifer has everyone write down their impressions before they talk to anyone else and write down specifically what they observed to support the conclusion you come to. This is how I always do it, but I’m always surprised at how few teams practice this. Noel asked about good and bad uses of interview time. I loved Jennifer’s example of what a bad use of time it is to say, “Tell me about yourself.” Sometimes I have candidates jump into providing this kind of information even though I hadn’t asked. Such people steer the interview into a well-prepared speech of all their best qualities that doesn’t give you a full picture of the candidate. Thayer then made a comment about the tendency of interviewers to try to make the candidates sweat. I agree with Thayer that this is usually the exact opposite of what you want if you’re trying to make the interview as much like the actual job experience as possible. iTunes link: https://itunes.apple.com/ca/podcast/episode-56-developer-hiring/id1195695341?i=1000430735771&mt=2 Website link: https://www.techdoneright.io/56 JAMES COLGAN ON THIS IS PRODUCT MANAGEMENT The This Is Product Management podcast featured James Colgan with host Mike Fishbein. James is a product manager for Outlook Mobile, which has 100 million monthly active users. James talked about his strategy for user growth being to make a product that is trusted by IT and loved by users. This led to their measures of success, such as usage and love for the product, measured by things like app store rating. James gave a great example of doing user research to create a product that is loved globally rather just in certain geographies. They did research in Asia and found drastic differences in the relationship between personal time and work time. They found North Americans and Europeans kept a strong delineation between work and personal time, but they found significant overlap between personal and work time among Asian customers. The data-driven nature of the product decisions payed dividends in both choosing the right features to work on and avoiding the wrong ones. They got the idea that they wanted to improve the ease of composing emails, but after looking at their instrumentation, they found that the average session length was 22 seconds. So instead they focused on consumption of emails over composition. iTunes link: https://itunes.apple.com/ca/podcast/188-listening-to-users-at-scale-is-product-management/id975284403?i=1000430581654&mt=2 Website link: https://www.thisisproductmanagement.com/episodes/listening-to-users-at-scale/ MATT KAPLAN ON BUILD BY DRIFT The Build by Drift podcast featured Matt Kaplan with host Maggie Crowley. Matt talked about how the book Creativity Inc. by Pixar founder Ed Catmull inspired him to see the similarities between creating products and telling stories. He says that every great story has a protagonist (the target user), starts with tension (the problem the product is trying to solve), has an end state (the vision for solving the user’s problem), has a core belief (the product differentiators), and consists of a sequence of events to get to that end state (the work we need to do to get the users from the tension to the end state). Maggie asked what the benefits are of thinking about products in this way and he explained that product management is about solving problems and telling stories. Stories could be used to convince salespeople that you’re doing the right thing, to tell engineers about what they’re going to build, or to tell customers about what your team has built. iTunes link: https://itunes.apple.com/ca/podcast/build-19-how-great-products-are-like-great-stories/id1445050691?i=1000430866513&mt=2 Website link: https://www.youtube.com/watch?v=swz0TnLwbrA&list=PL_sQbSaZtRqCn6JJSkjma79c8c4bLdaJH&index=4&t=0s FEEDBACK Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/channel/UCysPayr8nXwJJ8-hqnzMFjw Website:

Many of you have heard about Dynamicland, Bret Victor's new project. Omar Rizwan comes on the podcast this week to tell us all about it. He recently wrote an amazing write up about it, [Notes from Dynamicland: Geokit](https://rsnous.com/posts/notes-from-dynamicland-geokit/), that I'd highly reccomend to everyone interested in the future of computing. futureofcoding.org/episodes/28

Glen Chiacchieri has worked at the MIT Media Lab on Scratch, at Dynamicland with Bret Victor, and is now becoming a psychotherapist. He's known for his Legible Mathematics essay, his Flowsheets programming prototypes, and the Laser Socks game, among many other projects. In this conversation, we discuss: how he grounds his research in compassion, the tradeoffs between working on the "model vs UI" of programming, his software-company-in-the-making, based on Flowsheets, our shared dream for the future of open-source READMEs, and how Dynamicland does and does not point towards the future. The notes for this conversation can be found at futureofcoding.org/episodes/26.

## 内容简介：这一期聊聊我对于 Bret Victor 理想的看法，他的理想是：改造我们的低幼化社会。为人们提供工具，用以抵抗和摧毁消费主义文化（全方位的品牌包装与广告对人的情感操弄，物质主义，生造的时尚潮流），以及大企业对工作、娱乐和创造力的寡头控制。将权力、尊严和责任感还给个人。沟通反馈：Zoe.gongzy@gmail.com## 关于我：个人网站：infoier.com知乎：https://www.zhihu.com/people/gong-zi-yi-2/activities

## 内容简介：这一期聊聊我对于 Bret Victor 理想的看法，他的理想是：改造我们的低幼化社会。为人们提供工具，用以抵抗和摧毁消费主义文化（全方位的品牌包装与广告对人的情感操弄，物质主义，生造的时尚潮流），以及大企业对工作、娱乐和创造力的寡头控制。将权力、尊严和责任感还给个人。沟通反馈：Zoe.gongzy@gmail.com## 关于我：个人网站：infoier.com知乎：https://www.zhihu.com/people/gong-zi-yi-2/activities

Episode 26 of the Modern Agile Show features an interview with Mary and Tom Poppendieck, co-authors of numerous excellent books, including Lean Software Development, Leading Lean Software Development and The Lean Mindset. Mary gave a wonderful keynote at the Scandinavian Agile conference (2018) called Proxies and Permissions. In that talk, Mary pointed out that she and Tom believe that “people ought to be able to figure things out for themselves” rather than being fed recipes. In Mary's talk she highlighted Bret Victor's (@worrydream) Designer's Principle (from his talk, Inventing on Principle: https://www.youtube.com/watch?v=EGqwX...) that “creators need an immediate connection with what they create.” Mary describes how important it is for people on agile teams to be "autonomous and asynchronous”, to get feedback rapidly from what they build instead of waiting a long time to see the impact of what you do. This is especially true if you are running experiments. Mary and Tom discuss a variety of “proxies” that stand in the way of fast feedback and autonomy. Mary explains how “speed and safety” go hand in hand. Mary believes that many agile scaling approaches are “a crutch” for organizations that have tight dependencies between people and architecture issues that require lots of people to talk, rather than being able to work autonomously, as they do at Amazon. Mary and Tom discuss how they see the four Modern Agile principles and how they relate to their Lean work. Finally, Mary describes how teams need a “concept of leadership”, someone who works as part of the team and helps teach the team how to work well, solve problems and learn.

Can electrical engineers create tangible objects? Do we really need to be writing lines of code in a text-editor to be programming? Is it time for society to redefine what it means to compute? This week, Paul and Rich sit down with Bret Victor to discuss his journey from Electrical Engineer at Caltech, to UI Designer at Apple, to Creator of his ultimate vision, Dynamicland. The building is a computer; the computer is a building: This week Paul Ford and Rich Ziade sit down with Bret Victor to talk to about Dynamicland — a non-profit that’s inventing a new computational medium, where people work together with real objects in the real world (not alone with virtual objects on screens). We chat about the tech behind Dynamicland, the importance of creating intentional communities, and how a culture of secrecy at Apple inspired a life-long vision of community computing. Bret also shares a surefire way to impress a date — bring them to GuitarCenter and show them your analog modeling synth! 3:58 — Rich: “The bureaucracy got obliterated; all the machinery that usually slows you down was gone. The parents weren’t home!” 13:14 — Bret: “I came in the first day, went ot my desk and there was an iPad sitting on my desk. This was 2007. The iPhone just had been released. The iPad was not a thing at all… and I said ‘what is this?’ and my boss said ‘well we don’t know, Steve wants a tablet’.” 16:03 — Bret: “I was starting to see that my values and Apple’s values were a bit at odds. Apple ultimately wants to enable people to listen to their music, and read their email, and watch videos, and have an entertaining digital experience. I wanted to enable people to understand things more deeply or create amazing things that they couldn’t create before.” 22:08 — Bret: “It’s hard to have the level of motivation to pull off something really huge like that, if you don’t have the right support structures in place.” 22:08 — Bret: “We want to create a medium that works for all people. So growing our community, we’ve been pretty deliberate about reaching out to people who aren’t on Twitter and who aren’t traditionally advantaged by technology.” LINKS Bret Victor Bret Victor on Twitter Dynamicland Donate to Dynamicland Dynamicland on Twitter Alesis Ion Alesis Micron  The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity by Alan Cooper Edward Tufte William Cleveland  Magic Ink : Information Software and the Graphical Interface by Bret Victor  Joystick Example at Dynamicland with Paula Te David Hellman Track Changes is the weekly technology and culture podcast from Postlight, hosted by Paul Ford and Rich Ziade. Production, show notes and transcripts by EDITAUDIO. Podcast logo and design by Will Denton of Postlight.

¿Queréis participar? ¿Queréis participar y ayudarnos a decidir que grabar en WeCodeSign y proponer invitad@s? Descripcion del programa Diego Rodríguez, Jorge Aznar y Jorge Barrachina vienen a debatir sobre la importancia del diseño en la industria del desarrollo. ¿Debe el diseñador saber como funcionan ciertas tecnologías front-end? ¿Deben los desarrolladores saber sobre diseño? ¡Nosotros creemos que si! Conocer lo que hacen tus compañeras/os te hacen ser mejor profesional y saber trabajar mejor en equipo. ¡Esperamos que os guste el episodio y como siempre nos vemos al final! ¿Queréis participar? ¿Queréis participar y ayudarnos a decidir que grabar en WeCodeSign y proponer invitad@s? Aquí podéis participar en WeCodeSign. Recomendaciones Preguntas rápidas: Diego Rodríguez, Jorge Aznar y Jorge Barrachina Quién me ha inspirado: Pablo Garaizar (Txipi) Quién me ha inspirado: Brent Jackson Quién me ha inspirado: Adam Morse Quién me ha inspirado: Bret Victor Quién me ha inspirado: Ramón Corominas Recomiéndanos un recurso: Alist Apart Recomiéndanos un recurso: Interaccion del color, la (Alianza Forma) Recomiéndanos un recurso: Designer vs. Developer Recomiéndanos a un invitado o invitada: Javier Cañada Recomiéndanos a un invitado o invitada: Eusebio Reyero Recomiéndanos a un invitado o invitada: Pablo Garaizar (Txipi) Recomiéndanos a un invitado o invitada: qmarcos Recomiéndanos a un invitado o invitada: Ibon ¿Qué tema te gustaría que tratásemos?: Procesos de trabajo ¿Qué tema te gustaría que tratásemos?: Proyectos personales y como enfocar nuestro conocimiento en ayudar a la sociedad ¿Qué tema te gustaría que tratásemos?: Trucos y técnicas entre personas (human side of code) Contacta con: Diego Rodríguez, Jorge Aznar y Jorge Barrachina Twitter de Diego Web de Diego Twitter de Jorge Aznar Web de Jorge Aznar Twitter de Jorge Barrachina Links del programa La regla del 12 ‘Me gusta’ no es un argumento de diseño Workflows sanos y funcionales entre equipos (UX, UI, Front) - Juan de la Cruz. ForntFest 2.017 Máximo Gavete Open Ideo Diseño Social Open Source Design Xaviju Logitech Quadrupled Its Profits–With One Big Design Idea Recomendaciones de Ignacio Open Color Design Principles Bauhaus (Taschen 25) Open Source Design Patrocinadores Fictizia.com Contacta con Ignacio Web de WeCodeSign Twitter de WeCodeSign eMail de WeCodeSign Web de Ignacio Villanueva Twitter de Ignacio Villanueva

Jason Brennan joins Chris and Soroush to discuss his new project, Beach.Jason Brennan (@jasonbrennan)BlogBeach landing pageAlan Kay https://en.m.wikipedia.org/wiki/Alan_KayHyperCard.orgHyperCard on WikipediaGuerrillas in the Myst (WIRED, 1994)Emergent BehaviorTurtles, Termites and Traffic Jams by Mitchel ResnickHSLApple Reinvents Textbooks with iBooks 2 for iPad (2012)iBooks AuthorHopscotchA LEGO Mindstorms programBret Victor: Stop Drawing Dead FishSketchJason’s fork of PrototopeSwift Playgrounds“I think I’m more excited by people’s shitty versions of things (sketches, prototypes, etc) than the finished, polished thing” — @jasonbrennanBrian Lee O’Malley on InstagramOn the BeachThread from Jason: “Teachers have to worry about ‘how to graduate from Scratch to text languages’ because there’s nothing else to graduate to”

The last two-week-research-cycle was my most productive yet! In this recap, I debreif my Alan Kay deep dive, discuss tweaking my schedule after reading Peak, review conversations with Jaime Brandon and Dan Scanlon, read aloud my thoughts on proper computer use patterns and my prototype idea LogicHub, recap my early morning meeting with CycleJS creator Andre Staltz, and discuss the next steps for my StreamSheets prototype (which is why I'm putting my Bret Victor deep dive on pause). If you were able to follow all that, my hat is off to you. I barely made it through the recording and episode of this episode alive. If you need help pieceing this episode together, you can find the notes on my website: /futureofcoding.org/episodes/9-research-recap-five.html

Descripcion del programa Anler, desarrollador de Scala y Akka organizador de Haskell Madrid nos cuenta su paso en la programación funcional. Nos cuenta su experiencia tras venir desde Cuba, su paso por la educación tradicional, su experiencia como profesor y sus inquietudes por la programación funcional. ¡Esperamos que os guste el episodio y como siempre nos vemos al final! Recomendaciones Preguntas rápidas: Anler Quién me ha inspirado: Rocky y Sea Biscuit (películas) Recomiéndanos un recurso: Structure and Interpretation of Computer Programs Recomiéndanos un recurso: Humane Representation of Thought Recomiéndanos a un invitado o invitada: Bret Victor ¿Qué tema te gustaría que tratásemos?: Sorprendedme Contacta con: Anler Twitter de Anler Anler en Medium Web de Anler Links del programa Key Framework Clojure mootools jQuery PHP Haskell Ruby Lisp Perl Scheme Peep Code Tutorials Kaleidos Haskell Mad Scala Python Webpack gnome gentoo Richard Stallman Recomendaciones de Ignacio Master the JavaScript Interview: What is Functional Programming? Don’t Be Scared Of Functional Programming So You Want to be a Functional Programmer (Part 1) A practical introduction to functional programming Web de WeCodeSign Twitter de WeCodeSign eMail de WeCodeSign Web de Ignacio Villanueva Twitter de Ignacio Villanueva

2:40 - Introducing Tero Parviainen NgConf Presentation: “Generative Art in Angular 2” Website Github Build Your Own AngularJS ebook 4:10 - Hot Loading “Angular 2 Hot Loading with @ngrx/store and Webpack” article by Tero 5:45 - Using @ngrx/store 8:25 - How is Time Travel possible with reloading? 13:40 - Playback 17:10 - Backends and Side Effects 21:05 - Overloading and discarding of your old application 24:40 - Pressing F5 versus Time Travel 26:40 - Using Breeze.js 27:35 - Workflow setup 29:50 - Tero Parviainen and Music In-C on Github 34:55 - Using the process with NgRX and Redux 37:20 - Learning code languages and assembling your toolkit Picks: Carmen Popoviciu’s talk “Neural Networks and Machine Learning: Building Intelligent Angular Applications (Lukas) RxJS free course (Lukas) Hello World using every design pattern (Ward) The 12 Week Year (Charles) JS Remote Conf 2017 (Charles) Angular Remote Conf videos (Charles) RxJS Operator Selector (Tero) Bret Victor “Inventing on Principle” (Tero) Ultimate Angular course platform (Lukas)

2:40 - Introducing Tero Parviainen NgConf Presentation: “Generative Art in Angular 2” Website Github Build Your Own AngularJS ebook 4:10 - Hot Loading “Angular 2 Hot Loading with @ngrx/store and Webpack” article by Tero 5:45 - Using @ngrx/store 8:25 - How is Time Travel possible with reloading? 13:40 - Playback 17:10 - Backends and Side Effects 21:05 - Overloading and discarding of your old application 24:40 - Pressing F5 versus Time Travel 26:40 - Using Breeze.js 27:35 - Workflow setup 29:50 - Tero Parviainen and Music In-C on Github 34:55 - Using the process with NgRX and Redux 37:20 - Learning code languages and assembling your toolkit Picks: Carmen Popoviciu’s talk “Neural Networks and Machine Learning: Building Intelligent Angular Applications (Lukas) RxJS free course (Lukas) Hello World using every design pattern (Ward) The 12 Week Year (Charles) JS Remote Conf 2017 (Charles) Angular Remote Conf videos (Charles) RxJS Operator Selector (Tero) Bret Victor “Inventing on Principle” (Tero) Ultimate Angular course platform (Lukas)

2:40 - Introducing Tero Parviainen NgConf Presentation: “Generative Art in Angular 2” Website Github Build Your Own AngularJS ebook 4:10 - Hot Loading “Angular 2 Hot Loading with @ngrx/store and Webpack” article by Tero 5:45 - Using @ngrx/store 8:25 - How is Time Travel possible with reloading? 13:40 - Playback 17:10 - Backends and Side Effects 21:05 - Overloading and discarding of your old application 24:40 - Pressing F5 versus Time Travel 26:40 - Using Breeze.js 27:35 - Workflow setup 29:50 - Tero Parviainen and Music In-C on Github 34:55 - Using the process with NgRX and Redux 37:20 - Learning code languages and assembling your toolkit Picks: Carmen Popoviciu’s talk “Neural Networks and Machine Learning: Building Intelligent Angular Applications (Lukas) RxJS free course (Lukas) Hello World using every design pattern (Ward) The 12 Week Year (Charles) JS Remote Conf 2017 (Charles) Angular Remote Conf videos (Charles) RxJS Operator Selector (Tero) Bret Victor “Inventing on Principle” (Tero) Ultimate Angular course platform (Lukas)

This week Mike and Brian warm up with news and ideas around Apple. Then we dive in talking about our experiences with developing strategies for your career path. We referred to Bret Victor's "Invent on Principal" as well as Freeman Dyson's work as a physicist and his quote: "We are but atoms analyzing other atoms".

Colin Ray joins us to discuss the evolution and potential future of computer input methods, and strange twists and turns through the landscape of game controllers - most notably the Steam controller. In the words of Andrew: ENGELBART IS LOVE, ENGELBART IS LIFE. ENGELBART IS GENIUS. ENGELBART IS REMEMBERED FOR AN INPUT DEVICE HE DIDN'T EVEN INVENT. COLIN MADE HIS OWN STREET FIGHTER CONTROLLER DECAL. HOVER GESTURES. TOUCH GESTURES. LINE WOBBLER. ENGELBART. ENGELBART. ENGELBART. -The Mother of all Demos (1968) -A brief history of video game controllers -Sketchpad (1963) -Bret Victor of Worrydream -The insane GameCube keyboard controller -The Xbox Chatpad (which is stupid) -Enhance! Let's find some snakes. -🙌 S T E A M C O N T R O L L E R 🙌 -Steam Controller for video editing -Imbroglio -Andy Baio raised his son through the history of video games -A Brief Rant on the Future of Interaction Design -10/GUI -Microsoft hand tracking -Leap Motion -Super-cool hover gestures from Microsoft research (they can't be totally wrong about everything, after all)

02:00 - Gilad Bracha Introduction Twitter GitHub Blog Dart JavaScript Jabber Episode #008: V8 and Dart with Lars Bak and Kasper Lund Dartium 09:17 - Programming Language Evolution and Design Elm Ruby Rogues Episode #212: Elm with Richard Feldman and Evan Czaplicki 10:47 - Capabilities and Language Features Newspeak “Functional” 12:46 - Actors 16:41 - Live Programming Bret Victor on Live-Coding 19:07 - Smalltalk REPL (Read–eval–print loop) Monkey patching 29:01 - Designing a Language “Programming is an experience.” 38:59 - Complexity 42:41 - Newspeak (Con’t) 45:58 - Smalltalk or Newspeak? Squeak Pharo Dolphin Smalltalk VisualWorks 48:13 - How are programming languages like shrubberies Picks Stroopwafels (Chuck) Staked: The Iron Druid Chronicles by Kevin Hearne (Chuck) Calamity (The Reckoners) by Brandon Sanderson (Chuck) Katrina Owen: Here be Dragons (Jessica) The Slow Party Parrot Emoji (Jessica) Umberto Eco (Gilad)

02:00 - Gilad Bracha Introduction Twitter GitHub Blog Dart JavaScript Jabber Episode #008: V8 and Dart with Lars Bak and Kasper Lund Dartium 09:17 - Programming Language Evolution and Design Elm Ruby Rogues Episode #212: Elm with Richard Feldman and Evan Czaplicki 10:47 - Capabilities and Language Features Newspeak “Functional” 12:46 - Actors 16:41 - Live Programming Bret Victor on Live-Coding 19:07 - Smalltalk REPL (Read–eval–print loop) Monkey patching 29:01 - Designing a Language “Programming is an experience.” 38:59 - Complexity 42:41 - Newspeak (Con’t) 45:58 - Smalltalk or Newspeak? Squeak Pharo Dolphin Smalltalk VisualWorks 48:13 - How are programming languages like shrubberies Picks Stroopwafels (Chuck) Staked: The Iron Druid Chronicles by Kevin Hearne (Chuck) Calamity (The Reckoners) by Brandon Sanderson (Chuck) Katrina Owen: Here be Dragons (Jessica) The Slow Party Parrot Emoji (Jessica) Umberto Eco (Gilad)

02:00 - Gilad Bracha Introduction Twitter GitHub Blog Dart JavaScript Jabber Episode #008: V8 and Dart with Lars Bak and Kasper Lund Dartium 09:17 - Programming Language Evolution and Design Elm Ruby Rogues Episode #212: Elm with Richard Feldman and Evan Czaplicki 10:47 - Capabilities and Language Features Newspeak “Functional” 12:46 - Actors 16:41 - Live Programming Bret Victor on Live-Coding 19:07 - Smalltalk REPL (Read–eval–print loop) Monkey patching 29:01 - Designing a Language “Programming is an experience.” 38:59 - Complexity 42:41 - Newspeak (Con’t) 45:58 - Smalltalk or Newspeak? Squeak Pharo Dolphin Smalltalk VisualWorks 48:13 - How are programming languages like shrubberies Picks Stroopwafels (Chuck) Staked: The Iron Druid Chronicles by Kevin Hearne (Chuck) Calamity (The Reckoners) by Brandon Sanderson (Chuck) Katrina Owen: Here be Dragons (Jessica) The Slow Party Parrot Emoji (Jessica) Umberto Eco (Gilad)

章节（时:分:秒）： 00:00:00 前戏 00:05:42 片头 00:07:06 《IT 公论》播客两周年，《IT 公论》博客上线！ 00:10:08 听众反馈 00:22:07 互联网技术圈耻辱柱 00:32:44 Mac App Store 数字签名故障导致的问题 00:37:02 屏幕色温自动调节工具 f.lux 被苹果在 iOS 上封禁 00:45:53 iPad Pro 整体印象 01:00:46 tvOS 中的 UIFocusEngine 现身 iOS 9.1 暗示着什么？ 01:05:05 Smart Keyboard 01:08:32 Apple Pencil 01:17:26 iPad Pro vs. Surface Pro，以及计算设备的交互范式 01:22:14 完全用 iPad (Air 2) 剪辑播客的体验报告 01:27:53 从输出拟物（skeuomorphic output）到输入拟物（skeuomorphic input） 01:52:57 尾声 本期会员通讯将于稍后发至各位会员邮箱。每月三十元，支持不鸟万如一和 Rio 把《IT 公论》做成最好的科技播客。请访问 itgonglun.com/member。若您无意入会，但喜欢某一期节目，也欢迎用支付宝或 PayPal 支付小费至 hi@itgonglun.com，支付宝用户亦可扫描下方二维码： 相关链接 《IT 公论》两周年，博客上线 IPN 播客网络 Telegram 听众群列表 ReadQuick (节目里说成 QuickRead 了) 关于「栉」字的读音 Brillo 本周互联网技术圈耻辱柱：Instaagent f.lux 关于发光屏幕影响睡眠的论文：Evening use of light-emitting eReaders negatively affects sleep, circadian timing, and next-morning alertness (PDF) Divvy 《IT 公论》第八十三期：「真 pro 是不怕用户体验差的」 UIFocusEngine on iOS 9.1 《ATP》播客第一四三期 Ferrite Studio Recording Rio: iPad 替代笔记本还缺些啥？ 《内核恐慌》第廿八期: In the Beginning was the Command Line 《Thinking, Fast and Slow》 Bret Victor IPN 播客网络常见问题解答 人物简介 不鸟万如一：字节社创始人。 Rio: Apple4us 程序员。

如题。 本期会员通讯已发至各位会员邮箱。每月三十元，支持不鸟万如一和 Rio 把《IT 公论》做成最好的科技播客。请访问 itgonglun.com/member。若您无意入会，但喜欢某一期节目，也欢迎用支付宝支付小费（建议金额：一元、五元或十元人民币）：hi@itgonglun.com 或扫描下方二维码。 相关链接 革命的终结 Coin nvALT Notational Velocity Bret Victor Snoop Dogg 的 Instagram 人物简介 不鸟万如一：字节社创始人。 Rio: Apple4us 程序员。

本期话题包括 danah boyd 的《It’s Complicated》，Rio 实地体验 Force Touch 触摸板的感受，主打高音质牌的音乐流媒体服务 Tidal，以及 Meerkat 和 Periscope。 每月三十元，支持李如一和 Rio 把《IT 公论》做成最好的科技播客。请访问 itgonglun.com/member。 今天的标题看起来有点故弄玄虚，但我保证是认真的。 香港导演/摄影师杨凡和东方不败林青霞当然没有在玩 Periscope——虽然我不认识他们，但这个猜测应该八九不离十。2013 年 11 月 3 日，杨凡在香港《苹果日报》的一篇题为〈念念华严经〉)的专栏里讲了林青霞 Skype 视频的故事。林青霞答应时任台湾文化部长的龙应台以视频连线的方式参加一场记者招待会。大概是之前没怎么用过 Skype，她希望在正式出场前夜先和好友杨凡彩排一番。结果杨凡发现效果惨不忍睹： ……午夜后的美人终于和我 Skype 连上线。望见她那灯光不足的画面，就知美人对电脑白痴过我。我问美人什么时候懂得这电脑科技？她说昨天。接着打开麻雀灯，用不同的角度替自己打灯，有时又用一张小白纸作反光板，希望可以打个大平光。完全像个小学生…… 身为耽美派摄影师、为无数明星拍过写真的杨凡当然无法接受： 我心想一个记招怎可如此随便，何况吸镜率特高的林美人。我说为了你的粉丝，绝不能随便，今晚好好休息，明天下午到府上替你打个美人光，一定要美丽过美丽！ 说做就做，杨凡第二天提早几个小时跑到林青霞家里帮她布光，置景，「找三四个家仆将家具重新搬移，千万要做到简单自然而不着痕迹」。 这个故事一直在我心中挥之不去，原因之一是我也有过类似的经历。某次和一位瑞典仁兄视频，对方光线自然，肤色润泽，我则仿佛刚刚熬了两个通宵的死狗一般。数日后再次拨通他的 Skype 之前，我随手拿起桌上的廉价台灯从侧面照向自己，结果对方第一句话就说：「Ah! You have better lighting!」这要是被杨凡看到了，大概是连幼儿园水平都不如的失格把戏，但即便如此，打不打光，效果立竿见影。 这两个故事给我的教训是：视频好难。不是量子物理的难，视频制作不是某种需要特殊禀赋才能掌握的东西。但视频是如此「重」的一种媒介，灯光、布景、化妆、录音、摄像、表演都牵涉到种种必须反复练习才能掌握的技巧。只有当所有这些条件都被满足的前提下，一条还过得去的视频才能被拍出来。嗯，和你们这些写文章的人不一样，我们视频狗光是做到让人觉得能看已经竭尽全力了。 现在可以回到 Periscope 和 Meerkat 的话题。关于最近突然爆红的这两个视频直播软件的讨论大多聚焦在 Periscope 的产权归属上：作为被 Twitter 收购了的公司，它可以名正言顺地使用 Twitter 的社交圈信息（social graph）。相反，Meerkat 走红还不到一周，就遭到了 Twitter 的限制。但在我看来，视频制作的重量感才是 Periscope 类服务长期发展的最大阻力。一个普通人每天有多长时间是身处一种达到了播出级别的环境当中？又有多少时间和动力去把自己以及周围环境布置到可以相对不那么寒碜地出现在镜头前的状态？即便是林青霞，也需要老友职业摄影师特地跑来帮忙。 一个常见的误解是把「全方位」和「多角度」等同于「好」。任何有过自拍经验的人都明白，好看的角度是有限的。好的角度可以点石成金，糟糕的角度能把美女变成猪头。如果你认为 Periscope 一类的服务可以鼓励庶民在偶然性地经过突发事件现场时可以发挥「公民记者」的作用，请不要忘记这种使用场景早就被 YouTube 满足。更关键的是，公民记者并没有足够的动机出现在突发事件的现场。在场是偶然，不在场是必然。需要有多少个偶然同时在场，方可达到足够全的方位和足够多的角度？什么样的机制能从这些角度中选出少数值得留下的那几个？ 然后你会发现，传统的视频生产流程早已通过多年养成的专业主义解决了这些问题。 一个基本前提是：人类对于劣质视频（以及音频）的容忍度远低于对劣质文字的容忍度。看一眼满篇别字的潦草作文，如果观点有趣，拿了就走也不太亏。要你去看心中偶像在未经准备的状态下于屏幕前呈现出的怪相，就完全是另一回事了。视频和文字一样，是一种广义上的书写工具。「我没兴趣看你 140 个字的絮叨」和「我没兴趣看你家冰箱里的东西」的区别在于，除去创意和构思的时间后，写出一条聪明段子所花的时间比拍出一条精彩的实时冰箱视频要少太多。 当然，有一种人不会在意你粗制滥造的视频：爱你的人。对于他们，我们已经有了 FaceTime, Skype 视频，微信视频，LINE 视频…… 说了这么多，我们对 Periscope 和 Meerkat 还是持中立性的开放态度。如果你有兴趣知道 Rio 和李如一的冰箱里有什么东西的话，请在这两个系统里关注 @itgonglun。 李如一最近在玩的 app（Rio 最近没有玩什么 app） Layout from Instagram Last Voyage Scandal in the Spotlight 最近我们读的一些文章 重新发明了孤独 The Weak Universalism 相关链接 danah boyd: It’s Complicated Daisy Bell 歌词 IBM 704 在 1961 年演唱的 Daisy Bell 《二零零一太空漫游》中 HAL 9000 电脑被关闭的场景 Bret Victor Force Touch 触摸板背后的论文：Computational haptics : the Sandpaper system for synthesizing texture for a force-feedback display IT 公论第五十九期：「让世界人民合法地过上中国人的日子」 极低功耗的芯片技术 微软推出 Surface 3 亚马逊在加拿大 British Columbia 试飞小型无人飞行器 Santana: Borboletta (Spotify) 杨凡 杨凡关于林青霞和龙应台 Skype 视频的文章 Meerkat Periscope Tidal Layout from Instagram Last Voyage Scandal in the Spotlight Visual Novel 梗：All your base are belong to us 人物简介 李如一：字节社创始人。 Rio: Apple4us 程序员。

从宏观上说，人类进步，生活便会更丰富，似乎是不需要说明的道理。但具体到个人的微观行动，有时则不得不在两者之间取舍。本期话题包括苹果 2015 年第一季度的惊人财报，旧苹果和新苹果的使命，以及如何为用户着想。 每月三十元，支持李如一和 Rio 把《IT 公论》做成最好的科技播客。请访问 itgonglun.com/member。 今天的主题是苹果的 2015 年第一季度财报。如果大家有关注 Rio 在网上的行踪，就会知道他从不知何时开始，会在苹果每次公布季度财务状况之后用各种柱状图来分析结果。第一次看到这位程序员有此爱好时，李如一也吓了一跳，不过转念一想，Rio 在大学本科读的是商科，也就不奇怪了。 具体的数字请大家阅读 Rio 发表在 Apple4us.com 的《图解苹果 2015 财年一季度财报》。iPhone 销量的空前火爆委实令人吃惊。看起来大家对于 iPhone 6 和 6 Plus 的态度并不是「哼，苹果终于也忍不住学人家做大屏手机了」，而是「耶！苹果终于开始做大屏手机了，赶快买」。去年十月，Jonathan Ive 参加《名利场》杂志峰会，与主编 Graydon Carter 谈笑风生。当时媒体都热衷于报道 Ive 指责竞品剽窃，但他也谈及了苹果的不少设计理念与实践，其中之一就是对待大屏手机的态度。Ive 指出，在同等大小下，拥有圆滑边框的手机握在手中会感觉比边框锋利的小。圆框爱好者 Rio 在本期质问那之前为什么不把 iPhone 4 和 5 的边框也做圆了。对此我们只能说，苹果对于特定情况下事物的恰当尺度有自己的强烈信念：2007 年，3.5 寸就是最合适的屏幕大小；4 寸屏幕下，边框锋利也无所谓；到了 4.7、5.5 寸的大小，不做圆就真的会显得太大块。「但你说是就是吗？」有人要问。我想，身为作者，无论如何都还是要有这种「我说是就是」的狂妄与胆识才行。 大家认识「Hardcore iPad 游戏玩家」吗？我们不认识。资深游戏玩家难道不都在玩 PC 游戏和主机游戏吗？同时我们也不认识真的拿 iPad 做专业工作（即需要强劲计算性能）的人。这两件事加在一起，或许可以解释 iPad 销量连续多个季度的下跌。假如大部分人都不需要最新代 iPad 的高性能，那么三年换一台 iPad 也不奇怪了。如之前在节目中所说，iPad 上的杀手级应用——那种定义一个时代的应用——仍旧没有出现。 数字重要，不过这次财报电话会议里隐藏了更有趣的线索。Patrick Collison（我们也不知道他是何许人）在 Twitter 上把 Tim Cook 对苹果使命的定义拎了出来： Apple’s mission is to make the greatest products on earth and enrich the lives of others. 并和旧日苹果官方宣扬的使命放在一起对比： To make a contribution to the world by making tools for the mind that advance humankind. 在这条 tweet 引发的讨论中，无可替代的 Bret Victor (@worrydream) 给出了一篇题为《从自行车到跑步机》的文章，把这几个东西对照在一起看，可以明显看出科技大势在过去几十年里的变化。 一个以「让人类进步」为使命，一个希望「丰富他人的生活」。说高下立见可能有人不服气，毕竟当大娱乐家也是伟业。不过值得探讨的是：我们应该提供什么样的工具给别人？从广义上说，任何创作者都是工具制造者。就连艺术，也可以理解为扩充人类心智、思维与视野的工具。有的工具目的单一而明确，有的工具目的繁复而开放。对于使用工具的人而言，单一而明确的工具是简单易用的，但繁复开放的工具是强大而多样的。开放的工具对使用者的要求更加严格，我们也相信，使用这一类工具，才能够真正达到提升自我心智的作用。这，也是支持「开放」的终极理由。 至于这一番讨论和 IPN 播客网络旗下的《太医来了》从明天起将分成上下两集播出有什么关系，就请大家自己听这一期《IT 公论》的最后部分吧。 最近我们读的一些文章 以后卖到中国的西方电子产品都要加后门了？ 草·泥·马 有了虚拟现实，就不需要「悬置怀疑」了吗？ 相关链接 Rio 图解苹果 2015 财年一季度财报 Apple’s Jonathan Ive in Conversation with Vanity Fair’s Graydon Carter Bret Victor 的网站 worrydream.com 从自行车到跑步机 Patrick Collison 的 tweet Salman Khan 《太医来了》 人物简介 李如一：字节社创始人。 Rio: Apple4us 程序员。

从宏观上说，人类进步，生活便会更丰富，似乎是不需要说明的道理。但具体到个人的微观行动，有时则不得不在两者之间取舍。本期话题包括苹果 2015 年第一季度的惊人财报，旧苹果和新苹果的使命，以及如何为用户着想。 每月三十元，支持李如一和 Rio 把《IT 公论》做成最好的科技播客。请访问 itgonglun.com/member。 今天的主题是苹果的 2015 年第一季度财报。如果大家有关注 Rio 在网上的行踪，就会知道他从不知何时开始，会在苹果每次公布季度财务状况之后用各种柱状图来分析结果。第一次看到这位程序员有此爱好时，李如一也吓了一跳，不过转念一想，Rio 在大学本科读的是商科，也就不奇怪了。 具体的数字请大家阅读 Rio 发表在 Apple4us.com 的《图解苹果 2015 财年一季度财报》。iPhone 销量的空前火爆委实令人吃惊。看起来大家对于 iPhone 6 和 6 Plus 的态度并不是「哼，苹果终于也忍不住学人家做大屏手机了」，而是「耶！苹果终于开始做大屏手机了，赶快买」。去年十月，Jonathan Ive 参加《名利场》杂志峰会，与主编 Graydon Carter 谈笑风生。当时媒体都热衷于报道 Ive 指责竞品剽窃，但他也谈及了苹果的不少设计理念与实践，其中之一就是对待大屏手机的态度。Ive 指出，在同等大小下，拥有圆滑边框的手机握在手中会感觉比边框锋利的小。圆框爱好者 Rio 在本期质问那之前为什么不把 iPhone 4 和 5 的边框也做圆了。对此我们只能说，苹果对于特定情况下事物的恰当尺度有自己的强烈信念：2007 年，3.5 寸就是最合适的屏幕大小；4 寸屏幕下，边框锋利也无所谓；到了 4.7、5.5 寸的大小，不做圆就真的会显得太大块。「但你说是就是吗？」有人要问。我想，身为作者，无论如何都还是要有这种「我说是就是」的狂妄与胆识才行。 大家认识「Hardcore iPad 游戏玩家」吗？我们不认识。资深游戏玩家难道不都在玩 PC 游戏和主机游戏吗？同时我们也不认识真的拿 iPad 做专业工作（即需要强劲计算性能）的人。这两件事加在一起，或许可以解释 iPad 销量连续多个季度的下跌。假如大部分人都不需要最新代 iPad 的高性能，那么三年换一台 iPad 也不奇怪了。如之前在节目中所说，iPad 上的杀手级应用——那种定义一个时代的应用——仍旧没有出现。 数字重要，不过这次财报电话会议里隐藏了更有趣的线索。Patrick Collison（我们也不知道他是何许人）在 Twitter 上把 Tim Cook 对苹果使命的定义拎了出来： Apple’s mission is to make the greatest products on earth and enrich the lives of others. 并和旧日苹果官方宣扬的使命放在一起对比： To make a contribution to the world by making tools for the mind that advance humankind. 在这条 tweet 引发的讨论中，无可替代的 Bret Victor (@worrydream) 给出了一篇题为《从自行车到跑步机》的文章，把这几个东西对照在一起看，可以明显看出科技大势在过去几十年里的变化。 一个以「让人类进步」为使命，一个希望「丰富他人的生活」。说高下立见可能有人不服气，毕竟当大娱乐家也是伟业。不过值得探讨的是：我们应该提供什么样的工具给别人？从广义上说，任何创作者都是工具制造者。就连艺术，也可以理解为扩充人类心智、思维与视野的工具。有的工具目的单一而明确，有的工具目的繁复而开放。对于使用工具的人而言，单一而明确的工具是简单易用的，但繁复开放的工具是强大而多样的。开放的工具对使用者的要求更加严格，我们也相信，使用这一类工具，才能够真正达到提升自我心智的作用。这，也是支持「开放」的终极理由。 至于这一番讨论和 IPN 播客网络旗下的《太医来了》从明天起将分成上下两集播出有什么关系，就请大家自己听这一期《IT 公论》的最后部分吧。 最近我们读的一些文章 以后卖到中国的西方电子产品都要加后门了？ 草·泥·马 有了虚拟现实，就不需要「悬置怀疑」了吗？ 相关链接 Rio 图解苹果 2015 财年一季度财报 Apple’s Jonathan Ive in Conversation with Vanity Fair’s Graydon Carter Bret Victor 的网站 worrydream.com 从自行车到跑步机 Patrick Collison 的 tweet Salman Khan 《太医来了》 人物简介 李如一：字节社创始人。 Rio: Apple4us 程序员。

Onderwerpen Kaas, kaas, kaas! Het Oranje gevoel WWDC 2014 Flappy Bird in Swift De droom van Bret Victor Extensies op iOS De status van iOS vs. Android Alle low hanging fruit weg Alle foto’s worden nu op infinite loop bewaard Custom keyboards Hearthstone Hearthstone in de iPad App Store Google heeft SkyBox gekocht Appels en Peren backlog: En Bananen Chris Lattner’s Homepage Dankwoord Grote dank aan de vrienden van Appels en Peren: Soundcloud voor de bandbreedte, Nozzman voor het coverartwork en Clublime voor de introjingle.

Vale a pena pagar por ferramentas sofisticadas de desenvolvimento? - JavaScriptCast episódio 4 Por Manuel Lemos e Jean (Suissa) Nascimento O mundo do JavaScript está evoluindo cada vez mais e com passos ainda mais largos. Bret Victor criou um sistema de desenvolvimento de JavaScript que permite rodar e atualizar o código ao mesmo tempo em que se edita esse código. A ferramenta ainda não está disponível ao público, mas muitos desenvolvedores de JavaScript ficaram com água na boca e estariam dispostos a pagar um bom preço por ferramentas poderosas como essas.E você, pagaria por uma ferramenta sofisticada de desenvolvimento em JavaScript como essa? Este e outros tópicos de interesse sobre JavaScript foram debatidos entre Manuel Lemos e Jean Suissa Nascimento neste 4º episódio do JavaScriptCast.Eles também comentaram sobre os seguintes tópicos:Novidades no conteúdo no portal JavaScriptBrasil;O evento Pernambuco.js e a palestra sobre uso de storage em aplicações Web que funcionam offline;O site MicroJS para escolher frameworks para propósitos simples;A extensão de PHP V8JS para rodar JavaScript usando a máquina virtual V8;A subida de JavaScript no ranking TIOBE da popularidade das linguagens de programação;O jogo da Mozilla BrowserQuest para demonstrar tecnologias de JavaScript baseadas nas especificações das API de HTML 5.Por fim, eles também comentaram sobre algumas das últimas classes de JavaScript publicadas no site JSClasses, incluindo a classe Gestures, de Arturs Sosins, da Letônia, para reconhecimento de gestos desenhados pelo usuário com o mouse. Falaram também da jQuery URL Parser, de Hensel Hartman, da Suiça, para extração dos elementos de URLs, e a classe Timeouts, de Dom Hastings, do Reino Unido, para processamento mais sofisticado de eventos temporizados.

Scott and Anders discuss the user interface concepts Bret Victor puts forward in his "Inventing on Principle" talk at CUSEC 2012.