IDEs of March There are many articles about learning to code and mention where to learn or how to learn etc. Very few however mention where you are going to write the code once you learn it! Most beginner stuff have you working at that programming language’s terminal, which is great for getting the basics but you’ll quickly grow past that. So where does one actually write their source code?
So You Want to Learn to Code I’ve been getting a lot of inquiries recently asking a lot of similar quesitions. Often these questions are broad and hard to answer in an email or a DM, so I’ve decided to use my free time no longer taken up by watching sports to write a series of blog posts to answer them as best I can. One of the big ones I keep seeing over and over again is “What are the best resources to learn to code?
Ok this is going to be a series of blog posts about detaling my notes and thoughts as I work through DeGroot and Schervish’s Probability and Statistics 4th Edition. This may be useful to you it may not be but I generally find I learn things better if I write down what I’m thinking about them so without further ado, let’s begin! The History of Probability So apparently people have been gambling forever.
Ok if you’ve read the first tutorial on installing Postgres and getting your first database up and running, you’re now wondering “So how do I access all this data?” Well that’s where this tutorial comes in as we are going to cover some of the basic commands in SQL to get the data we want. Ok let’s get started and dive right in to our data. SELECT The SELECT command is going to be your workhorse command when working with SQL.
by Matthew Barlowe I’m going to cover two important concepts when it comes to coding: Continuous Integration and Code Coverage. Continuous Integration is the act of merging everyones code into the main code repository several times a day instead of doing it once a day or every few days. There are pros and cons to this behavior which is beyond the scope of the article, but I like Continuous Integration (CI) because it fits in with my own coding philosophy.