Update tutorials #485
Replies: 6 comments 2 replies
-
|
Here's the summary @KimberleyCook and I discussed so far. AimsFirst, I would like to ensure we all agree on the aims of the tutorial update.
Proposed lesson planThis lesson plan attempts to keep as much of the current HTML+CSS tutorial as possible and then make the back-end tutorial work on top of it by adding more capabilities to the project. I moved some concepts to bonus lessons to streamline the core lessons while giving students the ability to dig deeper onto specific subjects. I also pointed at places where we could use an external tutorial in place of or to complement our own. This is not an exhaustive list, there may be more.
QuestionsSome questions I had when writing this document.
|
Beta Was this translation helpful? Give feedback.
-
|
This looks great @brunogirin . Some suggestions:Part 2: Back-end:
Questions:How do we deal with Python for back-end vs Python for data science?
My Opinion on the below: Focusing on technologies we know well for which the tutorials will not require frequent updates:
pointing to external tutorials for the rest and to support our tutorials with additional content;
Reduce barriers to entry by making it possible to get started without having to install anything on the student's laptop;
Provide ways to go further through external tutorials;
Bind everything in a coherent development story.
|
Beta Was this translation helpful? Give feedback.
-
Yes, that was the idea of lesson 8 in part 2, section 2 but we could have a mini-project after lesson 5 indeed.
Yes, good point! Also Poetry makes this easy to set up.
I started with just Python but @KimberleyCook pointed out that the codebar web site is built in Ruby and is potentially a good project for people to contribute to. So it comes back to what we want the tutorials to be. One option would be to focus on Python but have a chapter on Ruby in the "other languages" lesson.
Well, that's the first thing we need to decide on! If we want to help move the needle on diversity in tech, we need to give an onramp to finding a job in tech, for those who want. So when I created this, I had in mind that parts 1, 2 and 3 combined cover what someone would need to apply for a junior dev position at a company like mine.
No indeed. My intention here was to make it possible, not to force it.
Yes indeed. That's why I ended up moving data science to part 4. |
Beta Was this translation helpful? Give feedback.
-
|
I think we need to know more about what's useful to our students. But something else I wanted to add is a page for resources, like virtual dev environments, and particularly code kata sites, like codewars, so they can practice what they learn. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, totally agree with a page of resources! Regarding virtual dev environments, I toyed with the idea of adding a lesson on this but every time I think about the subject, I over-complicate it so I am open to any suggestions on the subject. |
Beta Was this translation helpful? Give feedback.
-
Discussion at uncodebar 10 on 21 Sep 2024NeedsStudentWhat do you expect from codebar?
Maintainers
Suggestions
Governance
|
Beta Was this translation helpful? Give feedback.
-
Discussion during Organiser meeting on Thursday 26th SeptemberAt the end of relevant lessons, add a "Your Turn" section where we suggest ways the student could improve or amend the project:
Suggestions not discussed during the meeting:
@mikejeuga @KimberleyCook please add if you think I missed anything important that we discussed |
Beta Was this translation helpful? Give feedback.
-
Part 0: orientationWould an initial orientation part be useful? Possible scope of such a part:
|
Beta Was this translation helpful? Give feedback.
-
This is the start of a discussion with @brunogirin about updating the codebar tutorials
Beta Was this translation helpful? Give feedback.
All reactions