Hello!

My name is Andreas and I've been working as a software developer for 5 years (approximately 😁).

I'd like to discuss one tool that many developers neglect and that many new developers just don't guess about.

It's the flow chart and we use them to program our logic properly.

This piece of advice will be pretty short. But I believe it's very useful!

Did you know you can save an element as a global variable? Yes, you have tons of elements on your webpage and you can access them by name. Temporarily name like "temp5" but it's okay because you can rename it!

Let's start.

I see people around me (I'm working as a remote code mentor so "around" is used rather literally but anyway 😁) ask this question over and over again "Which language should I learn? How to prefer one language over another one? What if I'm wrong?" 

So after hearing this question approximately 1,000, 500 times I decided to write some manual that visuall helps you to decide which language to prefer. 

But first, let me answer the question "What if I'm wrong and chose a language that is not right for me?" My answer is pretty simple: "Even if so, nothing bad happens." Why? Because every time when you learn some programming language, it gives you the global programming experience and every next language or framework will be easier to learn. When I started my programming journey one of my first programming languages was a Visual Basic I used for the "visual database system" by Microsoft called Access. Do I use it now? Nope. Was it helpful? Very much! Because learning it gave me:

If you are a beginner web developer, you probably know that browsers have so-called developer tools that allow extensive debugging of any code (running in the browser itself). The breakpoints are one such feature that can be just a lifesaver (well, maybe not a lifesaver, but a timesaver, for sure!).

How to set the breakpoint

Open the dev tools (F12), then click the Sources tab, and on the left open the file you want to debug

Today we discuss this simple but very effective method that you can use when you are stuck with something and don't know the source of the problem.

Imagine: you wrote a big chunk of code without verifying it works. I never recommend doing that, instead, I would always move on doing really small steps.

But anyway, something is broken in your code and you don't know what it is.

The point of this method is you comment on all your new code to return it to the previous state when it's working. 

Hello everyone,

I decided to write a series of short posts revealing the dirty truth about how professional software developers debug the code that you could do it to!

We will review how to:

• find the source of a problem
• identify its nature
• fix it!...

If you want to change your JavaScript skills drastically, I highly recommend this book. The name may be a bit confusing: someone can think about usual design patterns (well, those, you know from the "gang of 4" like factory or decorator) but actually, it's rather about the patterns you can face in JS to wide extent: consider a pattern as a piece of code, or approach that can be reused again and again (and it's good) and an anti-pattern is an approach that it's better to avoid (you will find the classical design patterns here too).

Stefan starts with the basics of JavaScript and then dives deeper and deeper that at some point you start forgetting it's just about a "simple" programming language that runs in a browser!

If you are a web developer, you look at the DOM objects pretty often. To see them, we just right-click and then select the Inspect command, or we can do an old good console.log. But...

Many years ago I went to University for the second time. I was 25 and I did math pretty well - but at the level of a high school. When Uni started I was in the hospital because I had an unexpected surgery. When I returned after several days of absence, I went to the first lecture (the first for me) and it was not so bad. I didn't understand everything but at least it looked a bit familiar.

The next day we had the practice - I thought the teacher would explain how to solve the problems related to the lectures. But, to my horror, it was an absolutely unknown topic. I didn't understand any word, any symbol, anything. I thought "What the hell, this is not for me, because I will be not able to figure it out!" I was scared because I also thought that this topic had nothing to do with the lectures. I still don't know why the teacher chose to practice the topic we even didn't start but it never happened with other topics.

Let me share my small hack I started using recently.

When I started learning to program I asked many questions, I even had to register on Stackoverflow. But now, 2 years ago, I don't want my employers (especially the potential ones) to know the stupid questions I even asked.

So, I created another account and only answer there. Now it has more 1,000 points. And even my first acc has almost 5,000 points I would prefer to share my second account that has much bigger impact and looks more solid.

I hope, it helps somebody.