W1D1 - Getting Started - End-to-end working in IT - Agile - Jira - Git - AWS - Log-Unittesting[8Jun]
✅ W1D1 - Getting Started - End-to-end working in IT - Agile - Jira - Git - AWS - Logging - Unittesting [8Jun]
Join below channel
https://whatsapp.com/channel/0029Va4q...
📌 Recording:
https://youtube.com/live/RiyU871SpX8?...
📌 Session notes
https://docs.google.com/document/d/1e...
📌 Attendance Code: 7777
https://docs.google.com/forms/d/e/1FA...
📌Other links:
Jobhunting System
https://www.tausiefs.com/learn/JobSee...
Central Whatsapp Channel
https://www.whatsapp.com/channel/0029...
https://roadmap.sh/backend
📌Key Points: Agile SDLC, Git Workflow & Production Development Lifecycle
✅ Agile development is executed through Jira-managed sprints. Requirements are created as user stories, discussed in grooming/refinement meetings, clarified with the Product Owner, estimated using story points, and planned into sprint cycles.
✅ Architecture discussions happen before coding. Teams decide microservices structure, database choices (SQL/NoSQL), communication patterns (REST or messaging), caching, scalability, and security requirements before providing estimates.
✅ Industry-standard Git workflow uses a centralized repository with main → develop/integration → feature branches. Developers create feature branches, clone code locally, implement changes, and push updates through pull requests.
✅ Production-grade backend development follows layered architecture: Controller → Service → Repository → Model. Local API validation is performed using tools like Postman/Swagger, while logging is implemented using SLF4J and Logback instead of System.out.println.
✅ Code promotion flow: Local Development → Unit Testing (JUnit/Mockito) → Dev Environment → Code Review → Integration Branch → QA Testing → UAT → Production. Every change requires code review and validation before reaching the production environment.