Scrum is one of many implementation / interpretation of Agile.
Agile(Agile Software Development) is all about being the ability to make changes in your direction (It’s not about being fast) Agility is achieved by short feedback loops and Scrum is one systematic way of getting those short feedback loops.
Why Learn Scrum?
you might be a developer that will be joining a team that uses scrum (very common!), you may be a non-tech person hoping to join a devteam to get started with roles like QA,Product management, project management. Or you may just want to learn scrum and implement it in your worker (yes scrum is not just for software development).
Before you start with scrum, read about the Agile Manifesto first
most of the time we get invested on a tool/tech/problem and we just can’t move on without scratching that itch. we often think about “COULD WE?” rather han “SHOULD WE?” so we push the idea/tool/tech even if it is not really needed
Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.
Grady Booch author of Object Oriented Analysis and Design with Applications
I could list all of the qualities that I notice in clean code, but there is one overarching quality that leads to all of them. Clean code always looks like it was written by someone who cares. There is nothing obvious that you can do to make it better. All of those things were thought about by the code’s author, and if you try to imagine improvements, you’re led back to where you are, sitting in appreciation of the code someone left for you—code left by someone who cares deeply about the craft.
code reviews are meant to uphold an agreed upon standard
it is not an avenue to project your personal coding style to others.
1. build a standard 2. apply the standard via reviews 3. repeat step 1.
code reviews should have goals like 1. syntax 2. formatting 3. tests completeness (path coverage) 4. design adherence (oop, principles) 5. security (looking for insecure functions, known bad patterns, misuse of code,etc) 6. achieve consistency over cleverness 7. make the code look as if it was written by a single person 8. uphold project health
most of things listed above can be automated.
it is not meant to validate if another person’s way of coding matches yours
i’ve lead teams before, all of them were successful thanks to my cooperative teammates who helps me grow and uphold the standards via an objective process
to all aspiring tech leads, i hope this helps you the way it has helped me.
If you feel overwhelmed about starting courses like these, please remember that you do not need to finish them in one sitting (not many people can do that!), just select a topic that piques your interest, and watch one or two videos a day, that would go a long way into learning new ideas or sparking your interest for further learning.
SANS NewsBites is a semiweekly high-level executive summary of the most important news articles that have been published on computer security during the last week. Each news item is very briefly summarized and includes a reference on the web for detailed information, if possible.
Spend five minutes per week to keep up with the high-level perspective of all the latest security news. New issues are delivered free every Tuesday and Friday.