Hey Adam!

If you don't mind, for inclusion reasons I'll answer your questions in English:

• There are no plans to deprecate XMLHttpRequest as this would straight up break the web
• To be honest the difference between a web app and a webpage is rather blurry these days. Usually a webpage is something more static (like a blog, where you mostly read the content of the side) and a web app is an app built inside of the browser (Github is an excellent example)
• Take a look at Netlify, although there's nothing wrong with building stuff on Wordpress, although Wordpress is not "cool" these days, it's absolutely, definitely a valid solution for building sites
• If you're still studying I'd like to say that IMO English is the most important language in all of programming. What I mean by that is the vast majority of programming tutorials/courses/articles etc. are in English and since you're a student in Poland I'd 100% recommend you focus on that.

Don't disregard other classes of course :)

When it comes to career path for you - honestly, the world is changing so fast that I don't want to suggest you anything. The tech you may end up working on in 2028 may not exist yet 😅

Hey Bolaji! No problem, thanks for having me!

Like I said in the previous reply - I actually have a whole post about this very topic! dev.to/tlakomy/what-i-wished-someone-told-me-abou…

Let me quote the relevant part:

"Do not give up. It's highly unlikely that you will get accepted by the first conference you submit your talk to. Or the fifth.

Start with local community events. They're easier to get to than major conferences and you'll get your first experiences as a public speaker in a more comfortable setting. Those kinds of events are often recorded, which is a valuable addition to your CFP. In addition, give a talk at a knowledge sharing event at work. Next up - speaking at a conference.

At this stage, you most likely want to apply to as many events as you can (but don't send a CSS Grid talk proposal to a .NET conference). Be prepared to receive lots of "unfortunately your talk was not selected for X" emails. Or no feedback at all.

Keep on rocking."

Thanks for this amazing insight Tomasz Łakomy

I'd say that every frontend engineer should keep their eyes open for new tech but I wouldn't say that everyone needs to learn AWS.

There was a very similar question above so let me just reuse the answer (DRY, hah!):

AWS (and cloud in general) are going to become more and more important for developers but I don't believe that engineers have to learn AWS. My advice is to always keep your eyes open for new technologies but don't learn things just because they're trending - but once you'll have a use case for AWS, then by all means go for it! You can start here: egghead.io/playlists/learn-aws-lambda-from-scratc…

Hey Jasbindar!

I'm (obviously) biased but egghead.io (where I've published over 100 lessons already) is an absolutely excellent site with huge number of JavaScript (but not only!) lessons/courses.

I've written a bit with my history with egghead here, let me quote the relevant part:

"My story with egghead.io started back in late 2015. I got an offer from this shiny new company that was interested in hiring me, so that was neat.

The problem was that a shiny new company had a shiny new stack (at the time) - ES6, React, Flux, webpack. It was fair to assume that I'd have to know those things in order to pass the interview.

You see, the problem was that my stack at work was Backbone/jQuery/Grunt and I haven't even heard of React back then (when I did, I thought that JSX was the worst idea since pinapple on a pizza).

Getting an egghead subscription allowed me to level up as a developer in a month (that was tough, I don't even want to remember how many hours I've spent each day watching lessons and courses)."

This article also contains LOTS of resources to choose from: medium.com/@crofty.land/highly-recommended-sites-…

When it comes to goals - I'd say it's absolutely up to you! Building a project from scratch is an excellent way to learn and grow by the way, because that allows you to try out the programming theory in practice.

Hey slim, thanks - those are great questions! Let me go through them one by one:

1 - If I had to choose - it's better to write tests for those larger, more complicated components (for instance - containers rendering decent chunk of the application logic). It's more difficult but it'll also give you more confidence that your app works as intended and there are no obvious bugs.

Chasing 100% coverage IMHO is not necessary - not only it'll be a huge effort but also may not provide you with the confidence you'd like if your tests are validating the implementation instead of behaviour.

Not every component needs tests - small components with little-to-no-logic (like wrappers that only render their children wrapper in a div or something) don't really need tests.

In general - focus on testing things that give you the most value.

2 - I actually have a post about this! dev.to/tlakomy/what-i-ve-learned-about-testing-re… In general - focus on testing the behaviour of your app and not its implementation. You should be able to refactor your code without breaking the tests and make sure that the most important flows of your application are well tested.

3 - AWS (and cloud in general) are going to become more and more important for developers but I don't believe that engineers have to learn AWS. My advice is to always keep your eyes open for new technologies but don't learn things just because they're trending - but once you'll have a use case for AWS, then by all means go for it! You can start here: egghead.io/playlists/learn-aws-lambda-from-scratc…

4 - Ha, I also have a whole post about this! dev.to/tlakomy/what-i-wished-someone-told-me-abou…

But I'd like to emphasise one thing that you touched upon.

You ABSOLUTELY DON'T NEED to be a well known developer or work for a large, fancy tech company in order to start speaking at conferences. When I decided that I'd like to speak at conferences outside of my country (Poland), I had like 100 followers on Twitter, nobody knew who I was but I kept grinding.

In 2017 I submitted more CFPs than I can remember but I got a chance to speak at React Day Verona 2017 in Italy and afterwards I got a tremendous opportunity of speaking at many more international conferences which is a fantastic experience, I highly recommend that.

Hey Amit!

That's a good question and one that many developers are interested in - "how do I land my first job as a developer?"

Unfortunately this is not easy - there's lots of aspiring developers so the competition is rather fierce.

While I haven't applied for a first job for a while, I can definitely say that side projects help a lot. When I'm interviewing someone for a junior frontend engineer position it's much easier for me if I have some projects to take a look at. Not everything will come up during the interview so it's great to have something prepared to showcase your skills!

When it comes to coding rounds during the interview I'd say - it depends. Every company is different but I'd personally definitely include a coding round in a junior frontend engineer interview. The thing I tend to ask are small exercises that don't take too long to implement but allow me to have opportunities for discussion about JavaScript with the person I'm interviewing.

In general I can say that the vast majority of frontend interviews focus on assessing the knowledge of JavaScript itself so focus on that while preparing for an interview.

When it comes to preparing for coding round, check out code.devtools.tech by a friend of mine - Yomesh Gupta.

Good luck!

Great question!

To be fair - I don't have such a list 😅

From my experience every dev has a slightly different way of learning - I learn the best by watching videos (and experimenting/teaching afterwards), some prefer going through tutorials, reading articles and of course - reading books.

Personally I tend to read non-technical non-fiction books, growing as a person helps me grow as an engineer as well. Some of my favorites I've read in the last year or two:

• "Sapiens"
• "Extreme Ownership"
• "How to Win Friends and Influence People" - this is a terrible title but I cannot recommend this book enough
• "Radical Candor"
• "Incognito: The Secret Lives of the Brain"

When it comes to JavaScript recommendations, I've reached out to folks on Twitter and they responded with some excellent books:

twitter.com/tlakomy/status/1249664985787240449