Archived Blog Posts

My path into AI is tied closely to biomedical engineering and neurotechnology. I studied Systems and Biomedical Engineering at Cairo University, then moved into an MSc in Bionics Engineering on the Neural Engineering track at Scuola Superiore Sant’Anna and the University of Pisa. That background changes how I think about software. In neurotechnology, the code is not only a product surface; it is often the bridge between signals, clinicians, researchers, and the person using the system.

Voice AI agents are less forgiving than text agents. In chat, a slow or slightly awkward answer is survivable. On a phone call, latency, interruption handling, unclear escalation, and tool failures become obvious immediately. I saw this up close while helping a team recover from a voice agent product emergency. The work involved fixing their setup, clarifying scaling constraints in VAPI and Retell, and training the team on the operational realities behind call automation.

Retrieval-augmented generation is a strong fit for knowledge work when the bottleneck is not creativity, but finding, comparing, and applying the right information. Grant research is a good example: people need to search policies, eligibility criteria, deadlines, guidelines, and client constraints before drafting anything useful. In a production RAG system, the retrieval layer is not a decorative add-on. It is the product. What has to be designed A useful RAG system needs more than embeddings and a chat box.

AI automation consulting is most useful when it starts with business drag, not with a model demo. The valuable work is usually hidden in repetitive handoffs: inbox triage, policy lookup, grant research, lead enrichment, internal reporting, and support quality control. At EXODIA AI Technologies, I lead teams building applied AI systems for organizations that need dependable workflows more than novelty. One enterprise RAG system for a subsidized finance consultancy reduced grant researchers’ office work by 70% by moving policy retrieval, source comparison, and drafting support into a controlled internal workflow.

Intro Doesn’t matter whether it’s a CakePHP app for a client, your own personal CMS, or any other web based application. If your passing around passwords or other sensitive info you should really implement SSL. SSL provides 2 main perks to your visitors. First it encrypts all communication that flies across the web. This prevents curious or devious billies from getting your secrets. Secondly it ensures to the user that your server is in fact who it claims, and not a nasty ‘man in the middle" attack.