Scribelate

There are many different paths to learning a language. Today it seems like the number of tools that you can use to start your journey are almost countless. Regardless of the process you use, you will eventually come across the concept of comprehensible input. Here is a great article by Steve Kauffman about comprehensible input  - what is it and how does it work.  Basically it's finding the right content that let's you understand almost all of what you are listening to and building those listening skills.  As your understanding grows you will be able to figure out new words when you run across them.   The key thing to understand is that it needs to be content that you can understand.  If you are listening to some content and you can't understand any of it, the process becomes frustrating and a chore.  Pretty soon you will dread the exercise and eventually you will just stop.  It has to be fun for you to continue and more importantly for you to want...

This was an exciting week for me. It was New Year's Eve, and I felt like working on Scribelate, but I didn’t feel like diving into a lot of code work. I had already done much of the coding to get a fairly functional version running locally. Plus, I’d registered the domain scribelate.com a while ago. So, I thought it would be a great idea to try setting up a production environment on New Year’s Eve. It ended up taking most of the day and into the evening. I got pretty close but didn’t quite have a fully working version by the end of the night. When you think about all the different things that go into a production build, it’s a lot. Setting up server environments, deploying the production build version of the code, configuring a database, deploying the database model… there are so many moving parts. The biggest challenge I faced—and as I told my wife, "Ignorance is a terrible thing"—was with my backend services, which are written in Go. Typically, building a Go application...