Yuri and Miguel Meeting: Content × Form, Study Method and Learning Experiences (login/authentication), with a warm-up about games for next week.
Objectives
- Create the Alpha Scholars universe — a subject that Miguel wants to address (watch videos, write text). This is the destination of the 22 hours weekly (see §1).
1. Content × Form
- Content: mse, app. Form: schedule, commitment.
- Weekly load: 4 hours for ArteLonga, 22 hours for the Alpha Scholars.
- Deliveries on Fridays at 4 PM (or every two weeks).
2. Content (method)
- Learnings.
- Method: study about open source, open code and free software.
- Open source misses the point
- GNU Project Philosophy
- Comparison of common licenses: MIT and GNU GPL.
3. Experience: login and authentication (case study)
- Learn as a user.
- Structure feedback (suggestion →
feat, problem → <<<5>>, etc.):- Conventional Commits
- Semantic Versioning
- Login to GitHub.
- Next week: experience of internationalization.
4. Weekly study: open code × free software
Starting point — what Miguel already knows (learned at SENAI, without additional research):
- Open source software: direct access to what is being produced — allows modification.
- Free software: free access (free), but no access to the code.
GNU perspective (to contrast next week): for the GNU Project, free software is about freedom, not price — freedom to execute, study, modify and redistribute, which presupposes access to the source code. It is precisely the thesis of “open source misses the point”: “open source” emphasizes practical advantages; “free software”, the ethical question of freedom.
Open question (weekly study): reconcile the two readings — after all, what is the difference between open code and free software?
5. Next week — warm-up: Games
Miguel’s game history (timeline):
- First contact with video games: Xbox 360 — Assassin’s Creed IV: Black Flag.
- Two days ago: Naruto Shippuden: Ultimate Ninja Storm 4.
- Metal Gear Solid V — “that’s why I like it”.
- Minecraft (mods Mekanism and Create).
Other notes
- Trying to manually measure the time spent on each task.
- Explanation cycles: explain a feature and stop for questions → “root”.
- Ideal user experience.