Preparing the next view without exposing private workflow data.
Design a system. Diagnose tail latency. Ship a migration. Recover a failed rollout. Pick a focused ticket or follow a project through its delivery phases.
1380 tickets · 138 projects · 26 engineering fields · Four difficulty levels
Field counts and the engineering field filter use each project's primary field. Estimated ticket labels can span multiple fields.
60 matching tickets · Page 3 of 5
A stalled child leaves the supervisor buffering every request body until memory is exhausted.
Estimated field mix
Pattern topics
The worker exits after writing its output but before the acknowledgement frame; automatic retry may produce a second external artifact.
Estimated field mix
A timed-out worker launches a helper. Killing only the parent leaks the helper; reusing a process-group identifier risks signaling a newer process.
Estimated field mix
A corrupt fixture crashes every replacement worker, and immediate restart loops consume the supervisor CPU.
Estimated field mix
Pattern topics
The supervisor restarts with requests marked running but no in-memory correlation table and no proof whether workers completed them.
Estimated field mix
The local child-process harness is about to be mistaken for a production candidate-code sandbox.
Estimated field mix
A truncated PUSH instruction reads its operand from bytes beyond the supplied program.
Estimated field mix
One branch pushes a value and the other does not, so the merge point underflows only for certain inputs.
Estimated field mix
A crafted jump targets the second byte of a literal and reinterprets it as an opcode.
Estimated field mix
Debug builds trap on addition overflow while optimized builds wrap, producing different rule outcomes.
Estimated field mix
A backward jump with an always-true condition consumes a worker indefinitely.
Estimated field mix
A proposed LIST instruction allocates on every loop iteration and the prototype retains all intermediate values.
Estimated field mix
6 matching projects · Page 1 of 1
Build a bounded arena with explicit alignment, lifetime and corruption behavior.
Implement bounded scheduling, cancellation and shutdown without hidden liveness failures.
Build framed IPC, bounded buffering, process lifecycle control and restart-safe request identity.
Implement decoding, stack safety, resource budgets and compatible bytecode revisions.
Design a safe FFI contract with explicit ownership, error mapping and compatibility.
Wrap files, timers and readiness notifications with explicit partial-result and portability behavior.
Practice scoped changes, keep a portable implementation and verification record, and learn to explain operational tradeoffs. Choose a ticket whose prerequisites you can provide.
Use realistic work to structure onboarding, internal practice, and conversations about engineering decisions. Each project names the delivery benefit. Agree scope and compensation before requesting company-specific work.
CSV contains one row per ticket. Map fields and issue types in your tracker; project grouping and dependency keys are descriptive. JSON preserves the complete project structure. These downloads do not synchronize with Jira.