Deconstruct^*

Lessons from Lechon, Cabinets, and Software Engineering

Conceptualization

• The Art: Technical analysis mixed with gut-feel decisions.
• Ambiguous State: Vague requirements requiring exploration.
• Projects: Goals, missions, products, or physical services.
• Actionable Item: Precise, executable activities.

Target Examples:

Tic-Tac-Toe • Sari-Sari Store • Accounting • Dating App

Construct vs. Deconstruct

Construct: Development, execution, and implementation.

Deconstruct (Breaking Down): Slicing, compartmentalization, mapping dependencies, and abstraction into building blocks.

The 5 Building Blocks

• Assumptions: Baseline conditions expected to hold true.
• Pre-conditions: Strict requirements BEFORE action starts.
• Nouns (Entities): Objects, state-holders, and materials.
• Verbs (Responsibilities): Actions and active duties.
• Boundaries: Encapsulation walls and interfaces.

1. Birthday Party for Lola

Assumptions: Cozy family venue, costs split among cousins.

Pre-conditions: Budget collected & venue deposit paid BEFORE sending invitations.

Nouns: Lola, Cousins, Venue, Catering Food, Budget Pool.

Verbs: Reserve venue, order catering, collect contributions.

Boundaries: Catering doesn't care who decorates; only needs payment and address.

2. Mountain Peak Trek

Assumptions: Weather clear for 8 hours, hikers physically fit.

Pre-conditions: Register at Barangay Hall & inspect gear BEFORE stepping onto trail.

Nouns: Hikers, Trail Map, Barangay Registration, Emergency Gear, Guide.

Verbs: Lead Hiker navigates; Sweep Hiker tracks rear; Guide logs safety.

Boundaries: Local guide enforces safety & registration; ignores snack distribution.

3. Finishing Whole Lechon

Assumptions: Lechon served warm, side dishes laid out, family ready.

Pre-conditions: Portion Crispy Skin (Panit) BEFORE general free-for-all eating.

Nouns: Eaters, Panit, Unod, Liempo, Gusok, Ulo/Ikog, Sarsa, Bone Bucket.

Verbs: Carver chops heavy cuts; Refiller maintains drinks/sarsa; Eaters consume.

Boundaries: Internal eating style is encapsulated; cross-plate sharing requires explicit request.

4. Building Clothes Cabinet

Assumptions: Panels defect-free, room space cleared, tools ready.

Pre-conditions: Measure space & align slides parallel BEFORE inserting drawer boxes.

Nouns: Lead Builder, Helper, Frame, Drawer System, Hanger Rod, Tools.

Verbs: Builder levels & cuts; Helper holds panels; Fasteners lock joints.

Boundaries: Drawer runner doesn't care what clothes are inside; only cares about frame width tolerance.

The Core Concept of Abstraction

Abstraction means stepping back from specific real-world details to see the universal pattern.

The Universal Execution Pattern

You are always executing the exact same underlying pattern:

[Pre-Conditions Verified] → [Workflow Execution] → [Goal Achieved]

1. Sequential Actions (A → B → C)

Actions with strict dependencies. Action B CANNOT start until Action A completely finishes.

• Lola's Party: Collect Budget → Pay Venue Deposit → Send Invitations
• Lechon: Wash Hands → Going to Dining Table
• Cabinet: Measure Room Space → Cut Frame Wood → Assemble Outer Shell
• Mountain Trek: Register at Barangay Hall → Meet Guide → Step onto Trail
• Software: Validate Auth Token → Query Database → Return API Response

2. Parallel Actions (A + B Concurrently)

Actions independent of each other running at the exact same time to save time and boost efficiency.

• Lola's Party: Cousin A sets up tables WHILE Cousin B orders food WHILE You compile slideshow.
• Lechon: Carver chops unod/belly WHILE Refiller pours sarsa WHILE Eaters consume panit.
• Cabinet: Builder levels drawer slides WHILE Helper constructs drawer boxes.
• Mountain Trek: Lead navigates path WHILE Sweep monitors rear WHILE Guide checks trail.
• Software: Fetch user profile WHILE loading notifications concurrently.

Executive Summary

