Arxiv + google + papers with code is how I do it. As another user pointed out, focus on solving your problem. By doing this, you'll search and then naturally find relevant papers. After a while, a lot of papers become super easy to read because they're conceptually easy to grasp. Once you hit this point it becomes extremely easy to skim the content that you're searching for. Once I identify something interesting in my problem space or adjacent then getting through it is the hard part.
TLDR: Focus on a problem domain and search within it. Don't just shotgun it. If its relevant enough to you it will show up. Use filters like HN and whatnot.
Device R&D jobs seem like the way to go. Will likely be a lot of matlab, labview, c, c++ etc. I know a couple people who have had careers in robotics and I myself have done some work in embodied CV. Pretty much c++ without a ton of care around connectivity. Although as a project progresses you’ll basically be stuck doing networking and boy let me tell you networking with edge devices is a lot more annoying and low level than the beautiful rest or gql endpoints most engineers work with.
TLDR: big companies make networking easy because of crud. Pretty much all software companies are just crud apps (maybe with some sockets stuff if they’re cool)
No but shouldn’t be too hard to do. String together something like Lang chain with an instance of chroma running in a docker container. Just need a rest api for that, and then fork over a ton of money for embeddings and you’re done! Jk, but there is an openAI cookbook entry on doing this exact thing. Not sure about cost estimates but it will be quite expensive.
Arxiv + google + papers with code is how I do it. As another user pointed out, focus on solving your problem. By doing this, you'll search and then naturally find relevant papers. After a while, a lot of papers become super easy to read because they're conceptually easy to grasp. Once you hit this point it becomes extremely easy to skim the content that you're searching for. Once I identify something interesting in my problem space or adjacent then getting through it is the hard part.
TLDR: Focus on a problem domain and search within it. Don't just shotgun it. If its relevant enough to you it will show up. Use filters like HN and whatnot.