ziyadb

Joined 15 years ago

Karma
692
Submissions
56
Member since
Aug 15
Founder and CEO of Aide (https://aide.app). Multidisciplinary designer.

Email: ziyad(at)ziyadbasheer(dot)com Twitter: https://twitter.com/ziyadbasheer

View on Hacker News

Recent submissions

Comment · 2 months ago
The problem of handling recurring tasks predictably comes down to the probabilistic nature of LLMs, which are based on next-token prediction.

I founded a company called Aide where our goal was to help support teams reliably deploy customer-facing agents without worrying about poor interactions. The first problem we needed to solve was making them deterministic and eliminate the variance that comes naturally with base models.

Getting them to always adhere to brand policy, eliminate hallucination, and stay grounded in data was a fun challenge. Proud to say that we’ve devised a solution that runs well and it’s worked out quite nicely in compliance-heavy and regulated environments.

Comment · 2 months ago
I was surprised to read that Anthropic (and probably other data / model companies) are doing this and it's extremely disappointing, as working towards the benefit of humanity is not an exclusive right / domain of theirs but rather, is a shared responsibility and mission carried by all of humanity itself as a collective responsibility. Thus, the preservation of this knowledge, its availability, and accessibility are the most important things that we must ensure continue.

From a historical precedent standpoint, this is akin to the burning of the library of Alexandria, where centuries of knowledge was destroyed and leaving a limited version of the history, the surviving one, and depriving successive generations of significant amount of latent knowledge.

Despite the copyright restrictions that are forcing companies to do this, they should maintain archives that are publicly available. As stated in my first paragraph, they are not the exclusive stewards of humanity despite them anointing themselves as such. Granted, a lot of these books might not be that useful, but still a relic of times pre-machine generated text, which makes them valuable if only for their archival value.

Comment · 4 years ago
shameless plug but that's exactly what we're building at Aide (https://aide.app), I would love to chat and see how we can potentially help if this is something you're interesting in learning more about or deploying!
Comment · 6 years ago
would love to learn more about how you're using Freshdesk and the types of queries you're responding to! I'm building a customer support app that uses openAI's GPT3 to generate automated responses and it's been working great so far!

How can I reach you?

Comment · 6 years ago
The holy grail [https://beepb00p.xyz/pkm-search.html#future] of this really resonated with me and fully mirrors what I've been thinking about the past few months. In my observations, it's input capture, information organization, and subsequent retrieval:

Information Capture:

Input Capture - You’re going to have all-encompassing tracking and recording of all activity, but want configurable privacy on the extent to which you want your daily conversations and observations of external things you encounter and are exposed to. Capturing input needs to be holistic and incorporate all properties of encounters and new information.

Potential sources of input:

Vision — point of view recording, see snapchat spectacles, etc as primitive examples. Audio (voice notes and multi-party conversations) - voice calls, video, etc. and other forms of audio transmission where there is more than a single party in the interaction. Digital interactions You will need to keep track of web pages you visit at what times Conversations you see on Twitter, etc.

Properties and cues must be extrapolated from the information that is captured on input, in the case of audio, transcriptions are sufficient for transcription and retrieval purposes, however since video is a visual medium, it includes significantly more properties that need to be accounted for.

The aim here is to identify sufficient data points (cues) that are subsequently represented in such a way that they are easy to search across things you have encountered but only seem to recall a certain property or cue from. This is because of the fact that human beings tend to remember things in fragments, for instance, you might remember a certain color on a page that you visited within the last 6 months and nothing else.

So long as you are capturing sufficient input and actions then you should be able to go back to any given point in time. How and where are you going to store this information? Storing everything is going to be a large amount of data. The essence of the information and context must be preserved. If you want to wind back to an arbitrary position in time with the original context intact, you want to retain as much as you can in the most efficient manner possible, so determining which data points to retain is essential. (Once the content structure has been figured out, this will be viable).

Examples of Primary Cues:

Time - humans generally keep track of things in a linear time-based fashion. Color - invokes emotion and is memorable. Physical Location - the efficiency of information retrieval is highly influenced by the location at which it is originally synthesized, encountered, and stored. Keywords - the default conventional mode. Can and should be extracted from video/imagery and audio. Imagery - search for images based on their contents and ambience.

Potential Secondary Cue — Music - see historical associated input and actions while certain music was played. (What else?)

Meta Cues — Subjects - Automated tagging of keywords/encountered content.

Any combination of these queries is possible, but ultimately the killer feature is the ability to backtrack through time to find a certain piece of information that is made available thanks to the always-on recorded nature of your interactions with the physical and digital worlds combined.

Knowing what to store, and how, + displaying it needs to be worked on further.

Comment · 7 years ago
You really need to let us try it out without having to sign up. Imagine how many users that think "oh, yet another img -> html/css tool, I wonder how questionably it works" and then get discouraged by having to take a chance on something they have no idea how well/if it works.

I'll sign up anyway and give it a shot.

Comment · 10 years ago
Comment · 11 years ago
Comment · 12 years ago
I actually found the music and the video demo excellent! Great demo of your app.

The music was especially beautiful, I even looked it up. It's Planet Love by DJ Quicksilver in case anyone else liked it.

Don't let all these comments about auto-playing audio put you down. Great experience!

Comment · 12 years ago
Sure Eric! Shoot me an email: ziyad at buildingof.com and let's do it :)
Comment · 12 years ago
Comment · 12 years ago
Comment · 12 years ago
Hi Josh. I'm actually working on a book that is intended to provide you with the basic principles and how to actually build applications, which is something I've personally struggled with, considering the language-centricity of the majority of tutorials out there.

It's far from done, however, email me (email in profile) and I'd be happy to send you a draft.

Good luck with your journey!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton