DEV Community: Christopher Arnold

I'm such a noob. node js frustration

Christopher Arnold — Thu, 06 Oct 2022 19:32:17 +0000

just a quick vent session
update on my progress: I've been at this learning journey for about a year now. i got a solid handle on html, css, and basic vanilla js. I decided to start a react course today, and just setting up the environment threw me for a major loop.

Two steps forward one step back
I had already installed node and implemented it with tailwind css on a few projects. However, when trying to use it for a react environment, i run in to so many separate errors. So instead of starting with react components, in the next few days i will have to gain a better understanding of how node works, and how to use it with as few modules as possible.

While in the midst of tutorial hell, I re-downloaded node. It caused several errors and i was unable to follow my tutorial because the tutorial is from the context of someone who doesn't have node to begin with. I love js. Js is logical. Js is my friend. The terminal, and the way libraries work behind the scenes is like a potion to me. Just impliment it get it running, and don't think about how it works. a single threaded approach on learning works best for me. I've come to realize the importance of deciding the best thing to be learning at a given moment. An underlying goal is to develop the ability to intuitively decide when to dig deeper into a subject I'm on, when to back track, and when to integrate the next thing I need to learn.

Node has put me at another all too important crossroad, and I think its best for the time being to get a low-level understanding of how it works, and how to use it with multiple projects in the most efficient way possible.

Ultimately, becoming a better programmer is the goal, but i can make far more progress in the long term by growing as a learner.

I'm just logging my frustrations here in the meantime so I can later laugh at them a few years from now.

Learning how to learn JS

Christopher Arnold — Tue, 20 Sep 2022 06:51:54 +0000

Just a quick vent session after hitting my first(of many) wall with JavaScript

Rewind two weeks ago, I started taking a highly rated js course on Udemy. This is my first programming language so everything covered has been 100% new information. Initially I was able to retain information, and logic quickly(see previous post) When a coding challenge came up I felt prepared. I knew what to do step by step without assistance. After solving the challenge, I was even able to expand on it, or find a more efficient way of doing it, etc.....

until now
Section 2 covering the basics was going pretty smooth, or so it seemed... It tackled basic function declarations, expressions & arrows, how to call a function within a function, arrays, objects, for/ while loops. I could still internalize and understand the lessons. I could practice the methods afterwards and get things to work. however, when facing my challenge at the end of the section I became humbled beyond expectation. I realized quickly that I could not do any of the things I had just "learned".

I suppose there is a difference between learning and recalling
When faced with so much information, its hard to decide when to move on, and when to double down on a concept. I think back on learning CSS and time wasted memorizing things that I can look up in 5 seconds. It also seems apparent that Professional developers are constantly looking things up. It also seems to be true that people who are great at anything have a seep understanding of the fundamentals of what they do. That being said I'll probably just go back over anything in the lesson that I don't recall, hammer them down to the point of execution without assistance, and move on. It's just difficult because the desire to move on to the next thing is beckoning.

The best way to learn for me
The moment I began rapidly learning CSS was when I began building things of my own with it. The relentless will to try over and over to make something work has been my most powerful learning tool. The rub with JS is lacking enough knowledge to really build anything. I have only spent brief periods in dreaded tutorial hell, only to resurface unscathed. Now walking a plank over the flames, the desire to move on to a phase when I can build is growing by the day. Tutorials don't bore me per se. However, there's just another level of excitement when bringing an idea from my brain into code, struggling, and the sweet reward of seeing it work in real time.

Why is it easier for me learning beginner JS than learning beginner CSS? wow

Christopher Arnold — Tue, 13 Sep 2022 07:40:01 +0000

Learning CSS initially....
I started on freecodecamp if i remember correctly, I started with the basics of positioning, responsiveness, styling, classes etc. I remember thinking that I was retaining the information as I just cruised along through the curriculum.
That was until I tried to build a basic landing page, and immediately felt as if I were trying to write a book in Hebrew.. Every time something didn't work, I would spend precious hours trying to understand it. These were mostly issues relating to responsiveness and selectors..

After "building" two or three projects that were busted beyond repair, I eventually found my way. Its probably not good to compare your progress to others, but after hearing about how "quickly" people seemed to be cruising through HTML and CSS, I couldn't help but think I was just a slower learner. Eventually an understanding was formed, and Tailwind was added to my toolbelt.

I've spent around 10 hours learning vanilla JS so far, and it has been a lot more fun && easier to retain.

I've read quite a bit about the frustration and confusion people commonly go through with learning JS. I thought this would be an inevitable initial phase that I would have to push through. i was wrong, and i don't quite know why. I started with "The Complete JavaScript Course 2022: From Zero to Expert!" a Udemy course by Jonas Shmedtmann. It has been nothing but non stop fun.

Cruising through his examples, I follow along with my editor, making sure to practice in between lessons to be assured that I'm learning the concepts. He's given me three simple coding challenges so far, and I retained the logic far better than i ever could have with CSS. Granted, it is early and frustration certainly looms on the horizon. It's kind of like the calm before the storm when my perpetually violent cat is finally purring and allowing me to pet her :D.

So what is making it easier for me to learn JS than anything else I've had to learn in my journey so far?..
Just a quick list of potential reasons:

