Hello! I'm Aga. Welcome to my coding world!


## Lazy, meaning what?

The work of a programmer is full of challenges, without a doubt. But what makes a programmer 'good' or 'bad' at his job?

I often heard that the best programmers are the lazy ones. The Internet even calls for such an attitude in a developer's work!

However, this theory, repeated from mouth to mouth, simplifies the issue very much.

Because what does it mean to be lazy? According to the Cambridge dictionary, it's "not willing to work or use any effort" Okay, that sounds reasonable. But how does that translate into a programmer's job?

## Hard way to be a developer

First of all, you can't be lazy to become a programmer. Programming is not a piece of cake. You won't learn it with "not willing to work or use any effort."

Willingness to work and invested energy will be crucial here! You won't be a programmer in one night.

For example, it took me almost a year to learn to program in Javascript! And it was a year full of problems, with no hope that beating difficulties would be possible.

A lazy person cannot handle it and will give it up.

## Lazy developer or efficient one?

Okay, but let's assume that we are already programmers working in a company.

Are you being paid to slack at work? For being inactivity at meetings (because meetings are a waste of time)? For not showing any proactive attitudes, failing deadlines? Not writing tests or documentation (because you don't want to do it - too much work)? Maybe for the lack of willingness to develop skills and the lack of desire to be 'up to date? I am asking because this makes me think of a lazy person.

I know you're going to say, "No, it's not about that! It's about making your life easier instead of repeatedly doing the same boring stuff!"

And you are right. That's why great programmers are so good and often employed because they can solve problems effectively!

A good programmer will wrap repeating code in a reusable function. Need to do something time-consuming by hand?

A good programmer will write a script that will do it for him.

But let's think about it - is it a sign of laziness? In this little piece of a programmer's work, maybe so. However, I would prefer to call it efficiency mixed with impatience and willingness to improve work and make life easier.

To execute this sample script that does something for you, you need to work into it. It will not do itself.

I often hear that 'a lazy developer doesn't want to waste time on repetitive, boring activities'. But is this really about the lazy one? Or maybe about the one who cares about getting the job done efficiently.

## The flip side of the coin

We also touch on one more critical issue here: too much diligence.

The flip side of the coin is that you can be the hardest-working programmer in the world, but if you have nothing to do with efficiency and only work to work, you will also not be good at what you do.

The saying "work smart, not hard" works excellent for programmers.

We can call it laziness, efficiency, and wisdom, but we must remember the context here because the term 'lazy' is overused for me.

What do you think about it?


The work of a programmer is full of challenges, without a doubt. But what makes a programmer 'good' or 'bad' at his job? I often heard that the best programmers are the lazy ones.

To be (a lazy developer) or not to be


Today's post is short, but it concerns a handy thing in the Front-End world - Local Storage!

If you create applications in pure Javascript or one of the frameworks - in each of these cases, sooner or later, you will meet Local Storage.

## Okay, but what is a Local Storage?

In short, it can be called a type of 'warehouse' that functions in the browser next to cookies.

What's valuable - the data in Local Storage is available in the browser even after it is closed.

So when the user returns to our website after some time - the data will continue to be updated.

## We can store data in our 'warehouse.' What kind?

For example, is the user logged or not, information on whether the user has accepted the website regulations, forms inputs, etc.

However, we must remember one important thing: data in Local Storage is stored in a string and key-value format.

We have access to Local Storage through five main methods, which are:

`setItem()` - Adds a key and value  
`getItem()` - Get the value  
`removeItem()` - Removes an item by key  
`clear()` - clears all data from Local Storage  
`key(index)` - method useful for iterating over the keys; we can get the value from the index key

Below you will find a short demo of how Local Storage works.

To see this, open the link below in the two or more tabs and then click the button in one of them.

After you make a click, switch to the second tab.

You'll notice that the button color on the second tab will change too! Isn't that cool?

[OPEN THIS LINK IN TWO TABS](https://by3ol.csb.app/)

If you want to play with this demo yourself and maybe expand it a bit, here is the sandbox you can fork:

[CODE SANDBOX WITH LOCAL STORAGE EXAMPLE](https://codesandbox.io/s/localstorage-demo-by3ol)

That's it for today. When using Local Storage, remember that it is certainly not a place to store sensitive data!


Today's post is short, but it concerns a handy thing in the Front-End world - Local Storage! If you create applications in pure Javascript or one of the frameworks - in each of these cases, sooner or later, you will meet Local Storage. Okay, but what is it?

Local Storage synchronization - easy and powerful JS tool!


## Maps in front-end development

At some point in the career of every front-end developer, there will come a time when they will face the task of map implementation. There are many uses of maps in applications. Today I will focus on maps that contain a large number of points with specific coordinates. They can be, for example, delivery points, restaurants, shops, etc.

Because of its open-source nature, Leaflet is a standard solution that developers often use. Today we will talk about it.

Let's imagine now that our task is to add specific points to the map, but we do not add them only once after launching the map, but we send a request for points each time you move around the map (moving or changing the zoom level). Sounds familiar?

## Leaflet clusters in action

If so, you've probably come across the recommended Leaflet plugin, Leaflet.markercluster. We can find examples where 10,000 or even 50,000 points are implemented in the documentation! Furthermore, thanks to chunkedLoading, we can display many points on the map in a relatively user-friendly way. Below you will find an example of Leaflet clusters from the official Github page of the project:

[LEAFLET EXAMPLE WITH 50 000 POINTS](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.50000.html)

The plugin can handle significant challenges, so it will dynamically add points, right? Not so fast! Yes, Leaflet.markercluster is doing quite well, and this is also the solution I introduced in my recent project, but the key to success, in this case, is knowledge.

Now imagine this situation: at the beginning, you add 350 points to the map. Then, the user moves the map - we have a new map area, so we send another request for new points and generate 350 points on the map again. It sounds simple, but it is not. Because as you will find out - this operation takes a long time. Not tens of milliseconds, not even several hundred. It takes 2-3 seconds, and sometimes even more!

I don't even want to think about what numbers we can achieve with a slow internet connection. It happens every time you move the map or change the zoom! The more logic related to the map (added, e.g., search engine, custom marker icons, etc.), the more these results can be depressing.

You are probably thinking: why to add 350 points each time if we can remember those already there and add only those that have not been on the map so far. Additionally, you can delete those markers that are not in the map's visible area, right? Sounds wonderful :) However, in the case of Leaflet.markercluster, this type of operation can be a suicide!

## The solution to Leaflet.markercluster performance issues

Our team searched the entire Internet for answers, trying to handle the optimization of our map. We had many custom solutions (like a search engine and a lot of custom logic), but they were not the source of the problem, as it turned out.

Finally, one day I came across a fascinating note by danzel, who explained the situation in detail.

The original post you can find here:

[ORIGINAL POST WITH EXPLANATION](https://github.com/Leaflet/Leaflet.markercluster/issues/59#issuecomment-9320628)

It was like finding the Holy Graal!

As you've probably noticed, when you dynamically change points on the map, the quickest solution is to … remove all points and re-apply them! Even those that are already on the map! No selection.

CLEAN AND INSERT ONCE AGAIN

Why?

## Leaflet clusters methods comparison

All thanks to the efficiency of specific Leaflet.markercluster methods. You can find a detailed comparison of them below. I installed 10000 points for the tests and set them to change after moving the map, and I did sandboxes for three different cases. I didn't add additional logic to remove clusters out of bounds. I keep it simple in these examples and compare only add/remove methods.

You can see the results in ms in the console:

### removeLayer combined with addLayer

[SANDBOX LINK](https://codesandbox.io/s/leaflet-markerclusters-performance-test-removelayeraddlayer-0zclk)

### removeLayers combined with addLayer

[SANDBOX LINK](https://codesandbox.io/s/leaflet-markerclusters-performance-test-removelayersaddlayer-2wofo)

### clearLayers combined with addLayers

[SANDBOX LINK](https://codesandbox.io/s/leaflet-markerclusters-performance-test-addlayersclearlayers-q08xl)

As you can notice, clearLayers combined with addLayers are the two fastest methods, and I strongly recommend using them in your project!

The results are fascinating, and as you can see, the most obvious solutions are not always the best. By changing the method of adding and removing markers on the map, we have improved its performance more than 10 times!

Keep the above scores in mind if you implement Leaflet with Leaflet.markercluster.

It can save you many hours of searching for a solution.


At some point in the career of every front-end developer, there will come a time when they will face the task of map implementation. There are many uses of maps in applications. Today I will focus on maps that contain a large number of points with specific coordinates.

Rendering Leaflet clusters fast and dynamically - let's compare 3 methods


In this episode, you will learn what an algorithm is and why it is essential in the programming world.
Let's get started!

## What is an algorithm at all?

Each computer program consists of instructions on what the computer should do step by step.
You've probably prepared a meal with a recipe at any time.

Do you want to make spaghetti?

Step 1: fry the onion and meat in a pan.

Step 2: add herbs and tomatoes.

Step 3: cook for 30 minutes.

Step 4: cook the pasta al dente.

Step 5: serve pasta with sauce and grated cheese.

Spaghetti is ready!

Each step should be performed correctly and with the right ingredients to achieve a specific result - in this case, delicious spaghetti.

Our recipe is just an algorithm - instructions on steps to achieve a specific goal.

Just as spaghetti can be prepared in many ways, programming problems can be solved using different algorithms.

Of course, algorithms can be more complex (and most often, they are).

They may, for example, be based on conditions.
Example? Here you go fishing. When we break down this activity into step-by-step instructions, i.e., an algorithm, it looks like this:
Step 1: put the worm on the hook
Step 2: throw the bait into the water
Step 3: observe the float until it is submerged in the water
then we have the condition:
has the float submerged or not?
If not: keep watching.
If yes: get the fish out of the water and repeat steps from step 1.
If you're done fishing, pack your things and go home.

Remember! Computers are not masters of thinking, so if you forget about the last step, you will be sitting there until the end of the world ;)

## Examples straight from the IT world

Using the Google Maps application, you are dealing with AI algorithms. This is called a path-finding algorithm whose task is to find the most optimal route between selected points.

Another example can be the principle of an ATM. You come over, insert the card, and hand over the pin. If it is correct, you are asked for the amount of money to be withdrawn and get the money. If the pin is wrong, then you won't get your money. All steps in withdrawing cash from an ATM are based on algorithms.

This is how we communicate with the computer. We solve specific programming problems thanks to algorithms and writing out a sequence of instructions. We do this before we start writing the code. Thanks to this, we can write it more efficiently, because we have clearly written instructions!


In this episode, you will learn what an algorithm is and why it is essential in the programming world.

What is an algorithm? - the most straightforward definition ever!


## The traditional path of learning and career

Traditionally career path has been like climbing a ladder. Step by step up to success, working hard, waiting to be promoted. This often meant staying as long as you could at the same company. You have one deep area of expertise, and you focus on it.

But is it sufficient today?

## Why do you need a second skill in your life?

Today's world is changing very rapidly, and a career path now is like jumping from one ladder to another. It even looks more like a conveyor belt than a ladder. You have to keep moving and learning no matter your stage.

Your college degree shouldn't be the ending point of your education. Be prepared for lifelong learning. A second skill can help you handle an unexpected loss of your current job faster.

More and more companies prefer skills over qualifications. The non-traditional, flexible career path is becoming the new normal, especially in the tech industry.

It is happening right now, before our eyes!

## Self-learning today is easier than ever!

The Internet has changed everything.
It opened up broad information access avenues available to anyone with an Internet connection. You can learn from books, podcasts, blogs, courses online, etc.

You can learn where and when you want and connect with people worldwide! There are no limits to what you can learn. You can choose the topic and level of difficulty. You can start something from scratch. The only limit is your imagination.

## Why should you be a self-educator?

There are a lot of benefits to being s self-educator. The most important advantage is the proper mindset. Hungry for new information, open-minded, enthusiastic autodidact.

Being a student and teacher simultaneously allows you to be more flexible in the learning process.
Advantages of self-learning:

1. You can learn what and when you want — you don't have to follow a strict curriculum.

2. You go at your own pace — you are limited only by your motivation, discipline, and free time. You can spend a lot of time fully understanding a topic. It's not a race. Learn at your speed.

3. You practice and adopt lifelong learning in your life — it brings you many benefits in the future: renew self-motivation, improve self-confidence and self-discipline, and develop curiosity. You can use these skills later in other areas of your life!

Anyone can be a self-educator. It doesn't matter how old you are or where you live. So, what prevents you from starting learning a new skill today? Maybe now is the best time to learn something new.

Are you thinking about becoming a web developer? Check out this post about Computer Science Degree: --> [This one belief can ruin your career](https://agakadela.com/blog/this-one-belief-can-ruin-your-career) <--


3 benefits of self-learning that will help you achieve your goals


## To be considered a developer, you need to get a Computer Science degree, don't you?

Have you ever heard this sentence?
I used to think it was true. I felt that I couldn't be a programmer without finishing tech university.

I was going to a volleyball camp when I had my life-changing thoughts. I was a volleyball player and coach for teenagers. I still remember not wanting a 'regular' job because of my sports passion.

Camps, practices, and tournaments were engaging, and I didn't have time for 8 hours of regular work. I didn't want to give up my sports passion too.

My first idea? I can be a programmer because they **can work from anywhere in the world and have irregular working hours.** Perfect! But can a girl like me be a programmer at all? I didn't have a Computer Science degree. I have one degree from the Physical Education Academy. It has nothing to do with coding!

Despite this, I started to browse job offers for programmers - especially front-end developers- and noticed an interesting fact. In most of them, higher education was not a requirement! What? How it's possible?

It was a game-changer for me then.

I started **self-study in front-end development.** I learned HTML, CSS, Javascript, and all requirements that I saw in job offers. I learned between volleyball practices and camps (when I got free time). I learned a lot of new things, and that's how my coding adventure started, and it still lasted seven years!

During my career, I worked as a freelancer, had my own small business, worked as a full-time employee, and taught others how to code. I have tasted it all. To this day, no one has asked me for an education or college degree. **My skills only matter.**

## It would not be possible if I believed the myth about a science degree in coding.

I don't tell you that a Computer Science degree is something wrong. Not at all. It can be a great way to learn to code. I want only to tell you that if you don't have an opportunity to study Computer Science, you can still become a developer.

That's why I created this website - because I believe that you can live the life you want. Just like me!

Do you want to become a successful developer? [Follow me on Facebook](https://www.facebook.com/AgaKadelaCW) and share a comment on what you think about it.

### And remember, girl: knowledge is your power!


I used to think it was true. I thought that I can't be a programmer without Computer Science degree.

Hello! I'm Aga.

Welcome to my

coding world! 👩🏻‍💻

Recent posts

To be (a lazy developer) or not to be

Local Storage synchronization - easy and powerful JS tool!

Rendering Leaflet clusters fast and dynamically - let's compare 3 methods

What is an algorithm? - the most straightforward definition ever!

3 benefits of self-learning that will help you achieve your goals

This one belief can ruin your career...