User
Write something
Weekly AI Community Meetup is happening in 5 days
Pinned
Soft Launch: The DDS Builder Codex
We’re quietly launching the DDS Builder Codex for our Skool community. It is your starting roadmap to understand the four stages of your AI journey: Identity, Learning, Building and Community. I invite our community members to complete the Codex, follow the instructions provided inside, and share your learning journey with the community. Your feedback will help us improve the experience before the wider launch. Start here: https://www.skool.com/decoding-data-science-6929/classroom/740bbfa7
Soft Launch: The DDS Builder Codex
6th Edition AI Accelerator Bootcamp
It was my first time participating in the bootcamp with Decoding Data Science (DDS) and it was a great experience overall. Mr. Mohammad and the team have worked hard to create a detailed and comprehensive bootcamp that enables participants from various backgrounds to understand the material and apply it towards the project. The DDS team and the participants of the bootcamp were all supportive which made the process of learning and applying AI skills easier.
0
0
From Idea to Agent: The CarePilotAI Story Goes Public
Every builder remembers their first published word about the thing they're building. This is mine. Today CarePilotAI makes its debut on Decoding Data Science — the story of an agent that quietly runs a clinic's front desk while the humans focus on the humans. Booking. Insurance. Billing. Payment. All handled. All auditable. All 24/7. Thank you to @Mohammad Ahmad and the DDS community for the platform, and to everyone who nudged this from a slide into a system.
From problem statement to a production-ready enterprise assistant in one weekend. 🚀
✨ Wrapping up the final checkpoint of the Decoding Data Science **AI Accelerator Bootcamp** by shipping my project: *Chappie — DDS HR Intelligence* 🤖💼 Instead of building a simple toy wrapper, the goal across Workshops 2 and 3 was to design a production-style Retrieval-Augmented Generation (RAG) system that HR teams and employees can actually trust. Here is a breakdown of the architecture, engineering decisions, and key takeaways from the build: 🛠️ Architecture & Tech Stack : ❇️ Orchestration & Data Pipeline: Built with LlamaIndex to chunk, index, and retrieve unstructured enterprise HR documents (handbooks, leave policies, and remote work FAQs). ❇️ Vector Database: High-performance indexing and semantic search powered by Pinecone. ❇️ Reasoning & Generation: Grounded LLM generation with OpenAI embeddings for high-dimensional semantic matching. ❇️ Interactive UI: A custom, dark-themed Gradio interface deployed directly to Hugging Face Spaces, equipped with session memory and quick-access prompt presets. 💡 Core Engineering Focus Areas 🔹 Strict Document Grounding & Citations: Every response provides verifiable citations directly referencing the source policy (e.g., Source: DDS Leave Policy (Synthetic) v1), eliminating ungrounded speculation. 🔹 Boundary & Fallback Handling: When a user asks for personal/confidential records outside the document scope (such as real-time individual leave balances), the assistant avoids hallucination and routes them to official support channels. 🔹 Session State & UX: Built-in session memory to retain conversational context, paired with quick-access buttons for standard HR questions (parental leave, carry-over rules, health insurance). 🔗 Live Hugging Face Space: https://lnkd.in/dz6MatpR Returning to build with @Decoding Data Science once again reinforced that enterprise AI isn't just about prompt tuning—it's about clean data pipelines, evaluation benchmarks, and reliable guardrails. On to the next build! 💻
From problem statement to a production-ready enterprise assistant in one weekend. 🚀
🚨 A machine sensor doesn't send data directly to your dashboard.
So what actually happens between the machine and the dashboard? Imagine a vibration sensor attached to a motor. The sensor detects a vibration. But that's only the beginning. 👇 Sensor → MCU / PLC → Communication → Edge → Cloud → Dashboard At each stage, something different happens: 🔹 Sensor — captures the physical signal 🔹 MCU / PLC — reads and processes the data 🔹 Communication layer — moves the data 🔹 Edge — can filter, store, process or analyze it locally 🔹 Cloud — provides scalable storage and analytics 🔹 Dashboard — turns the data into something humans can understand And this is where Industrial IoT becomes interesting. The real engineering challenge isn't simply: “How do I connect a sensor to the internet?” It's: “Where should the data be processed, how should it move, and where should decisions happen?” ⚙️ I'm starting a new series exploring this journey — from Embedded Systems and MCUs to Communication, Edge Computing and Smart Factory Architecture. This is Part 1: From Sensor to Smart Factory. 👇 Which layer are you most interested in — Embedded, Communication, Edge or AI? Decoding Data Science Mohammad Arshad #IndustrialIoT #IIoT #EdgeComputing #SmartFactory #EmbeddedSystems #Industry40 #Automation #IoT #Engineering #ArtificialIntelligence
🚨 A machine sensor doesn't send data directly to your dashboard.
1-30 of 461
powered by
Decoding Data Science
skool.com/decoding-data-science-6929
Learn AI, data science, and career growth through practical workshops, mentoring, challenges, and a supportive community.
Build your own community
Bring people together around your passion and get paid.
Powered by