How to deal with procrastination

Everyone's different but I find that if I want to learn something new, I HAVE to find a concrete use case for it first. It's utterly futile (and I'll just procrastinate forever) if I just try to only slog through a bunch of tutorials without an endgame in mind. Biting off more than I can chew usually works for me because I'm stubborn AF.

Start blindly flailing like a madlad on a project until I can define a particular gap in knowledge. 2. Research said gap. 3. Rinse, repeat.

I found a great article about it.

I will post it here later

What article
And they were never heard from again...

I find that if I procrastinate on learning, the best course of action is to go blindly in, try, get frustrated, find info, create chaos and just absolutely fail.

Surprisingly this breaks the procrastination cycle for me. But I can't promise that this will work for you.

The other option is to just watch a tutorial on the phone, which may break barrier (unlike actually sitting infront of a computer deciding that you will invest time into this).

Procrastination is like getting into the pool for the first time in the morning. Gradual exposure to the cold water is the most painful way to go. The fastest way to get going is to jump in!

make a weekly target, and baby step, don't just go too big... take example console app, 3 construction fundamental, etc...

Make a example of what weekly target I can do
- Look example tuts on https://www.geeksforgeeks.org/c-sharp-tutorial/
  
  Make a weekly progress on at least 5-7 points on the list, take example Fundamentals, contain Hello World! Program Identifiers Keywords Variables Literals Data Types Operators Enumeration
  
  Make it done in one weeks, and try to make a simple project in the ends, based on the things you already learn.
  
  It will help.
  
  Then Collections
  
  ArrayList Hashtable Stack Queue
  
  One weeks.
  
  After that you can try linq I guess? Or follow the list thoroughly...

Do you think enums need to have a reason to be in order? Like, the example I was looking at today said winter, spring, summer, and autumn. But this is a cyclical order. Is an enum the best representation of a cyclical order? Isn't it more of a ordinal number thing?

This should be a different post, but it depends on what you're planning to do with them. Enums are flexible and could totally make do there regardless of semantic cyclical-ness. Remember with enums you're able to just ignore the values altogether; that's one of the major reasons to use them. If I have a limited list of flags that I use directly in code, they don't have to change at runtime, and don't need additional data associated to them (like 'number of days' or something similar), I'll use an enum.

If you wanted to actually cycle though them in your code, it might be clearer to use both a manager class with a enum. Inside the class, you could use a something like a CurrentSeason property and have a NextSeason, PreviousSeason method to cycle through them. Using modular arithmetic would allow you to change the number of items to cover future features like seasonal transitions or something without having to modify any of your code.
- I was employing subtlety as a strong suit. Wasn't it obvious?

I'm fundamentally a hardcore procrastinator, but I'm also a senior manager of a software team at an aerospace company, so procrastination is not compatible with my job.

My personal approach is to keep a list of the things I need to do, with a realistic date I have to do them (not the drop dead date, but when I should really do them). Then I've just pushed myself to make sure I've cleared my list, at least of the near term stuff, before I do anything that's not on the list. I also tell folks when I'm give them stuff so I'm on record as having made a commitment.

I think no matter how you slice it, beating procrastination requires some personal discipline. The trick is to find an approach that works for you.