Skip to content
Tomer Naydnov
arc / explorer

Read-only portfolio demo · Fictional data

Original app recordings
Explore student / Activity library
Your world, your style

A world for learning

Write

A thoughtful answer, with space to develop it.

11 / 31
Individual

THE EXAMPLE CHALLENGE

Explain why a program should validate an input before using it.

JORDAN’S EXAMPLE RESPONSE

Before using a sensor reading, I would check whether it exists. A missing value is different from zero.

That small check lets the program give a useful explanation instead of comparing something it does not have.

Version 2Submitted example
01

Plain-text response with character count and minimum/maximum length

02

Debounced draft saving with visible status

03

A submitted version and published feedback

What this part of Arc does
  • Plain-text response with character count and minimum/maximum length
  • Debounced draft saving with visible status
  • A submitted version and published feedback

This is a browsable portfolio interpretation of Arc’s workflows with fictional examples. Navigation, filtering and theme previews work here; editing, execution and platform services belong to the original application.

Inside the original application.

This demo view is grounded in Arc’s source. Explore the recorded workflows for a look at the original interface.

All original recordings ↗
Source references & review notes
  • app/Platform/Domain/Task/Handlers/TextTaskHandler.php
  • resources/views/components/task-types/editors/text.blade.php
  • resources/js/text-task-editor.js
Read the portal research & evidence boundaries ↗

Source reviewed at development revision 5549bf96. Original captures have their own pinned revisions; the live platform has a separate release.