Usually, for static content, Github Pages is a solid choice. It's free, fast and is loaded with goodies. If you do modern web app development with JamStack , Github Pages is enough most of the time. For remote procedures, I usually use Zeit / Vercel . They have a free tier and cheap prices, though their product catalog might be lacking at times. Unbezahlte Werbung durch Nennung und Verlinkung von Personen, Produkten, Organisationen oder Unternehmen.

I recommend taking a close look at the docs When setting (saving) objects in the localStorage, the API will always return undefined - you are doing everything all right. Also, it can only store strings, so you first have to serialize your object before storing it. You can use JSON.stringify() for that purpose. When getting (loading) strings from the localStorage, the API will always return a string or null , so you have to check for null and if a value was loaded parse it back to an object. It you turned the object into JSON, you can use JSON.parse() for that. Example of using the localStorage: https://codepen.io/minecrawler/pen/pojYpNE

The most? Hmm, well, I'd say I love how supportive my superiors are. Most of the time, they feel like parents watching my back, making sure I can do what I love, even if that means going to lengths for me - or letting me go. And sometimes, they feel like colleagues, whose job it is to manage me, but they are still people, and they are very down to earth, and I greatly respect them for that. Just at the beginning of this year, our BU was restructured, and I decided that I want to go to the new & dedicated front-end team. Which meant that I had to leave my then current group leader. He helped me transition to the other team and was a great help! I am very happy, and I think having such superiors is just awesome!

Depends on where you start. Are you a pupil or student? Start by creating your own homepage, create websites you think are cool, and once you think you got it take a look at small local businesses. They usually don't have websites or old ones, and you can offer them to create a website for cheap money. While you get some pocket money (a few hundred € or $ a month), they get a site for cheap. When you look for a job, you can use all those websites as reference for professional work experience on your CV, plus you already had to deal with customers, which is invaluable. Customers and stakeholders usually are difficult people to deal with, and the earlier you learn how to handle them, the better. However, if you already have a job and want to change to front-end, it's a bit different. Especially if you have no experience or knowledge at all, you will have to spend quite some after-hours learning. Depending on where you work, you might want to try to talk to your boss or HR department. They will be able to move your headcount to a front-end position without going through an application process. Alternatively, they might try to find a project, which you can use to learn side-by-side with a senior developer who shows you the ropes. If you have to apply at another company to get a front-end position, you should try to build a portfolio. I recommend getting involved with opensource projects. They usually have open user stories of varying difficulty, which you can use to learn and improve yourself while getting feedback from other devs and professionals. Also, you can write your involvement onto your CV, and it will count as the experience you need to score a job.

