sllozier / honor_evaluator

👋 Hi, I’m Sarah

| | |

🦄 About Me

I am a Full Stack Software Engineer located in Maine, USA.

As my father-in-law likes to say, I am not your "average bear".

I discovered my passion for engineering later in my career and I consider this an advantage.

When I am not learning new tech, teaching future engineers or building applications, you will find me camping 🏕, fishing 🎣 or hiking 🥾 with my sweet family 👨‍👩‍👧‍👦.

I bring drive, curiosity, and compassion to everything I do!

---

🧰 Tech Stack

Category	Technologies
Frontend
Core
Mobile
Cloud
DevOps
Testing
Misc
Editors

See ➡️ Full Tech Stack, for a list of projects using each of the above technologies

---

📊 Metrics

	-

➡️ More Metrics

✨ Recent Activity

1. ❗️ Opened issue #4 in sllozier/cmsc215_project2
2. ❗️ Opened issue #3 in sllozier/cmsc215_project2
3. ❗️ Opened issue #2 in sllozier/cmsc215_project2
4. ❗️ Opened issue #1 in sllozier/cmsc215_project2
5. ❗️ Closed issue #2 in sllozier/bookshelf-app

➡️ More Activity

honor_evaluator's Issues

Testing Requirements

I must have both positive and negative tests for each class:

StudentTest:

• Positive Test 1
• Positive Test 2
• Positive Test 3
• Negative Test 1
• Negative Test 2
• Negative Test 3

UndergraduateTest:

• Positive Test 1
• Positive Test 2
• Positive Test 3
• Negative Test 1
• Negative Test 2
• Negative Test 3

GraduateTest:

• Positive Test 1
• Positive Test 2
• Positive Test 3
• Negative Test 1
• Negative Test 2
• Negative Test 3

Project2Test:

• Positive Test 1
• Positive Test 2
• Positive Test 3
• Negative Test 1
• Negative Test 2
• Negative Test 3

Complete README

Items to add to README

• Personalize User Guide
• Format title area
• Add UML
• Add contact information
• Add helps section

Code Review

Complete code review

Project Structure and Config:

• Follows Maven's standard directory layout.
• pom.xml correctly configured (groupId, artifactId, version).
• Dependencies necessary, up-to-date, and conflict-free.
• Proper plugin configurations.

Code Quality:

• Code readability and maintainability
• Adherence to coding standards.
• Effective error handling and logging.
• Adequate unit test coverage.

Build Process:

• Efficient build steps.
• Correct Maven lifecycle phases.
• Valid custom build scripts/modules.

Dependency Management:

• Appropriate dependency scopes.
• No unused/outdated dependencies.
• Necessary dependency exclusions.
• Check for security vulnerabilities in dependencies.

Documentation:

• Updated pom.xml and project documentation.
• Adequate inline comments and documentation.

Performance:

• Maven configuration optimized for performance.
• Configuration for parallel builds, if applicable.

Security:

• No security vulnerabilities in dependencies.
• Sensitive data properly secured.

Code Complexity:

• No overly complex methods/classes.
• Static code analysis to identify issues.

Best Practices:

• Adherence to Maven best practices.
• Easy for new developers to understand/setup.

Comments

More detailed comments to code:

• student-data-module: StudentData.java, StudentDataTest.java
• main: Graduate.java, Project2.java, Student.java, Undergraduate.java
• test: GraduateTest.java, Project2Test.java, StudentTest.java, UndergraduateTest.java