-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find a way to keep "objectives" folder contents up-to-date (possibly automation) #1210
Comments
cc @gsong @MichelleGlauser @alodahl for their input |
I agree that a half sheet with simple visuals would be more effective. Not sure what "general curriculum summary doc" refers to, since the link is blank. |
@gsong sorry fixed the link. It's a google doc someone made: https://docs.google.com/document/d/1Pr44pAKmq0NvfFiFEtqULzHPBZQnNsc6o040Qd4XxiE/edit that we share with potential sponsor companies |
A suggestion on the document you're creating (and this may already exist), I would also talk about what are some appropriate roles or specific tasks you feel a Techtonica apprentice would be able to perform by the end of the program. I'm not as interested in what they've learned (other than broad strokes) vs. what can they realistically do for my organization. Hope that makes sense. |
Hi @vegetabill , we discussed this over hangouts, but for the record:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
After discussing, we've decided to keep the objectives folder and contents, but we need a way to keep them in sync. One Solution:
we can try embedme, which we used at gap and it seems to work great: https://github.com/zakhenry/embedme.
Original issue:
The objectives files are aggregated from all of the individual lesson files. Michelle said the audience for these was the SEAM and sponsor companies who wanted more details beyond the general curriculum summary doc. (admin only)
IMHO, these files are not very valuable to either audience group due to being overly detailed. Because they are duplicated data, they will also always be out of date and a maintenance burden. I suggest we remove them. If engineering orgs need more details, we should just direct them to the root README which gives detail and links for the contents. Any SEAM will need to build their own mental of the curriculum, which I plan to help by building something more visual/high-level (see #1209 )
Discuss...
The text was updated successfully, but these errors were encountered: