Here is one more web application for your amusement.
That is a github link. The project has not been deployed to a web host.
What is it and why? The README sums it up.
NoYes App is a directed-graph questionnaire application built with Django, HTMX, and PostgreSQL.
Users navigate questionnaires node by node — answering YES/NO questions, reading statements, and reaching terminal endpoints. The graph supports loops and rejoins (not a strict tree), so questionnaire designers can build branching, cyclical, or converging paths.
The idea originated in 2011. Originally named Trouble Flow Trouble shooting flow charts. I still have the first post in Obsidian, moved from the original TiddlyWiki. This would be at a company called Tendril.
Problem
I spent the afternoon writing a trouble shooting guide.
It is basically a flow chart with customer questions. Each question has a yes/no answer, that leads to the next question.
For example, “Are the LEDs on the front of the box lighting up?”,
Yes question 17,
No, “Is it plugged into the wall?”
Idea
Why is this in Excel? Why not do it as a web application, Saas?
Input questions, an explanation for the person on the phone, and the answers. Based on the answer, go to the next steps.
One better. Let the customer service send the questions to the user with a unique ID, so you can track the answers.
One better than that, let the user do stuff on the customer site, inside a frame and answer questions as you work through the web site. See the question and what you are doing. Let the user get screen shots if they get to an unexplained state.
Easy web application.
HA HA
It is like 20 questions on steroids, completely flexable.
It turns out the links between questions are edges of a graph between nodes that are the questions. This was interesting. It led me down a rat hole about graphs and graph theory when Tendril did a layoff in 2012.
I tried multiple times to use it as a simple application for learning beyond a Django tutorial. There was always a block.
February 2014
I tried to get the [[Idea – YesNoApp|YesNoApp]] site going again in Django 1.6.2. I put the model in and setup the first question link. That seemed to work.
The place I rat holed was working on new versions of Bootstrap. There are themes and some are asking for payment. There are a half dozen examples on the get bootstrap site.
25 February 2015
What is causing a knot under my left shoulder blade and the scattered energy?
The answer was obvious and caused instant relaxation. It is the Big R, resistance. The [[Idea – YesNoApp|YesNoApp]] is dangerously close to being shippable. Maybe not perfect, but shippable. The lizard brain is scrambling around searching for a place to hide, trying to divert my attention with a shiny new thing. I caught it, and it is like catching a guilty child. There is some shame, but also a big relief that they don’t have to live the lie any more. Listening to the body is good.
January 28, 2016
There are enough adjacent ideas that would keep me busy for years.
The overwhelm is the topic. I keep blathering on in here about it. My brain goes to things like the [[Idea – YesNoApp|YesNoApp]] or something else that feels easier, at least more self contained. I go home and don’t even take the time to run though the tutorial. So I have a knot in my left shoulder that won’t go away.
There are many more, some even more sad and embarrassing. Django is now at version 6. I was working with 1.6, so long ago.
Anyhow, nothing is ever wasted. In 2015, when Micron needed people to work on the Automata processor, a graph processing engine build with DRAM technology, I had graph knowledge and experience, and got a new gig in Boise.
Still, the Yes/No app never materialized.
Until Today
With Claude Code and about 3 days of mornings and evenings using the lowest paid level of Claude, here it is.
The domain name yesno and all combinations are taken. I have “noyesapp.com”, and I’ve sat on it for years. If I deploy the application, I can get the name pointing to the correct IP. That would be cool
In Obsidian, there is a Tiddler with NoYes examples. Each Questionnaire can be public or private. Public Questionnaires will appear on the landing page for anyone to see.
Now, typing out all of the above, we both realize there is more to do. Plus support for VirtualJudge. The work is never done.
It works well. There are some items to polish, but overall I am happy.
Leave a Reply