Assuming you're talking about engineering tasks, here is some miscellaneous advice to help you work more efficiently[^1]: - Develop mental models. Build heuris

Assuming you're talking about engineering tasks, here is some miscellaneous advice to help you work more efficiently[^1]: - Develop mental models. Build heuristics. They allow you to recognize common scenarios more quickly and iterate on known solutions, instead of starting from scratch. - Write down high-level lessons from a project. Focus on generalizing the lessons. - Figure out how many "fucks to give" you have in a given time period. If one can complete 1 unit of work per day, then they can probably exceed that amount by 50% periodically, but will need an equal or greater amount of time to recover for the next few days. This also applies to weeks, months, and the year. - Take extended breaks from programming and computer science. Think about other things. Hopefully you have some unrelated hobbies, if not spend some time developing them. Programming is a marathon, not a sprint. Slow is smooth, smooth is fast. Lastly, not to plug my website[^2], but hopefully this is relevant: https://ashwinsundar.com/blog/compiled/learning-hard-things.html https://ashwinsundar.com/blog/compiled/learning-hard-things.... [^1]: Efficiency, not speed, is the metric worth focusing on. [^2]: Search engine crawlers are disabled