In general, I'd go for what is most common in the company or what the team is most familiar with. There are a lot of great frameworks out there and each languages has its merits and its PITAs... Hypothetically, if I had to develop a "highly used API" and given the chance to decide on everything and assemble my team accordingly, I would probably go for Rust , because it's an awesome language, very stable and very innovative in the right places. For the framework, I would probably go with actix . It is easy to use and the fastest web framework out there. Alternatively, I might consider Rocket , as it feels similar to Spring (not saying that Spring is good, but it's kind of standard). At the same time, hypothetically, if I had to develop a "less used API" and given the chance to decide on everything and assemble my team accordingly, my choice would definitely be TypeScript. About every cloud provider and their dog provide some kind of NodeJS hosting. All web devs know at least JS, and TS is the better alternative. The only issue is performance and costs. Anything JS is inherently bad at it and while scaling is possible, costs quickly skyrocket compared to alternatives. On the upside, everyone knows JS and it's very easy to kickstart a project. For the framework, I'd use either Express or Loopback , probably double-checking professional support options for both. The industry-alternative would be to go Java with Spring. Most big companies I know about are looking for Spring devs, so you can't really go wrong with it.

I am working mostly on my gaming stuff. Lately, I want to test out a few mechanics and techniques, so while waiting for some basic features in Amethyst, I thought about prototyping things using BabylonJS . However, some advanced things are pretty hard in 3D, so instead I created a 2D dungeon-crawler-like game. I am using Pixi.JS for rendering the game, since it makes working with WebGL a breeze while not being overly opinionated. I easily was able to slap my ECS lib underneath, which is great for the game logic. One thing I learned was that simplified art is a no-no for the average player, but since I am not good at drawing and arts, I decided to try and have my computer procedurally draw for me. That's useful for one of the features in my game, where stats influence the player appearance. It's definitely worth investigating, and 2D is a lot easier than 3D for now, so I can get a feeling for how to do and organize things. I know that there already is at least one paper-doll lib for JS I know of, however I really need to experiment with it myself, and also I did not like some of the concepts... If you are an artist and have some tips on proportions, I would love to hear about them. I am stuck with a study about Miss Korea, which I will have to use otherwise for concrete numbers (and some Manga courses, which usually are hard to translate into numbers) Not much to see, yet, however I am back from vacation (in Japan), so let's see what I can get implemented in the coming weeks 🚀

No, in my current project, we do not have a bug fix day. Personally, I am not a big fan of it, anyway. We work in 3-week-Sprints, so we can estimate our scope and put in a chunk of bugs (sorted by priority) as well. Then, we do soft zero-bug development, which means we try to do bugs first. That's not always possible, because there are too many bugs, and not all of them are all that relevant (like an API endpoint returning 200 instead of 204). So we fix the most important ones, then do features, and if there is time at the end of the Sprint, we do more bugs.

Since I do not assume that this is the most elegant solution I think it's quite a good solution, which will keep a lot of bots out. However, bots are getting better, and such honeypot fields are a rather old concept... Another idea would be to add a Captcha (for example "I am not a robot" verification by Google). On top of that there are algorithms for analyzing a text for emotions and intents, which might help you categorize spam even then. However, let me tell you something: AI is catching up, and even if that weren't bad enough, there are services on the dark web on which humans earn money by solving Captchas (even the fancy Google ones) for bots - so that the bots can still do their thing - or by filling whole forms manually. It's a fraction of a cent per Captcha or form-fill, but that adds up over the hours, and these people are very trained in doing their thing by doing it for hours. Battling spam is like fighting windmills. You start out with a form, and bots will swarm it. You use a honeypot field, however bots might not even use it. You add a Captcha, but somehow the spam still keeps coming your way. You add an intent-detection algorithm, which at least puts spam into a moderation queue, but spam-bot authors aren't dumb, and if your site is an interesting enough target, they will find a way to fool the system. I have seen some such posts even here on Hashnode, which take reference to the specific article... arghh. The solution I propose is to not solve the problem. Currently, JAMStack is one of the most hyped new things in webdev; for a good reason. You do your thing (create/admin a website), and leave the complicated stuff to the experts, who do that as their thing all day. They are also GDPR-compliant, and if you put a link, it's usually not even your problem anymore, because the user leaves your page (briefly) :) This means, instead of putting a form onto your Wordpress page, you might want to put a link to a survey site, or use an embed for one. The survey site will then conduct the voting and feedback taking for you, and use their battle-tested algorithms to fight bots and spam for you. You will receive the results (which then are, GDPR-wise, your problem again) from the other service and can do whatever you need to do with them. Of course, GDPR-wise, you can also check out the other service's options to see if you can trigger the deletion of certain records, which would fill that gap in your control-chain. GDPR, however, is still a very difficult topic, and even many big companies struggle a lot with how to handle (sub-)contractors and data-transfer for processing purposes.

I use both, because each of them has its pros and cons. You should use the best tool for the job, not your personal preference ;)

[x] VanillaJS Once you feel comfortable with it, you will see that all of the above frameworks and libs are just using some kind of pattern, which you can easily apply and decide on a per-project basis which one you need.