Artwork

Content provided by Avi and Bugsby. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Avi and Bugsby or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Episode 11 - Efficiency

35:48
 
Share
 

Archived series ("Inactive feed" status)

When? This feed was archived on September 01, 2024 07:07 (2M ago). Last successful fetch was on February 27, 2024 03:53 (8M ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 189033369 series 1618642
Content provided by Avi and Bugsby. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Avi and Bugsby or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

References

Elasticity of demand

System I and II

Achieving flow

Failure mode of computer scientists in building tools: You Aren't Gonna Need It, Premature Optimization,

Dominion (again) / Isotropic

Overdamped/underdamped control. For the short version, see this Quora answer. For the math, see this.

Efficiency practices

Making (and checking) checklists

Series of many small efficiencies: bumping drawers closed with your hip, staying in touch with best balance contact point

Pipelining

Merging steps (in general, streamlining processes)

Retrospection - which behaviors over last week could have been improved?

When successfully correcting an error: what practices would have avoided that error in the first place? What would those practices have cost me, and would it be worth it?

Scheduling - both making good use of time, and avoiding schedule failures that require costly correction

Recognizing inefficient behavior patterns

Main takeaway: the balance between optimizing for a value function and checking whether you need to update the value function is the key to efficiency.

  continue reading

18 episodes

Artwork
iconShare
 

Archived series ("Inactive feed" status)

When? This feed was archived on September 01, 2024 07:07 (2M ago). Last successful fetch was on February 27, 2024 03:53 (8M ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 189033369 series 1618642
Content provided by Avi and Bugsby. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Avi and Bugsby or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

References

Elasticity of demand

System I and II

Achieving flow

Failure mode of computer scientists in building tools: You Aren't Gonna Need It, Premature Optimization,

Dominion (again) / Isotropic

Overdamped/underdamped control. For the short version, see this Quora answer. For the math, see this.

Efficiency practices

Making (and checking) checklists

Series of many small efficiencies: bumping drawers closed with your hip, staying in touch with best balance contact point

Pipelining

Merging steps (in general, streamlining processes)

Retrospection - which behaviors over last week could have been improved?

When successfully correcting an error: what practices would have avoided that error in the first place? What would those practices have cost me, and would it be worth it?

Scheduling - both making good use of time, and avoiding schedule failures that require costly correction

Recognizing inefficient behavior patterns

Main takeaway: the balance between optimizing for a value function and checking whether you need to update the value function is the key to efficiency.

  continue reading

18 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide