100DaysOfCode

100DaysOfCode

I’ve been telling myself that I’m going to spend more time coding, but it’s hard to make the time for working on code when you work with computers all day. So, I’m deciding to force it upon myself to code for 100 days straight. No matter how much or how little I do, I’m going to be doing something to advance my software development skills, whether it be learning a new editor, language/framework, or architecting some infrastructure in the cloud to make use the fun stuff I’m building.

I plan to spend most of the front half of these 100 days working on this blog, with vim to see how I can improve my workflows through it. Admittedly, I have a LONG ways to go before I’m competent enough to match my speed with other editors… either way, you can track my notes in http://github.com/mochsner/.vim, where I’ll be documentating things that I learn, as well as files for my vim customizations. I expect to spend much of this journey just learning about vim, so apologies if there isn’t enough actual “code” in this round of #100DaysOfCode.I normally use VS Code, so I’ll also be using the VSCodeVim plugin as well.

Anyways, here’s to an exciting (& busy) time of the year - happy coding!

Day Reflection
2019.06.10 (Wed, Day 1) Play the VIM game; start RSS feed for Jekyll blog; discuss code idea with Ann-Marie (calendar)
2019.06.11 (Thu, Day 2) Researched RSS feed for Jekyll blog, including tags feature for share: twitter feature.
2019.06.12 (Fri, Day 3) Setup / tested RSS feed for Jekyll blog, including a general social-feed template that Twitter feeds inherit from. This integration is used in conjunction with ifttt.com, where you have “if this event, then that action”. This led to some pretty cool realizations of what ifttt can do, including publishing to google sheets, facebook messenger, Slack, Telegram, Wordpress & a huge assortment of 3rd party web services.
2019.06.13 (Sat, Day 4) It’s Saturday, but I’m hoping to be able to take some time later today to try to get SSL working for mochsner.io in AWS. Github’s instructions seem to explain it pretty well in https://help.github.com/en/articles/troubleshooting-custom-domains#https-errors, but the GUI AWS Console was pretty confusing last time & I wasn’t able to figure it out. That led me to learn of the AWS CLI, which I’m not too familiar with but want to become more comfortable with.
Follow-up: Didn’t actually get it working. Still can’t figure out where in AWS CLI to get an A-record setup without creating the $50 monthly charge for a hosted zone (same issue I ran into last year). Still need to do a bit of digging / maybe ask around on other blogs that seem to have similar setups. Fortunately, I was able to have some fun with Linux & get VSCode & VSCodeVim installed.  
2019.06.14 _(Sun, Day 5) I was able to play around with PSCore6 today, which is pretty powerful. After just a few minutes, I came to realize that you can pipe objects / information between powershell commands & linux commands, such as Grep. Not sure what the limits of this interoperability are, but I’m excited to find out!
2019.06.15 _(Mon, Day 6) I spent a good bit learning about Vim, as well as been to play with AD / Powershell a bit (which definitely makes the life of a Systems Administrator a bit easier). When dealing with multiple servers, being able to query AD can make things a bit less monotonous :)
2019.06.16 (Tue, Day 6) - Simple to-do, since I’ll be sleep deprived: Follow steps in Debugging VsCode Ext to generate a .vsix & test if VSCodeVim will work in my VENV used at work. The more practice with Vim (even if it’s just Netscaler commands & occasional Powershell), the better! Since VSCode is version 1.28.0, I’ve deduced the VSCode dependency to most likely be v1.0.4 (2019-01-31).
- It’s been a long day & there’s little actual coding I’m doing (outside above mention), but I’m getting comfortable with VIM! Opted today to use VsCodeVim to generate some Splunk/Netscaler commands for work, which worked out pretty well (even considering time restraints & the semi-awkward middle ground that is VsCodeVim). Tomorrow, I’ll look into scripting my environment to import plugins/extensions, since I’m starting to appreciate a more predictable (& responsive) experience.  
2019.06.17 (Wed, Day 7) - I worked with Vim Plugins today, as well as my VimRC. Not too much coding, but a good bit of research & also got to use the ServiceNow API to mass generate request forms that were handed off to a co-worker (pretty nifty)
2019.06.20 (Sat, Day 8) - Started hackerrank.com exercises for learning Bash - mostly simple I/O stuff, but it was generally a pretty good exercises where I got to practice my VIM skills (since I don’t get to do that a lot at work). I anticipate that my daily coding might slow down a bit, as I want to make sure I’m coding with my VIM workflows improved. Although I’ll be trying to code every day, I’m going to be focused on making sure I’m focused in the right areas.
2019.06.23 (Tue, Day 8.1) - Work’s picked up a bit, but that’s okay. I’m doing decent at learning VIM, but want to look into making sure I’m comfortable using it in a work setting. I’m not quite there yet, but hope to be there soon. Will have updates on that progress!
2019.08.07 (Wed, Day 9) } Welp, sure has been a while since I’ve coded something & posted here (work has sped up a LOT). Stil, I’ve managed to continue learning VIm at a moderate pace, which is nice. I’m working on getting a nice mechanical keyboard without keys on them as well, so I can work on my typing skills. Will update progress on how that goes. Regarding current progres, I’m working on developing a Rails-App-Menu (Web App), which has been lot of fun, but also difficult. Currently at a bit of a stand still from jumping straight into a full-stack solution, without thinking through how test-driven development (JSpec) works, which seems to be one of the best parts about rails. Will continue working (& posting)  
Written on June 10, 2019
comments powered by Disqus