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.
1380 matching tickets · Page 86 of 115
A change notification for an unknown URI crashes the document map. Validate document lifecycle.
Estimated field mix
Emoji before an error shifts the underline. Add position conversion matching the negotiated encoding.
Estimated field mix
Delayed changes replace newer document content. Track monotonic document versions and ordered edits.
Estimated field mix
Parser results are published after users type more text. Bind diagnostics to the source snapshot checked.
Estimated field mix
Completion suggests keys inside string literals and comments. Restrict suggestions using syntax context.
Estimated field mix
Rename replaces matching text inside comments and unrelated scopes. Resolve the selected symbol before creating edits.
Estimated field mix
Applying an old quick fix corrupts newer text. Include the snapshot version in the edit contract.
Estimated field mix
Repeated completion cancellation leaves tasks in memory. Add request-scoped cleanup for all terminal paths.
Estimated field mix
A malformed request resets the whole server and loses open buffers. Isolate parsing and protocol failures.
Estimated field mix
Editor reports are difficult to replay. Record synthetic protocol transcripts with deterministic response assertions.
Estimated field mix
Relative spellings create duplicate graph nodes. Define canonical module identity under an explicit workspace root.
Estimated field mix
A missing import yields an internal file error. Map resolution failure to the importing source span.
Estimated field mix
138 matching projects · Page 11 of 12
Evolve a quoting module as partner contracts diverge, while keeping calculations reproducible and abstractions proportional to the problem.
Build a bounded browser editor whose tree operations, history, subscriptions, and exports remain coherent under failures and repeated use.
Support two incompatible notification providers while keeping domain decisions, instrumentation, and overload behavior explicit.
Replace a growing set of warehouse eligibility switches with a small, bounded rule language that support can inspect and engineers can evolve.
Evolve a long-lived account module while preserving tenant boundaries, client contracts, and a credible route back from partial migration.
Coordinate return inspection, replacement stock, and refunds across controllable provider boundaries while keeping uncertain outcomes visible.
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.