c0d3-app

it is open source: https://github.com/garageScript/c0d3-app It used to be closed source, but it was only because I wasn't confident about the quality of the codebase. Now it is much better. > My personal experience when I was a gsoc admin was that it was hard to get the students stick around after the end of the summer, do you manage and have some tips to share? First you should realize that some people just don't really see the point in coding. These people are just going to wander off. The ones who are dedicated though, its important to spend time to talk to them and make sure your project aligns with their goals. Then they will contribute above and beyond. Our project mission is simple because most students want an engineering job: Working on c0d3.com repository will not only help you gain the skills as a software engineer, it also cou

> software engineering is more than code. Software developers live, breathe, and puke software development. 100% agree. Which is why its important that students are working together on projects so they can write specs, documentation, tests and structure code in a way that the next engineer can take over easily. Our weekly sprint planning helps facilitate that. Take this PR for example, it has tests and went through 15+ comments and approved by 2 other students before it got merged in: https://github.com/garageScript/c0d3-app/pull/243 I think your are thinking of a curriculum that just teaches students how to code and then have them build side projects by themselves and show it off. And I agree, that is not software engineering, it is just code.

we got a sentry.io alert of an error, we think this may be you. filed a bug: https://github.com/garageScript/c0d3-app/issues/244

Exactly. Which is why c0d3.com emphasizes understanding users and working together as a team. All code contributions are code reviewed and there is code coverage: https://github.com/garageScript/c0d3-app/pulls?q=is%3Apr+is%...

Good suggestion! One of the students took a first stab with this PR to build a contributors page to featur students who have contributed features and are looking for a job: https://github.com/garageScript/c0d3-app/pull/227 If anyone has better ideas, please share!

Last year, I mentored a few students who are learning coding to become a software engineer from non-traditional backgrounds. Rather than encouraging them to leetcode and practice for interviews, I taught them software engineering practices and mentored them to build c0d3.com together as a team. c0d3.com will be a free learning site where other students like them can learn coding and then help improve the site. As a senior engineer, I made sure to not write any code myself and focused on helping them with code reviews, architecture questions, and holding sprint meetings every Monday at 9:30pm. We document our daily sprint updates here: https://github.com/garageScript/c0d3-app/wiki/Sprint-H1-2020 To get beta users for our app, we started a free coding group at our local libraries and got a few dozen active users: https://www.meetup.com/San-

Last year, I mentored a few students who are learning coding to become a software engineer from non-traditional backgrounds. Rather than encouraging them to leetcode and practice for interviews, I taught them software engineering practices and mentored them to build c0d3.com together as a team. c0d3.com will be a free learning site where other students like them can learn coding and then help improve the site. As a senior engineer, I made sure to not write any code myself and focused on helping them with code reviews, architecture questions, and holding sprint meetings every Monday at 9:30pm. We document our daily sprint updates here: https://github.com/garageScript/c0d3-app/wiki/Sprint-H1-2020 To get beta users for our app, we started a free coding group at our local libraries and got a few dozen active users: https://www.meetup.com/San-

I've been teaching coding (on the side) and doing software engineering for the past 10 years. There's a recent surge of self learners who believe in studying coding the way they believe should be studied (which is ironic, given how little experience they have). The moment they got a job, they turn around and proudly talk about "This is how I did it, you learn x, y, z and you can get a job like me" and influence the next batch of self learners. Bootcamps also buy into this ideology. Instead, the engineers I appreciate on my team has very little to do with what they know. Instead of hiring engineers who only cares about the latest and greatest, I value engineers who: communicate openly, write good tests, and cares about the product enough to fix bugs without having someone create a jira ticket for them, and has good debugging skills. When I

"Learn to Code" is very different from learning to become a good, reliable software engineer. The skillsets are very different. I think alot of technical schools are optimizing for "Learning to Code" with modern frameworks used at work, leaving much to be desired if I want to hire a bootcamp graduates. I'm experimenting with a system where students only learn the bare minimum and built up what they know by asking questions and working together as a team to build a product with the intention that another student will take over their product one day. This mimicks an engineer's workflow better: asking questions because documentation is lacking, working with other engineers, being receptive to feedback, writing code with the intention of somebody else taking over your code, etc. It seems to work so far, the last batch of students did some rea

My journey to rediscovery the joy of programming started at a local FreeCodeCamp meetup group. I simply showed up every meeting and got to know some of the regular students. I helped them with problems that were simple for me, but explaining concepts creatively to them was a very interesting experience. The students needed a project to show on their resume so I got together with them to have weekly sprints like a mock engineering team. I taught them good coding practice and slowly built up an engineering team of student engineers during my free time. It helped me rediscover engineering practices and finding open source tools that mirror what I use at work is really eye opening and made me a stronger engineer at work. I understand things with a greater depth. I don't contribute any code, I just code review, do product planning, and conduct