joddystreet
Joined 9 years ago
Joined 9 years ago
Not horrible is - caring about the outcome, and using AI to make it possible, irrespective of the skill level.
Horrible is - everyone trying to copy paste someone else’s work without caring.
I think, human thought + ai built is the “not horrible”, might even be awesome
Eylo (a take on Hello) a voice first agent platform, multi-tenant, focused on B2B2C use-cases - https://github.com/DigiCred-OSS/eylo-os
It’s a distilled fork of a closed source product that we are offering to our customers.
Chatgpt is a better planner.
Have a discussion in Chatgpt, have Claude to plan work chunks and have GLM to deliver, Codex to review and fix, delivers an overall a better version.
Problem - It’s just too much of a context switching.
Solution - I am thinking about a new product, a collaborative workspace where I can run this workflow.
Claude generates more code, tries to build things that are not planned or needed, repeats same mistakes over and over.
Chatgpt on the other hand just does enough, within a project would not repeat the same mistakes, tries to guess your workflow, so you don’t have to ask it to run the same.
If you need more control over your code/projects, if you know what you want to get done, use Codex.
If you have no idea what you’re doing and are happy to let LLM drive the thing, use Claude.
Codex/Chagpt is for the competent.
python superset would have been perfect.
I do hope the language thrives and gets a community.
All the best to the modular team.
- Canvas for Agents
- LLMs for learning.
| Idea: Don't use LLMs for summarisation. | Proof of concept - https://www.youtube.com/watch?v=1oF9M5hAazw | Repo - https://github.com/veris-pr/bwaiz
At digicred, we were managing these in google drive and jira, but with 500+ enterprise customers, and their annual vendor reviews, this practice became unmanagable.
CAOS is a dedicated workspace that helps us manage these assessments like projects, additionally, CAOS turns the questionnaires into a system of record. Questionnaires become structured, answerable work. Finished answers and your compliance documents become a searchable, citable corpus. The next questionnaire starts from what you already said, with every claim traceable to the document or prior answer it came from.
It is self-hosted. Your policies, your answers, and your customers' questionnaires stay on your infrastructure.
Recently open-sourced - https://github.com/DigiCred-OSS/caos-os
Supports - Postgres - DynamoDB - Clickhouse - Redis
Primary idea is to evolve from SQL client to a Database Client, where users would be able to host queries, share queries and the work remains auditable.
Previously it was an SQL client, a PopSQL alternative. But I am trying to re-work the architecture so that it can support more databases, and services (query-as-service, query-as-reporting-job, etc).
- Loaders/Spinners should be fun - https://github.com/p-raj/pixi-loader