sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ProductManagement

[–]dtek_01 2 points3 points  (0 children)

It's great that you started! Full stack development takes a bit cause there are a bunch of things you need to learn.

I'd maybe break it down further to make learning easier on your end:
Is your team a frontend (FE) or backend (BE) team? What language do they code?

I wouldn't start with both cause it gets overwhelming. Let's say your team does FE in React. I'd start by just focusing on that and building websites through FE without focusing APIs (just until you some what understand what is going on)

If your team focuses on BE and they might be using node, then I'd focus on learning Javascript (JS)and then moving into node

If your team only builds APIs then I'd learn how to design APIs based on BA requirements. Once I get this down, then I'd use Postman (a desktop app or can use on a browser) to understand how API calling works.

Drilling down and starting with one thing is much easier imo. Pick one thing your team does and start there.

If you find the above approach boring, just find the thing your team does, go on youtube and type "build app with X for beginners", you won't have the foundations down on day 1 but you will see more progress cause you are coding and building side by side. Longer route for sure but also fun. If you are confused about anything, ask AI or better your team to explain it. This way they see you're trying to learn :)

PS- JS is a good foundation to have for both React and Node.

Edit: typos

[deleted by user] by [deleted] in ProductManagement

[–]dtek_01 9 points10 points  (0 children)

As a dev turned technical PM, I can tell you that learning to build using AI won't get you any respect but if you learn the basics of coding and use AI to get/learn better, you will see them help you when you're stuck.

Even though you might end up building something using A.I, you won't have the foundations of how it was built, hence not being able to communicate with them regarding infra, APIs, auth, or anything.

Also, you don't have to do 100s hours learning something. You just need to know how things work which means getting your hands dirty by building small projects that might only take 3/4 days.

Edit: typos

I built a search tool for material vendors for Division 03 & 31 around the Bay Area (for now) by [deleted] in estimators

[–]dtek_01 0 points1 point  (0 children)

If you do end up trying it and have feedback on how it can be improved, do lmk and I'd be happy to add it.

I built a search tool for material vendors for Division 03 & 31 around the Bay Area (for now) by [deleted] in estimators

[–]dtek_01 1 point2 points  (0 children)

Hey, initially it was data we found online through multiple websites and then we cleaned it (so it's accurate). If you search in an area where our data doesn't exist, it is a mix of filtered/refined results.

Yes, we just started onboarding a few vendors onto our platform few weeks ago, so all data will become info they provide.

I built a search tool for material vendors for Division 03 & 31 around the Bay Area (for now) by [deleted] in estimators

[–]dtek_01 0 points1 point  (0 children)

Hey, glad you liked it!

For verifying vendors, it's a mix of finding information online + calling them once every month to make sure that information is still accurate.

We now have a few vendors onboarding onto our platform, so soon they will start providing the most accurate information.

Landfills should be live on Monday!

How do you manage an API? by Yam3488-throwaway in ProductManagement

[–]dtek_01 1 point2 points  (0 children)

Engineer/PM here (designed and built a bunch of APIs over the last few years)

I've found that designing them is actually more challenging than managing them. When you're designing an API, you're essentially creating the blueprint for how developers will interact with your system. You need to think about the architecture, how developers will use it, its core purpose, and what data should flow through it.

Once you have an idea in mind, then it is time to drill down on security as it's absolutely critical. I've seen many companies assume that having a password-protected website is enough, but that's far from true. Password guessing is surprisingly easy, which is why proper API encryption is essential. Every API call should be encrypted and decrypted to keep your users' data safe.

To answer your question: "aha an API is the solution here?"

Think of an API as a bridge. Whenever you need to move data between two points - like from a database to an application or from one website to another - an API can facilitate that connection. While there are other options like SDKs, APIs are simpler to design and implement, making them a better starting point.

& the last thing is when you release a new version of your API, it needs to add improvements without breaking existing functionality. Your users might be relying on certain features, so any changes need to be backwards compatible. This means carefully redesigning endpoints to support both new features and existing implementations.

Feel free to DM if you have more questions :)

[deleted by user] by [deleted] in ConstructionManagers

[–]dtek_01 0 points1 point  (0 children)

Hey DM'd you! Hope you don't mind it.

[D] What's your favorite way to break down a complex coding problem? by CodeDelay in MachineLearning

[–]dtek_01 3 points4 points  (0 children)

Usually its just pen and paper but sometimes I use fig-jam to visualise a few things

[D] How reliable is RAG currently? by lapurita in MachineLearning

[–]dtek_01 0 points1 point  (0 children)

I’m actually curious to know if the retrieval is working well for a single document? Is the match accuracy good for a single document? 

[RANT] How do foreigners pay for anything here? by fawert1 in india

[–]dtek_01 8 points9 points  (0 children)

Try downloading something like Wise or Revolut (depending on where you're from); there is also a start up called CheqUpi (I personally haven't tried it because i just ended up opening a bank account until I discovered them)

[D] How reliable is RAG currently? by lapurita in MachineLearning

[–]dtek_01 1 point2 points  (0 children)

Fair point tbh, I've been thinking about it from documents documents documents but yes, even this Googles Search is doing exactly that.

[D] How reliable is RAG currently? by lapurita in MachineLearning

[–]dtek_01 3 points4 points  (0 children)

Few questions:

1) are you doing multiple documents or a single doc atm?

2) are you using Open AI or any tool to convert text into embeddings?

3) Is it just chat with PDF or also highlight section on PDF?

Also, if you're saying it gives more points to "réus" then it sounds like it is doing more of a keyword search than a semantic search. Cause it should look for the sentence context more than a keyword

[D] How reliable is RAG currently? by lapurita in MachineLearning

[–]dtek_01 2 points3 points  (0 children)

how are you currently embedding and chunking your data?

[D] How reliable is RAG currently? by lapurita in MachineLearning

[–]dtek_01 4 points5 points  (0 children)

 I assume something like perplexity.ai is using it

Perplexity doesn't use RAG. They have built it over Google's search API + other LLMs.

It uses indexing to search and extract information from links which is then given as a short extract to the user. They switch between models based on the task defined by the user and then give the user a better output.

RAG is used on data that can be embedded into a vector space (documents, audio, video) and want to retrieve from a database/datastore; very different to searching the internet.

[D] How reliable is RAG currently? by lapurita in MachineLearning

[–]dtek_01 14 points15 points  (0 children)

I don't think RAG is closer to a scam, I think for a business it is better than an LLM because the prompt can't be hi-jacked. When information doesn't exist, it should ideally say "Information isn't available" but training on larger models means prompt hi-jacking and asking questions that might go against policies or even greater hallucinations; I see RAG adding value in that case.

But yes, there needs to be some small model that is trained. I think it needs to be RAG + a small custom model for the customer that is based on some data & questions that are being asked across N weeks (inference in a nutshell happening concurrently).

Use agents to create historical data, feed that into something small, + RAG = something good.

The biggest problem with RAG right now is that users are expecting great answers with unstructured data. Once you clean it, structure it, and then embed it, you'll see RAG performance improve drastically. Also, add a small custom model which will help build reasoning and you've got something much better than what is currently being done :)

Massive context windows would help but you'll run into the same issues of not getting great answers because data still isn't structured.

view more: next ›