Make computing personal again (News)

20 Jan 2025 · 10 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

The Changelog: Episode Summary - Make Computing Personal Again

Podcast Overview

  • Title: The Changelog: Software Development, Open Source
  • Description: A weekly briefing on software news, deep technical interviews, and discussions about the open-source community.

Episode Details

  • Episode Title: Make Computing Personal Again (News)
  • Description: This episode discusses various topics around personal computing, AI tools, career paths for engineers, documentation practices, and a new web framework.

---

Key Discussions

  1. Making Computing Personal Again
  2. Speaker: Benj Edwards
  3. Main Argument: The personal computer experience has been compromised by surveillance capitalism and DRM.
  4. Rhetorical Questions Raised:
  5. What did software subscriptions cost in the past?
  6. How did various tech companies monetize user data?
  7. Key Quote: "It’s possible to learn from history and integrate the best of today’s technology with fair business practices that are more sustainable and healthy for everyone."
  8. Call to Action: Collective efforts are necessary for reclaiming personal computing and digital autonomy.
  1. Insights on Devin – AI Tool Evaluation
  2. Participants: Hamil Hussain, Isaac Flath, John O. Whittaker from Answer.ai
  3. Evaluation of Devin: An AI tool for autonomous software development.
  4. Key Takeaways:
  5. Initial excitement was noted, but practical usage revealed limitations.
  6. Tasks were often too small or ill-defined for effective AI handling.
  7. Human intervention is crucial for optimal performance of generative AI coding tools.
  1. Individual Contributions (IC) vs Management Paths
  2. Speaker: Asaph Zamir
  3. Main Insight: Many engineers feel pressured to move into management for career growth, which may not be the only or best path.
  4. Key Quote: "The IC path isn’t just a valid choice. For many, it’s the path that leads to the highest potential and greatest satisfaction."
  5. Strategies for IC Career Development:
  6. Develop a technical brand.
  7. Seek technical leadership opportunities.
  8. Stay current and curious.
  9. Build strong relationships.
  1. Rethinking Documentation
  2. Speaker: Fabrizio Ferri Benedetti
  3. Core Idea: Existing documentation frameworks often prioritize tech writer's needs over user actions.
  4. Proposed Model - Seven Action Documentation:
  5. Appraise
  6. Understand
  7. Explore
  8. Practice
  9. Remember
  10. Develop
  11. Troubleshoot
  12. Goal: Improve documentation by focusing on users' actions and needs.
  1. Nue: A Standards-First Web Framework
  2. Speaker: Tero Piirainen
  3. Overview: Introduction of Nue, a web framework prioritizing standards and modern web technologies.
  4. Key Issues Addressed:
  5. Front-end engineering problems exacerbated by complex frameworks.
  6. The design engineering problem associated with JavaScript monoliths.
  7. Vision: To create a better development experience by stripping away unnecessary complexities.

---

Conclusion

  • The episode covers the pressing need to re-personalize technology, the evolution of AI tools in software development, alternative career paths for engineers, effective documentation strategies, and a fresh approach to web development with Nue. The discussions emphasize user-centric perspectives, the essential role of human expertise in tech, and the importance of ethical practices in the tech industry.

---

Additional Notes

  • For more insights, check out the companion newsletter for upcoming topics and previous episodes.
  • Guest appearances in previous episodes include Alicia White from Embedded.fm and discussions on NVIDIA tech and modern terminal experiences.

Call to Action

  • If you enjoyed the episode, consider leaving a five-star review and stay tuned for future discussions and interviews!

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:29What up nerds? It intentionally waits a brief period after you run off the side of a platform before it plummets you to your eminent demise. It's named after the Wile E. Coyote cartoons, and it's apparently been making me feel better at video games than I actually am for the entirety of my life. Ignorance, as they say, is bliss. Okay, let's get in to this week's news. It's time to make computing personal again. Benj Edwards definitely describes how surveillance capitalism and DRM turned home tech from friend to foe by asking a litany of rhetorical questions about the past. What percentage of your income had to go towards annual software subscriptions on a 20th century Windows PC?

1:17Which part of this TV set kept track of everything you watched and then secretly sold the data to advertisers? Which part of Windows 95 fed you ads without your consent and kept track of everything you did remotely so Microsoft could keep stats on it? Which part of Amazon.com in 2000 tried to get you to buy millions of no-name counterfeit and dangerous goods propped up by stealth advertising and fake reviews? which part of Google in the 1990s and early 2000s blanketed its results with deceptive ads or made you add Reddit to every search to get good results that weren't overwhelmed by SEO seeking filler content.

1:57When you say it like that, Benj, hmm. He continues, quote, every generation looks back and says, things used to be better, whether they are accurate or not. But I'm not suggesting we live in the past. It's possible to learn from history and integrate the best of today's technology with fair business practices that are more sustainable and healthy for everyone in the long run, end quote. Benj has a few ideas on what we can do individually to push this idea forward, but he believes it will take collective action to make meaningful changes, quote, whether through purposeful reform or the eventual collapse of digital strip mining, I believe the personal computer will eventually rise again along with our chance to reclaim control of our digital lives.

2:43Thoughts on a month with Devin. Hamil Hussain, Isaac Flath, and John O. Whittaker from Answer.ai put Devin, the product whose creators promised it to be a fully autonomous software engineer, through its paces. They were optimistic. Quote, something about Devin felt different. If it could deliver even half of what it promised, it could transform how we work. But while Twitter was full of enthusiasm, we couldn't find many detailed accounts of people actually using it. End quote. Their conclusions confirm my priors, so I'm happy to share them with you. Jono says, tasks it can do are those that are so small and well-defined that I may as well do them myself, faster, my way.

