I Fell Into the "Bootstrap Trap"

Eric Fortney — Tue, 15 Dec 2020 03:10:53 +0000

Yep... I fell into the "Bootstrap Trap."

What's the "Bootstrap Trap?"

Well, simply put, it's not focusing enough time on learning CSS without the help of frameworks.

The past 5 years I've been dabbling in web development, but never really focused on it and put effort into learning until mid to late 2019. CSS always was the bane of my existence.

That was, until I found Bootstrap and other similar CSS libraries/frameworks. "I get a grid with this? Hell yeah! That will make CSS much easier." And, it did.

Sure, Bootstrap and company are fantastic tools and arguably make CSS easier, or do they? With CSS Flexbox and CSS Grid we now have the ease of use of Bootstrap in native CSS.

Seriously though, don't skimp on learning just plain ole CSS. I did. But now I'm fixing that. The additions (yes, I'm behind 🤷‍♂️) of CSS Grid and Flexbox are gamechangers to me. They are incredibly simple to work with and use.

I actually ENJOY CSS now. I never thought I would be writing those words, but I do.

Why was learning Bootstrap so soon a bad idea?

It was a shortcut, at least that's how I see it now. Bootstrap sure is easy, but it's also incredibly heavy and even reliant on jQuery.

My total package size when using just plain CSS vs using something like Bootstrap is the difference between night and day; especially if you are pairing it with any JS framework/library like React or Vue.

Along with that, it taught me some bad CSS practices. I'm still working to correct these. When learning something new like CSS, our brains absorb all the new information like sponges, whether you retain that information or not. "Oh I'll just add some padding here.... some margin there... hmm... that still doesn't look right."

That might not be 100% Bootstrap's fault, but it didn't help because I skimped on the basics.

How are we supposed to build a strong "building" of knowledge without a firm, sturdy foundation? I found out the hard way that this was NOT the correct way to go about learning something that seems so daunting.

Seriously, don't skimp out on the basics. And this includes learning vanilla JS vs jumping right into frameworks/libraries. React has a steep enough learning curve as it is, why would you make it harder on yourself?

Well, when SHOULD I use/learn Bootstrap?

After you have plain CSS down. No, you don't have to master it (does anybody?), but learn about the commonly used tools and properties in CSS: margin, padding, z-index, Flexbox, Grid, etc. These WILL do what you want. After all, Bootstrap IS CSS, among other things.

Have I mentioned how amazing CSS Grid and Flexbox are? They make CSS so enjoyable to use. Once you get a decent understanding of them, it's so simple, too. If I could, I'd go back in time and give past-Eric and good ole slap to get him straightened out.

Don't make the same mistake I did. Learn CSS. It's difficult, and learning it sucks, but it's so worth it in the long run.

This is my favorite resource for learning or refreshing my memory about CSS Grid, and this is my favorite resource for CSS Flexbox.

What mistakes did you make early on that you would change if you could?

Photo by Pankaj Patel on Unsplash

What It’s Like Being A Newbie Dev

Eric Fortney — Sat, 05 Dec 2020 04:38:39 +0000

It’s not easy being a new Dev. We get this overwhelming feeling of “what in the hell am I supposed to do now?”- at least, I do. What’s the next project? What’s the next thing to learn? Why does everything look so bad?

Well, I’m slowly starting to learn that it does get easier. The more I use React, or Vue, or whatever framework you want to use, the more I understand. It’s almost cliché at this point but, “just dive into projects, you’ll learn” really is true.

The hard part, though, is figuring out what do we make? Another Twitter clone? Another todo app? I’m not sure about y’all, but I didn’t want to go with the same-ole-same-ole apps.

So what did I make?
Well, something I found useful to me. I’m also a photographer so I wanted a website where people could go and see my work, that’s where my portfolio came from. I wanted something fast, easy to add to, and stylish. I would say 2/3 were achieved.

But going along the lines of what to build, think about what you like to do besides coding. For me, I love space, rockets, and Formula 1. So I built a web app that uses the r/SpaceX API to display when the next SpaceX launch is. You can check out that small SPA here.

But that honestly doesn’t help with the never ending question of “am I good enough?”

From my experience, nothing tells you “yes, you are ready.” You will know; you will feel it. You will have a feeling of “Yes, I’m finally ready”

And then you will get rejected, and rejected, and rejected. It sucks. I hate it. I get rejected daily. But I’m not letting it stop me.

It takes minimal effort to apply for jobs. It takes all the effort to keep going. Build more. Learn more. Do more.

It gets easier, but it’s never easy.

What’s your feelings as a newbie? I’d love to hear in the comments!

DEV Community: Eric Fortney

I Fell Into the "Bootstrap Trap"

What's the "Bootstrap Trap?"

Why was learning Bootstrap so soon a bad idea?

Well, when SHOULD I use/learn Bootstrap?

What It’s Like Being A Newbie Dev