Climb Credit (NMLS# 1240013) is an innovative student financing and payments platform that makes career creation and transformation more accessible, affordable, and accountable than ever before.
Driven by a mission to empower individuals to unlock their career potential – no matter what their credit profile – Climb identifies programs and schools with a demonstrated ability to improve the earnings of their graduates.
Then they provide learners with financing and payment options that are priced and structured to meet the unique needs of those seeking career elevation and increased earning power.
Recognizing the dynamic and diverse nature of an economy in rapid change, Climb partners with schools that teach everything from cybersecurity to healthcare, heavy machine operation to data science, and culinary arts to coding.
While some colleges are struggling to meet the real-world needs of their students, Climb and its partner schools are committed to an inspiring practicality that brings real career results as individuals Own Their Next chapter.
Leave things better than you found them
a. We own the code, even the crappy parts. Every time we touch something, we make it better for our future selves.
Keep moving forward
a. If it’s better than what’s in production, bias to moving forward.
b. That doesn’t mean releasing buggy code; it means good is better than perfect.
c. Don’t rush - do things as fast as you can but no faster
a. Err on the side of over-communicating, but realize that people’s time is important
b. Ask questions
c. No topic is off limits
Support your teammates
a. Help review each other’s code, test each other’s branches
b. Be willing to reassign tasks per scheduling constraints
a. Work/life: It’s a demanding job. Keep yourself mentally fresh. Understand how you work best so we can create the ideal conditions for you and the team.
b. Code updates: Over-scoping is better than under-scoping, but don’t let it paralyze you. Be balanced when ‘leaving it better than you found it.’ A quick refactor or rearrangement is good, but a full rewrite of something should be its own project.
c. Learn new tools, but choose when to use them wisely
a. When doing something, think about how much work it’ll take for you (or someone else) to repeat it. There’s usually something you can do to make that easier.
a. Document your code. Over-documentation is better than under-documentation.
b. Self-documenting code is best. Comments can lie, code (usually) doesn’t.
Develop as a developer
a. Teach what you learn
b. Learn and adapt