I want to expand on #2 - the right tool for the job might not be a flashy new library/framework/tool, but it might be one you don't already know. You shouldn't

I want to expand on #2 - the right tool for the job might not be a flashy new library/framework/tool, but it might be one you don't already know. You shouldn't pick new technology because it's new, but you should have a surface-level understanding of what lots of technology does so you might be able to connect the dots with your use-case and explore something foreign in depth. Equally risky to using flashy tools is over-reliance on the old tools you know, which may not be best suited to the task.