codeHub is a platform where coders can learn, code, and share.
codeHub’s goal is to create and maintain a comprehensive directory of open source libraries, and help people discover new open source projects to contribute to.
Open Source Libraries:
The library feature allows you to submit an open source library that you’ve just published on GitHub or elsewhere. A good library is one that has broad usefulness for other developers, or at least for you; has well-defined scope; and is well-documented. The most popular libraries are those that are useful across various domains, like json_pure for parsing JSON, or sequel for connecting to databases.
Submit a Library:
If you know of a great library that’s not in the directory yet, please submit it! Just make sure it meets the criteria above. If the library is yours, make sure to set your repository as public so we can see its documentation; if it’s someone else’s, put in the URL so we know what language it’s written in.
We do our best to approve all submissions within 48 hours (usually much less).
CodeHub is a platform where coders can learn, code, and share.
Our mission is to empower you to code the future. We believe everyone should be able to contribute to open source projects, and we make it easy for you to contribute from any device.
You can use our desktop app (currently only available on Mac) to clone a project from any repository on GitHub.com or create a new project from one of our starter templates. You’ll also be able to push your changes back to GitHub with a single click.
We’re excited about the potential for this technology and we can’t wait to see what you build with it!
CodeHub is a platform where coders can learn, code and share. By using CodeHub, you can learn code by viewing the contributions of other coders from around the world. You can also share your contributions with others and get feedback to help you improve.
CodeHub is a place to become better at coding and to find opportunities.
CodeHub is a place for like-minded people to come together and develop their skills while enjoying their craft.
codeHub is a broad technology platform that includes both web and mobile products.
codeHub helps programmers learn and share their knowledge, as well as write code together.
coders can find jobs, get hired, and collaborate on open source projects.
CodeHub is a platform where coders can find mentors, share their code, and learn. You can also check out the style guide for this project.
Our goals for CodeHub is to provide a space for coders to connect and grow. CodeHub is an open source community that welcomes all levels of coders. We are excited to see what you build!
We’re looking for talented programmers who enjoy solving challenging problems, writing excellent code and building an ambitious platform.
We use Ruby on Rails, React, Redux, PostgreSQL and a variety of other tools to help us do our best work. We write clean code supported by unit tests and interact with well-designed APIs. And we deploy multiple times a day.
We’ve built a collaborative culture with regularly shared learnings from the challenges we’ve faced and the solutions we’ve developed.
We have an office in San Francisco’s Mission District with free snacks, occasional catered lunches, and team events ranging from happy hours to game nights to company offsites. But if you prefer to work remotely, that’s totally fine too!
If this sounds like you, we’d love to hear from you!
Building software is like building a house. In the early phases you need to do some preliminary work: clear the site, lay bricks, put in doors and windows. But until the roof is on, you can’t really use it for much except storage.
Similarly, in software, it’s tempting to write code that does first-order things – like grab a user name from a login screen and look it up in a database – as soon as you think of them. But until you’ve built higher-level components, ones that do something a user would notice, it’s hard to test what you have or say whether it’s any good.
So while I was doing this groundwork, I used to pester Paul with questions like “What are we going to do next?” Sometimes he’d have an answer ready; sometimes he’d have to think about it.
Over time we realised we were facing two related problems. One was deciding what order to build things in; the other was knowing when each feature was done. The former problem had no obvious solution because we didn’t know enough about programming yet to tell which features would be easy and which hard. The latter problem seemed easier: until something met our standards of quality, it wasn’t done. But how high were