The new GitHub Copilot is super cool and the hype behind it is reasonable. After a couple of hours of playing with it and reading about it, however, I quickly realized that it is just a cool tool and not a threat. In fact, I keep asking myself which problems it will actually solve and how much we developers should care.
Chances are that you have copied some code snippet from Stack Overflow in your journey to become a developer. Simply put, the Copilot tool is an advanced and automatic version of that practice. …
You may not survive as a developer if you don't understand how to structure data and write algorithms that collect, analyze, and transforms the data. That is true despite having to learn data structure or data structure algorithms. What is required is for you to understand the idea behind working and manipulating data.
The graph data structure helps us create so many powerful things that the likelihood of you using something which makes use of this non-linear data structure is high. It is used whenever there are multiple and complex connections between data points which makes it perfect to represent Maps, Networks, and navigation systems.
Video Version of This Article
This post is an improved and more detailed article version of the Graph Data Structure Series on Youtube that you can check if you prefer videos.
A graph is a non-linear abstract data structure which pretty much means it is defined…
Promise. It is a super-fun and powerful feature of the language, but its limitation is that it can only handle a single event (when something is done or has failed).
Because of that,
Observables can be much more useful in many situations.
Observables can provide
Promise’s features, work with zero or more events, and work like streams. By default,
Observables can be canceled and only start when you subscribe instead of immediately like
Let's start by admitting that every developer Googles or searches for something in some other way. What sets developers apart is what they Google — not whether they Google or not.
The quickest and simplest answer is that it is a great way to grab quick solutions and move on to the next problem.
In a fast-paced work environment, developers are focused on delivering features and squashing bugs. Almost no one has time to sit down on a problem. Sitting on a problem may be costly for the team and the project — not to mention your job.
The HTML input field is simple, powerful, and does what it was meant to do. With over 30 attribute options it is one of the most robust and worth learning about HTML tags. Because users are constantly interacting with fields on the page, a lot of effort is put into making it appealing and easy to interact with but a lot can go wrong.
One thing that developers who don’t know better often shove aside is semantics in HTML. Semantics is one of the most important features of HTML5 and should be mastered by any web developer.
The most popular video on my YouTube channel is “When to use Section vs Article vs Div in Html?” and it made me realize how many developers out there are trying to understand the meaning behind these tags as they enter the web development industry. Because of that, I decided to put it all in one article in simple words.
You really can’t avoid the tree data structure. Whether you are aware of it or not, tree data structures are almost everywhere. It is the file system in your computer, spellchecks, and keyboard word suggestions, the HTML DOM, your object-oriented class structure, etc. The tree data structure is powerful, flexible, and fun to work with. One that every programmer should feel comfortable using.
Video Version of This Article
This post is an improved and more detailed article version of the Tree Data Structure Series on Youtube that you can check if you prefer videos.
The tree data structure…
Any developer aspires to be good. Unfortunately, a lot of them fail or get stuck in a specific level of their careers. If you ask any developer, the likelihood of them having someone that inspires them in the field is high. Gaining experience or becoming a specialist in a certain area is always the dream and most developers want to continue to code as long as possible, but what are the right things to focus on?
Over the time of my career, I had the chance to work with many pros and experienced developers who preached the same ideas. While…
As developers, it is easy to go by without dealing with large data amounts or data that requires complex logic around it. For that reason, it is easy to neglect the need to improve your skills around working with data. The problem becomes obvious when you try to advance your career. There, everything is about data and it is not all programming-related.
Whenever I conducted interviews in the past, most of the candidates struggled to create logic or handle particular data pieces. Whenever they figured out a solution, sometimes that solution proved to be inefficient if the data amount increases…