API Design Philosophy - BERTopic for Topic Modeling

Key Takeaways

and I'm curious to also pick your brain on your API design philosophy um you identified some of the main the three pillars uh that you think of in in bird topic but I'm sure while you're also doing other other libraries there are a few things that um you've picked up or Lessons Learned uh of what makes a good um API and I think for example I mean there's a very clear psychic learn sense to to some of that um here's a picture of your mind on just API design philosophy what makes for uh a good API design for for tasks like this I think if I go back to something I've shown previously is this and this so we have modularity you can you can change whatever you want but out of the box it worked well enough for a lot of use cases so what most people want when they're trying new technologies they just want it to work you have three lines of code it works it runs and then you can look at it and say okay this is a horrible package I go with something else that's fine um but you can also say okay it's almost there and I want to change these these and these things and that has been the focus mostly on of the coding of the design that I had in mind making sure that for most usage it works out of the box because topic modeling is also used by a lot of people who don't code 24 7. for those people it needs to work and for for the ones that want to dive into it a little bit deeper and they can expand upon it similarly with designing all of this it has been a struggle at times to find that balance between out of the box you know it worked well enough and you can do everything you want with it and you can see that back in some of the things that I've I've designed a few years ago so at some point I opened up the possibility to use your own umap model and the the parameter is still you map underscore model but you can throw in k-means or anything else in there so technically we should change that to Cluster underscore or or reduction on the score model or something like that um so so with a few years of developing this you see some of these things being snuck in um into the package and some of things are better than others and some things still work and and you know should be improved amazing uh we have a lot of questions we're going to get um to them I don't think we're going to be able to answer all of them I would uh suggest to people to visit the cohere Discord there's a talking language AI Forum there and there's a specific thread for bird topic and this discussion um and so and this goes for both people seeing it live but also people seeing it on on YouTube later uh we'll keep it alive you can keep answering your question we'll have the community answer we'll do our best to uh get the the questions answered there um before we take a couple more questions I'm curious to hear your very high level sort of overview of let's do maybe polyphoses first or let's say let's do keyboard first and then uh polyphose