← Course overview
Orientation · before Week 1

Think Like an Engineer, Not an Assembler

This course teaches through one finished machine. Before you copy any part of it, spend a session deciding how you would solve the problem — because the reference build is only one answer among many good ones.

~1–2 hrs Paper / notebook, no hardware

Concept The problem, stripped of every assumption

Here is the entire brief, before a single part gets chosen: sort a mixed bag of Skittles by colour, automatically, with no hand-sorting once it starts. Everything else in this course — a rotating wheel, a spectral sensor, a Raspberry Pi, a laser-cut frame — is a choice that was made to solve that brief, not a requirement baked into the problem itself. A good engineer separates the two: the problem is fixed, the solution is not. Every workable solution, however different it looks, ends up doing the same five jobs — it just does each one a different way:

Kit What you need this week

  • A notebook or blank paper
  • A pencil
  • About an hour of quiet thinking, done before looking at Week 1

Build Step by step

Step 1

Name the five jobs

Any sorting machine, however it's built, has to solve five separate jobs. Write these five headings on a page, with space under each:

  • Feed — get Skittles from a bulk pile to “one at a time, in a known position.”
  • Sense — measure something about the one currently presented.
  • Decide — turn that measurement into a decision (“this one is red”).
  • Act — physically move that specific Skittle to the right destination.
  • Structure & power — hold everything in place and keep it running.
Step 2

Brainstorm three ways to solve “Feed”

Don't judge ideas yet, just list them. To get started, here are three real options: a gravity hopper with an agitator dropping Skittles into an indexed wheel (this course's approach); a conveyor belt carrying them past a sensor one at a time; a vibratory bowl feeder, like an industrial parts feeder, lining them up single-file. Add a fourth of your own — even “a person places them by hand” is a legitimate answer for a first prototype, it just removes automation from that one job.

Step 3

Brainstorm three ways to solve “Sense”

This course uses a dedicated spectral sensor (the AS7341) with its own onboard illumination LED. Other real options: a camera with image-processing colour detection (more flexible, more compute needed); three simple photodiodes behind red/green/blue filters, compared directly (cheaper, cruder); or, at the extreme, a person calling out colours by eye. List at least one you hadn't considered before reading this.

Step 4

Brainstorm three ways to solve “Act”

This course uses a rotating slide that tips each Skittle into one of several fixed positions as it turns. Other real options: moving cups or bins on a carousel that come to the Skittle instead of the other way round; a row of pusher solenoids or servos, one per colour, each nudging a match sideways off a shared belt; or a small robotic arm that picks up and places each Skittle individually — slower, but trivial to reprogram for a different number of colours. Sketch one of these as a rough diagram, not just a sentence.

Step 5

Read why this course chose what it chose

The specific combination this course builds — wheel feeder, spectral sensor, Raspberry Pi Zero, rotating slide — wasn't picked because it's the fastest, cheapest, or most elegant solution to the brief. It was picked because, in this order, it touches the widest range of transferable skills: parametric CAD, 3D printing and laser cutting, stepper motors and homing, I2C sensing, basic classification, mechanical actuation, and system integration. A conveyor-and-camera version might be a better product; it would teach a narrower, more software-heavy set of skills. Keep this distinction in mind for the rest of the course: you're being shown a good teaching path, not being told the only right answer.

Step 6

Choose your direction and write why

Decide, in writing, one of two things: (a) you'll follow this course's mechanical design broadly but you're free to swap in a different approach to one or two of the five jobs as you go, or (b) you're deliberately building something structurally different from the start. Either is a completely valid answer — write one paragraph justifying whichever you pick. There is no wrong choice here, only an unexamined one.

Make it yours
  • Look up one real industrial sorting machine — a recycling material-recovery facility, a postal sorting system, a seed or coffee-bean sorter — and identify which of the five jobs it solves differently from every option listed above.
  • Try to invent a sixth approach to “Act” that isn't in the list above. Constraint-free brainstorming here pays off later, when a real mechanical problem needs an unconventional fix.

If it breaks Troubleshooting

Nothing comes to mind for a subsystemStart from a completely different domain — how does a vending machine dispense one item? How does a change-sorting coin machine work? Borrowing a mechanism from an unrelated machine is a normal, respectable engineering move.
Every idea sounds like a worse version of the reference buildThat's fine, and common — the point isn't necessarily to diverge, it's to know why you're not diverging. “I considered X and Y but chose the course's approach because Z” is exactly the kind of reasoning this exercise is after.
This week's checkpointA short written (or sketched) comparison exists covering at least two different approaches to at least two of the five subsystems, plus one paragraph committing to a direction — even if that direction is “follow the reference build.” Keep this page: Week 12's retrospective asks you to revisit it.
Next week: Week 1 — setting up the Raspberry Pi and getting comfortable in Python, whichever direction you chose above.