Never tried it, and probably never will. Their ad-based business model, which looks like the one that AdBlock Plus fired up, looks rather shady to me.

I personally do not think that Musk is a great personality if seen from the social side, but without doubt he pushed things forward where others failed to provide ideas for the future. He invented PayPal when we were stuck with old money, he started SpaceX to challenge NASA to make space flights more accessible and last but not least Tesla could be seen as responsible for the latest rush in EVs. I can't think of another person, neither Bezos, Nadella and for sure not Mr. Cook, who might come up with the big next thing.

For me hardly any statistics are really helpful. As long as SO does not allow to view results per country or region it's more like "well.. okay, the rest of the world thinks this way". Would be more interesting to get insights for Germany or the EU alone. Also, to be honest, there's not much which changed completely in comparison with last year.

To be honest: use the .com domain as your primary and buy the .dev and .solutions domain too. You can point them to the .com domain with a 302 redirect which preserves SEO rankings. Reserving domain names is a pretty important thing if you ask me: if they are gone it's either impossible or horribly expensive to get them back.

It really depends on what you want to achieve. If you are familiar with Laravel and need in-depth integration with authentication, databases and whatever not, Lumen is a good way to start. If you want to develop really small microservices it may make sense to fire up a index.php and throw some Symfony components in it. They provide basic functionality without much overhead.

If you prefer native apps and develop on macOS, check out Paw . Neither free, nor open source, but a really good application. (Available via Setapp if you have the subscription.)

Absolutely agree. It's really hard to get that fine line between "working hard enough to get the job" and "working too hard so you end up as a wreck". It's understandable that especially young developers have to work more. It's pretty the same for every profession: to start you career you have to learn and work more. But there's that point where you start to damage your health and - no matter which job you have chosen - at that point you should reduce your workload.

Thank you for your response. The problem with using the built-in cache is, that you have to manually implement it for each query. Example: $cache_key = '15_latest_users' ; $cache_duration = 1440 ; $users = Cache::remember($cache_key, $cache_duration, function () { return User::orderBy( 'created_at' , 'DESC' )->take( 15 )->get(); }); The first problem you can see is the cache keys itself. The Rememberable package works by using the hashed SQL statement as the cache key to prevent any collisions with cache keys that may be used elsewhere. Caching database queries manually is very hard.

That's a good questions. The thing is that probably nobody is able to give you a good answer to this. It's more about personal preferences than anything else. I personally like the backend part more, that's why I started my career by building Drupal modules and plugins instead of focusing on HTML and CSS. If you are not sure, try both by building a small(!) app on your own that involves both a backend that handles data and does computational stuff, and an appealing frontend that displays the data. But nothing too complicated but rather more than a To Do app. Wish you much success!

Please do yourself a favor and read the two guides provided by Marco Alka . From my point of view they both provide a solid starting point for your journey. After that, try to outline what you want to achieve because Full Stack Developer man basically mean everything. The most used definition of a full stay dev is one who can provide both "backend" and "frontend" work: backend usually means stuff happening on the server while frontend usually describes stuff happening in the client browser, especially the look and feel. However, this can also mean everything because there are hundreds of programming languages that can be used to build an application. For the backend I refrain from recommending a specific language here because it just does not make any sense. Instead: Search local job offers. You probably want to find a job in your hometown, not on the other side of the world. Take a look at trending/important languages . It makes sense because those usually have a lot of job offers. Maybe you already have some preferences from your student classes. This gives you a good overview on what you could learn. Any further steps depend on your choice. See this choice like the choice for a car: choose a modern one with a rich featureset and you may get further. But you don't drive one car for the rest of your life: You probably will learn another language later. For the frontend I highly recommend to not start with Javascript. There are a lot of evangelists out there who see the face of the world wide web being Javascript alone, which is simply not true. Please do everyone - including yourself - the favor and learn the basics first: HTML and CSS. The web is based on those two technologies and learning both is the first step in becoming a developer who is actually capable of translating a vision, a design, into a webpage. Javascript, to get back to this topic, was made to extend the functionality of HTML and CSS and not the other way round. Nevertheless JS is an important part of the web and can also be used as a backend-language. Learn the basics, learn the language, and not any libraries or frameworks because they come and go. What's important is that you understand how to use the language itself. Everything else will come by itself. :) Feel free to comment if you have any further questions.