harshraj22

Challenges
Mistakes/Failures
Enjoyed
Leadership
Conflicts
What You'd Do Differently 

harshraj22

git add upstream https://github.com/harshraj22/Practice_plan.git
(add upstream branch, as you created local git repo now, it isn't expected to have an upstream)

git fetch upstream
(fetch all changes from upstream to local repo)

git rebase upstream/master
(rebase your current branch from master of upstream, you can also use git merge --allow-unrelated-histories upstream/master if you prefer merge commit)

git remote rm origin

johncurcio

wgcv

rajatdiptabiswas

#!/usr/bin/env python3

"""
Binary Indexed Tree / Fenwick Tree

https://www.hackerearth.com/practice/notes/binary-indexed-tree-made-easy-2/
https://www.topcoder.com/community/data-science/data-science-tutorials/binary-indexed-trees/
https://www.youtube.com/watch?v=v_wj_mOAlig
https://www.youtube.com/watch?v=kPaJfAUwViY
"""

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules