Open-source project
mouredev/retos-programacion-2023 avatar
mouredev/retos-programacion-2023

mouredev/retos-programacion-2023: weekly logic katas in any language

Ejercicios de código semanales en 2023 de la comunidad MoureDev para practicar lógica en cualquier lenguaje de programación.

5,663 stars2,856 forksPythonApache-2.0

At a glance

What is it?
A community challenge repository from MoureDev: one exercise per week, statements in Spanish, reference solutions in Python, and community submissions grouped by language. Useful for deliberate practice, not for production code.
Who is it for?
Adopt it if you want a dated, self-contained set of exercises with a reference solution per challenge and a folder of community answers in many languages; it fits self-study and study groups better than a course syllabus. Skip it if you need graded difficulty, automated tests or a maintained library, because each challenge stands alone and there is no test harness in the repository.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 47 days ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • mouredev/retos-programacion-20235,663 ★ · +11
Star history
Repository2026-09-232026-11-15
mouredev/retos-programacion-20235.7k5.7k

11 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What retos-programacion-2023 actually is

This is a challenge archive, not a library. The README describes it as a project of weekly challenges from the MoureDev community for practising programming logic in any language. Each challenge has a publication date, a difficulty label (Fácil or Media in the entries shown), a statement file, and a directory holding corrections grouped by programming language. The README states explicitly that the challenges have no relation to one another and can be solved completely independently, so you can jump to number 12 without touching number 3.

The intended reader is someone who already knows basic syntax in at least one language and wants structured practice. The listing starts at challenge #0, dated 26/12/22, and continues weekly into 2023. The repository's primary language is Python, which matters because the maintainer's own solution is linked as python/mouredev.py for every challenge listed. Python is the reference implementation, but the README says any language can be used and community corrections are grouped by language, so the answers are not confined to one ecosystem.

How a challenge folder is laid out

The data flow is flat and file-based. The repository root contains .github/, .gitignore, Images/, LICENSE, README.md and a single Retos/ directory. Inside Retos/, each challenge is a folder whose name encodes the number, the Spanish title and the difficulty, for example Reto #0 - EL FAMOSO FIZZ BUZZ [Fácil]. Inside that folder there is an ejercicio.md with the statement, a python/ subdirectory with the maintainer's solution, and further language subdirectories contributed by the community.

The README links to each part separately: a video correction on YouTube, the maintainer's solution file, and the community folder. That structure is the whole mechanism. There is no build system, no package manifest, no test runner and no index generated from the code. The README itself is the index. Anyone consuming this repository reads Markdown and runs a single script per challenge.

Installing nothing: running your first challenge

The repository does not document an install step, because there is nothing to install. You clone it and run a file. The README points to retosdeprogramacion.com/semanales2023 as the place with full information, and to the Discord server's Eventos section for the live schedule.

Start by cloning and moving into the first challenge folder. The path contains spaces and a bracket, so quote it:

bash
git clone https://github.com/mouredev/retos-programacion-2023.git
cd "retos-programacion-2023/Retos/Reto #0 - EL FAMOSO FIZZ BUZZ [Fácil]"

Read the statement, then run the maintainer's Python solution to see the expected behaviour before writing your own:

bash
cat ejercicio.md
python3 python/mouredev.py

What you should see is the FizzBuzz output the statement describes, produced by the file the README links as MI SOLUCIÓN. Once that runs, create your own file in the same folder, in whatever language you are practising. Nothing registers it, nothing validates it; the comparison is manual, against ejercicio.md and against the community folder. If you want your answer to live alongside the others, the README's ¿Cómo puedo participar? section is the place that explains how to contribute, and it is worth reading before opening a pull request.

The 2023 archive problem: it is a snapshot, not a track

The README states that a new challenge is published each week and corrected live on Twitch the following week. That publishing cadence belongs to 2023. The repository's last push was on 2026-09-29, so the code is not abandoned, but the weekly rhythm described in the README is a description of how the material was produced, not a promise about what arrives next. Anyone arriving now is reading a finished set, and the homepage retosdeprogramacion.com/semanales2023 is the live surface for the project rather than this repository.

The practical consequence is that the difficulty curve is fixed and shallow. The visible listing alternates Fácil and Media, with no hard tier in the entries shown, and there is no progression mechanism: no prerequisites, no dependency between challenges, no scoring. If you want a curriculum that builds from variables to data structures, this is the wrong shape. It is a bag of independent katas, and the README says so directly. The other limitation is language coverage asymmetry. Python has a maintainer solution for every challenge; other languages depend on whoever contributed. A challenge folder may have a rich community section in one language and nothing in another.

How it differs from Exercism and Codewars

