colorfulMinds

I really enjoyed the two days I spent alone working on this MVP project. I got the chance to practice many topics covered in the curriculum at my own pace. Also I was able to experiment with new stuff that I didn't do before; like using bootstrap 4 with react and searching for APIs that supplied me with the data I needed for my app. It was a very awesome experience that I'd love to repeat again and again. I'm fairly satisfied with the outcome I made after these two days since it was a solo effort entirely. I didn't struggle thankfully, just the usual bug search and debugging here or there.

Deployment is the hardest part in the lives of computer coders, it's harder than making apps and games. Any game that you have ever used for example on your computer had to go through many operations to be in the final form it is when you first bought it. The last operation is deployment as you might have guessed. It's about getting your video game ready to use and play on any computer out there. Many issues could happen while deploying the game since we have many environments to deal with these days.

For the past couple of years I have been learning how to work with front-end languages and technologies like HTML, CSS and a little bit of  Javascript. However,  I have never really touched upon the backend until this month. It was challenging at first and we spent most of our time getting ourselves familiar with the new syntax and the many many many frameworks and libraries that are usually used together in combo when working on this side. Fullstack web development means creating an application and taking care of everything concerning it's functionality and UI.  We've been learning the basics of Javascript for the past couple of months and a little bit of CSS, HTML and jQuery.Now in the immersive we learned more front-end frameworks like backbone/react and angular. And for the backend we learned the basics of nodejs and express. For persistence of data we learned how to use sqlite3, mysql, knex, bookshelfjs and mongodb which I really liked. Putting a...

If that were to happen then I would remove all taxes. Also I would help all refugees and make teaching how to code free.

SQL databases are called relational database management systems RDBMS, have predefined schema and are table based. While NoSQL databases are document based and have dynamic schema. Famous example on SQL would be MySQL and for NoSQL would be MongoDB.

I once had a conflict with a person(a friend) that was doing something incorrectly and it was obvious to everybody around them. I tried to tell them that but they didn't like the truth and tried to blame me for my honesty, even though we were supposed to be honest with each other. Nothing major happened after that, we just talked it over and solved the conflict without letting it get out of hand.

So in nodejs the methods are primarily nonblocking and by that I mean that  the code inside of them is executed without stopping the execution for the other parts of the program until it finishes it's current operation. A famous example would be reading a file using the fs module: const fs = require('fs');  const data = fs.readFileSync('/file.md'); Here the second line will block the execution until it finishes the current task at hand, so this is Synchronous. The counterpart would be the Asynchronous: const fs = require('fs');  fs.readFile('/file.md', (err, data) => {  if (err) throw err;  });

We have used multiple libraries so far like jQuery, React and underscore. For frameworks I'm not sure but I think we can consider react, angular and backbone as frameworks. The difference between these terms is mainly about the inversion of control; where your code calls a library function when needed to accomplish a certain task like calling underscoe.js functions. However, it's different for frameworks where your code will be called by the framework itself, and it's regularly more complex.

RESTful APIs describe the principles that data can be transmitted with over the internet. However Web APIs or more commonly web services are a way to communicate between programs or devices online.

MVC stands for Model - View - Controller, it's a design patter that is very famous and popular among developers these days. It's used to build scalable apps that separate the content into three different layers. The model contains the persistent data of our app like variables and functions. The View is responsible for rendering the components on our html page. The controller does the even-handling through listeners to listen to when the model data changes. When the model data changes then the controller will sense that change and the view will re-render the page with the updated data. This is mostly everything that I know about MVC up until now.