Django and Python
under tensionBoring on purpose. Database-driven tools that keep working after we hand them over, because the next person to open the code can read it. No framework of the month.
Smart Web Dev — the workshop
In 1801 a loom in Lyon read a stack of punched cards and wove a picture nobody had to supervise. Every database, login screen and gradebook since is the same trick: independent threads that hold only because they hold each other.
We are Smart Web Dev. We build simple, secure web platforms for businesses and schools — usually in Django and Python, usually for people who never asked to become the IT department.
His loom read holes in card stock and wove whatever the cards said — including, in 1839, a silk portrait of Jacquard himself made from 24,000 punched cards. Charles Babbage kept one on his wall while designing the Analytical Engine. Ada Lovelace wrote that it "weaves algebraic patterns just as the Jacquard loom weaves flowers and leaves." Storage, instructions, output. It was all there before electricity.
The warp
On a loom the warp is strung before a single row is woven, and it stays under tension until the cloth comes off. Get it wrong and nothing you weave later can save it. We have three.
Boring on purpose. Database-driven tools that keep working after we hand them over, because the next person to open the code can read it. No framework of the month.
Five years in Guatemalan classrooms gave us the only test that matters: if a tool needs a manual, it isn't finished. We build the thing, then we watch someone who has never seen it try to use it.
Passwords, permissions, backups. Not a feature you bolt on at the end — it is tension you set at the start, or the whole cloth pulls apart the first time something goes wrong.
Who weaves
Small studio, on purpose. You talk to the person writing the code, and they answer.
@nelson63dbGuatemala
Python developer, Bitcoin hodler, bookworm.
@Facu6MArgentina
Front-end developer, building interfaces people do not have to think about.
@Remedu787
Python and the English side of the work — the person who reads what we wrote before a client does.
Pictures and bios come straight from GitHub. If they don't load, GitHub is rate-limiting us — everything you need is above anyway.
The weft
The weft is every row that crosses the warp. Nothing here works without the three threads above holding still.
Quizzes, gradebooks, progress dashboards — shaped around how your teachers already work, not around somebody's product roadmap.
Most of the pain of moving online is the migration, not the software. We do that part, and we do it before you have to explain it to anyone.
Blogs, workshops and interactive experiments that make math, science and programming something you try, not something you read about.
We set up the protection, then explain it in words your staff will repeat to each other. A rule nobody understands is a rule nobody follows.
Guatemala. Free resources, training sessions and support that outlast the invoice, because digital literacy is infrastructure too.
What the cloth is for
You can only weave until the threads run out. It is the only honest way we know to think about technology, so we say it out loud here instead of hiding it in a footer.
We build on open protocols and repairable things. A tool you cannot open, move or fix is not yours — you are renting it, and the rent goes up. We take Bitcoin because money should work like the web: no permission needed. And we keep the two counters below on this page, where our own work has to sit next to them.
Counting down at current emissions. Every platform we deploy runs on electricity that comes from somewhere, and the deadline does not move because a project slipped.
Installing your own software on your own phone is being closed off. A device you cannot put your own code on is a rental with extra steps — and every student we teach deserves better than that.
That is the whole position. If it sounds like how you would want your own tools built, tell us what you are working on.
Pull a thread.