u/var_ya

Thank you!

Thanks, I will check it out.

Boost on technologies and frameworks on say last 2 years would be very useful. I just want it in more organised way than regular self-studying (which I do all the time anyway). I liked the idea of bootcamps and want to participate but I am already a senior developer and most of the available courses are not relevant :-(

I recently tried this package to get PDF viewer on our documentation website. We used to share our monthly presentations as just links. Now we can show them in browser on the very pages of the website. Worked pretty well.

I use styled-components and I love them! If you are interested in code, this is an open repo with my personal website on Gatsby https://github.com/varya/varya.github.com

I would not use flags for a language switcher. English language is not only spoken in Britan whose flag you are using. I think it would be more correct to use language codes which are "en" for English and "it" for Italian.

If the input is under your control and you are building a static website with Gatsby, you don't need to worry. Otherwise, you can read this https://dev.to/jam3/how-to-prevent-xss-attacks-when-using-dangerouslysetinnerhtml-in-react-1464

Depends on what they mean by "BEM". The article refers to class names, this is definitely not so much needed nowadays when we have a lot of nice CSS-in-JS solutions. But if by "BEM" you mean structural way of thinking about UI elements, it is 100% applicable to any technology. For example, in our team we are following BEM principles when naming CSS variables.

I think you should ask at Stackoverflow, it is a better place for cross topic questions. When posting there, it is good to provide code samples so that others better understand what you mean.

Actually it has ES6 support already. You can enable it with "esnext" option through config.

https://twitter.com/jscs_dev/status/565866815071723520

Not at all. It is supported by almost all the modern browsers http://caniuse.com/#feat=object-fit

Browsers can auto-update now, this makes things much faster than in the last decade :-)

I know how to use cron, thank you :-)

Self-evaluating anonymous functions are needed to create a scope. I guess whose who write them needed the scope.

When maintaining, new code can affect your module. So, before you start to develop the project again, it's good to make such TODOs first. However the best practise would be write tests for a module before it is released.

This site is for common contribution. Thus, if you've spotted a misspelling, you are very welocme to send a pull request with corrections. There is a link after the article text to provide the changes.