DEV Community: Murilo Viana

Left and Right Shift: Bitwise Operators in Python

Murilo Viana — Thu, 11 Apr 2024 00:25:18 +0000

Last week while browsing on X (Twitter), I came across the following quiz:

What do you think the correct answer would be? Do you know what the >> sign means?

This sign means that the language will perform a bitwise operation. But what exactly is that?

Don't worry if you're not familiar with this operation. At the time, reading through the tweet's comments, most people had responded True. According to them, the operation to be executed would be "4 greater than 2". Since 280 characters are not enough to cover everything I'd like to address in solving this quiz, I decided to write this text to introduce a concept that seems to be little known.

Bitwise Operations: Left and Right Shift

Let's start with the basics. As the name of the operation suggests, bitwise is an operation done directly on the bit, meaning it's an operation directly understood and supported by the processor, making it extremely fast.

There are various bitwise operators, but we will only discuss two of them focusing on solving the quiz: left shift and right shift. The idea of these operations is to move the digits of a certain set of bits to the right or left. It's as simple as that!

Let's suppose we have the following binary: '0b100111' ('0b' at the beginning is just a binary representation indicating that every bit to the left is 0). When we perform a left shift on it, we will move the bits one place to the left, adding a new bit to the right of the binary. This new bit will always be 0 for this operation, resulting in a new binary.

For right shift, the idea is quite similar, the difference is that we will move the bits one place to the right. Thus, the bit farthest to the right of the old binary will be removed from the new binary.

Python Syntax

Great, now that we know what the shift operators are, let's move on to the syntax in Python. The binary used in the previous examples ('0b100111') is the representation of the number 39, so, to perform a left shift of just one bit from this decimal we use the following command:

>>> 39 << 1
78
>>> bin(78)
'0b1001110'

The first element of the operation is the number whose bits we want to move (39), the operator << represents left shift, and the second element (1) is the number of bits that will be moved in the direction of the operator (left <<).

"Hold on, does that mean we can perform more than one shift at the same time?"

Exactly! For example:

>>> 39 << 2
156
>>> bin(156)
'0b10011100'

The same syntax applies to right shift: the first element is the number whose bits we want to move, the operator >> represents right shift, and the second element is the number of bits that will be moved in the direction of the operator (>> right).

>>> 39 >> 1
19
>>> bin(19)
'0b10011'
>>> 39 >> 2
9
>>> bin(9)
'0b1001'

Notice, whenever we perform a left shift operation the binary increases. Consequently, its decimal representation also increases. On the other hand, when performing a right shift operation, the binary always decreases, as does its decimal representation.

Back to the Quiz

Now that the concepts of left and right shift are clearer, returning to the quiz we realize it's not that difficult after all. The operation to be done is a right shift of the binary representation of the number 4 ('0b100') moving the bits twice to the right.

>>> 4 >> 2
1
>>> bin(1)
'0b1'

Therefore, the correct answer to the quiz is 1.

So, did you get it right on the first try? I hope you're now more familiar with this type of operation. Comment here if you want to know more about other bitwise operations.

5 Practices I Use to Improve Myself as a Senior Developer

Murilo Viana — Mon, 01 Apr 2024 19:46:33 +0000

After years of working in the software development field, I've reached the esteemed position of a Senior Developer. It wasn't an easy or quick journey, but to help you get there, I've shared some tips that I wish I had received during my career:

5 Tips I Wish I Had Received When I Was a Junior Developer
5 Tips I Wish I Had Received When I Was a Mid-Level Developer

Now, to complete my trilogy of posts celebrating over a decade of learning and knowledge gained in software development, I present the 5 practices I use to improve myself as a Senior Developer.

Find Problems

It's expected that Senior software developers are independent, and this goes beyond the ability to solve problems, being essential also in the capacity to identify them.

The most exceptional professionals I've worked with didn't passively wait for demands. On the contrary, they took the initiative to actively seek out significant debts in the applications. However, this search takes time, as it requires investigating different parts of the system, which involves code review, metrics analysis, and discussions with team members.

The purpose of this exploratory approach is to discover problems, such as technical bottlenecks, system gaps, negative impacts on user experience, among others, to then bring them to light. In other words, it's to bring these critical points to the attention of those responsible. At this moment, another vital competency emerges: persuasion.

