Software DevelopmentAPI Contracts and Status Codes for Order Processing
Software Developer
Document the request shape, response shape and expected errors for each endpoint. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentState Machines and Transitions for Order Processing
Software Developer
Define valid states and check each proposed transition against the current state. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentRetries and Duplicate Events for Order Processing
Software Developer
Use a stable event or request identifier to recognize previously handled work. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentSQL Queries and Reconciliation for Order Processing
Software Developer
Define the grain of a query and reconcile its output against known fixture totals. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentUnit and Integration Testing for Order Processing
Software Developer
Use isolated tests for decisions and integration tests for behavior across system boundaries. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentDebugging and Observability for Order Processing
Software Developer
Reproduce the issue, trace the request through each stage and record the first point where behavior differs. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentCode Review and Release Readiness for Order Processing
Software Developer
Review changes against requirements and run the affected checks before release. Practice with a paid order, a canceled order and a retried request.
10 lessons · Portfolio project
Software DevelopmentRequirements and Acceptance Tests for Support Ticket Systems
Software Developer
Translate a requirement into observable inputs, outputs and edge cases. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentData Modeling and Relationships for Support Ticket Systems
Software Developer
Choose stable identifiers and represent relationships with explicit keys. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentInput Validation and Error Handling for Support Ticket Systems
Software Developer
Validate at the boundary and return a clear error before changing state. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentAPI Contracts and Status Codes for Support Ticket Systems
Software Developer
Document the request shape, response shape and expected errors for each endpoint. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentState Machines and Transitions for Support Ticket Systems
Software Developer
Define valid states and check each proposed transition against the current state. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentRetries and Duplicate Events for Support Ticket Systems
Software Developer
Use a stable event or request identifier to recognize previously handled work. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentSQL Queries and Reconciliation for Support Ticket Systems
Software Developer
Define the grain of a query and reconcile its output against known fixture totals. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentUnit and Integration Testing for Support Ticket Systems
Software Developer
Use isolated tests for decisions and integration tests for behavior across system boundaries. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentDebugging and Observability for Support Ticket Systems
Software Developer
Reproduce the issue, trace the request through each stage and record the first point where behavior differs. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentCode Review and Release Readiness for Support Ticket Systems
Software Developer
Review changes against requirements and run the affected checks before release. Practice with five tickets including a missing owner and one unknown priority.
10 lessons · Portfolio project
Software DevelopmentRequirements and Acceptance Tests for Learning Progress Systems
Software Developer
Translate a requirement into observable inputs, outputs and edge cases. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project
Software DevelopmentData Modeling and Relationships for Learning Progress Systems
Software Developer
Choose stable identifiers and represent relationships with explicit keys. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project
Software DevelopmentInput Validation and Error Handling for Learning Progress Systems
Software Developer
Validate at the boundary and return a clear error before changing state. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project
Software DevelopmentAPI Contracts and Status Codes for Learning Progress Systems
Software Developer
Document the request shape, response shape and expected errors for each endpoint. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project
Software DevelopmentState Machines and Transitions for Learning Progress Systems
Software Developer
Define valid states and check each proposed transition against the current state. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project
Software DevelopmentRetries and Duplicate Events for Learning Progress Systems
Software Developer
Use a stable event or request identifier to recognize previously handled work. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project
Software DevelopmentSQL Queries and Reconciliation for Learning Progress Systems
Software Developer
Define the grain of a query and reconcile its output against known fixture totals. Practice with two learners, three lessons and one repeated completion event.
10 lessons · Portfolio project