Oh I learned a bunch.  One thing I'm glad I avoided was procrastinating completing features.  For example, if you're working on your player's death, complete the whole system before moving on the something else.  If you're working on a specific enemy's AI behavior, try to complete the WHOLE enemy before moving on the something else.  When you're working on a game with no deadline, it's somewhat fine to bounce around, but when you only have a week, doing so will only start to pile more and more incomplete functions into your game.  It's also more speedy in my opinion to do so, which is how I managed to implement a bunch of different stuff in my game.   Theres a bunch of other stuff I learned too I think.  Jams are surprisingly informative lol

My first jam too. 

I think I learned more from other people's games than mine.

The importance of color palette. This is huge. Can make or break a game. I knew this was important but the jam showed me how much. 

Also, difficulty. A game too easy is boring, but it's better to lean towards the easier side. It's hard to have good pacing in a game and the worst thing is an unfair stage. I have a level which I thought is too easy so I added more hazards, which made a lot of people to feel frustrated with this specific level. But, had it been too easy, people won't feel something special. And it's better to have a neutral level than a frustrating one. 

I learned better methods of hiding level streaming to have my games remain with no loading screens. This was the main reason I wanted to make this game since my bigger project is planned to almost have no loading screens. I also have a bit more experience with being stricter and exact with LODs. I know I learned smaller things from this jam but I can't really think of anything else too significant. 

hi all, I wrote a complete post about it here https://itch.io/jam/brackeys-5/topic/1231056/yin-and-yang-in-search-of-harmony-lessons-learned