Anyone who has worked on large projects knows that demands are numerous and, often, not organized in the best possible way. Therefore, it's crucial to argue the importance of solving these fundamental issues with leadership, elucidating the consequences of not addressing them, so they can be properly prioritized.

What do I do? Present data! By providing data that demonstrates code inefficiency, high cost, low performance, or any other aspect negatively affecting the application, you significantly increase your chances of success by highlighting new problems that need to be addressed.

Don't Overengineer Solutions

Focus on developing solutions that meet the current needs of the system, avoiding the trap of adding unnecessary complexity or anticipating future improvements. As a computer scientist, I'm fascinated by solving difficult and complex problems in the most sophisticated and optimized way possible. However, we often lack the time and resources for such at work.

What do I do? Build only what's necessary. This doesn't mean "do it sloppily", it's just an approach that avoids potential over-scaling or layers of abstraction that may not be necessary at the moment, or may never be.

Avoid over-planning for the long term. Focus on launching the product, tool, or feature so that it meets the current requirements, and then improve and scale it gradually, based on metrics, feedbacks, and the real needs of users. This avoids spending time extending the construction of an overly complex system that may not meet the real expectations.

Finally, accept technical debts. In the real world, factors external to software development influence deliveries. Thus, there will always be aspects to be improved later. The sooner you recognize this, the easier it will be to manage situations of over-engineering.

Understand the Business of the Organization

The impact of a Senior Developer goes beyond the technical aspects of the projects they are part of; it's also expected that there is an alignment with the business objectives of the project. Therefore, it's crucial to understand how technical aspects affect the financial outcomes of the organization.

The phrase "engineering is an isolated area" is something I've heard in various contexts, but I consider this view outdated. The business concerns of the organization must be fully understood by the software development area, allowing prioritization of projects that have the potential to generate significant value, whether by increasing revenue, improving efficiency, or reducing costs.

What do I do? Participate in discussions. Although it can be exhausting to be part of many conversations, strive to be as present as possible in them. After all, you never know when valuable business information might come up. Volunteer to participate in meetings discussing projects or future directions of the organization, keeping yourself always aligned with corporate objectives.

Promote a Positive and Productive Culture

Significant technical contributions are what's expected from a Senior Developer, but their role goes beyond. It's essential to promote a positive and productive work culture, a crucial element for the success of the organization by increasing the ability to attract and retain talent.

What do I do? Cultivate the culture. Leadership becomes much more effective when it's exercised by example. Therefore, foster collaborative cultures, through hackathons, meetups, conduct pair programming sessions, write influential articles on blogs, speak at conferences, and actively involve yourself in optimizing your organization's interview process. These initiatives cultivate a dynamic and welcoming work environment.

Once, I came across the phrase "be an architect of culture." I believe this phrase perfectly defines what is expected of a Senior individual: someone committed to creating an inclusive and supportive environment where everyone is encouraged to learn, grow, and contribute to their fullest potential.

Seek Inspiration

Surely, there are people who inspire you, those to whom you aspire to reach the same level of achievements but might not know, or even believe, it's possible to get there.

What do I do? Talk to these people. Seeking to understand how they act, deal with certain situations, the way they think, and how they achieved their goals shows a path to be followed. If you don't have direct access to them, look for content that addresses these exceptional personalities and try to emulate their positive behaviors.

Often, we fall into the error of comparing ourselves to others instead of being inspired by them, which can be demotivating. However, the truth is quite simple: the goal is to compare ourselves to what we were yesterday, aiming for the level we want to reach based on our inspirations. It's with this purpose that I share my experiences and learnings, hoping to inspire and be inspired by others. In this way, I continue to improve myself to become an even better developer, and I hope you can also achieve your best version.

5 Tips I Wish I Had Received When I Was a Mid-Level Developer

Murilo Viana — Wed, 20 Mar 2024 16:05:47 +0000

After sharing the 5 tips I wish I had received when I was a junior developer, I am very pleased to list the 5 tips I wish I had received when I was a mid-level developer.

This compilation of posts comes as a way of giving back for all the learnings the technology community has provided me with during more than 10 years of career. So, without further ado, let's get to the tips!

Understanding Algorithms

Algorithms are the backbone of any efficient solution, and understanding them not only improves the ability to solve problems logically and effectively but also opens doors for code optimization and the implementation of innovative solutions. Having a solid understanding of algorithms means navigating complex technical challenges with greater ease.

