Mr. SeeFun.Dev
Open in Telegram
He/Him Building, coding, and sharing Github- https://github.com/sifenfisaha Portfolio- www.seefun.dev Dm- @see_fun
Show moreThe country is not specifiedTechnologies & Applications35 793
1 232
Subscribers
+624 hours
+317 days
+8930 days
Posts Archive
1 232
يا مَن تُحِبّونَ النبيَّ محمّدًا
صلّوا عليه وسلّموا طولَ المدى
فصلاتُكم وسلامُكم نورٌ لكم
في أمسِكم وبيومِكم ولكم غدًا
اللهم صل وسلم وبارك على نبينا محمد 🤍
@sifendev
1 232
Does anyone remember the WebSocket alternative for serverless frameworks that I posted about a while back? I completely forgot the name.
@sifendev
1 232
Basically, a WhatsApp agent is an AI chatbot that replies to you directly on WhatsApp. it could act as a receptionist, a customer support agent, or a general AI assistant.
let's say you own a car dealership, and most of your customers use WhatsApp to check available cars, ask about prices, or book appointments with the manager.
if you already have a full e-commerce website, what i used to do was build an AI agent on top of the existing backend. the agent would have access to the necessary data and tools, allowing it to check car availability, look up prices, book appointments, and handle other tasks.
building these agents for multiple projects was incredibly repetitive and time-consuming. explaining the entire process to my teammates every time wasn't ideal either.
so i built a framework that handles all the complex parts. now, you just need to build the tools your agent needs, which is pretty simple, and the framework takes care of the rest.
@sifendev
1 232
The main reason i built this is because i build tons of whatsapp agents for clients, and tbh, it's not fun doing the same thing over and over again.
on top of that, explaining how to build them to my teammates wasn't ideal, so i built this framework to help them build whatsapp agents seamlessly, without all the pain.
@sifendev
1 232
1 232
me not getting a speaker invitation at the omarchy meetup after convincing half the community to switch😭
@sifendev
1 232
Repost from Mo' tries
Aight aight, there is this lil thing I made that am proud of lowkey.
It's a react router style routing lib for kotlin. Written in pure kotlin so you can use it anywhere.
It uses the builder pattern, you basically add your routes and the final .build() function makes a readonly prefix tree.
The reason we have a prefix tree (or Trie) is because we want a data structure that can look at a route like
/home/apps/me and select from the routes under each one (home, apps and me) the correct one.
Generally, when you see tree data structures in the wild, they usually solve a multiplexing problem (choosing one option out of many).
It's pretty neat, I used TDD for it.1 232
1 232
Repost from N/a
Just like a nest is built one small piece at a time, I'm building my career, projects, and life -- with plenty of bugs 😅, random nonsense 👀, and lessons along the way.
I'm not here because I have everything figured out. I'm here to learn, build, be consistent & disciplined, share what I know, and learn from you guys <3.
This isn't just my nest. I hope it becomes a little place for all of us to lay down ideas 🤭, learn, share, grow, and figure things out together.
Hopefully, by keeping to add one piece at a time, we can look back someday and see how much we've built together.
