Hacklab ASU logo Hacklab ASUHacer, reparar, aprender juntos

About

About Hacklab ASU

What Hacklab ASU is for, who writes it, how claims are checked, and where to write when we get something wrong.

The short version

This is a blog and nothing more complicated than that. Nothing is deleted once it is up, so the archive is the full record, written to the standard of the line under the logo, Hacer, reparar, aprender juntos.

Most of what is written about electrónica y cultura maker is written by people who have never had to live with the results. Hacklab ASU is the opposite arrangement, and that is the whole idea behind it.

What we cover

  • Juegos. Videojuegos vistos con ojos de maker: mods, consolas retro, sandbox y comunidades que construyen.
  • Electrónica. Circuitos, Arduino, radiofrecuencia y placas caseras explicadas paso a paso.
  • Móviles. Sistemas alternativos, privacidad y mantenimiento de teléfonos que queremos conservar.
  • Reciclaje. Reutilizar, reparar y fabricar con lo que ya tenemos en vez de tirarlo.
  • Proyectos. Proyectos de fabricación casera, del escáner de libros a las herramientas del taller.

Nothing gets filed under three headings at once. If a piece does not have an obvious home, that usually means it has not been thought through yet. The busiest sections are juegos, electrónica and móviles.

Bylines

There is no house byline here. Each piece is signed, and each signature leads to everything else that person has put their name to.

Lucía Benítez, Editora y electrónica. Lucía empezó reparando radios viejas en la mesa de la cocina y hoy escribe sobre circuitos, Arduino y radiofrecuencia sin dar nada por sabido.

Mateo Giménez, Videojuegos y cultura maker. Mateo modifica consolas retro y escribe sobre juegos de construcción, mods y las comunidades que mantienen vivos los juegos viejos.

Sofía Duarte, Impresión 3D y reciclaje. Sofía diseña piezas en OpenSCAD y prefiere arreglar un objeto antes que comprar otro, aunque tarde una tarde entera.

Who pays for this

The site pays for itself through a small number of outbound links. It has never been enough to change what gets written, and the day it is, we will say so here.

About the name

People ask about the name. There is rarely a good story behind a domain, and there is not one here either. Hacklab ASU was available, it was short enough to say out loud, and it has been the name long enough now that changing it would be more confusing than keeping it.

How this is put together

Every piece here starts with a question somebody actually asked. If we cannot answer it from experience or from a source we can name, it does not get published.

We buy what we write about. It is slower, it is more expensive, and it is the only arrangement that lets us say a thing was not worth it.

The full process, including corrections and commercial links, is set out on the editorial policy page.

The limits of this site

We are not the right place for advice tailored to your exact situation. Hacklab ASU publishes general guidance, and the difference matters more than it sounds.

Telling us we are wrong

Point at the sentence. Write to [email protected] or use the contact page. Factual errors are fixed quickly, and when a correction changes the conclusion of a piece we say so at the foot of the page rather than editing quietly.