There appears to be some underlying principles between intermediate representations and possible, reliable transformations.
Intermediate representations are often used to keep the architecture more manageable -- in compilers, for example. But these internal representations appear to increase expressability, which goes beyond the architecture.
For example, software development development cycle has several transformations: from requirements to user stories to design, and then to code. The stages are getting a revival, because they appear to be helpful when working with LLMs.
If we think LLMs as transformation machines, the transformation is reliable to the extent the source internal representation can capture the explicit semantics. The less LLM needs to make up in the content, the more reliable the end result.
This is close to how LISPers approach coding: invent a DSL for what you want to do, implement it in your DSL, and then implement the DSL. This approach seems to work well when creating systems that use LLMs.
I feel the same. More projects, more ambitious projects. I would have not been able to even imagine sone of the things I am building now, not to talk about implementhing them alone.
Protonmail (and I guess all others including Gmail, except Fastmail) has a nasty feature, where the sender can put an expiration date on emails and practically get a confirmation you received the email without you ever knowing you received the email.
If the expiration is for example one day, you might never see it.
To my knowledge, Protonmail does not even show information that the email has expiration. Nor can you access log of deletions.
This feature was used against me on a court trial.
I am doing approximately the same for some of these as well, plus CRM. For me, CRM is just a list of contacts with a state and some other fields, plus record who was contacted and when. But I can directly pull information that is relevant to me. Integrating to an external CRM is more work and arguably more risky than rolling your own.
For an individual project? Seems kind of far off that an individual project would take load that one server could not handle, even at open source level. Or do you mean allow people to create projects freely?
Service management is business oriented, what is the service we are providing and how do we deliver it, and how do we agree with the customer what we deliver. And when the data is structured, other interesting oppurtinities become possible.
This particular use case is people working together to collect data in a workshop. 10 people don’t want to see somebody searching for the right place in a form, it interrupts the flow of the meeting. You need to capture the ideas raw, and then structure later. That is where question anout how unstructured data is captured in strucured format pops up.
It is a workflow I directly support in my tool, not a generic tool like yours.
Continuing USM tools, set of tools for better service management based on Unified Service Management (USM) model. The basic idea is better to define your services as data, instead of documentation.
Recently I have had trouble with Sentry. I have a site that has a lot of data coming in (2M page views per month) and Sentry starts being unusable for a solo developer. And on the other hand, I have several Django projects where I want to have common way to handle bugs.
I am feeling Sentry UI is too complex for my use cases, and on the other hand, I would like to automate the process as much as possible -- and the idea of automatic bug fixing is neat!
I am experimenting with Bugsink. Supporting Bugsink internally but build some tooling around it for automatic bug detection and fixing would actually be a sweet spot for me.
I was actually working on last weekend with something that has similarities. I am working on USM.tools, which allows specifying your services in structured way.
There is a need to specify some of the data in semi-structured way, and I am using markdown for that.
So there is this interesting relationship between unstructured, semi-structured and structured data, and markdown hits that middle ground.
Can I suggest you make some Jira etc. templates on your landing page clickable, so a visitor can grasp your idea more easily? For me it was not clear whether the specs are just plain markdown, or do you have some additional tagging there.
Maybe 10 years ago I started to build Guitar Hero style game with real electric drums, initially to teach myself drumming. The idea was to extract drum information from real songs (so I was exploring a DSL as well). I guess modern AIs could be used to implement this much quicker.
I have a hobby or we could even say an addiction of having lota of ideas for various kinds of things. Part of the fun is inventing a name, visual identity, logo etc. and donain nane is part of it. Maybe they never reach production but many have. I have tools to automate boring parts like any developer would — and I could essily use something like this.
I was recently using an inexpensive paper shredder. I had an urge to put in too many papers at one time, which jams the shredder. Taking into account the time needed to unjam the shredder, the end result is that it takes more time for me to process the papers if I give in to my urge than if I resist the urge and only put in just the right amount of papers. Then I can claim that the "shredder is of bad quality", instead of seeing how I contribute to the problem.
As my aim was to shred papers efficiently, my "sin" (sin = to miss the mark, not to hit the aim) was greed, and the virtuous path is to successfully to resist the urge. The blessing I get from the virtuous path is the joy of the flow when I efficiently shred the papers.
Yesterday, I was in a shop when I was hungry, and I felt the urge to buy a large chocolate bar. Being hungry, it would have been a constant struggle not to eat all of it if I had bought it. Eating a whole large chocolate bar does not make me feel so good.
As my personal aim is to feel good, eating a whole large chocolate bar at one go is a sin in relation to that aim. I successfully resisted the urge to buy the large chocolate bar -- and did so by buying a small one. That way I did not "sin" too much towards my aim of feeling good, because small chocolate bar did not affect my well-being almost at all.
On the surface, it might appear more virtuous to not buy any chocolate bar. However, I know myself from prior experience that if I had "successfully" resisted the natural urge at the shop, it might have caused me to later to be unable to later resist the urge to buy a large chocolate bar from a kiosk.
So knowing myself to be the imperfect human being in these scenarios, buying a small chocolate bar at the shop was actually more aligned with my aim of feeling good than not buying it, because the end result was more aligned with my aim of feeling good.
Modern psychology would probably say that this urge is in my superego. Maybe as a child, I learned that I don't usually get what I need, so when something is available, I feel the urge to take as much as I can -- i.e. greed is something that I will encounter in many things that I do, keeping me from hitting the mark. As this is very common way humans miss the mark and deeper in the psychology, it is a Deadly Sin.
Some theological and psychological perspectives posit that the belief that this urge is a part of me -- i.e. I identify with the urge, I believe that "I am greedy" -- is actually part of the problem. So a better formulation would be instead of "WHO decides how much I need" to ask "WHAT IN ME decides how much I need". And then, what is a healthy and useful relationship towards those urges. And it may be different in different circumstances, hence resisting the urge to put in too many papers, but replacing the urge with a lesser one in case of chocolate bars.
The point might not be to learn to "control" the urge -- we can learn from system theory that excessive control might cause a backlash -- in terms of some systems even literally. More healthy relationship is often to just observe -- and then learn how such urges affect my well-being -- i.e. to learn more about myself. Often the observation itself is enough to have an effect.
We can take a corporate analogy (literally, corpus = body) and ask, what in organizations (again, organization has the same literal root as organism) cause them to be "greedy". In other words, what drives organizations to have an urge for excessive profits that they ignore the harms they cause to employees, society at large or even customers (i.e. enshittification). This urge appears very similar as the urge in humans.
That question will lead to other interesting questions about politics, economics etc. For example, you can ask, what is the aim of such corporations, and whether that aim produces results aligned with the aims of societies at large, etc.
The Seven Deadly Sins provide an interesting perspective to human psychology even in modern times. Greed / avarice is defined as wanting more than you need.
Well for example this is very unique idea and even in the current state it has been very useful at a customer. Almost completely vibe coded but idea is fully mine.
Intermediate representations are often used to keep the architecture more manageable -- in compilers, for example. But these internal representations appear to increase expressability, which goes beyond the architecture.
For example, software development development cycle has several transformations: from requirements to user stories to design, and then to code. The stages are getting a revival, because they appear to be helpful when working with LLMs.
If we think LLMs as transformation machines, the transformation is reliable to the extent the source internal representation can capture the explicit semantics. The less LLM needs to make up in the content, the more reliable the end result.
This is close to how LISPers approach coding: invent a DSL for what you want to do, implement it in your DSL, and then implement the DSL. This approach seems to work well when creating systems that use LLMs.