Labs Learners Guide
Last updated
Was this helpful?
LAMBDA_LABS_Family_Promise
Last updated
Was this helpful?
This guide contains information, policies, and guidelines specific to Labs. You should still refer to and comply with all of the information, policies, and guidelines in the . For example, the Lambda School and the do still apply and must be adhered to while in Labs.
You should bookmark this page as it will be very useful for you during your time in Labs.
Please be aware that infrastructure components for Labs projects will not be maintained after you complete Labs. This includes online servers and domain names. You should expect your application to either stop working or drastically change (as new teams continue to make enhancements) soon after your Labs session ends. All learner-developed source code is released under the MIT license, so if you want or need to your application to be running after Labs, you can fork the repository and deploy to the infrastructure of your choosing.
Please do not link to your Labs project on your resume as those links will likely be broken soon after Labs ends!
See the FAQ in the ‣ section for more details.
Documents to help your team succeed in Labs
How you'll use Trello for project management
A guide to ensuring a productive stakeholder meeting
A checklist to ensure your engineering architecture is sound and complete
A template for your team to use to create helpful pull requests
A rubric to use when evaluating how you're team is doing with pull-requests
All about the Student Peer Review program
Crucial items when you're close to the finish line each sprint!
Documents to help you succeed in Labs
A glossary of terms you'll hear in Labs
How do I stay in the know?
Specialize in a real industry role
Walk through your work with every pull request
Special live sessions with staff
What you need to know about your Learner Profile
All you need to know about Labs Roundtable
One of our most frequently asked questions
A list of the critique sessions that will take place during Labs
Labs Managers meet with TPMs on each product near the start of each sprint to review and critique the sprint scope they've set for their team.
An Engineering Manager walks through a few representative pull requests as case studies once per sprint.
Design Leads meet with the Design Manager at least once per sprint to present design planning for group discussion.
All teams on each product and that product's TPMs meet with Labs managers near the end of each sprint to present progress, blockers, and a path forward.
Who you gonna call?
If you need technical support from a Labs Manager, you can use the daily pulse check module in Canvas or you can contact specific managers as outlined below
24/7 Hotline support for emotional distress: 1-800-273-8255 (TALK)
Note: I called them, they are here to talk, to listen, and help people find local resources for dealing with suicide crises, suicidal ideation and any kind of emotional distress. The representative I spoke with recommended not being cautious with referring people to them, and made a point to reassure that asking if someone is considering self-harm is not a trigger for them to cause self-harm.
Crisis Text Line: Text "START" to 741-741
-
Online Chat: