Meeting yuri × Miguel: 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 explore (watching videos, writing text). This is the destination for 22 weekly hours (see §1).
1. Content × form
- Content: mse, app. Form: schedule, commitment.
- Weekly load: 4h for ArteLonga, 22h for Alpha Scholars.
- Deliveries every Thursday at 4pm (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 by being the user.
- Structure feedback (suggestion →
feat, problem →fix, etc.):- Conventional Commits
- Semantic Versioning
- Login on GitHub.
- Next week: internationalization experience.
4. Week’s study: open source × free software
Starting point — what Miguel already knew (learned at SENAI, no additional research):
- Open source software: direct access to what is being produced — you can modify it.
- Free software: free access (free of charge), but without access to the code.
GNU perspective (to be contrasted this week): for the GNU Project, free software is about freedom, not price — freedom to run, study, modify, and redistribute, which presupposes access to the source code. This is precisely the thesis of “open source misses the point”: “open source” emphasizes practical advantages; “free software”, the ethical question of freedom.
Open question (week’s study): reconcile the two readings — after all, what is the difference between open source and free software?
5. Next week — warm-up: Games
Miguel’s history with games (timeline):
- First contact with video games: Xbox 360 — Assassin’s Creed IV: Black Flag.
- Day before yesterday: Naruto Shippuden: Ultimate Ninja Storm 4.
- Metal Gear Solid V — “that’s why I like it”.
- Minecraft (Mekanism and Create mods).
Other notes
- Trying to manually measure time spent on each task.
- Explanation cycles: explains a feature and stops for questions → “root”.
- Ideal user experience.