Yuri × Miguel meeting: content × form, study method and learning experiences (login/authentication), with a warm-up on games for next week.
Objectives
- Create the Alpha Scholars universe — a topic Miguel would like to cover (watching videos, writing text). This is the destination of the 22 weekly hours (see §1).
1. Content × Form
- Content: mse, app. Form: agenda, commitment.
- Weekly load: 4h for ArteLonga, 22h for Alpha Scholars.
- Deliveries on Thursdays at 16h (or every two weeks).
2. Content (method)
- Learnings.
- Method: study on 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 the user.
- Structure feedback (suggestion →
feat, issue →fix, etc.):- Conventional Commits
- Semantic Versioning
- GitHub login.
- Next week: experience with internationalization.
4. Weekly Study: open source × free software
Starting point — what Miguel already knew (learned at SENAI, without further research):
- Open-source software: direct access to what is being produced — it can be modified.
- Free software: free access (gratuitous), 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 run, study, modify and redistribute, which implies access to source code. It is precisely the thesis of “open source misses the point”: “open source” emphasizes practical advantages; “free software”, the ethical issue of freedom.
Open question (weekly study): reconcile both readings — after all, what is the difference between open source and free software?
5. Next week — warm-up: Games
Miguel’s story with games (timeline):
- First contact with video games: Xbox 360 — Assassin’s Creed IV: Black Flag.
- The day before yesterday: 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 pause for questions → “root”.
- Ideal user experience.