For all the self-taught geeks out there, here our content library with most of the learning materials we have produces throughout the years.
It makes sense to start learning by reading and watching videos about fundamentals and how things work.
Machine Learning Engineering (16 weeks)
Full-Stack Software Developer
Search from all Lessons
Curated list of small interactive and incremental exercises you can take to get better at any coding skill.
Curated section of projects to build while learning with simple instructions, videos, solutions and more.
Guides on different topics related to the technologies that we teach in our courses
Social & live learning
The most efficient way to learn: Join a cohort with classmates just like you, live streams, impromptu coding sessions, live tutorials with real experts, and stay motivated.
Testing software is one of those tricky activities that seem easy at first, but you can quickly get into a rabbit hole if you don't know what you are doing.
All apps have lots of bugs, even if you are the most brilliant developer on earth. Senior developers understand that statement, and that's why they get obsessed with doing everything they can to implement best practices and prevent bugs.
There are so many different ways something may go wrong.
Companies have big teams with dozens of people behind the quality teams because thorough testing is complicated.
We don't recommend doing all types of testing; when applications are over-tested, the development cycle is slow because you have to run all these tests every time the software is compiled or published.
Thru the past 10 years these are the following types of tests that have been developed:
We will focus on two types of testing: Unit Testing and Story Testing as we consider those 2 the most important ones and, in some times, more than enough to ensure a reliable application.
Write down all user stories and acceptance criteria before coding. Make sure everyone agrees. Setup a bug database with priorities and a Kanban board with status-based tracking. Plan your tests. Have a "bug report template" Test for unhappy paths, errors and exceptions.
According to the agile method, your application requirements start as "user stories". User stories are straightforward and plain-english ways to describe software functionalities.
As a student, I would like to deliver projects for review.
Usually a user story can be structured like this:
As a [role], I can [feature] so that [reason]
The following is an example template to fill; you don't have to use all the sections, but please make sure the bug you create has a concise and reproducible description that is easy to understand for everyone on your team: