Search for a command to run...
Software Developer (Full Stack) with 4 years of experience building scalable web applications across frontend and backend. Focused on performance, security, and clean architecture. Skilled in troubleshooting, agile collaboration, and delivering production-ready solutions. Driven by continuous learning and delivering high-value, user-centric solutions.
No comments yet. Be the first to comment.
The Problem: Manual Token Transfer Between Environments Modern web applications often rely on authentication tokens stored in the browser's localStorage to manage user sessions. During development, teams frequently work across multiple environments—s...
If you juggle personal projects on GitHub and company work on Bitbucket, you’ve probably run into this: You push your work code, and Bitbucket says — "This user cannot be matched to an Atlassian account." Why? Because Git is still using your person...
So, you've just dived into the world of Linux and you're itching to get your hands on some cool software. Fear not, fellow penguin enthusiast! In this guide, we'll explore five hassle-free ways to install applications on your Linux machine, using eve...
Discover the simplicity of Docker with our guide on "No-Nonsense Docker Commands for Developers." Streamline your container workflow effortlessly and boost your development game with straightforward, practical instructions. Build Image : Build an ima...
Unlock layout flexibility with min-width: 0 in your CSS toolkit. Tread carefully to avoid unintended layout surprises. Enhance responsiveness, but respect default styles for a harmonious design dance. 🚀 Pros of min-width: 0 for All (*) Flexy-Flex L...
Some Ordinary Developer
10 posts
A not-so-ordinary tech blog
In simple terms, a git branch is a way to create a copy of your code at a certain point in time, so that you can work on new features or make changes without affecting the original code. It's like creating a new "branch" in a tree - the main trunk of the tree (your original code) remains intact, while you can make changes and additions on the new branch (your new code).
Each branch has a unique name, and you can switch between branches to work on different parts of your code. When you're finished making changes on a branch, you can merge those changes back into the main branch (also known as the "master" branch) so that they become part of the main codebase.
Using branches is a common practice in software development, as it allows multiple people to work on the same codebase simultaneously without interfering with each other's work. It also helps to keep the code organized and makes it easier to track changes and revert back to previous versions if necessary.
Quick tip create branches with "feature/task-you-are-working-on"
There is no one-size-fits-all answer to the best way to use Git branches, as it depends on your specific workflow and project requirements. However, here are some general tips that can help you use branches effectively:
Use descriptive branch names: Give your branches meaningful names that describe the changes you're making, such as "feature/user-authentication" or "bugfix/404-page".
Create branches for specific tasks: Create a new branch for each task or feature you're working on, rather than making changes directly to the main branch. This will help you keep track of changes and isolate any issues that arise.
Use feature branches: Consider using a "feature branch" workflow, where each branch corresponds to a specific feature or set of related features. This can make it easier to manage changes and collaborate with other developers.
Use pull requests for code review: When you're finished making changes on a branch, submit a pull request to merge your changes into the main branch. This allows others to review your code and provide feedback before it's merged.
Delete branches when they're no longer needed: Once a branch has been merged into the main branch and is no longer needed, delete it to keep your repository clean and organized.
Use tags for releases: When you're ready to release a new version of your software, consider using Git tags to mark the specific commit that corresponds to that release. This can help you easily track which version of the code was used for a particular release.
Overall, the key to using Git branches effectively is to stay organized, communicate clearly with your team, and follow consistent workflows that work for your project