Saying "Stop using feature X" is the wrong way to educate people. Teach both sides of a given feature and let people decide for themselves. Are there better ways to align an element? Sure, probably. But the problem I'm trying to solve is probably not the same as the problem you're trying to solve. Maybe a float works better for me in my project.

Instead of "trusting" it, why not paste it into something like https://regex101.com/ and be sure?

It's not often I comment on Hashnode posts anymore; I think the majority of the articles here are garbage or kids doing homework assignments. But this article relates to me. When I started programming back in 2000 I didn't take it very seriously. I was 20 at the time, worked technical support at an international bank and was content. I was into cars at the time and so started a car forum that took off and succeeded. That website was my gateway into my first programming job. But it took time. That took place over a year; building the community, learning PHP and html, etc... I lived with my parents at the time and so the only major bills I had were a car loan, insurance and cell phone. I didn't need to make money from it. I did it cause it was fun and I loved my car. Fast forward 20 years and I've had many development roles and am currently Director of my team. This 3-6 months goal you have may be short or it may be ambitious. Just because you can read and write in a given language doesn't mean you "know" the language which may be why recruiters or companies are hesitant to hire you. It could be you're really bad at interviewing. It could be you don't have much work to show for your time. It could be anything really. So my advice to you is; go to production. Write something in the language you want to work on; build it and ship it. We have git and github now a days (didn't have those back in 2000) and so that helps to show off work, but get something into production and get people using it. Stay persistent - keep plugging away. Possibly adjust your expectations or goals. I'm a car guy; my dream car is a Lamborghini. I'm also realistic and that's a 400k car + maintenance and insurance. So I aim high and if I end up in the middle (Porsche or BMW) I'll be happy. An internship should be pretty easy to get (I've never done one so not sure how those go) but maybe your aiming for companies that get tons of applicants. Maybe try a smaller company or contribute to a github project you like. IE: get your name out there. Keep working towards the job you want, but be willing to take what you can get in the interim. You're not married to your job. Every job for me has been a stepping stone to the next, preferably with better pay and benefits. That's not to say you shouldn't stay at a company for 2+ years, but make a move when you think you're ready. You'll know when that is. Most important; don't give up. If you really want a career as a developer, persistence is key. My goal has never been to work for google or apple or etc... I hate big companies and prefer smaller mom and pop shops. Good pay can be had anywhere, you just need to look for it. Had a great job a few years ago; all of 12 employees. Not a startup but an amazing boss and great pay and benefits. We made a great product at a great price and that's how we succeeded. Happiness and fulfillment can be found anywhere. Good luck!

Spoiler alert: it is. Passion is not specific to programming. You should be passionate about any job you hold be it programming, dentist, garbage collector, accountant. Passion is a drive to do better; to learn more; to want to find out what's next and pursue it. Why would I go to a doctor or dentist that wasn't passionate about their career? That person probably doesn't care about new techniques or drugs or procedures. If it's just a job to them, how do I know they actually care about my health? Same thing for programming. If you're not passionate about what you're doing, how do I know you have my project in your best interest? That you look at code holistically and try to make it better? It's ok to not enjoy programming. It can be a good pay check and a decent job. But if you don't enjoy it, I'd probably look for a new career. I'd rather hire a passionate junior developer that wants to do a great job and learn more than a non-passionate senior programmer that is calling it in. You don't need to be the best programmer. But you at least need to care about the work that you do and show interest in it. Who would want to hire a developer that isn't otherwise? I've been a web developer for 20 years now. TWENTY. I am not the best Angular developer out there but my job title and experience would say I'm pretty damn good. I am passionate about the work I do; strive to do a great job every day and hit my deadlines and treat my team with respect. Passion to learn and do a good job got me to where I am. Not looking for the next best paycheck.

The gist of your argument (IMO) is that because JS follows "some" similar processes of a compiler (tokenizing, specifically) that it is in fact, compiled. The problem with this argument, as j stated, is that all languages would fall into this and that's not correct. When anything is actually compiled, it's expected to act and operate identically on all hardware and os's it's compiled for. If I write an iOS app in Swift and it's compiled for iOS, I can expect that app to work exactly the same on any platform that can run an iOS app (obviously, different versions of iOS may produce different results but that's getting off topic) VS Chrome has a Javascript engine, Safari has a Javascript engine, Firefox has a .... Javascript engine. And while some of these browsers may use the same engine as a base, this is also why "sometimes" things work fine in Chrome and IE and sometimes they don't. They are all processing the JS as it comes in and "interpreting" it as they're designed to do so. In a compiled JS app - they wouldn't. The code would be executed and the result is the result every time. Another point, going further down this rabbit hole - a compiled language usually means the OS or the machine itself is executing the code directly. If JS was compiled, there would be no reason for the browser to execute and interpret the code. Now you could say Chrome is the "os" in this case and Chrome is executing the compiled code but IMO that's a stretch. There is still an engine looping through and interpreting the code. iOS, MacOS, Windows, Linux, et all are not interpreting compiled code - they're simply executing it.

