DEV Community: Anup Bartakke

Initializing the Stack...

Anup Bartakke — Sun, 31 May 2026 09:32:48 +0000

The Declaration

Procrastination and habit of perfection together, sometimes forms a lethal obstruction in your path towards progress.

Being close to my second year in Bachelor of Technology (B.Tech) in Computer Science & Business Systems, I was desperate to start learning a major skill such as Full Stack, DSA + Leetcode, Python + AI and so on.
Amidst all this confusion, I kept slacking-off for almost half of my vacation until something hit me very deeply.

The Initialisation

Immediately, I pulled up some Full Stack Development videos on YouTube and firmly promised myself that I would do it no matter what. A moment that also pushed me to towards it was freeCodeCamp had just dropped a 47 HOUR Full Stack Development Course powered by Scrimba !
I embarked on that pathway right away and as I kept getting deeper into it, I started referring to the Scrima[https://scrimba.com/fullstack-path-c0fullstack] website as well.

I modify the mini-projects a little (quite a lot actually) so I can experiment more !

Github Repository Link

The Spark

My interest deepened as I got deeper into the course and boy, it was phenomenal. The way Per Harald (the main guy) taught those courses starting from basic HTMl (body/head tags to anchor-hover), CSS (styling elments to flexbox) I flew past everything smoothly.
My emphasis on Per Harald's teaching style was that on every step of the tutorial he kept the spirits up by consistent motivation and making me proud of the mini-projects I completed.

I diligently followed each and every project and typed down every line of code (I used my VSCode setup instead of Scrim so I can get used to the dev environment and CLI better.)

The Consistency

Now I am so addicted to coding and development that even though my exams are close, I still continue that course every single day. Currently I am at the JavaScript Challenges part (aprox 6:46:00 mark in the tutorial) and will start 'The Blackjack' Project in a couple of days !

Github Repository Link

Thanks Scrimba. Looking forward to the Pro Version and complete the course ! https://scrimba.com/?via=community

My legendary set-up (ignore the cable-management pls, its temporary)

The "Bug Hunter" Git !

Anup Bartakke — Sun, 26 Apr 2026 18:56:19 +0000

There is a specific point in every developer’s journey where you stop just "writing code" and start managing the entire repo cos you're just a solo developer. For me, that happened when I stopped thinking about my "to-do" list and started using the GitHub Issues tab to plan whatever repo I was working on
Apparently, I understood Pull Requests and Merges before Issues cos I never tried to understand it's purpose fully; but today I decided to give it a serious try.

I used to think Issues were only for massive open-source teams, but even as a solo developer, using an Issue-driven workflow has changed the game:

1. The Technical Debt Trap:
I caught a loop that was running infinite times and was about to cook my PC. I simply created 'Issues' regarding it and plus the other problems in my code.

2. The CLI Advantage:
I am in the habit of using the GitHub CLI (gh issue create) for most of my work (like pushing code, commit message). Command Line Interface makes it quite easy to do so.

3. The Clean Merge:
Linking my Pull Requests to those Issues meant that the moment the fix was merged, the issue was officially resolved and documented in the commits.

Moving the "to-do list" out of my brain and into the Issues tab has cleared up so much mental bandwidth. If you aren't using the Issues tab for your personal repos, you’re missing out on the best organizational tool in the dev ecosystem.

Those Green Squares! (Github Edition | Part 1)

Anup Bartakke — Sat, 25 Apr 2026 18:24:46 +0000

Check out my GitHub Profile ! [https://github.com/thebartakke-anup]

The Addiction of the Green Square...
You create a repository, you push a few lines of code, and suddenly, you see it: that first bright green square on your GitHub profile.

At first, it’s just a tracker, but soon, it becomes a high score or a streak. You find yourself wanting to "commit just one more thing" before bed. You start thinking about your code in "daily streaks." If you’re like me, you’ve realized that GitHub isn’t just a storage unit for code it’s a productivity engine that’s surprisingly addictive.

The "Staging Area" Learning Curve
When I first started, I underestimated the "git add .". I later realised that it is a loading dock, preparing a package for a journey. I learned the hard way that you can’t just throw things into the file and hope that it is pushed.

There’s a logic to it:

The Working Directory: Where the chaos happens
(and where my Python and C files live).
The Staging Area: The "Confirmation Screen" where you decide what’s actually ready for the world to see.
The Commit: The permanent seal, that should be a clear, professional headline of what you’ve built.

The "Cooked" Moment: Surviving the Rebase
Every developer hit that wall. You’ve coded your heart out, you’ve committed your changes, and you type git push... only to be met with a wall of red text.

"Rejected." "Fetch first." "Remote contains work that you do not have locally."

In that moment, you feel "cooked." But as I discovered today, it’s usually just a sync issue. Maybe GitHub created a ".gitignore" file that your laptop doesn't know about yet. This is where the "git pull --rebase" becomes your best friend. It’s the "handshake" that aligns your local work with the cloud, ensuring files sits perfectly in GitHub’s template.

Quality Over Quantity
The temptation is to push every typo just to keep the streak alive. But the real "pro move" is intentionality. Whether it’s spreading out 10 C language exercises over 5 days to show consistent growth, or grouping logic into clean, readable commits, your GitHub profile is a real digital ledger you can be proud of one or two years down the line.

Is GitHub addictive? Absolutely. But it’s the best kind of addiction. It forces you to be organized, it rewards your consistency, and it turns the lonely act of coding into a visible journey of progress.