Well, bash script actually uses sam-build and sam-deploy if you look at it. However, it does a few other things too. Mostly, I used json-refs to be able to split template into smaller (managable) files AND also optimize yaml for API Gateway's DefinitionBody. $ref there can only be used ina few places and with json-refs I can use it anywhere, making my definition body really small and easy to write/extend. Second reason is to make it easier to include AWS build/deploy into main build/deploy script that runs the same for both frontend (Webpack) and backend (AWS). And all that for different stages. It seemed much cleaner to separate the two instead of using sam-build in main build script.

I don't see why not. After over 30 years in development, it feels only natural that you expand your field of expertise to different areas, often at the same time. Backend, frontend, even wider.

Codility.com has a nice practical lessons with pdf explanations of different algorythms for each lesson

mc

I don't know many 5 year old beginner developers so your Q is a bit contradictory :) So I'll try to explain it like explaining to a beginner developer. By beginner, I expect at least to know what global variables, modular architecture and scope are. Since this beginner doesn't really know what state is (thus also what state management is), I'd like to compare MobX to a fancy global variable(s). Every module in your app has some properties that often need to be visible (modifyable?) to other modules in your app. Some really really novice developers might make it work with global variables and be happy. It will take them some more studying to learn it's not a good idea. Even then, some might try to pass variables/properties between modules, only to find out it becomes unmanageable mess prety soon. MobX to the help! Instead of storing it to global variables, or passing it all around the placae, you can use MobxX to store (manage) it. Then, MobX will do so much more than just keep it accessible to other modules, it can execute some actions (calculations) to them, let your modules know as soon as some property changes, etc. While MobX is just another state management tool, in my opinion it's the best one to compare to ease of understanding global variables. Redux is a state management tool too, but I wouldn't use this story to describe it. That's why I like MobX. It really almost seamlessly integrates into your code, like it's not even there, like you're dealing with some global variable and it just works. Of course, sooner or later you'll have to dig in and understand listeners, actions, etc. and then this comparison will become technically incorrect, which it is.

Can yoi tell me whats your field in frontend and experience?

I cannot talk about whole Balkans, but for Croatia only. Id say its noy difficult to find a job here in IT, especially if youre good. Average IT salaries are about double compared to contry average salary. Foreign companies have their IT centers here too, like Siemens, Ericsson, etc. So I'd say there is a deficit of IT workers here just like in most other EU countries. I think your only problem might be a working permit if you're from BiH. Since you're not a EU member yet Im pretty sure you can not get it easily.

In general I dont like abstraction over standard technologies. That's why I dont like ruby, sass, why I prefer pure Javascript compared to Typescript, etc. At first it sounds like an improvement, but then that abstraction leads to forgetting the base knowledge and things change in time. Both base technologies and abstractions, and then it leads to funny situations. That said, among those non-abstracted template engines I prefer handlebars for its simplicity and readability

It is a bit offtopic maybe, but lately I use neither. Amazon Cognito service makes life much easier

Sinclair ZX Spectrum BASIC in 1986