devstein

Let there be message boards: https://abbs.dev

If anyone else is looking to migrate from Celery to DBOS, we also made this transition and wrote about it https://dosu.dev/blog/migrate-celery-to-dbos-dosu

Very happy we made the switch.

What top K do you use for vector search before passing into the reranker?

I think the only way to keep documentation up-to-date is to have it as part of the PR review process. Knowledge needs to evolve with code.

We working on this at https://dosu.dev/ (open to feedback!)

I believe this is why the importance of written (human) knowledge is only increasing, especially internally at companies. Written knowledge (i.e documentation) has always served as a knowledge cache and a way to transfer knowledge between people.

Without fundamental changes to the LLMs or the way we think about agentic systems, high quality, comprehensive written knowledge is the best path to helping agents "learn" over time.

If it's for personal use I'd recommend https://github.com/TriliumNext/Trilium

^this, but many non-code documents with manual steps can also be kept up-to-date as long as there is a way (a) relate it back to the codebase or another source of truth (b) detect conflicts (when someone says something in contradiction to an existing document)

Disclaimer: We are building this at https://dosu.dev

Couldn't be more spot on. This is exactly why I started Dosu https://dosu.dev/ to reimagine on the "knowledge" side of software engineering.

A useful pattern for serializing Python classes for integration tests that span multiple services

I agree about docs as a tool for thought.

What about the other side of docs, keeping them up to date?

There has been an influx of AI-generated bug reports to popular OSS projects. It's unclear if this is malicious or someone built a tool with good intention that is now causing maintainers to be inundated with issues.

Has anyone stumbled upon an AI tool that helps submit bug reports to OSS project?

https://www.theregister.com/2024/12/10/ai_slop_bug_reports/

Nvm turned out to be a GitHub issue

Just noticed 404s on dbt core - was this announced recently?

https://github.com/dbt-labs/dbt-core

the future of OSS maintenance: https://dosu.dev/

Big fan of Aider.

We are interesting in integrating Aider as a tool for Dosu https://dosu.dev/ to help it navigate and modify a codebase on issues like this https://github.com/langchain-ai/langchain/issues/8263#issuec...

Thank you for the feedback! That's good to know

Just launched a new marketing site with fun animation that requires scrolljacking.

Do you think it's worth it?

Oh nice. It's been a while since I've used LaTeX, but ChatGPT is great with it :)

Agreed! The status meetings we've thought about are:

- Status of project - Summary of weekly work (retro) - Breakdown of work by project

Any status meetings we are missing?

What would be a better workflow? Would it be useful if Dosu took a first pass at clarifying tickets with PMs?

I feel this one. I think there is a ton of room for automation in daily/weekly reporting and status updates

Agree. Where do you find the majority of notifications coming from?

Alerts? Github notifications? Internal questions?

This is spot on (I'm the founder of Dosu).

IMO, we are quite far from the capabilities of reliable issue -> PR generation yet even though it seems in reach.

For this reason, Dosu is focused on question answer, triaging, and generally context gathering because we see it as a pre-requisite to PR generation.

Dosu (https://dosu.dev) | Software Engineers | SF - Hybrid | Full Time

Maintaining you're code should be easier than writing it.

Checkout Dosu in action: https://github.com/langchain-ai/langchain/issues/11371#issue... https://github.com/run-llama/llama_index/issues/7684#issueco... https://github.com/langchain-ai/langchain/issues/11359#issue...

jobs at dosu dot dev

Does anyone know the backstory?

I'm working on a platform to help automate and accelerate the job search process: https://sharedrecruiting.co/

It's also open sourced and powered by GPT https://github.com/shared-recruiting-co/shared-recruiting-co

Check it out and let me know what you think! I'll reach out to chat more :)

I'm working on a platform to help automate and accelerate the job search process: https://sharedrecruiting.co/

Check it out and let me know what you think!

It's also open sourced and written in Go + Typescript :) https://github.com/shared-recruiting-co/shared-recruiting-co

I'm working on an candidate-centric, open source recruiting platform, called SRC ("source"). It promotes transparency and collaboration between candidates and companies by giving candidates the same access to automation and GPT-powered tooling that companies have.

For candidates, SRC is a recruiting email assistant that automatically manages their inbound job opportunities and builds them a personalize job board, so they can hit the ground running whenever they are ready for something new. In the future, SRC will act as a personal recruiter proactively reaching out to companies that meet your criteria and seeing if they are interested.

The goal is to rebuild the modern recruiting stack from the candidate's perspective, emphasizing transparency and collaboration at each step of the recruiting process.

Check it out and let me know what you think! https://github.com/shared-recruiting-co/shared-recruiting-co

New contributors are welcome :)

This Neovim colorscheme: https://github.com/marko-cerovac/material.nvim