Hard Fork
Our 2026 Tech Resolutions + We Answer Your Questions
Kevin Roose & Casey Newton
2 Jan 2026
22 min read
1h 28m
TL;DR
Kevin and Casey share their 2026 tech resolutions: Kevin commits to mastering short-form video to meet audiences where they are, while Casey vows to stick with his finally-perfected productivity system using the Capacities app with AI-powered 'blip' tracking for story research. Both reflect on how finding purpose and presence—rather than chasing productivity hacks or meditation apps—proved more effective than traditional self-help in 2025.
Hard Fork is the New York Times' flagship podcast exploring the intersection of technology, culture, and society. Hosted by tech columnist Kevin Roose and Platformer's Casey Newton, the show tackles emerging tech trends—from AI and crypto to social media and startups—with sharp analysis and humor. Each episode combines breaking news coverage with deeper investigations into how technology reshapes our world.
Takeaways
1
**Short-form video isn't just hype—it's inevitable for journalists** Kevin argues that platforms are shifting decisively toward video content, and journalists should stop resisting and instead figure out how to do it authentically rather than letting influencers and low-quality creators dominate the space. This isn't about going viral or adopting gimmicks, but finding ways to deliver substantive journalism in formats where audiences actually are.
2
**Purpose beats productivity tools every time** Both hosts discovered in 2025 that reconnecting with their sense of purpose—attending events, writing books, meeting interesting people—did more for burnout and focus than any meditation app or productivity system. Tools are only as good as the clarity of goals and sense of meaning they support.
3
**Build systems around your actual needs, then lock in** Casey's 2026 resolution to stop switching productivity tools reflects a matured understanding: spend time identifying what you actually need (journaling, lightweight task management, narrative tracking via 'blips'), build a system around that, then commit to it for a year rather than chasing incremental improvements. Stability in your system infrastructure yields more returns than constant optimization.