I found the rule about absolutely positioned elements interesting given that I often thought their containing block was the closest relatively positioned parent. As outlined in that documentation, though, it's just the closest element that is not statically positioned.
Also, the ability to observe professional athletes in high definition. When I was first getting into tennis, I found it incredibly useful to see the best in the world practicing 4k 60fps [0].
I felt this way when approaching my personal site. I was falling into the Gatsby trap and then realized all I needed were HTML, CSS, and a few JavaScript files. I think you see over-engineered solutions as a result of career driven development and the hype around these libraries/frameworks on forums/social media.
> many people don't understand any better why or how React is good and when it's bad to use...
Your comment was very insightful, but I feel like you've left me on a cliffhanger. I'm someone who got into the industry right when React was reaching enterprise levels, so I missed out on what came before it. I got my job, was told to learn React, and have gone from there.
Is there any way you might be able to expand on the problems you were solving with your declarative approach, why it was useful, and how you think React should be used in modern day web development?
As someone who doesn't play piano, what you were describing reminded me exactly of my typing experience. I'm glad to see you thought the same! You mentioned the 4th and 5th fingers on the keyboard specifically — what is the correct finger placement for those keys relative to what you think most people do?
> Does it? I've worked in React, at enterprise levels, for close to 3 years now. Except for the addition of hooks, there hasn't been a whole lot of churn. React today is still the react of yesteryear, but with extras.
I have been using it since you could only track state in class components, and I personally think it looks drastically different with the evolution of hooks. I interpret components differently than before. The patterns for doing most things has changed, such as the inherent deprecation of the higher order component and render props pattern. I'm not implying that it's bad there have been changes (some are absolutely warranted), but rather explaining how I do believe the library looks different than it did before hooks.
I thought I was going crazy or that my English has gotten worse. Thank you. I initially read this as Ticketmaster going out of business and was shocked.
I experienced this. When I moved, my sloppiness and classiness improved tremendously. However, I've recently started to notice it getting back into its old ways now that I'm more settled. The benefit is that I'm much more aware of it, and am able to recognize it and address it instead of never noticing it to begin with.
This is unrelated to the topic at hand, but your point about the Texas heat led me to another train of thought. It seems that when it comes to temperature extremes, heat is the first to get criticism. But I very rarely hear any complaints about the frigid temperatures in places like Minneapolis, Chicago, or Boston. I'm trying to wrap my head around it. Are humans better situated to deal with colder temperatures than hotter temperatures? Or is it just the simple fact that it is easier to layer up than it is to layer down?
Indeed; native Hacker News UI is my favorite experience on the web when it comes to discussion. I also enjoy the old Reddit stylesheets. Something about these two designs and their predictability is a joy to use. It's ironic since I love developing front end UI, yet the experiences I enjoy using more are often the most trivial.
I know you asked for a course, but I cannot recommend MDN's Learn CSS section enough [0]. It's long, but it was the only resource that got me over my CSS imposter syndrome. They go over so many great principles and have wonderful examples. I'm a huge advocate of tutorial videos, so I was surprised at how helpful I found their documentation.
My biggest tip of advice for anyone dipping into CSS is to focus on _why_ CSS is behaving the way it is instead of memorizing the different properties and selectors. Some principles in CSS won't ever go away, and they will even explain how the newer features that "settled down" CSS work and make then even easier to use.
I really enjoyed the testing library when I used it. I recently came back to it and felt like they removed a lot of the documentation that I liked about the library. I'm not quite sure why they did, but it was very helpful to see their examples for integrating with common third party libraries.
That’s a great point. And upon reflection, I realized the timeframe is unique to the person. Maybe it’s two weeks for some people, and maybe it’s a year for others. I think the common denominator, though, is that you’ll know when you’re getting that passion back, whenever it may be.
I'm going to keep it very simple; tell yourself you're not going to program for two whole weeks. You may feel uncomfortable letting yourself go, but it will give you a much needed break and you will come back more energized.
Speaking a bit more anecdotally, what worked for me when I facing a similar problem was shutting off the computer immediately after work and allowing myself to relax and prioritize other hobbies. I was watching more documentaries and vlogs, as well as going outside and hiking on the weekends as opposed to being bunkered down at my desk. This opened my eyes to what there really is in life, and I now view programming almost completely differently as a result, but in a sustainable, healthy way. I slowly built my passion back up, but not as compulsively as before. I don't program just to program anymore, which actually makes me more efficient.
I know your struggle and I wish you the best. Accept you need time off and it will get so much better.
You are exactly right about the hobby and niche interests. On the other hand, the larger subreddits that represent groups of people (such as a city, sports team, university, etc.) will have that echo chamber effect.
Does anybody have a counter argument for just using macOS notes if you exclusively use Apple products? They sync nicely with my devices and make note taking pretty simple for me.
This sounds like a good idea if you are on top of things. I was going to push back by saying it almost sounds like a chore, but a lot of the reason notes are jotted down is in fact to learn. So this process makes a lot of sense in retrospect.
I was playing the note chasing app game, too. I eventually settled on the native iOS/macOS notes. I like it because I don't get paralyzed by trying to perfect the organization of my notes, and it syncs across my devices as expected.
I didn't think I had any other interests other than programming. I felt like I had nothing else. One day, I was inspired to go hiking. Ever since, my weekends changed from sitting on a computer, doing something I already did at work, to exploration and being on my feet.
Go try something new. If it clicks, great. If it doesn't, I'm sure there is something else you'll find, too. Just get out of your comfort zone.
In hindsight, I think one of the smartest decisions I made for myself was to first try coffee black. Since I didn't know any better, it was extremely easy to commit to it, and I am appreciative of it today. I wish I could influence more people to do it at their age, because I think a lot of people would appreciate it when they're older.
> it takes time for the chemical reactions in your body to tell you you are full
This is why I suppose I don't enjoy eating when I am "starving" as we like to say when we haven't eaten in a while. I am so hungry that I can't even enjoy the meal because the hunger pangs I am feeling don't subdue until I am practically done with the meal, and sometimes, even afterwards.