Thank you Justin for this amazing content. I have been also looking for a learning track that takes you through building a sample app where you get hands-on experience of full stack development. Lot of the other learning platforms have really lengthy and tedious front-end and back-end tracks that talk about the technology itself but not how to use it. By the time you go through the entire course, you forget where you started from. Instead if we have learning tracks that allow to build a small apps quickly it would be much more interesting. for example - small task management app, an app that hosts blog etc.
Checking out your top post on APIs, I have to note that Merriam-Webster's brief definition online, while not using the best choice of words, is still a better explanation. Add in the huge bonus of brevity and it exceeds yours even more.
An API is a set of "exposed" functions and etc. that can be used to control a piece of software. It could also be called a translator. Indeed as the simple definition says it allows you to do things without having to be completely familiar with the software you are controlling, nor do you need to use the same language that software was written in. The focus on inputs and outputs is misplaced to say the least.
This is so awesome! Looking forward to all of your great content in a more structured format
Thank you Justin for this amazing content. I have been also looking for a learning track that takes you through building a sample app where you get hands-on experience of full stack development. Lot of the other learning platforms have really lengthy and tedious front-end and back-end tracks that talk about the technology itself but not how to use it. By the time you go through the entire course, you forget where you started from. Instead if we have learning tracks that allow to build a small apps quickly it would be much more interesting. for example - small task management app, an app that hosts blog etc.
Nice – this newsletter is definitely not going to teach people how to code but there are some good resources out there
Super cool. Thank you.
Checking out your top post on APIs, I have to note that Merriam-Webster's brief definition online, while not using the best choice of words, is still a better explanation. Add in the huge bonus of brevity and it exceeds yours even more.
An API is a set of "exposed" functions and etc. that can be used to control a piece of software. It could also be called a translator. Indeed as the simple definition says it allows you to do things without having to be completely familiar with the software you are controlling, nor do you need to use the same language that software was written in. The focus on inputs and outputs is misplaced to say the least.
woohoo!