I think it would probably be important to start by saying that the looks and functionality of this blog are all pending on whether I learn something new or decide to implement something new or better. That probably sums up why I titled this blog post the way I did. I wanted a way to record and show what I am studying and programming. If I waited til I felt accomplished in what I am doing before starting this blog it probably would never come to being. So while this is going to be a bumpy road, I think it best to document my adventure.
That being said, I don’t claim to know everything. And when I’m dealing with computer science, I usually claim to know nothing. It is tough when you realize you don’t even know what you don’t know. Obviously if I didn’t enjoy it though, I wouldn’t be doing it. So while it may be a exercise in masochism, I enjoy almost every second.
With those two introductory points out of the way, I really just want to address the direction I hope to take this blog into in the (more near than far?) future. I obviously want to communicate with others, so one of the first thing I want to implement something like a comment box for people to leave feedback. That is gonna require some studying into something that is persistent, that will stay on the website even after I update and such.
The second thing I would like to dive into, and hence put onto my blog is a twitter API. I haven’t worked with another company/person’s api before so I’m pretty excited to mess with it, even though I’m going to be plenty lost at first.
TLDR: Goals to focus on:
- Look into a persistent comment system for the blog.
- Look into implementing my twitter feed onto the blog.
Link of the day, courtesy of @talk2megooseman at his twitch stream, https://go.twitch.tv/talk2megooseman:
How to get "create-react-app" to work with your API
A reoccurring theme that I am already predicting is me always wishing I was getting these blog posts out a day earlier. Of course, some days I work all day at work and some days are going to have my free time, so I probably shouldn't let it bother me that I haven't posted in 4 days. Luckily, I think tweeting my #100DaysofCode progress will probably make it easier to look back and remember what the previous days held in store.
So first thing I spent a lot of time for on Saturday was working with a prebuilt bootstrap theme. I really like working with bootstrap, but it is definitely one of those things that I think I have a handle on and then end up surprised later when I’m troubleshooting. So with this bootstrap theme, we were supposed pretend as though we had a business. Considering the teacher wasn’t allowing Lorem Ipsum, it was frustrating spending so much time making up imaginary company information versus actually coding. The takeaway from this was realizing that my portfolio navbar isn’t exactly working the way it could be on mobile because the bootstrap pre-built theme we were working with had an awesome mobile navbar.
The second thing of note is there is a calendar now on the blog site. While almost all of the credit needs to go to a Youtube video I’ll link below, I am happy that I have some form of a calendar on the blog. That being said I still want to add a lot more functionality and I really would prefer to have it be my own beast rather than something I followed along with a youtube video on. Not to mention I need to tinker with where I put it on my page tomorrow.
I think posting my goals or what I’m going to attempt next really helps put my best foot forward for the next day so I’m going to follow the pattern of the last post.
TLDR: Goals to focus on:
- Figure out how to make my navbar look better on mobile devices.
- Move my calendar to a proper place.
- Look into adding some functionality to the calendar.
Link of the day, courtesy of Yusuf Shakeel and his youtube channel:
Design a Calendar for your Blog and Website using HTML5 CSS3 and JavaScript