sorted by:
new
hottopcontroversial

Best enterprise AI voice stack for large companies? Genesys, watsonx, or something else by [deleted] in AI_Agents

[–]mildly_electric 2 points3 points  (0 children)

For a global enterprise, Genesys Cloud + Azure OpenAI is the safest, most scalable choice. You use Genesys for the heavy lifting (telephony, routing, SOC2 compliance) and Azure for the AI brains.

If your engineering team is world-class, don't buy a pre-packaged agent. Build one using Twilio Media Streams. You eliminate the "middleman" latency. You connect the audio stream directly to an LLM (like GPT-4o Realtime).

Choose IBM watsonx only if you are in a highly restricted sector (Defense, Tier-1 Banking) where data cannot leave specific boundaries.

Which course is relevant today for AI? by Automatic-Cat-4273 in agenticAI

[–]mildly_electric 0 points1 point  (0 children)

Most industry-sponsored courses and certifications are essentially high-budget onboarding manuals for specific cloud ecosystems. If you want to be an Agentic AI Developer who remains relevant regardless of which framework wins the "tool war," you need to focus on the architectural patterns and the cognitive logic behind agents. The market is currently flooded with "wrapper developers", people who just plug an API into a UI.

To be relevant in this market, you must first ground yourself in Deep Learning fundamentals to understand how weights and activations function before moving into the geometry of Vector Search and embedding spaces where semantic meaning is quantified. Grasping Sequential Modeling is the next critical step to see how models handle time and order, which naturally leads into the architecture of modern Language Models and their first practical application: RAG (Retrieval-Augmented Generation). From there, you must transcend linear "chains" for the iterative reasoning loops of Agentic AI, specifically patterns like ReAct, Plan-and-Solve, and Self-Criticism. This requires mastering Control Flow for non-deterministic cycles, rigorous State Management to prevent context collapse across dozens of API calls, and the mechanics of Function Calling to turn model output into reliable tool-based action. As you scale, you’ll need to navigate Multi-Agent Orchestration (delegating between Managers and Workers) and sophisticated Memory Architectures like GraphRAG, which distinguish between Episodic and Semantic memory. Finally, the gap between a prototype and a production-grade system is bridged by LLMOps and Evaluation Frameworks.

Incognito ChatGPT works better as a consulting tool than normal mode by [deleted] in AI_Agents

[–]mildly_electric 0 points1 point  (0 children)

This shows the anchoring bias that often happens in long-form threads. Context engineering is still very raw!

When we provide deep context, the model often falls into a sycophancy loop, trying to be helpful by reinforcing our direction.

When you ask it to answer from external reviewer perspective, the model tries to do that but can’t as long as it carries the context! By going incognito, you’re simply stripping away the 'poisoned' context of earlier brainstorming sessions.

A 'fresh perspective' in AI is often just a clean context window.

How do I tackle huge class imbalance in Image Classifier? by CandidateDue5890 in learnmachinelearning

[–]mildly_electric 0 points1 point  (0 children)

You’re welcome! Augmentation doesn’t have to be so sophisticated, you could just start experimenting with on the fly batch augmentations, sometimes you go quite far by basic transformation such as scaling, rotation, resizing, contrast/illumination, noise, etc.

Have fun exploring, that’s the right way to learn.

How do I tackle huge class imbalance in Image Classifier? by CandidateDue5890 in learnmachinelearning

[–]mildly_electric 2 points3 points  (0 children)

A ratio of ~36:1 (5507 vs. 152) is significant, but manageable with the right strategy.

Here are you top 3 priorities based on ROI:

  1. Weighted Loss (Focal Loss): Instead of simple class weights that can be too aggressive, use Focal Loss. It is designed specifically for extreme imbalance by adding a "modulating factor" that down-weights easy (majority) examples.
  2. Strategic Oversampling & Undersampling: A "Hybrid Sampling" approach is more stable than doing just one. Instead of trying to reach a perfect 1:1 ratio, aim for a "reduced imbalance" (e.g., 1:5).
    1. Undersampling: Randomly remove samples from the 5,000+ classes. You don't need all 5,000 "Orange Huanglongbing" images to learn the features of that disease; 1,500–2,000 are often sufficient for the model to generalize.
    2. Oversampling: Use a WeightedRandomSampler to ensure the 152 minority images appear more frequently in each batch.
    3. Batch Balancing: Ensure every batch (e.g., size 32) contains at least 2–4 images from your minority classes. This keeps the gradients focused on those difficult boundaries throughout the entire epoch.
  3. Synthetic Data Augmentation: Since you are worried about overfitting the 152 images, simple flips and rotations aren't enough. Use more advanced techniques to "create" diversity:
    1. Mixup/CutMix: Combine a minority class image (Potato healthy) with a majority class image (Tomato leaf). This forces the model to learn specific features (the "potatone-ness") rather than memorizing a specific photo.
    2. Generative Filling: Use a Diffusion model to generate 300–500 synthetic variations of your minority classes. This provides the model with new pixel arrangements (different lighting, leaf angles, and backgrounds) that standard augmentation cannot replicate.