~ / crew

The whole
prickle.

Two people. Both engineers, both designers when it's needed, both slightly underslept.

portrait · 01
// electrical engineer · software · DSP · management
Lucas

Electrical engineer. Writes the software, owns the signal-processing side, and keeps the project on track when the deadline starts breathing down our necks.

DSPSoftwareProject management
portrait · 02
// mechatronics engineer · hardware · software · AI · CAD
Julian

Mechatronics engineer. Lives in the seams between hardware and software — solders the boards, models the parts, writes the code, and trains the model that ties it all together.

HardwareSoftwareAICAD
// how we split work

No fixed roles. Honest defaults.

We rotate, but here's what usually happens by hour 6 of any hackathon.

hour 0–2

Both: scope & demo storyboard

We sketch the demo flow before we write a line of code. If we can't draw it on one A4, the project is too big.

hour 2–6

Julian: bring up · Lucas: scaffold

Julian wires the hardware and gets a "hello world" off the metal. Lucas scaffolds the repo, the data path, and whatever pipeline the demo will sit on.

hour 6–24

Build the loop

Whichever subsystem blocks the demo, both of us pile on. The other systems wait.

hour 24–36

Both: polish · pitch · sleep

One of us records a backup demo. The other rehearses the pitch out loud. Whoever sleeps less presents.

// the third hog

Want to hack with us?

We sometimes invite a third person for events that need a specific skill. If that's you, send a project link and one sentence on why you'd want in.