First two weeks in a 10-week Web Dev Bootcamp

Two weeks ago, I started a 10-week Web Dev Bootcamp.

Here are my thoughts, experience, and how I’m trying to take advantage of these two first weeks.

I divide this post into three parts.

Part 1: How do I like the bootcamp up to now and why.

Part 2: What I’m trying to incorporate in my learning process to take the most of it.

Part 3: Why it may be a good idea to attend a web dev  bootcamp.

How do I like the bootcamp up to now and why

During these first two weeks of my learning journey, there are several aspects of this Web Dev Bootcamp I found that fit with my way of learning.

Format

Classes are text-based and you don’t need to watch endless videos.

Structure

I’m happy with the way Flavio has structured the lessons.

There is one module for each week and each module is broken down into small lessons.

Approach 80/20

The bootcamp is focused on the  80/20 approach which means it covers the most used and more important concepts. It’s not exhaustive but it’s relevant.

That 80/20 approach motivates me to follow the lessons and lets me face my doubts about being able to learn.

And up to now, I’m learning the basics of HTML and CSS.

With this approach, it’s the opposite to swim into the infinite universe of technical concepts and descriptions that exist in the web development world.

Also, that approach makes easy the aha moments and see the relationship between elements and concepts and how one builds on the previous one or how one connects with the previous one.

And finally, that 80/20 approach is straightforward because the theory is just enough and it’s what it’s needed for the also straightforward exercises and examples in each lesson.

What I’m trying to incorporate in my learning process to take the most of it

I’m trying to create a system and build some habits to enjoy this learning journey and take advantage of it.

Time and effort

 I spend no more than 3 hours per day, 5 or 6 days per week.

Even if I have more time available I prefer to keep it to the 3-hour max.

In my case, I have zero tech background and need time to process new information to make sense of it.

Don’t copy/paste

When there are exercises and demos inside the lessons, we have to do them following instructions, and I write the code, and I don’t copy/paste.

Since I’m writing the code I’m able to notice my errors: misspelling tags, wrong symbols, a missing character, and malpositioning attributes or values.

A notebook to write and review learnings

I have a notebook where I write my main learnings for each lesson. 

Since the lessons are on Notion, we can duplicate the file and make comments and annotations I certainly do but I also prefer to write some of them by hand in a notebook.

Learning in public

I have this blog and I try to publish twice a week my main learnings or some findings I got and think will help others that are starting from scratch in web development.

Extra resources

When I want to double-check or see more information about an aspecto or concept, I use the following resources:

Having said that, in most cases, I prefer not to look for more information because I want to avoid that saturation or overwhelming feeling when I have too many choices.

Biweekly review

Every two days, I review previous lessons. 

When reviewing my notebook and going over the lessons, I can find connections and relationships between key aspects or concepts.

That allows me to recognize key learnings, fix some learnings, and also to identify some meta-learnings.

Meta-learnings

I’ve identified some meta-learnings that make me a happier person than the one before starting this bootcamp.

I think the 80/20 approach is key and I want to keep that approach and use it for other aspects and themes. It works very well for me.

Simplicity: The importance of the simplicity principle. To look for simple but effective solution to a problem.

Building capacity with propuse: What makes sense to solve and put time and effort.

That means to take into account what is possible to build and if it is worth it to be built.

Problem-solving mindset: I think this bootcamp is an opportunity to exercise and develop a problem-solving orientation.

Why it may be a good idea to attend a Web Dev  Bootcamp

During the last 2 years, I’ve been looking for alternatives to learn to program for people with no tech background and starting from zero.

So I’ve checked some online courses, YouTube channels, and long-form blogs posts.

For example, I tried CS50 course and I quit after the third lesson. In my opinion, it’s a great and motivating course but is overwhelming as well.

Or maybe, I’m not ready to take it yet.

Also, I’ve looked at some bootcamps.

I was looking for something with a certain level of intensity but not overwhelming and straightforward.

In my opinion, a good web dev bootcamp is a space where you concentrate time and effort and if you do the work, you’ll see a progression.

Not all bootcamps meet those criteria but I think Flavio’s online Web Dev Bootcamp does.

In Flavio’s web dev bootcamp you get an instructor that has applied his knowledge and experience to structure a well-crafted online bootcamp with an approach, that at least in my case, fits with my way of learning.

After hours of study and exercises in these 2 weeks, I’m starting to see I have some building blocks or Lego pieces which are basic concepts of HTML and CSS, and understand how, for what, and why they work together.

I’m stacking some key building blocks in my journey.