Been building a platform around this, have one customer who has been happily using my solutions for 5 years now. Seeking to bring others onto the platform.

Email in profile. USA East coast based, but willing to work worldwide

From around GPT 4 results got "Good enough"...I generally try to explain what problem I'm trying to solve, set limitations and boundaries, tell it to ask me questions, have it write up a plan with steps then we take one step at a time.

These new models are starting to feel like iPhone releases where the improvements / feature set feels incremental.

Same on the Claude side which I use for work

Before I think he was using AI and other tools to translate his messages since english isn't his first language. His own words, then AI translated it. Sounded kinda clunky, but I could sense the human behind the words and I gave grace since I can only imagine how hard it is to properly communicate your ideas when English isn't your first language.

But now it's gotten to a point where I can tell he's not using it for just translation. I'm gonna need to chat with him.

Redacted example below

```Hey @PERSON_WHO_ASKED_QUESTION Both good, and the retrieval one isn't written down anywhere. In order.

One corpus or four. My lean is one. Same chunks and embeddings tables, source_type column to tell them apart.

Values I'd propose, flat rather than nested: paper, dataset_description, dataset_readme, dataset_contributors, dataset_records, dataset_files. Description and readme split because their units already differ, one row versus one row per paragraph. A discriminator that can't separate those isn't doing much. The existing 440 rows would need backfilling to paper.

Chunk id in the same spirit: dataset doi, source type, ord. So EXAMPLE_DOI.

Worth checking before any of this matters: does chunks.doi carry a foreign key to papers.doi in 0001_init.sql? If it does, a metadata chunk with a dataset doi can't go in that table at all, and separate storage stops being a choice. Ten second read, I haven't done it. Shout if you get there first.

Retrieval is the one that's bigger than it looks. Search once across everything and nothing guarantees a paper chunk and a metadata chunk both land in the top k. The facts we want relate the two, and the generator can only write those if it sees both sides in the same window. So if one type systematically wins the ranking, that class of fact doesn't get worse. It becomes impossible.

Which way it goes I don't know. Two mechanisms pull opposite ways. Metadata chunks are short, tens of tokens against roughly 450 for a paper chunk, so they may just lose. But we embed context header plus text, and on a short chunk the header is most of the vector. The header is the dataset name, which is also most of the query. That points the other way.

Cheaper to measure than argue. Load one dataset's metadata, run a normal dataset level query, record the rank of the first chunk of each source type. Runnable as soon as any one of our four subtasks lands.

After that it's one pool, per source with quotas, or one pool with a floor per source type. I'd rather not pick before there's a measurement. ```

I've been working on a side project that I started in 2020. If I wanted to implement a new feature it was: - Wait for regular work hours to wrap up around 5 or 6 PM - Get dinner and rest / relax until around 8 or 9 PM - Open up the editor, think about the problem, Google things, read stack overflow which gets it 95% of the way there, Google more, dig deeper into the docs finally find what I needed - Write a function, make some progress, run into another roadblock, repeat previous point - Look up and it's now 1AM. I should write tests for this, but I'll add that to the backlog - Backlog only ever grows

Now with AI I describe what I want, it does the grunt work likely cleaner than I ever could, adds tests and warns me about potential edge cases.

I don't know about 10x, but I'm releasing new features that my client cares about faster and I have more time to myself.

All of the negativity around AI writing code sounds like people who would say "You can't trust the compiler, you need to write the machine code yourself"

Will AI fuck up? Yes But I'm the human in the chair guiding it, and learning myself how better to prompt it to keep it from those fuck ups with every iteration.

$875 a month for service and support on a custom built loyalty platform.

Make about $25K up front to build it, then followed up with maybe another $20K worth of various features over the last ~5 years

Starting this month $875 a month to keep supporting them and helping grow his vision (credit management for events...ie: get a nfc wrist band at a party as part of an all inclusive package, has $xxx.xx worth of credit, tap your wrist band to pay)