Learning CSS taught me how to be a better learner. I tried so many resources, and learning styles that I was able to find methods that work best for me.
The Complete JavaScript Course 2022: From Zero to Expert is laid out in such a way that you begin by slowly learning basic concepts so you don't just get thrown into the deep end kicking your feet while drowning. Jonas takes his time and explains not just the code, but the logic behind it in a way that the logic is intuitive enough that it requires less specific memorization. That differs vastly from me trying to learn CSS properties, and the meanings behind them. Just went in one ear and out of the other!
JS is more intuitive for me because of its logical nature. Once I understand for example basic boolean logic, I can quickly anticipate how the code will be computed. Wheras with CSS i was often using more of a trial and error approach. I remember being like ,"I'll try switching it to position relative and see if it works" when something in JS isn't working for me "so far" I know its probably me misunderstanding the logic, or something to do with syntax.

4.) JS is more fun (for me at least). I remember making a responsive nav work in CSS for the first time and just being happy that i was done with it so i could move on to the next thing. the prospect of trying to do it agin but with a hamburger menu was likened to eating glass, nty lets move on.

Earlier today I passed a simple coding challenge, and was hit with a sheer sense of excitement that I got this little if else comparison with && || operators to work. The way my brain works, it began willingly pondering so many different use cases for this simple logical pattern leaving me hungry for more.

I know JS will not be easy once i make more progress
I'll probably be humbled in the very near future, but once I get through the next hurdle I'll still be hit with that "AHA" moment that leaves me craving more. Please feel free to comment on my impressions or the hurdles that lie ahead. Thanks for following and the next post will probably be about me coming back down to earth..

Early CSS tailwind snags

Christopher Arnold — Thu, 25 Aug 2022 07:14:01 +0000

Just a quick recap on my experience with tailwind so far

Before starting tailwind I spent quite a bit of time with trying to understand basic css/scss. I was able to do animations, transitions, make a basic responsive landing page, and style elements efficiently.

When I began using tailwind I was smitten right away, by the ability to prototype designs so quickly. I still love the power of tailwind which i have yet to fully tap into. I did however, naively underestimate the bar to entry.

I'm currently building a landing page with Tailwind, and here are some pros and cons I've come across so far. I'll just stick to the ones I don't see mentioned frequently in threads:

I love how easy it is to set breakpoints at different screen sizes.
It is fascinating how some things like element styling, positioning, transitions, are able to be done so much more efficiently especially in smaller chunks. Yet i spend much longer being hung up on the effects of sm,md sized classes and the like. Maybe i should try a mobile first route initially...
With pure CSS I grew accustomed to plugging in a custom .btn class for a button and being done with it. the tradeoff being obviously it was a pain starting out building, and organizing the classes.
It has been easier to efficiently position items where I want them to be for either mobile, or full screen sizes However, I get hung up on the nuances of making either of them responsive. Sticking with it seems to be the better option long-term because it's not like media queries were the most expedient. I know I'll probably get more fluid soon, and be grateful for the persistence.

It's a beautiful lesson to learn, not getting to comfortable in my ways especially in a trade that's perpetually evolving in some ways.

Learning the hard way to understand how the fundamentals work, but not allowing myself to get too comfortable doing things one given way seems to be a prudential route.

First impression of TailwindCSS. How much CSS should I know?

Christopher Arnold — Tue, 09 Aug 2022 02:57:44 +0000

After a 6 month Dive into CSS/SCSS, Tailwind is a godsend.

Back when i started with CSS, I made a goal not to move on to anything else until I had a well-rounded understanding of how it really works. I spent time learning complex selectors, flexbox, box-model, animations, units, containers, etc. Had I not made the investment, I don't think i could use or appreciate Tailwind this much on first impression.

After learning how to style and make individual sections responsive I (foolishly) began building my first portfolio project with CSS. Architecture, and the need to build so many custom classes was such a time drain.

Luckily a buddy of mine told me that i could probably get a grasp on tailwind, implement it, and build my project more quickly than continuing with just pure css. Immediately, I was concerned that I wouldn't be able to build on my CSS knowledge while using it. My worries were put to rest this evening when I saw that I was still able to create and integrate my own css along side their massive library. I've only spent a few days with it, but it's like there are new conveniences around each corner. It's like spring time after a long winter.

I wouldn't recommend starting tailwind unless you have a solid grasp on CSS.
As you will most likely hit unneccessary stumbling blocks.
On a side note I truly wonder how many people take the time to understand css early, and if it was the best use of my time. I guess time will tell. I'm just alarmed at how often i hear mention of people only spending a week, or month with CSS, and declare that they have "Learned it". I can't say I blame them. I could have 5 months of JS under my belt by now. On that same token, taking that time taught me how to be a better learner. I'm hoping it all pans out when the JS headaches begin...

Keep trying until you get it

Christopher Arnold — Thu, 04 Aug 2022 01:25:35 +0000

I felt the need to come here and make a post because the most incredible breakthrough just happened for me. I started building my first portfolio project(only HTML & SASS) about three weeks ago.

I did my basic reset and made a basic animation nav bar in the first hour, so I was flying pretty high. Then I ran into a set-back using flex-box for the hero section. The h1, and paragraph in the first column were shrunk vertically and it frustrated me to no end. I thought this would be a quick 5 minute fix.

I went over my flex-box course thinking it had to do with a property I was mis-using, tried everything I could think of over the last three weeks. Tonight I saw that I had the line-height set to 1.2rem for h1 elements instead of just 1.2. Fixed it right up and now the landing page is almost complete.

It was immensely frustrating, but even more rewarding.
Never give up.