Implementation Flashcards
(18 cards)
What does “well implemented” code mean?
Code that is easy to maintain, follows standards, and uses collaborative strategies.
Why are coding conventions aims and methods?
Aims - making code easier to understand, producing software built by one team not 20 individuals, setting quality standards
Methods - name variables like this, write comments like this, organise class contents like this, name files like this.
What are examples of Java coding conventions?
Variable naming, consistent commenting, structured class contents, and using tools like linters and formatters.
Name three team scenario people you could be in software engineering.
1) The Developer, 2) The Dev Manager, 3) The Integration Team.
What are some key strategies for writing good code in a team?
Test-Driven Development (TDD), Comment-Driven Development, Paired Programming.
What is Test-Driven Development (TDD)?
Writing tests before the code, then coding to pass the tests—improves accountability and clarity.
What is Comment-Driven Development?
Writing comments first to plan and explain logic, then coding to fulfill them—facilitates design and communication.
What are 3 common debugging strategies?
1) Breakpoints & stepping through code, 2) Print statement tracing, 3) Binary search for error localization.
What is Rubber Duck Debugging?
Explaining your code line-by-line to a rubber duck to identify logic flaws through verbal explanation.
What is a “linting test”?
A tool that checks code against style and quality rules, often used before human review.
What is the purpose of bug tracking systems like Bugzilla?
To log, trace, and manage bugs, supporting collaborative debugging and code improvement.
What’s the key difference between testing and debugging?
Testing finds bugs; debugging locates and fixes them.
What is “paired coding”?
Two people code together—one writes code, the other reviews or plans—promotes quality and shared knowledge.
Bug reporting in a team
Someone calls up a bug in your code.
You need to try and reproduce it
What were they doing when it happened, what was th immediate action before the bug was found, what was the ‘wrong outcome’
Debugging using IDE features
Use breakpoints to check values one step at a time
Variable inspection
Trace tables
Exception-based breakpoints
Debugging using print statements
Add lines of code that print the status of your variable
Useful for logic errors
Debugging - mistakes
Always fix the bug not the symptom
Fagan inspections
Print out code and do a group inspection
Step away from the computer and explain it to each other