Lechon Execution Engine

1. GUARDRILS & PRE-CONDITIONS
   - Verify lechon is served and family is gathered.
2. INITIALIZATION (Sequential Setup)
   - say_prayer_before_meals()
   - slice_lechon_parts()
   - give_utensils_to_eaters()
3. CONCURRENT EXECUTION (Parallel Core Phase)
   - parallel_eating_discarding_properly()
     ├─ Eaters: Consume panit, unod, belly
     ├─ Carver: Chop dense cuts (ulo, gusok)
     ├─ Refiller: Pour drinks & sarsa
     └─ All: Throw bones into Bone Bucket
4. TEARDOWN (Sequential Finish)
   - burp() → clean_up()
    

Cabinet Execution Engine

1. GUARDRILS & PRE-CONDITIONS
   - Verify room measurements and layout complete.
2. INITIALIZATION (Sequential Setup)
   - measure_and_cut_wood_panels()
   - assemble_outer_frame()
   - align_and_mount_backing_panel()
3. CONCURRENT EXECUTION (Parallel Core Phase)
   - parallel_assembling_and_fitting()
     ├─ Builder: Mount slides & hanger rod
     ├─ Helper: Assemble drawer boxes
     └─ Fasteners: Secure hinges & doors
4. TEARDOWN (Sequential Finish)
   - verify_alignment_and_smooth_glide()
   - clean_up_workspace()
    

1. Raw Capacity & Hands-On Skills

How much do you TRULY know about each other's shipping capacity?

• Assume the goal is a responsive web application...
• What can each member actually write or debug without relying on AI?
• Do you know who handles raw CSS layout vs who can write database queries?
• Honesty here prevents catastrophic bottlenecks later!

2. Deployment & Budget Realities

Where will this actually live, and who is paying?

• Platforms: Vercel • Render • DigitalOcean • AWS • Azure • Google Cloud
• What is your real budget? ($0 free tier vs $20/mo cloud bills)
• Deploying isn't an afterthought on final defense week—it is a baseline constraint!

3. Team Configurations & Relationships

Some team configurations work seamlessly; others break down under pressure depending on compatibility, grit, and commitment.

4. You Are Human (Plot Real Calendars)

• You have house chores, family responsibilities, and personal lives.
• You might have love lives, dating commitments, and mental burnouts.
• Be honest with your time: Don't promise 40 hours/week if you only have 5.
• Plot actual vacant dates on a shared calendar before assigning tasks!

5. The Team Math Paradox ($1 + 1 \neq 2$)

Know your team's combined capacity BEFORE locking in your project scope.

6. Frustration & The Hard Questions

Acknowledge right now: You WILL get frustrated with each other.

• When tempers flare, will you still push to finish the project?
• Or is it better to realize you aren't compatible teammates at the very start?
• Choosing teammates strictly based on social convenience is a trap.

7. The Mountain Trek Analogy (Behaviors)

Just like trekking up a steep peak, individual behaviors impact collective survival:

• Hiding fatigue, hoarding resources, or walking off-trail harms the entire crew.
• In software: Unannounced ghosting, silent blocking, or secret refactoring are detrimental to the health of the project.

8. Appealing to Your Assessors

When designing a project, look closely at who is grading you.

• What do your panelists care about most? (Data integrity? UI polish? Business logic?)
• Imagine what best appeals to them and tailor your core presentation highlights to those values.

9. Tech Stack Choice vs. Final Pitch

Are you picking a stack for familiarity, or for speed and reliability?

10. AI as a Learning Tool, Not a Band-Aid

Build your hands-on skills—not just your token count.

• Use AI to explain concepts, suggest architectures, and accelerate learning.
• Don't use AI as a crutch to blindly paste code you cannot defend.
• The ultimate goal of this project: You becoming a true builder and problem-solver, not just a prompter!

What We Do Together

• Hands-On Workshops: Real-world cloud engineering, backend architecture, & DevOps.
• Knowledge Sharing: Learn directly from local builders, industry veterans, and fellow students.
• Networking & Growth: Build meaningful professional connections beyond the classroom.
• Safe Space to Learn: Ask questions, experiment with projects, and level up together.