i'm also starting to try to bridge this out as a more generic platform and look for new clients.

$875 a month in the USA is a nice bit of extra cash. Server costs are coming in around $300 because I haven't optimized aws and there are some legacy systems I'm supporting(VPC costs are killing me) but it'll be nice to have some extra cash to pay off some debt and maybe buy some things to fuel new hobbies.

Nothing much to show other than one client, but I'm on the cusp of charging them monthly vs getting paid by the hour.

Why is that? Is it due to the nature of chemicals it uses?

Right now it's been commissioned by one customer and is a hodgepodge of duct tape and glue.

Trying to slowly refactor functions so I can truly make a platform and onboard new customers.

Mostly consider myself Lucian and I feel like I've assimilated into the American tech population. My history now is just a interesting fun fact. Don't meet too many people from the Caribbean in general in tech circles, so it's always fun to get a reminder that they're out there.

The price is a bit high, but glad to see it in the real world.

Started off as a one off solution for a single client, but then I realized that I could generalize it.

The one off solution is running for my client for the last year, but the generalized API is still just a docker container on my PC.

I've been starting to write about the dev process[1]

[1]https://darrelld.com/signal/21/

AI of course just answers it. I can ask it follow ups, I can give it loose code and it just gets it. My grammar can be riddled with spelling errors and it still gets it. I can go back and forth with it and get a fine tuned answer.

When I used SO I had always just wanted an answer, but had to accept answers that were close, but not quite what I needed.

God forbid if I needed to post a question. I'd immediately get hit with over moderation, or someone closing the question for whatever reason.

I used to be an avid SO contributor up until around ~2015. I saw the mod community turn snarky. AI is just a better way to get stuff done.

https://news.ycombinator.com/item?id=41353838

I went to school with the son of the owner. For about 3 years off and on he'd been asking me about building apps, where he could find good devs, what price to pay.

I'd sent him some info, but never got too involved. Then the pandemic hit, and I found myself with a bit more time to kill, so I listened more to what they needed.

They basically wanted to get a loyalty program going at their gas stations and partner gas stations, but wanted custom rules which their current provider couldn't do with their off the shelf solution.

They also wanted to use one of those old school CC machines that were everywhere before the likes of square showed up. But getting your hands on those units is expensieve.

So I started planning it out. They needed to store customer data, and needed a point of sale device to swipe customer loyalty cards on, which needed to read in customer info, do a deduction, or a store credit top up and print a receipt.

I found a android terminal machine off alibaba, opened up android studio and started hacking away. I hadn't done more than a basic android hello world at this point.

For the backend I used django to get started quickly, and they were very happy to use the django built in admin panel to do stuff as needed, and view transactions.

After I got the devices talking to django, I had to integrate a loyalty vendor they already sourced, and just went along with it, but that was a mistake. The vendor points API doesn't really add much value on what django can already do for me, and my new goal is to become that vendor since I think I can do their product better.

But basically I iterated on it for about a year, launched a little over a year ago, still working out some edge cases and kinks, but they do roughly 25K transactions a month on devices spread out at over 20 stores.

They want to bring it to new islands, so I'm trying to remove some of my duct tape fixes with more stable fixes so that can be smooth sailing come next year.

EDIT: Might get back to writing and update with a much longer post. Draft:

https://darrelld.com/signal/21/

It's turning into a full time side gig that's paid off in handful of batches (~$25K and running)

I'm trying to become a loyalty vendor API.

Would really like to work on my own interconnected systems of blogging tools and social media. Kinda a blend between having your own site and myspace? Not really targeting a market or anything like that, just think it would be cool to do for personal use and sharing with family and friends

This is what I had to learn to let go of imposter syndrome. All the mental hand wringing, constant worry and fear even after they said "good job".

Instead nowadays I wait for someone else to tell me I'm not a good fit for the job, otherwise I just keep on plugging along.

I may have played around with it on a couple of HTML pages written in Notepad way back.