Please enable JavaScript.
Coggle requires JavaScript to display documents.
Negar's Journey, Code Ownership (Martin Fowler) - Coggle Diagram
Negar's Journey
Intellij
short keys (dzone&Negar)
current file structure
Ctrl + F12
search in all
double shift
multi curser
alt + shift
changes
whatsapp
balloon
alt+Enter
git commit push pull
Ctrl + k (shift,l)
reformat
ctrl + alt [+shift]+L
Switch to the editor
Ctrl + Alt + F12
Super Method
Ctrl + U
Jump down the hierarchy
Ctrl + Alt + B
Method call hierarchy
Ctrl + Alt + H
usage and define
Ctrl + B
recent changes
Alt + Shift + C
مناسب برای پیش از کامیت کردن
It's like close unmodified tabs
"open all modified tabs!"
دوستان دوباره چیز خفن معرفی میکنم
(اگه میدونستین مسخره م نکنین)
توی intellij
اون پایین version control رو بزنین
بعد تب local changes
بعد روی default changelist بزنین
کلید f4 رو بزنین
پشماتون بریزه😌
Best (and Worst) Java Exception Handling Practices (able.bio - DavidLandup)
Code Ownership (Martin Fowler)
Strong code ownership
breaks a code base up into modules (classes, functions, files) and assigns each module to one developer. Developers are only allowed to make changes to modules they own. If they need a change made to someone else's module they need to talk to the module owner and get them to make the change. You can accelerate this process by writing a patch for the other module and sending that to the module owner.
Weak code ownership
is similar in that modules are assigned to owners, but different in that developers are allowed to change modules owned by other people. Module owners are expected to take responsibility for the modules they own and keep an eye on changes made by other people. If you want to make a substantial change to someone else's module it's polite to talk it over with the module owner first.
Collective code ownership
abandons any notion of individual ownership of modules. The code base is owned by the entire team and anyone may make changes anywhere. You can consider this as no code ownership, but it's advocate prefer the emphasis on the notion of ownership by a team as opposed to an individual. (The term collective code ownership comes from Extreme Programming, although in the second edition the practice is called Shared Code.)