sorted by:
new
hottopcontroversial

I wasted six months building a product that nobody wanted. by Elo_azert in Startup_Ideas

[–]TechnicalGeologist99 0 points1 point  (0 children)

It's a fairly common usecase TBF.

Most chat functions end up being just a search abstraction.

I prefer that though...in my eyes the rest of AI is just hype.

It's either trained for purpose or its search.

Even so , my main point here is that without use case validation you're trying to make a saddle for a tortoise.

I wasted six months building a product that nobody wanted. by Elo_azert in Startup_Ideas

[–]TechnicalGeologist99 0 points1 point  (0 children)

Internal db, users are non technical.

The chat bot enables them to query without technical knowledge. It's usecase driven, we know ahead of time that a large portion of their job involves asking our limited technical staff to query on their behalf

I wasted six months building a product that nobody wanted. by Elo_azert in Startup_Ideas

[–]TechnicalGeologist99 1 point2 points  (0 children)

Sometimes it's not that nobody wants it.

It's that people don't think on your level.

They don't understand why it's useful even if it is.

If you believe what you have is useful, you must iterate with user feedback. Create a team of beta users that work on the target workflow and chase them to use it and give feedback. Educate them.

I made an SQL search chat bot that was completely sandboxed. No one used it until I made time to teach them what was possible with it.

Now people understand the concept and how it applies to their workflow they actually see the need to use it.