You shouldn't need @import "~bootstrap/dist/css/bootstrap.css"; or <link rel="stylesheet" href="../node_modules/bootstrap/dist/css/bootstrap.css"> Putting bootstrap.css into angular.json > styles should be enough. You should also initialize jQuery in app.component.ts Because Bootstrap (still) uses jQuery, you should consider using something like https://www.primefaces.org/primeng/ It's based on Bootstrap (loosely) and doesn't require jQuery. Ie: using Bootstrap with Angular isn't ideal now a days.

Can we please stop asking this question? Please? Pick the best tool that a: your team knows and knows well, b: gets the job done, and c: within budget both time and money. If it's React - great! Use that. If it's Angular - use that! Same thing for Vue or whatever else comes down the pipe in the next 50 years. There is never, and will never, be a correct answer to this question.

The problem with these masonry scripts has always been they work great for images but once you try to use it with a div and or tables of data, it completely fails unless theres a fixed width container / children (ie: not responsive) I'd love to see a tutorial on that - I've used dozens of masonry scripts and they never work right for div children

Everyone's capacity to pick up a new skill is going to be different. IMO 20 hours is not enough to be proficient in any language, let alone JS. I would completely ignore a resume that said anything like 20 hours of education. Learning / getting good at a programming language is a life style. You don't need to live and breath it, but you need to work at learning it day in day out. This is why it tends to be easier to learn things on the job. You have a built in 40 hours / week commitment to learn it. Further - learning a language doesn't mean you're good at it. Anyone can rattle off methods and functions built into a language. What makes a good programmer is the ability to take those things you learned and build stuff or talk intelligently about it. When the boss asks "how would you approach X problem" the difference between answers from someone with 20 hours and 10,000 hours of experience will be night and day. Good programmers bring their years of experience with them to a problem / job and 20 or 100 hours just won't cut it. Being a problem solver is so much more important than memorizing the syntax for a language.

In the beginning all we had was photoshop. You'd go through a PSD and cut it up any crazy colors or backgrounds or etc... and save them all to photos and rebuild the grid so to speak using a table with 0 for all spacing or borders or etc... If you were fancy, you'd do it with slices which allowed you to name each slice and save them in 1 shot. Option 2 if you didn't have fancy backgrounds or fancy menu bars - you'd just use the tools you had. Click on a line of text - get the font size, weight, color - into css all that goes. Click on the ruler tool - 18 px from the left, 20 px from the top - into the css all that goes. If someone sent me a PSD now a days, i'd do option 2 - if the site called for it, option 1 also probably. We use Figma - it's nice. Click a design element, get its properties - into the css file it goes. I personally don't let any tool export css for me - I want to pick and choose the properties and build the css file as I think is appropriate - making classes as generic as possible to be re-used elsewhere - so if Figma does that - news to me lol... Not much has changed though - use the tools you have access to, get your measurements and properties and build the html / css appropriately.