The obvious alternatives are Exercism and Codewars, and the difference is in what surrounds the exercise. Exercism ships a CLI, per-language tracks with a defined syllabus, and an automated test suite you run locally; the tests are the feedback loop. Codewars runs your submission against hidden test cases on their servers and returns a pass or fail plus a rank. Both give you machine-checked correctness.

This repository gives you a statement file and human-written solutions to read. There is no test harness in the tree, so correctness is judged by you, or by the Twitch correction video, or by diffing your output against python/mouredev.py. That is weaker as a feedback loop and stronger as a reading exercise: the value here is seeing how several people solved the same small problem in different languages, side by side in one folder. Exercism will tell you that you failed. This will show you five ways the problem can be framed. If your goal is measurable progress through graded material, pick Exercism. If your goal is to read and write small programs in a language you are learning, the folder-per-challenge layout is the reason to be here.

Licence and the cost of keeping a fork

The repository carries Apache-2.0, and the LICENSE file sits at the root alongside README.md. Apache-2.0 permits reuse and modification with conditions, including preserving notices and stating changes. That is a permissive licence, but it is not the same as public domain, and the community solution files inside each Retos/ folder were written by many contributors whose individual copyright is not itemised anywhere in the repository. If you plan to copy solution code into a project of your own, read the LICENSE file and the contribution guidance rather than assuming the root licence settles every file.

Upgrade cost is close to zero in the dependency sense and non-trivial in the maintenance sense. The repository has no published GitHub releases and no version to pin, so a fork never needs a merge conflict resolved against a moving API. What it does need is the discipline to keep your own solutions separate from the upstream folders, because the README-driven index and the folder names are the only structure, and a rebase across renamed challenge directories is manual work.

Who gets value from a dated kata set

Three groups benefit. First, someone learning a second language who wants the same problem expressed in several languages and can compare a Kotlin file against a Python one in the same folder. Second, a study group that wants a fixed, finite agenda: the README gives a date and a difficulty for each challenge, so a group can schedule without designing exercises. Third, anyone who prefers reading a reference solution after struggling, which the README makes easy by linking MI SOLUCIÓN and COMUNIDAD separately for every entry.

The people who should look elsewhere are those who need graded difficulty, automated verification, or a progression that assumes prior challenges. This repository has none of those, by design. It is also a poor fit if you need the exercise statements in English: the titles and statements are in Spanish. That is not a defect in the project, but it is a real barrier for a reader who does not work in Spanish, and it is the first thing to check before planning a study schedule around it.

Editorial conclusion

Adopt it if you want a dated, self-contained set of exercises with a reference solution per challenge and a folder of community answers in many languages; it fits self-study and study groups better than a course syllabus. Skip it if you need graded difficulty, automated tests or a maintained library, because each challenge stands alone and there is no test harness in the repository. Before committing, open one challenge folder and check that the ejercicio.md statement and the python/mouredev.py solution match the language you intend to practise, then confirm the LICENSE file at the repository root before reusing any solution outside your own study.

Frequently asked questions

What is mouredev/retos-programacion-2023?

It is a repository of weekly programming challenges published in 2023 by the MoureDev community to practise logic in any programming language. Each challenge has a statement, a difficulty label, a date, a reference solution in Python and a folder of community solutions grouped by language.

Which programming languages can I use for the challenges in mouredev/retos-programacion-2023?

The README states that you can use any programming language. Community corrections are grouped by language inside each challenge folder.

Do I need to install anything to solve the challenges in mouredev/retos-programacion-2023?

No. The repository documents no install step; you clone it and run a file from the challenge folder. The README points to retosdeprogramacion.com/semanales2023 for the full information about the project.

Are the challenges in mouredev/retos-programacion-2023 related to each other?

No. The README states that the challenges have no relation between them and that you can solve them completely independently, checking only the difficulty level. There is no prerequisite chain or progression between challenge numbers.

Where are the corrections for each challenge in mouredev/retos-programacion-2023?

Each challenge entry in the README links a video correction on YouTube, the maintainer's own solution (MI SOLUCIÓN, typically python/mouredev.py) and the community folder (COMUNIDAD) for that challenge. The README also says the previous week's challenge is corrected live on Twitch.

What licence covers mouredev/retos-programacion-2023?

The repository is licensed Apache-2.0, with the LICENSE file at the root of the default branch. The repository does not itemise the authorship of individual community solution files, so check the LICENSE file before reusing solution code outside your own study.

Official sources

  1. Issues
  2. License: Apache-2.0
  3. mouredev/retos-programacion-2023 on GitHub
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/mouredev-retos-programacion-2023.svg)](https://hysenlabs.com/projects/mouredev-retos-programacion-2023)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/mouredev-retos-programacion-2023.svg)](https://hysenlabs.com/projects/mouredev-retos-programacion-2023)

Was this useful?