Practical example: Imagine you're working on an e-commerce system that needs to display products by price, from cheapest to most expensive. A straightforward approach is to use a sorting algorithm to organize the data. Here, understanding the nuances between different sorting algorithms, such as QuickSort, MergeSort, and BubbleSort can make a big difference. While BubbleSort may be simpler and more intuitive, it's less efficient for large data sets compared to QuickSort or MergeSort. Choosing the right algorithm not only ensures that users have a smooth experience while browsing through products but also optimizes server resource use, which is crucial for maintaining scalability and system performance.

Knowing different algorithms and their applications allows for a deeper understanding of how systems work internally, facilitating the identification of performance bottlenecks and possible improvements.

Contributing to Open Source Projects

Contributing to open source projects is an extremely enriching and valuable practice for any developer. This experience not only offers the application of practical knowledge in real and diverse projects, which is very exciting, but also promotes a deeper understanding of team collaboration dynamics and software project management.

Practical example: Contributing to open source projects can range from fixing bugs, improving documentation to developing new features. Platforms like GitHub and GitLab are excellent starting points to find projects that match your interests and skills. A good tip is to start with technologies that you use on a daily basis, so you'll have an easier time understanding where and how to contribute.

Contributions to open source projects serve as a showcase for your work, allowing other professionals and companies to see your skills in action. This can open doors to career opportunities, besides being a very significant differentiator in your resume.

Time is Code

In a world where tight deadlines and piles of tasks are the norm, managing your time effectively is not just a skill, it's a necessity. Developing a routine that maximizes your productivity without sacrificing your well-being is essential to advance in your career. Avoiding procrastination and establishing a balanced work routine can not only increase your efficiency but improve your quality of life.

Practical example: The Pomodoro Technique is a proven method to improve concentration and reduce fatigue. Working intensely for 25 minutes followed by a 5-minute break helps maintain focus and productivity throughout the day. But it's important to remember that flexibility is key. Adjust work and rest periods as needed, especially for tasks that require more time and concentration. Some people are more productive in the morning, while others find their peak efficiency at night. Adjust your routine to take advantage of these periods of higher productivity.

While consistency is crucial, we are humans and not machines. There will be more productive days and less productive ones. The important thing is to maintain a healthy balance, recognizing that the quality of work often outweighs the quantity. Allowing yourself moments of rest and recovery is not a luxury but an essential part of the creative and productive process.

Developing Soft Skills

Technical skills are often emphasized, but developing soft skills can be the differentiator that stands out a person in the job market. But what are soft skills? They are interpersonal and communication skills that facilitate effective interaction and collaboration among people in the workplace.

Practical example: A great scenario to develop soft skills is to get involved with communities, whether technology-related or not. In this way, you'll always be dealing with different people and different viewpoints, making you develop these skills constantly.

Importantly, soft skills are not only related to conflict management but also to every kind of communication you have during your day. Always strive to be responsible with your speech and decision-making, and remember that maxim your mother surely told you one day: "Respect is good and I like it."

Yes, nobody said that developing these skills would be easy, but it will make a significant difference in your career, especially if you aspire to leadership positions.

Always Staying Updated

Staying up-to-date with the latest trends, tools, and practices is crucial for any developer. Being attentive to updates not only ensures that you are using the most efficient and secure solutions available but also highlights your dedication to providing the best value in your projects.

Practical example: Imagine a situation where a new version of a popular framework is released, offering significant improvements in performance, security, and features. By staying updated and quickly learning the new characteristics and improvements of the framework, you can integrate all these values into the projects you are part of, bringing benefits that improve their performance.

Moreover, understanding and applying the latest innovations can open doors to new opportunities, whether in more challenging projects, positions of greater responsibility, or even in new fields within technology.

Enjoy the Journey

I like to say that each challenge is an opportunity to grow. So, go for it! I hope these tips can help you overcome your challenges during this journey.

5 Tips I Wish I Had Received When I Was a Junior Developer

Murilo Viana — Mon, 04 Mar 2024 17:22:20 +0000

Welcome to the world of software development! If you've taken your first steps in this amazing journey, you've probably realized there's a lot to learn. But fear not! I'm here to give you 5 tips I wish I had received when I was a Junior Developer, which will help you on this journey.

This is the first of three posts I will make as a way of giving back for all the learning that the tech community has provided me with over more than 10 years of career. So, without further ado, let's go!

Code Versioning

Learning to use version control systems, like Git, is indispensable in the modern development world. These tools not only make managing code changes easier but also allow for easier collaboration with other developers.

