One of the most valuable professional habits drilled into us from week 2 at NIAT is proper Git version control and Pull Request (PR) etiquette. In most traditional universities, students share project code by emailing ZIP files named "final_v2_really_final.zip" or copying folders onto pen drives. At NIAT, that habit is banned from day one.
Every team project requires creating a GitHub organization, configuring branch protection rules on main, and following GitFlow. You create a feature branch (feature/auth-endpoints), commit small atomic changes with descriptive imperative messages (feat: implement JWT refresh handler), and open a PR with screenshots and test results. Before any code merges into main, at least two peers and a lab mentor must review the diff and approve it.
At first, getting your PR rejected with 8 review comments asking you to rename variables, remove console.logs, and handle error edge cases feels frustrating. But after three months, you realize this is the exact workflow followed by top engineering teams at Google, Uber, and Swiggy. When I went for my internship technical rounds, the interviewer asked me how our team resolves git merge conflicts and manages CI/CD pipelines, and answering felt effortless because we do it every single afternoon.
Edited