3:26Larger tasks where I might see time savings I think it will likely fail at, so no real niche where I'll want to use it. Here's Isaac's take. I had initial excitement at how close it was because I felt I could tweak a few things, and then slowly got frustrated as I had to change more and more to end up to the point where I would have been better off starting from scratch and going step by step. And Hummel's findings. Devin struggled to use internal tooling that is critical at Answer.ai, which, in addition to other issues, made it difficult to use. This is despite providing Devin with copious amounts of documentation and examples.

4:01I haven't found this to be an issue with tools like Cursor, where there is more opportunity to nudge things in the right direction more incrementally. I think Hamill's last comment nails it. The current state of the art in generative AI coding tools, despite impressive demos, only brings meaningful value when paired with a competent human programmer to nudge things in the right direction at every step. Why senior engineers should stay ICs. For many successful software engineers, management seems like the only path toward career advancement. Asaph Samir, however, has learned something quite different after years in the industry.

4:40Quote, in my years of mentoring developers, I've seen too many brilliant engineers jump into management because they thought it was the only way forward. But here's the thing. The IC path isn't just a valid choice. For many, it's the path that leads to the highest potential and greatest satisfaction. In this post, Asaph makes his case for the individual contributor path. If you're sold on the idea, he also lays out four strategies to build your icy career around. One, develop your technical brand. Two, seek out technical leadership opportunities. Three, stay current and curious. And four, build strong relationships.

5:20It's now time for sponsored news. On January 30th, you can watch Augment Code in action during their live demo. But what is Augment Code anyways? It's the developer AI for complex code bases, providing you with real-time, deep understanding of the code so you can be super productive right away. Quote, Augment taps into your team's collective knowledge, your code base, documentation, and dependencies. It's the most context-aware developer AI, so you won't just code faster, you'll build smarter. Join Solutions Architect on Schumann Pandy while he demos how it can help you get up to speed on new projects, write effective unit tests, refactor legacy code.

6:04Don't just code faster, build smarter with Augment Code. Register today and they'll send you a link to join the talk and an email reminder before the session. And thanks to Augment Code for sponsoring ChangeLog News. The seven action documentation model. Fabrizio Ferribanetti thinks most of the existing documentation frameworks focus too much on the tech writers and not enough on the actions of users who are consuming the docs. Quote, the prescriptive emphasis on what docs must be produced instead of describing what user needs should be addressed echoes an architectural mindset where one builds walls because of course a house must have rooms.

6:44What are we, barbarians? This apparent lack of flexibility disincentivizes writing the content that's needed. End quote. Fabrizio proposes a new documentation model that is centered on seven actions that the docs are meant to satisfy. The actions are roughly in order, but not strictly. One, appraise. Two, understand. Three, explore. Four, practice. Five, remember. Six, develop. Seven, troubleshoot. He develops and explains each action and the approach you'd take in providing docs to accompany the user on their way, finishing with this. As it happens with theoretical models, this one isn't backed by extensive research or factorial analysis.

7:25The model is distributed as is, and under no circumstances can you hold me accountable for having ruined your lunch. However, I hope it provides a useful perspective for technical writers seeking to create more purposeful documentation. A standards-first web framework. New creator, that's N-U-E, creator, Tero P-I-R-A-N-E-N. Tero P-I-R-A-N-E-N. P-I-R-A-N-E-N. Today, new takes a new, more natural direction. It becomes a standards-first web framework. The focus has always been to strip away artificial layers and help developers take modern HTML, CSS, and JavaScript to their absolute peak. This shift is important because now we can more directly work on solving the two key issues in front-end development.

8:18End quote. Those two key issues, as Taro sees them, are the front-end engineering problem, which can perhaps be boiled down to React and Friends, spoil the fun, and the design engineering problem, which can perhaps be boiled down to JavaScript monoliths, spoil the fun. Taro is disappointed with the front-end ecosystem, so he's building something that he hopes will show the old, new way to build better websites. That is the news for now. But also scan the companion newsletter for even more news worth your attention. Such as, you have built an Erlang, using coding skills to make passive income, and Docker on macOS.

8:55Is it still slow? In case you missed it, last week we published two awesome shows, an interview with Alicia White from Embedded.fm, and a news roundup with Adam and yours truly, talking NVIDIA digits, Waymo infinite loops, and modern terminal experiences. Scroll up in your feed to find those and stay tuned for this week, because Wednesday we are speaking with Ashley Jeffs, all about his open source ride and selling Benthos to Red Panda. And on Friday, we're joined by Chris Brando and Matthew Sanabria from GoTime spinoff FallThrough.fm. Have a great week. Leave us a five-star review if you dig our work.

9:33And I'll talk to you again real soon.

From the publisher

Benj Edwards wants to put the "personal" back in "personal computer", the answer.ai folks took Devin for a month-long spin, Asaf Zamir explains why senior engineers can remain ICs and still have a fulfilling career, Fabrizio Ferri Benedetti rethinks documentation by putting user actions first & Tero Piirainen lays out his case for Nue, the standards first web framework.

More from The Changelog: Software Development, Open Source

All 232 episodes
Make computing personal again (News)The Changelog: Software Development, Open Source · 10 min
Listen in VO