Code versioning acts as a digital diary of your project, where each commit tells a part of the story. This practice helps not only in keeping a detailed record of changes for bug fixing but also is crucial when collaborating on projects with many people, allowing everyone to work simultaneously without overriding each other's work.

Practical example: start using Git in your personal projects. Practice making small and meaningful commits, and don't forget to write clear and descriptive messages; your future self will thank you for these messages. This will help you better understand the history of your project, in addition to preparing you to work as a team.

Besides using Git to manage your code, familiarize yourself with code hosting platforms like GitHub or GitLab. These platforms not only offer a place to store your repositories in the cloud but also provide powerful tools for code review, project management, and continuous integration, which are fundamental for collaborative and professional development.

Mastering the Art of Googling

Knowing how to search efficiently is as important as knowing how to program. The ability to quickly find solutions, answers, and explanations not only saves time but also accelerates your growth. It's not just about typing a question into Google; it's about crafting a question in such a way that you find the most relevant and helpful answer possible.

Practical example: Imagine you're working with Django, a popular web development framework in Python, and you encounter an error when trying to migrate your database. Instead of just searching “Django data migration error”, include specific details of the error, such as “Django db.migrations.exceptions.InconsistentMigrationHistory”. This narrows down the search to discussions and solutions highly relevant to your specific problem. Moreover, exploring forums like Stack Overflow can be incredibly useful, as others often have faced and solved similar problems to yours.

Important, when you find the solution to your problem, take a moment to understand the cause of the error and how the proposed solution resolves it. This not only solves the current problem but also broadens your overall understanding, making it easier to solve or even prevent similar problems in the future.

Learning from the Community

The journey of a developer is marked not only by the code they write but also by the connections they create. Learning from the community not only accelerates your professional growth but also opens doors to new opportunities, ideas, and collaborations. The exchange of knowledge in a collective environment enhances innovation and problem-solving in ways that solitary work seldom achieves.

Practical example: Participate in local developer communities, whether through meetups, conferences, or specific technology groups, is a very valuable way to learn from others in the field in addition to building your professional network.

Write Code Regularly

This is a golden tip: write code. And then, write more code. Theory without practice is like a car without fuel; you know where you want to go, but you can't get there. Therefore, practicing constantly is what turns raw knowledge into refined skill, allowing you not only to understand but also to effectively apply what you've learned.

Practical example: Participate in coding dojos, meetings of developers who practice programming together. The idea of these meetings is to collaboratively solve a challenging problem, aiming to improve coding skills, teamwork, and problem-solving. It might be scary to write code in front of others at first, but that starts to change when you realize that much more experienced people also make mistakes, making the environment welcoming and a great learning experience.

Another possibility is to solve coding problems online on platforms like LeetCode, HackerRank, and CodeSignal. They offer a variety of challenges that can help you improve your programming logic and algorithmic skills.

Don't be too hard on yourself; every mistake is a lesson, and every challenge overcome is a step forward in your development journey. Continuous practice not only helps solidify what you already know but also reveals new areas of knowledge and skill you didn't even know you needed to explore.

Keep Curiosity Alive

In programming, curiosity doesn't kill the cat; it turns it into an exceptional developer. Besides staying up-to-date with new technologies, it's crucial to go further and understand the fundamental concepts that drive the tools and languages you use. Knowing “how” something works is useful, but understanding “why” it works that way opens a new level of proficiency.

This approach not only improves your ability to solve problems more effectively but also enriches your understanding of the design choices behind the technologies you use. This empowers you to make more accurate choices in your projects.

Practical example: when learning a new library or framework, take time to explore its architecture and the problems it aims to solve. For example, if you're working with a certain language, don't just learn its syntax; seek to understand the language's data structures and how they work.

It's important to remember that technology is constantly evolving, and what is standard today may be replaced tomorrow. However, fundamental principles often remain relevant. By nurturing your curiosity and seeking to understand the “whys” and “hows”, you not only adapt more easily to changes but also stand out as a developer who brings value to any team or project.

Enjoy the Journey

Everyone started somewhere, and every challenge is an opportunity to grow. These five tips are just the beginning but are fundamental in establishing a solid foundation in your career. So, continue learning, be curious, and if possible, share your experiences and learnings with the community. Maybe you'll be the inspiration someone else is looking for!

Do you find these tips interesting? Leave your comment to further enrich this discussion \o/