When I was and undergrad and junior grad student, I regularly burned myself out on deadlines. I actually work WAY harder now. And I'm able to do it because I learned to manage my energy better. Here are some lessons I learned.

Thread. 👇
The most important thing I learned was to recognize if I'm not working productively on something and step away. To make a sports analogy, pushing through fatigue is how you get better but you shouldn't push through injury. Taking a break early can give you a lot more time back.
Another lesson was to take recovery seriously. Previously, this meant sitting in a catatonic state after I had overworked myself. I now have processes for winding myself down daily, weekly, monthly, and annually. They include meditation, yoga, writing, and doing non-work things.
Also: rest doesn't have to be passive. As a former runner, I learned that cross-training (doing other aerobic workouts) was important for staying fit and preventing injury. Actively working different parts of your mind can be more effective than resting your mind altogether.
And sometimes, recovery just means doing nothing. To everyone who feels pressure to always be doing something: it's a whole lot more productive to rest BEFORE you get burned out than after. If ever you want to feel better about doing nothing, just ask me how much Netflix I watch.
I saved one of the biggest lessons for last: reducing angst overhead. A lot of the time I used to spend working, I was actually angsting. This took energy and did not get me anywhere! This was such a big lesson for me I wrote a blog post about it here: jxyzabc.blogspot.com/2016/03/the-an…

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with ⚡️ Jean Yang ⚡️

⚡️ Jean Yang ⚡️ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jeanqasaur

11 Aug
Taylor Swift as important papers in programming languages, a thread.

"An Axiomatic Basis for Computer Programming," C.A.R. Hoare, 1969. Introduced Hoare Logic for proving program properties.

"Abstract interpretation: a unified lattice model for static analysis of programs by construction or approximation of fixpoints," Cousot & Cousot, 1977. Introduced abstract interpretation for statically analyzing program properties. Now used by Airbus.

"Design and synthesis of synchronization skeletons using branching time temporal logic," Clarke & Emerson, 1981. The first paper on model checking for program correctness. Led to the 2007 Turing Award.

Read 10 tweets
5 Aug
Ok I couldn't resist. Taylor Swift as classic programming textbooks, a thread.
Read 9 tweets
4 May
Programming constructs as cats, at thread. 🐱

Tail recursion
Strong static typing
Read 6 tweets
27 Apr
Just had an good conversation with @panmanphil about data flows:
🧐 Why enforcing privacy/access policies in software is hard
😫 Why static and dynamic analysis aren't the solutions of people's dreams
🛣️ Why data visibility/data mapping is The Way

@panmanphil 🧐 Enforcing security/privacy policies on data flows is not as simple as checking a rule as data leaves the database. *Which* rule you check for *what* data matters and is hard to keep track of. Either devs need to track this or software needs to track this. It's hard for devs.
@panmanphil 😫 Automatic policy enforcement requires automatic data tracking. Tracking data at runtime comes with unappealing performance overheads. Tracking it statically, before you run, gives you way too many false positives. Anything short of this leaves major gaps.
Read 7 tweets
25 Apr 19
Taylor Swift as iconic computers, a thread
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!