build/ classes kotlin jacoco test.exec reports jacoco
Pietro Di Bello xpepper
What's the difference between a Junior / Intermediate / Senior developer?
Junior is capable but needs someone with more experience to teach, mentor, guide, or direct them. They are still learning, on the job, and you should expects the risks associated with such a person.
Intermediate can work on their own but isn't ready to lead, manage, mentor, or teach. These are the core of any team. They are proficient in their respective language and are probably learning others.
Senior devs are those beyond the bounds of a skillset. They may be leaders, teachers, or mentors in your organization. They can direct the priorities, roadmap, and business related to the development of your product. They are likely proficient in more than one technology, not necessarily other programming languages; perhaps they are familiar with database architecture, search algorithms and science, hardware and scalability, et
When you find it difficult to write a concise, focused, isolated test, the production code has unhealthy dependencies to loosen, invert, or break.
Here, “concise” means having no irrelevant details; “focused” means failing for only one reason; “isolated” means executing without side effects on other tests.
My notes on the video series "London vs Chicago TDD styles" by Uncle Bob And Sandro Mancuso
The git repo of the kata is here: https://github.com/sandromancuso/cleancoders_openchat/
"starting-point" branch is where both implementations began: https://github.com/sandromancuso/cleancoders_openchat/tree/starting-point
"openchat-outside-in"branch captures the tomato by tomato history of the London approach.
"openchat-unclebob"branch captures the tomato by tomato history of the Chicago approach.