In regards to "Big Interfaces make weaker Abstractions", I disagree with your example - you have to balance it with clean code. "toHex" and "toOct" methods make more sense and is more readable than a signature of "to(value, radix)". The former doesn't require knowledge of the method's signature, the latter does to know that the second value is what base you're converting the number to. However, I do agree with the point of the section.

Yep! And that makes sense. Really the biggest benefit to Bootstrap are the grid system and the built in components, like modals and that ilk.

I would be willing to go with a on-site programming interview, whiteboard questions (I think they're useful to decode how someone thinks), take home questions that last for an hour, and take home quizzes. I'm not willing to do take home tests that last for hour or more, or creating and giving presentations when that is not part of the job description. Also going on site more than once. Once is easy to do, multiple times is harder. I will suffer hanker rank if it doesn't take more than an hour of my time. When sending in this one job application takes a whole day and then I have to go through a five round interview process, that is hopeless.

I would not listen to that, but I'm not a big fan of ASMR to begin with. I find it creepy and hard to listen to.

If find separate declarations easier to read. I knew someone who would put them all on one line: let a = 1, b = 3, x = 5, y = 10 etc...

Hello! I'm Lucy from Texas. I am a full stack developer. I appreciate a community like this for me to continue learning. :)

Interesting article. My thoughts is that Bootstrap used to help a lot, before the days of css grid and flexbox. I still use it for quick prototypes, although for a project that will go to production and seen by many, I'll probably use css grid.