Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • JavaChallenge JavaChallenge
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Jobsity
  • JavaChallengeJavaChallenge
  • Wiki
  • Java Challenge

Java Challenge · Changes

Page history
Update Java Challenge authored May 20, 2021 by Jobsity Admin's avatar Jobsity Admin
Show whitespace changes
Inline Side-by-side
Showing with 0 additions and 3 deletions
+0 -3
  • Java-Challenge.md Java-Challenge.md +0 -3
  • No files found.
Java-Challenge.md
View page @ 2af46f05
...@@ -114,9 +114,6 @@ Carl 10 ...@@ -114,9 +114,6 @@ Carl 10
- SRP: Single Responsibility Principle (Classes are self contained. They do the task they need to do and nothing else). - SRP: Single Responsibility Principle (Classes are self contained. They do the task they need to do and nothing else).
- Liskov’s Substitution Principle: Interfaces (OOP, Swap principle.. Makes the program able to be extended). - Liskov’s Substitution Principle: Interfaces (OOP, Swap principle.. Makes the program able to be extended).
- Dependency Inversion Principle: Code should depend on interfaces, no concrete implementations. - Dependency Inversion Principle: Code should depend on interfaces, no concrete implementations.
- Coupled code: If code has too few classes we should not accept this candidate, even if the program works perfectly. Code violates SRP, classes demonstrate mixed concerns. Bad OOP in general.
- Abuse of static and singleton: Usually this indicates a junior candidate since this makes difficult to use the Substitution Principle.
- Duplicated code: Reused code should be encapsulated.
- Include well-known libraries and good use of the JDK API. - Include well-known libraries and good use of the JDK API.
- Build mechanism (gradle, maven, shell, NO IDE). Program should compile and run out of the box. - Build mechanism (gradle, maven, shell, NO IDE). Program should compile and run out of the box.
- Packaging complete. Zip should contain a readme file explaining how to compile the project, and contain the test text file to check the output - Packaging complete. Zip should contain a readme file explaining how to compile the project, and contain the test text file to check the output
......
Clone repository
  • Java Challenge
  • Home