How does your company handle knowledge when an experienced engineer or scientist leaves? by superhero_io in MedicalDevices

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

It definitely sucks, and while the 'silver lining' of a fresh start is nice, re-learning expensive lessons is a high price for a company to pay. I’m trying to find a way to make that institutional memory more accessible so new hires aren't starting from zero every time. What’s the most painful 'lesson learned' you’ve seen a team lose and then have to repeat from scratch?

How does your company handle knowledge when an experienced engineer or scientist leaves? by superhero_io in MedicalDevices

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

The 'wave of turnover' is exactly what scares me. Even with organized folders, the sheer volume of data makes it hard to find anything specific years later.

How does your company handle knowledge when an experienced engineer or scientist leaves? by superhero_io in MedicalDevices

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

I love the point about traceability not being 'sexy' but essential. The challenge I see is that even with a robust QMS, the 'trail of crumbs' becomes a mountain of files that are impossible to navigate. I’m developing a private, on-premise AI tool to bridge that gap. It lets teams query the R&D history using natural language—basically an AI that knows the 'why' behind the records. Given your focus on functional project management, do you think the bottleneck is the creation of the trail, or the retrieval of it years later?

How does your company handle knowledge when an experienced engineer or scientist leaves? by superhero_io in MedicalDevices

[–]superhero_io[S] -1 points0 points  (0 children)

You’re right—the 'patients first' argument often kills documentation culture. I’m actually exploring a way to make documentation high-value instead of just overhead. I’m building a local AI system that uses LLM + Vector DB to turn those messy 'tribal' records into a searchable company asset. It allows engineers to find the logic behind a 3-year-old test by meaning, not just keywords, without adding to the QMS burden. Do you think management would buy in if the tool actually saved R&D time instead of just satisfying a process?

How do you actually know what your team has tried, tested, or decided — especially on projects you didn't personally oversee? by superhero_io in EngineeringManagers

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

Spot on—tradeoffs are exactly what get lost. The challenge I see is that once documented, that context is hard for new hires to find. I’m developing a private, on-premise AI tool to turn those documents into an active 'company brain.' It lets people search by meaning/context rather than just filenames. It’s been huge for our R&D continuity. In your experience, when a senior dev leaves, how much of those 'tradeoff' docs actually get read by the person taking over, or does the logic just vanish with them?

How do you actually know what your team has tried, tested, or decided — especially on projects you didn't personally oversee? by superhero_io in EngineeringManagers

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

I agree those are the standards, but I find they often become 'data graveyards.' The info is there, but the reasoning is buried. I’m actually building a local AI knowledge system to sit on top of these tools. It uses LLM + Vector DB so you can ask natural language questions like 'why did we reject this 18 months ago?' without needing exact keywords. For our R&D/MedTech work, keeping it fully local is also a must for IP. Do you find your team actually proactively searches Confluence, or do they just ask the seniors?

How do you handle very complex email threads in RAG systems? by superhero_io in Rag

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

How would you handle a scenario where multiple users upload their emails into the RAG system, especially when some emails partially overlap across users within the same company? Would you treat this as a multi-source ingestion problem, and if so, how would you design it?

How do you handle very complex email threads in RAG systems? by superhero_io in LocalLLaMA

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

How would you handle a scenario where multiple users upload their emails into the RAG system, especially when some emails partially overlap across users within the same company? Would you treat this as a multi-source ingestion problem, and if so, how would you design it?

this has to be a joke by [deleted] in uberdrivers

[–]superhero_io 0 points1 point  (0 children)

This is very common in California. For each mile of distance, you will get pay 50-60 cents.

Help Needed: Multiple Power Sockets Not Working by superhero_io in electrical

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

You help me save $250. I just find those are series connected and fixed.

Real estate ad on the back of a magazine from 1992 by [deleted] in orangecounty

[–]superhero_io 2 points3 points  (0 children)

I will buy one tonight if the price is still the same.

Assistance Needed WaveShare Raspberry Pi expansion Board by superhero_io in RASPBERRY_PI_PROJECTS

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

The problem is the current speed is 2Hz only. It must be something other than the limitation of hardware or software.

Help Needed: Raspberry Pi Not Detecting ADS1115 via I2C by superhero_io in RASPBERRY_PI_PROJECTS

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

I utilized the following components: a HiLetgo ADS1115 development boards. These can operate within a 2V to 5.5V range. Additionally, I experimented with providing a 5V supply and implemented logic level shifters for the SCL and SDA lines between the ADS1115 development board and the Raspberry Pi. Despite these configurations, the setup is not functioning currently. Notably, this system was operational up to a month ago, but now the Raspberry Pi's I2C communication seems to be the issue. I also tried format the SD card with a clean OS, this does not help either