Starting something new

Hiya folks. I'm starting a little blog.

My story so far (for context):
I'm not a professional software developer, but last year I decided I wanted to become one. I don't have an undergraduate computer science degree (I studied business/marketing), and before last year I had never written a single line of code in my life.

I worked for a few years after graduating -- A couple in marketing / market research / brand-strategy, and then a couple as a semi-technical career coach at a big tech company. I say 'semi-technical' because I was career-coaching software engineers (i.e. I knew the lingo, and I knew the keywords). But I didn't code, nor did I really know what I was talking about when I asked a software engineer if they 'focused more on frontend or backend,' what 'frameworks' they had experience with, if they had experience 'implementing APIs,' etc., etc.

But I wanted to know what I was talking about. So I started doing little online coding classes that I could find for free/cheap (Codecademy.com, Udemy, Coursera...). Nothing fancy, I was doing basic HTML/CSS, a TINY bit of javascript, and learning a minuscule amount about algorithms/data-structures. That was all great until I got addicted to it and needed to find a way to speed up my learning -- long story short, I left my job in September 2017 and enrolled in a full-time, immersive coding bootcamp.

So that's me.

Regarding this blog:

Honestly I'm not sure how this will actually manifest, but...

• The length of these blog posts will probably range from 3-sentences to 5-pages 
• The content of these blog posts will probably range from super-technical, to whatever is on the opposite end of that spectrum. Topics might include professional/personal development, solving a specific coding challenge, learning a new (or reinforcing an existing) coding technique/syntax/skill/framework, job-search best-practices, random musings about stuff, and anything/everything in between. 
• The primary intention of these blog posts will be to 1) hold myself accountable and 2) document/reinforce my learning. My intention isn't to "teach," but maybe by following along you'll learn something new / find something to relate to. 

I'll try to work on a blog post every week, and hopefully publish a few times a month. Blogger friends tell me that that's a little ambitious... gonna give it the ol' college try. If I fail -- luckily it's a blog not open-heart surgery (shoutout to those heroes).

Also... I'm not really gonna proofread these posts for spelling/grammar errors or run-on sentences or sentence fragments or comma splices. That said, I do want to practice communicating effectively (especially when it comes to technical concepts), so feel free to let me know what I could be doing better. I won't get offended.

Lastly, I'll be exploring concepts that interest me, but happy to take requests / collaborate. I'll find somewhere on here to put my contact info.

Thanks and love you guys,

noah