Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/moradoadrian/carneroDev/llms.txt

Use this file to discover all available pages before exploring further.

Carnero.Dev is not just a coding contest — it is a student-driven engineering marathon with a clear mission: build technology that solves real problems. Organized by the TICs career at ITR Roque, the event compresses an entire product development lifecycle into 36 consecutive hours. From problem identification at kickoff to Demo Day pitches at the close, every moment is engineered for learning, collaboration, and shipping real software under pressure.

​
Mission

The core mission of Carnero.Dev is to empower university students to address genuine community challenges through technology, creativity, and collaboration. The event is deliberately structured to mirror the pressures of real-world software development — tight deadlines, ambiguous requirements, and the need to ship a working product regardless of the obstacles encountered along the way. Every team that participates leaves with a deployed product, a refined pitch, and a concrete understanding of what it takes to build something that matters. The organizing team — students from the TICs department — believe that the best way to learn software engineering is to build, break, and rebuild under real conditions.
Carnero.Dev is entirely student-driven and community-supported. The event is organized, managed, and run by TICs career students at ITR Roque — making it one of the few hackathons in the region where the organizers and participants share the same academic background and institutional environment.

​
Event Format

Carnero.Dev follows a structured 36-hour continuous development sprint:
  • Start: Friday, October 16, 2026 at 09:00 AM — kickoff ceremony, team formation confirmation, and challenge brief reveal.
  • Development Block: 36 consecutive hours of uninterrupted building, with mentoring access throughout to give teams expert guidance and course-correction opportunities.
  • Demo Day: Sunday morning — all teams present a live demo and pitch of their functional prototype to a judging panel.
  • Team Size: 1 to 4 members, enrolled in TICs or related university careers.
  • Output: A fully deployed, functional software product pushed to a public repository.
All code must be original and initiated within the official competition window. Pre-built templates, open-source libraries, and publicly available APIs are permitted, but the core solution must be developed during the event.

​
Core Values

The competition is built around six pillars that guide how teams approach their challenge and how judges evaluate final submissions:

Creativity

Original thinking and novel approaches to problem-solving are at the heart of every winning project.

Software Engineering

Code quality, architecture decisions, and technical depth are judged alongside product vision.

Teamwork

Collaboration under extreme pressure, role distribution, and collective ownership define strong teams.

Innovation

Disruptive integrations, unconventional stacks, and ambitious feature sets are recognized and rewarded.

Problem Solving

Identifying a genuine, well-scoped problem is the first and most critical step of the challenge.

Real Impact

Projects that address meaningful needs in education, health, community, or the environment are prioritized.

​
The Challenge Framework

Every project at Carnero.Dev must demonstrate progress across three core phases that mirror a real product development cycle:
1

Identify a Problem

Detect a real need, challenge, or inefficiency in your university, social, or institutional environment. The sharper the problem definition, the stronger the project foundation.
2

Propose the Solution

Design a creative, technically viable, and disruptive proposal to address the identified problem — explaining what the product does, who it is for, and why the chosen technical approach is the right one.
3

Build the Prototype

Develop a functional software prototype during the 36-hour competition window. The prototype must be deployed to a live environment and pushed to a public repository before the submission deadline.

​
The Carnero.Dev Terminal

The event identity is built around a terminal-style interface that reflects the engineering culture at its core. The official challenge brief is delivered in a format participants know well: 
$ cat event_rules.txt
> 1. Teams of 1 to 4 members enrolled in TICs or related careers.
> 2. 100% original development started within the hackathon block.
> 3. Deployments ready in production and pushed to public repositories.

$ ./run_hackathon --target_roque
[INIT] Loading hack environment. Hackers detected. Get ready to code!

Build docs developers (and LLMs) love

Get started for freeTalk to us