index.php

<?php include "header.php";?>


    <div class="container">

      <div class="jumbotron">
        <h1>Basic Programming Stuff</h1>
        <h3>Here we'll go over some basic programming things you will likely need to know.  I won't teach you programming languages because there is already a lot of material out there but I'll show you where to go for a lot of it and what things you will need to know.</h3>
        <hr/>
        <h2>New Tutorials</h2>
        <p>Finally the first one on actual programming is up with the first <a href="js1.php">javascript tutorial</a> done in my own style.  This is very long but goes over a lot of basic programming knowledge as well if you haven't been exposed to it.</p>
        <p>I've also added prereqs onto the beginning of every tutorial thus far.</p>
        <hr/>
        <p><b>Frontend Programmer</b> : A frontend programmer will deal with the user interface and all the interactions that the user has with the program, anything programmed to run on a clients machine in a web-app is frontend (so one can think of frontend to also mean 'client side').  A website is basically all frontend work as it can be constructed without any backend programming at its most basic level.  The entire interaction of the frontend programmer with the backend (server) programmer is through an Application Programming Interface (API).  The ideal is for it to be a REST API where REST stands for Representational State Transfer, which basically means that each request to the API is independent of the last one.  The frontend makes a call to the server using a common structure and the frontend passes some data that informs the server what it needs and the server responds in kind.  It is the backend programmer's job to construct this API, the frontend programmer needs only use it.  The frontend programmer will be heavily using HTML/CSS/Javascript.</p>
		<p><b>Backend Programmer</b> : A backend programmer constructs the support structure of the program and deals with pulling data from a database and sorting/analyzing/sending it.  Also the backend programmer deals with server side details such as encryption, sessions (how to know if a user is logged in or not), as well as interactions through an API.  Much of the backend programmer's job is to construct a robust and easy to use API for the frontend programmers to pull from.  The backend programmer may use server scripting languages (BASH/PHP) or even call upon compiled programs (JAVA/C/C++) to get these jobs done.  An example might be to construct a program that runs daily that aggregates data from a database and makes it avaialble for the user through the API for that day (So they can see the daily totals of something).</p>
		<p><b>Database Administrator</b> : While a backend programmer needs to know how to query the databases the exact structure and organization of the databases need not be known.  The task of optimizing indexes, data structure, ensuring scalability and uptime of the database itself is the realm of the database administrator.  The database administrator doesn't write many programs and often times it is a lot of scripting to check the status of the database and maintain it.  The two bread-and-butter database standards are SQL and NoSQL, characherized by my favorite the MySQL server and MongoDB.</p>

      </div>

    </div> <!-- /container -->

  </body>
</html>