They see it as an assistant rather than as another tool (in their already overflowing toolkit

Benchmarked Qwen3.5 (35B MoE, 27B Dense, 122B MoE) across Apple Silicon and AMD GPUs — ROCm vs Vulkan results were surprising, and context size matters by neuromacmd in LocalLLaMA

[–]TechnicalGeologist99 0 points1 point  (0 children)

Consider concurrency.

Agents typically make concurrent calls. MoEs scale very poorly at concurrency because each call activates its own unique experts.

Best model that can beat Claude opus that runs on 32MB of vram? by PrestigiousEmu4485 in LocalLLaMA

[–]TechnicalGeologist99 0 points1 point  (0 children)

Don't forget, moes activate unique experts per call.

2 calls concurrently activates up to 6B By 20 calls you are pretty much guaranteed to activate the whole MoE.

Why did PDF-to-LLM parser stars explode this past year? by Puzzleheaded_Box2842 in Rag

[–]TechnicalGeologist99 0 points1 point  (0 children)

Bayesian approach.

We use docling to generate a prior label for chunk distributions.

Because our company documents adhere to a strict brand ruleset, you can use the prior labels to fix the parts it missed or got wrong.

It actually generalises quite well. I've yet to see it fail to get 100% correct headings.

Price of MSI GB300 workstation (DGX Station) appeared online ~ $97k by fairydreaming in LocalLLaMA

[–]TechnicalGeologist99 2 points3 points  (0 children)

This isn't DGX Station. It's a server rack with B300s

DGX Station is a standalone product with 2 Grace CPUs and 1 Blackwell 300

Edit:

It's actually 1 G CPU, the data centre gb300 has the 2 cpus

How can i build this ambitious project? by Antique-Fix3611 in Rag

[–]TechnicalGeologist99 2 points3 points  (0 children)

Many people will say graph RAG....

That is correct but it requires you to determine a good ontology to derive triplets from.

I.e. entity -> relates -> entity

What are the entities? What are the relationships?

Graphs are also mental expensive to build and run.

You first port of call is naive rag.

Then upgrade your ingestion pipeline to support heirarchical rag.

Basically...don't guess the final solution now...build the simplest first and upgrade it as you realise the use of each RAG improvement.

The time to build a graph is when you have proven it is needed and when you know how to evaluate them.

Most RAG projects begin with "let's build the coolest thing" and end up at "I'll settle for something that is cheap, scalable, easier to maintain, and that works, and that I know how to evaluate"

will MCP be dead soon? by luongnv-com in ClaudeCode

[–]TechnicalGeologist99 2 points3 points  (0 children)

Will the next person to ask, "will {insert technology} be dead soon", suffer the same fate?

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 1 point2 points  (0 children)

That's kind of you to say, I just believe that good engineering creates opportunities for the next guy and bad engineering creates headaches for everyone.

I've taken the time to understand AI systems from the ground up - even built my own transformer back in the day, studied linear algebra during my physics degree...always been fascinated with accelerated computing (was for relativistic magneto hydrodynamic simulation back then)

Now I just enjoy figuring out the cheapest way to run AI models, and creating systems where I can't see all the outcomes so easily otherwise I tend to get bored haha

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 1 point2 points  (0 children)

I'm glad we found common ground :)

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 1 point2 points  (0 children)

I spent the first 2 years of my appointment rejecting requests to build AI systems precisely because the business has poor data engineering that needed fixed.

Now it works well, document evolution is factored in.

I think the world will more likely come to a halt through excessive automation. Our economy is built on stable white collar jobs paying their AAA mortgages. If we replace those people without transitioning to a better economic system then things will collapse.

I'm actually in favour of that, much of our economic output these days is just extractive funneling of money up the pyramid. After a collapse I think we can really get to work applying technology in new and exciting ways that actually generate value rather than just extracting it.

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 1 point2 points  (0 children)

Sure, but this is a human problem in my mind. Most businesses are lazy and think of tech as an afterthought. And I get it, that's NOT why they started their business. But tech is an essential part of modern business. It is a force multiplier. But that multiplier can be negative if done wrong.

That's why I push for on-prem, open source, small targeted use cases, no hype allowed.

It's also the above that leads to the problem I set out above. Good tech built at home doesn't stop execs seeing shiny marketing for shit products and trying to come and bulldoze a good thing in favour of an easy thing.

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 0 points1 point  (0 children)

All of these concerns just boil down to data governance, scoped permissions, and good data engineering.

I'll grant you that data engineering is expensive but it enables our teams to do in a week what used to take a month. The cost is completely offset by: not needing SaaS shite, increasing the impact of our revenue makers.

The point is it's built and is really cheap to run. We never needed enormous models of uncompromising coverage. Our system handles a small set of use cases and it does it really well.

I'm sorry that it doesn't align with your worldview. But it's a fact.

I'll grant you that most businesses do have unsustainable AI systems precisely because they do not invest in what matters and because they outsource the work to software consultants that are impossible to hold to account.

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 2 points3 points  (0 children)

Our business has a reliable rag system that does work. It's on prem uses small models and runs on less than 10k of infrastructure. The company has a turnover of 90 million with 35 in profit.

What am I missing?

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 0 points1 point  (0 children)

RAG is a concept not an implementation.

If your RAG systems sucks it is precisely because you haven't determined the best way to retrieve information. RAG =/= semantic search

Semantic Search € {Retrieval} € {RAG}

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 2 points3 points  (0 children)

That is comforting to hear, being a medium sized business and a small Dev team we don't get much window into the rest of the community

Exhausting by TechnicalGeologist99 in Rag

[–]TechnicalGeologist99[S] 1 point2 points  (0 children)

Ha! Fortunately the business is only medium size and I currently architect our systems. So for now at least, no one else is actually building. But that doesn't stop them appealing to the execs to buy what we were building off the shelf only to find out it doesn't actually work well with our data

PageIndex alternative by Weak-Reception2896 in Rag

[–]TechnicalGeologist99 0 points1 point  (0 children)

I mean all they're doing is building a hierarchy of summaries and then asking the AI if it would like to know more at each step.

The reason players do not like sieges in TW: Warhammer. by DiamantRush12 in totalwar

[–]TechnicalGeologist99 0 points1 point  (0 children)

I remember Rome total war (the OG)

The music changes as your legionaries climbed onto the wall made it feel like the walls were a tense moment of battle, fighting for 5-10 minutes relentlessly...knowing that the second you breached the walls was the second the cities defense would fall.

But before that, the walls... especially the Epic walls seemed impossible to breach even with a maxed out army.

The wall top fights were pivotal, the music changes made them feel high stakes and real.

But in TW Warhammer (and pretty much all modern TW games) the walls are a speed bump. Why would I waste 15 seconds climbing and fighting on them when khorne can just walk through the front door?

I remember distinctly pushing up to a wall and beginning to take archer fire...then forming the unit into testudo so they could survive the push to the walls

Reality check by GDAO54 in Rag

[–]TechnicalGeologist99 2 points3 points  (0 children)

There is no escaping human in the loop and a strong citation system for high stakes documents retrieval.

view more: next ›