~/meetings / 2025-10-02
Meeting #2

> 2025-10-02

Two new faces joined — Whit demoed Brindl and walked through Next.js live, Los shared his Firebase sales tracker. Group reviewed last meeting's ideas, chose the volunteer/community opportunity board as the first project, and brainstormed its structure. Agreed to move to biweekly meetings.

3 attendees(Whit, Los, Sean)
##topics covered
  1. 01.AI coding assistants and the limitation of outdated/deprecated API knowledge (Grok discussed as more current)
  2. 02.Whit demos Brindl — React component architecture walkthrough, mobile view
  3. 03.Los demos his sales tracking app built for his brother's business — Firebase backend, built using Cursor
  4. 04.Cursor AI editor overview — VS Code-based, stronger AI integration than Copilot
  5. 05.React vs React Native — component-based architecture, reusability
  6. 06.Go (Golang) as a backend language — interest expressed
  7. 07.Live Next.js scaffold walkthrough — file-based routing, layout file, components folder
  8. 08.Tailwind CSS explained — utility classes vs traditional CSS files
  9. 09.JSX/TSX explained — HTML-returning functions, TypeScript vs JavaScript typing
  10. 10.Review of last meeting's ideas: volunteer board, FAST suggestion tool, Cooking Connections recipe log
  11. 11.New idea: returns tracking tool — standardized item-by-item return flow instead of everyone doing it differently
  12. 12.Group picks volunteer/community opportunity board as the first project to build together
  13. 13.Brainstorm: board structure — upcoming events feed, past events section, RSVP without login, post-event photo recaps, admin-only posting
  14. 14.Game engine discussion: Godot, Unity, Game Maker Studio, Dreams (PlayStation)
  15. 15.Meeting format discussion — alternating discussion and build sessions, biweekly cadence
##decisions & next steps
  • →Volunteer/community opportunity board chosen as the first group project
  • →RSVP will require no account — just name and partner number
  • →Admin-only event posting to keep content controlled
  • →Homepage: upcoming events feed at top, past events below, post-event photo recaps
  • →Whit will build the basic foundation on his own time; group adds features at future meetings
  • →Move to biweekly meetings, alternating between discussion and build sessions
  • →Meetings stay during work hours — store-approved and keeps it accessible
← meeting #1meeting #3 →