The start of learning / starting something new usually has a rocky start. There is a lot to learn when creating an entertaining and informative product. After my first week of streaming I have documented and put together a list of things to work on. Some things I need to work on:
- Have a better idea of what to accomplish during the stream / be able to explain it
- Stop over engineering things ( Start Small then expand after a strong base project )
- Do research prior to prove proof of concepts
Day 1 Stream ( 3 hours )
I felt like I had a good head start and had planned everything out. Was making good progress but screeched to a halt when coding while I was tired. I need to learn where my stopping point is.
Day 2 Stream : Part 1( 1.5 hours )
Continued on from the previous nights code. Ended up shooting myself in the foot by over engineering everything.
Day 2 Stream : Part 2 ( 2 hours )
After taking a breather and scrapping the code. I built a clean and solid base project to start off of. This was a good idea due to the fact of not having to try to write code as I would in a real situation. After all this is just a prototype while being as cheap and cost effective as possible ( saving my time ).
Day 3 Stream: ( 2 hours )
It’s days like today where I really enjoy streaming, although I do wish logic could have been implemented faster and more efficiently. Today was a big win in the entire CRUD process of socket servers and laying the foundation of the year to come with the Internet of Things projects!
Day 4 Stream ( 3.5 hours )
Had a cheat day. Didn’t want to code on socket server but wanted to get some coding in. I fumbled my way into coding a widget that sits on this website and will only show when i’m live streaming. It is a subtle red button that asks you politely if you want to come watch me be a geek and code!
Total time spent: 12 Hours