Can you do me a solid and go to your learning tab, and copy and paste all your classes so I know the order and term they're in? I'm appreciate it! Also - how many tracks of business do we have as well as AI and Engineering? Let me know below so I can be as accurate as possible? If there is more than one track, I'll comment and ask you to do the same so I can get these study guides generated with Maestro! Thank you in advance! EXAMPLE: I'm in AAS for AI Software Engineering so I'll get this for the copy and paste and yours should look similar: [LONG PASTE] (Academic year 1 Term 1 Jan 05 - Mar 23 PY101 · Introduction to Python programming 4 credits Jan 05 - Feb 02 PSYC100 · General psychology 4 credits Feb 02 - Feb 16 CS101 · Software engineering principles 4 credits Feb 16 - Mar 16 Term break Mar 16 - Mar 23 Academic year 1 Term 2 Mar 23 - Jun 08 CS102 · Data structures & algorithms

I'll have full notes and study guides for all classes in both Business and AI uploaded to the virtual campus by Friday, that will satisfy each learning. style! Stay tuned and if you haven't already, join us (still in alpha and zoom API integrations aren't set up yet) @ https://maestro-campus-link.base44.app (from your computer, refresh the browser if you hit an error) and skip through the 24 Q test if you want (they'll be changed soon to personality/learning style quizzes for mentor matches and so much more)! With Claudia integrated next month (a project showcase portfolio manager for each user), the student body can very well help save Maestro's standing by coming together and building this TOGETHER! Trust in each other, and trust in our school!

You may (or may not!) have seen some little pet projects I've shared previously. Well, here's another (and relevant, for once!) https://trackrabbit.github.io/maestro-notes/ What is it? My notes, formatted. Each module is divided into weeks (*note - Maestro continues numbering and skips break weeks. Since this would be inconsistent per cohort, my numbering schema is Week 1, Week 2, etc., restarting at each module.) Pre-formatted .PDF Handouts are available via the aptly named "Download as PDF" button. What isn't it? It's not a cheat sheet. There are no answers to reviews, exams, or finals. And there won't be. Known Issues: - Formatting inconsistencies: I rewrote my Python script that generates the PDF using a different library (from weasyprint to ReportLab) about midway through. I have an action item to regenerate the earlier PDFs so they are consistent. *Note - I'm pre-creating the PDFs instead of calling the system print function because it doesn't respect formatting. Tooltips are collapsed, etc. It was ugly, and my OCD/ADHD wouldn't allow it! ReportLab is an open-source Python library used for generating PDFs and graphics. It can translate the raw HTML and produce an identical PDF document (with a little CSS trickery!) - I recognize the cold, clinical nature of the site. I'm considering implementing my Mood button! (Shameless feel-good vibe code!) *** This is a big work in progress! I have about 3 or 4 modules to do (a separate page/PDF for each week of the module). My daily sprint is 2 weeks a day, but being my own project manager means I can approve missing my deadline! As I'm in Computer Science - AI Engineering, my notes are just for that track. Maybe, if someone is willing (and more importantly, if there is any interest), I can implement the Business track as well, using their notes as a source. If you happen to click around, please let me know of any issues. Broken links, formatting, etc. I have a punch list but want to catch 'em all.

So I’ve been behind on posting my notes. 🤦🏼‍♀️ I was sick and got behind in coursework and started trying to get my notes done as I was working through it… Then ChatGPT (the app version I’ve always used) started being a butthole 😂 It kept telling me it didn’t have access to the tools it needed and apparently didn't want to help me make my notes. 🥴😅 The web version is immensely better and worked for me, thankfully!! I was ready to cry, tbh. But I have everything up to week 3 of CS102 posted. I’m working on finishing up Week 4 and it will be up soon!! But everything is updated in my linktree now!!! So sorry for anyone that it inconvenienced with them not being posted sooner! Just happy I’m able to get them done again. I spent WEEKS trying to get the app to make them, talking in circles with it. Ugh!! Oh well! Lesson learned to just use the web version from now on! Here’s the link again if anyone needs it! https://linktr.ee/madison.page87

Let's talk about WBS! A Work Breakdown Structure (WBS) is a way to break a project into smaller, manageable pieces of work. It helps you organize the project by showing: ~the major parts of the project ~the smaller tasks inside each part ~what work has to be completed to finish the project Think of it like taking one big project and turning it into a step-by-step hierarchy. Simple way to think about it: If the project is “Set up a fundraising event”, the WBS answers: ~What big sections of work need to happen? ~What smaller tasks belong under each section? ~How can we organize the project so nothing gets missed? Key idea of a WBS A WBS is usually organized from top to bottom: Level 1: The entire project Level 2: The main deliverables or major work areas Level 3: The smaller tasks/subtasks under each work area Sometimes it goes even deeper if needed. Deliverable vs Task vs Schedule - Deliverable = thing/result - e.g., “Final survey questionnaire”, “Clean response dataset”, “Member feedback summary report” - Task = action - e.g., “Draft survey questions”, “Send survey emails” - Schedule item = action + time - e.g., “Send survey emails on March 3” WBS focuses on deliverables + the work that creates them, not on dates or who does it. Good WBS elements (what “good” looks like) - Deliverable-based: named as a thing, not a verb string - Better: “Survey instrument finalized” - Weaker: “Work on survey questions” - Clear and specific: someone can tell what is “done” - Estimable and assignable: small enough that you could (in theory) estimate it and give it to a person Analogous estimation = using a past, similar task (analogy) to guess how long a new task will take. One catch: with analogous estimation, we usually stay close to the past number unless we have strong data. So instead of cutting it in half right away, we might say: - Last time: 4 hours - This time: maybe 3–4 hours, unless we have proof it’ll be much faster