This is continuation of Git Basics series.

1. What is Git?
2. Know Your Git Terminologies

Local Git Repository:

Setting up a local repository is pretty simple. By local repository I mean making your project a git repo on your work-station.

Open git-bash. Navigate to root of your project folder. In my case it is — android-test.

Sowmya\android-test$ git init

Syncing With a Remote Repository:

Congrats! Now your project is a git repository. If you want to upload it to a remote repository(have a copy in the cloud) you could use a cloud hosting service like github, Gitlab or bitbucket. In my case, I am using a github repo.

So…

This article is a continuation of Git Basics series.

One of the challenges I faced while learning Git was the keywords used. Once you know what each command means your life becomes a lot simpler.

It would definitely take a few screws up to get a hang of it.

But the best part is every screw-up can be undone.

1. Config: ‘git config’ allows you to get or set any repository or global options. It allows you to set variables in the config file.

2. Init: ‘git init’ initializes your working directory to a git repository. …

Think of Version Control as the system which meticulously keeps a history of every change you make in your code in every file of your project. It logs every detail of what the change was, at what time was it made and by who etc.

Think of it like if you are an author and you keep editing the book it keeps track of all history and revisions so you can easily go back to the version you like if you make mistakes or want to fix something.

It also helps give credit to the author and makes collaboration easier…

Yet another article trying to explain how to pitch! Like there aren’t enough already.

I know, I know! I have read ‘em too, but bear with me here.

For more than a decade, I have been pitching about my ideas, business, getting interviewers to hire me, and people to get interested in what I do. I do it genuinely and passionately as I enjoy solving problems.

I am an engineer at heart, any problem you throw at me piques my interest but making people understand the solution is harder than you think. …

While using dependencies in your Android projects sometimes it’s natural for some strange errors to pop which do not make any sense. For instance, suddenly a firebase dependency seems broken when you add a different dependency. Sometimes you can have dependencies that do support incremental builds.

These kinda problems arise because the libraries using certain dependencies might have a different version of the dependency than you do.

But as the dependency graph grows, it becomes harder to visualize which dependency has a different version.

If you are facing issues with your Gradle builds in Android Studio because of your dependencies…

For the longest time, I have made it a habit to attend quite a lot of interviews. One of the reasons being I was terrified of appearing for interviews at one point in time and I started to give interviews just to practice and get over the fear. The more interviews I gave the better I performed.

In this article, will be listing the most common interview questions I was asked recently in a couple of interviews by some big companies involving Android, Java and Kotlin. I will be adding more questions as and when I come across.

1. What is…

By now, I have heard several excuses from developers and managers who had their reasons not to pair program. As far as I’ve seen, the doubts and inhibitions arise from experiences involving bad practices.

Two of the earliest ENIAC engineers, Jean Bartik and Betty Snyder were a pair in the 1940s when they worked on the first ENIAC machines. “I believe that the best programs and designs are done by pairs, because you can criticise each other, and find each other’s errors, and use the best ideas,” Bartik said.

If two of the early programmers in the history of computer…

As a programmer, are you guilty of writing hacky code that stinks or pushing code without tests? Me too … and everyone else I know.

At times, I had to be empathetic toward myself as a developer who, pressed for time, allowed untested code to sneak in. Other times, I thought I was pleasing managers who thought quick wins implied faster delivery at the cost of quality.

Whatever be the reason, it’s us developers digging our own grave by adding or approving smelly, untested code. In such environments, it didn’t take too long before technical debt piled up to form…