Hi Thomas, Tailwind is indeed a wrapper (I prefer the term framework at that point because it adds value not just simplify), but also takes in customisation aspects at build time (which makes generated inline-css totally legit to use, since it is totally dynamic with the generated classes/variables ...). It also offers the variants part (the hover:text-white for example) which is easy to read/use. Finally, as I am saying in the article, it offers the possibility for a standard across projects and companies. That's where the biggest strength is, like any framework that becomes popular.

I like the approach as well, but from a purely logistical perspective, mixing JS and CSS might create more bottlenecks when working with designers/integrators that only familiar with HTML/CSS. The CSS-in-JS approach is also tricker to organise properly in my opinion ! I overall prefer to separate the two. On the other hands, some developers will find it much more convenient to work with an all-in-one solution 🙂

The answer is that your component doesn't have a listener to be notified of an update. What you need to understand is that react updates components in 2 situations : The component props have changed The component state changed Your component `App` right now neither update the store or receive different props. Here is what is happening to your application right now : App is mounted App calls `getState()` App mounts `Counter` End You actually got close to the answer by calling `store.subscribe` ! I suggest you think a bit more by calling it into your component `App`, and do some stuff there and see if you can find out a way to notify `App` that your store has changed, so it need to re-render. I also suggest you, once you're familiar with that design pattern to take a look at react-redux , which is the way most people bind their Redux store to their react application right now. It'll basically do all the work you need to do right now for you ! Keep up !

It is true I didn't thought to add the scope description. Thanks for completing my answer :)

Aside from reading docs and tutorials (there is good resources down below in the others comments already). What arrow functions are in simple terms Let's try to explain it simply : the arrow functions are so to say a shortcut to write functions more efficiently and make them more simple to read, making the code less overcharged. function example (params ...) {} const example = (params ...) => {} Those two ways of writing functions are doing the exact same thing, but you're gonna tell me : "It's not much shorter is it ?" That's because arrow functions have been made for more "on the go" usages. Most of their strength come from the fact that you can abstract some of the function keywords when using an arrow function. If you want your function to return something they take in parameter for example, here is the 3 ways you can write that : function getFirstElem (array) { return array [ 0 ]; } const getFirstElem = array => { return array [ 0 ]; } const getFirstElem = array => array [ 0 ] Beginning to see the interest ? When your function is a pure function (which means there is no side effects, the return value is only based on the input of the function. Check-out functional programming here ), you can skip the curly braces and just write your return value (or with parentheses if you need to wrap some operations together or return an object for example). You can also (which is not as important) skip the parentheses around the parameters when there is only one of them. When to use them : Pretty much all the time ? Technically you can write all your code with arrow functions if it is your wish, depends on what norms you setup for your code. As I said earlier, they come in particularly handy in case you want to write pure functions ! Hope it make your mind a bit clearer about those lovely functions !

Having done quite a lot of internships myself, and tried multiple types of companies and teams, I would definitely recommend you to try finding an internship in a small size company , where you'll be challenged on multiple skills, and have less risk to be used as a disposable asset. The best internships I did were in young startups, where you can and have to be as independent as you can . The tech stack you should go for is your decision only , I don't see the point of choosing something you dislike ! Though, if you don't know where to start, web-development is the most easy kind of internship to find (and always good to have a try if you don't know about it), or Java development is also pretty common for interns. In any case, assure yourself that the company hiring you for an internship states a clear goal for you during your time there, with some milestones for example. Lastly, try to get in touch and build a strong relationship with an internship referent. Having a mentor in a company is important, it is even more as an intern. Hope that helps !

First, get yourself introduced to the language syntax and mechanisms by doing the tutorial you can find on the language website here . It is very concise, and it'll give you a very good overview of what you can achieve with Golang. Once you are okay with that, you can jump right in and start experimenting. Of course, you can also still checkout more docs and tutorials if you're the study type ! (Checkout https://github.com/golang/go/wiki/Learn, you should find something). Since I suppose you're gonna want to code an API, I would definitely recommend to begin by looking at 2 things. They are at the core of any web-service API. Any HTTP Framework for setting up a basic API. You can check Gin-Gonic , which is the most popular, but you can also check Iris , Mux or any other you find attracting ! Any ORM you like to interact with your database(s). The choice is large here, I personally use Gorm (it has bindings for most popular SQL databases), but you can also checkout mGo if you use mongoDB for example. Happy coding !

They do offer translations on most public and road signs, and indeed, the Korean alphabet is the most simple alphabet you'll find in Asia, even more simple than Katakana/Hiragana in Japanese. The grammar is almost identical to Japanese, and Chinese, they all have a common root (which is Chinese). The pronunciation though, is quite harder than Japanese (for a French like me at least).

I lived in South Korea, people there speak quite good English, and I never really had any major problem because of my very average Korean. On the other hand, Koreans aren't confident about speaking English (the Asian confidence-lacking syndrome), and it was sometimes super hard to get in touch if you don't start by speaking Korean a bit to make them feel like to try English.

From my own experience living in Asia, it is absolutely not a problem. I am not a native English speaker myself, and neither are the people over there. Actually, in some cases, (Japan in mind) they even prefer you speaking the local language. That said, it is important to have a good level of English, and some capabilities in the local language will be a big plus.