TECHNOLOGY 

Published on

KembaraXtra–Computer Terms – 386
The designation 386 typically refers to the Intel 80386DX microprocessor, a 32-bit CPU that marked a major step forward from the earlier 286 line. It introduced full 32-bit registers, a 32-bit data bus, advanced memory management capabilities, and support for protected mode with large address spaces. The 80386DX became the foundation for many desktop and server systems and enabled the development of more powerful operating systems and applications.


Picture
Published on

KembaraXtra–Computer Terms – 386BSD
386BSD is a version of the BSD UNIX operating system created for systems based on the Intel 80386 processor. It is distinct from BSD386, which was produced by Berkeley Software Design, Inc. Released in 1992 as a freely distributable system, 386BSD played a key role in the history of open-source UNIX-like operating systems. Over time, it gave rise to two significant descendants, NetBSD and FreeBSD, each of which evolved into separate, widely used projects. These later systems continued and expanded the design goals of 386BSD, focusing on portability, robustness, and performance across a wide range of hardware platforms.


Picture
Published on

KembaraXtra–Computer Terms – 386DX

The term 386DX refers to the full-featured Intel 80386DX microprocessor, a 32-bit CPU with a 32-bit data bus and 32-bit registers. It supports advanced operating modes, including protected mode, and can address large amounts of memory. Systems built around the 386DX were capable of running sophisticated multitasking operating systems and applications that significantly outperformed earlier 16-bit platforms.


Picture
Published on

KembaraXtra–Computer Terms – 386SL

386SL is the name used for a variant of the Intel 80386 processor designed for portable and low-power computing environments, such as early laptop computers. This chip integrates power-management features and other functionality that reduces energy consumption, extending battery life while still maintaining compatibility with 80386 instruction sets. It allowed laptop manufacturers to deliver mobile systems with PC performance levels that were similar to desktop machines of the time.


Picture
Published on

KembaraXtra–Computer Terms – 386SX

386SX refers to a cost-reduced version of the Intel 80386 microprocessor. While it retains a 32-bit internal architecture and instruction set, it uses a 16-bit external data bus and often a narrower address bus. This made it cheaper to integrate into computer systems, as it could be paired with less expensive support chips and memory subsystems. As a result, 386SX-based systems offered many of the programming advantages of 32-bit processors at a lower overall cost, although with somewhat reduced performance compared to 386DX systems.


Picture
Published on
Artificial Intelligence – Testing and Maintaining Your Applications

Building AI systems—whether they learn continuously from new data (online learning) or are trained once and used afterward (offline learning)—requires more than just creating a model. It also requires ongoing testing and maintenance to make sure everything keeps working the way it should. No matter how the model learns, we must establish reliable monitoring systems and safety checks that alert us whenever the model’s predictions or its essential infrastructure start acting unexpectedly.

Expanded Explanation

In traditional software development, testing is relatively straightforward: for each specific input, we know exactly what the output should be. This makes it easy to write tests that verify whether the system behaves correctly.

Machine learning, however, doesn’t follow that neat pattern. A model may produce different outputs for inputs that look similar, and those outputs depend on many factors—training data, randomness, environment, even hardware differences. This makes classic, rule-based testing harder to apply.

Despite these challenges, testing remains crucial. In machine learning projects, “testing” involves carefully verifying the following:
  • Inputs: Are we providing the model with data in the right format and within expected ranges?
  • Outputs: Are the predictions reasonable, consistent, and within acceptable boundaries?
  • Errors: Are we handling failures, missing data, or unexpected behaviors safely?

In this chapter, we will explore practical methods for testing machine learning code, including strategies tailored for systems that behave unpredictably. We’ll also go through best practices that help ensure reliability even when perfect reproducibility isn’t possible.

Keeping AI Applications Healthy After Deployment

Once an AI model is released into the real world, the job isn’t over. Models may degrade over time as the world changes—a phenomenon known as model drift. To keep the system stable, AI applications must be continuously monitored and maintained.

DevOps tools, such as Jenkins, play an important role here. They can automatically run a set of tests every time a new version of a model or application component is created. Only if all tests pass will the updated version be allowed to move into production. This reduces the risk of shipping broken or unsafe updates.

While we do not expect machine learning engineers to design full development or deployment pipelines on their own, it is important to understand the key principles behind them. These concepts help you collaborate effectively with DevOps teams and ensure that your models are safely and efficiently deployed.



What This All Means?

Imagine you built a robot that gives you advice—maybe it helps with homework or tells you what game to play. To make sure your robot stays helpful and doesn’t start acting weird, you need to check on it regularly.

Testing

Testing is like asking the robot:
  • “Are you listening correctly?”
  • “Are you answering in a way that makes sense?”
  • “Are you freezing or making mistakes?”

In regular computer programs, the answer is the same every time, so it’s easy to test. But with AI robots, they might give different answers because they learn from data. That makes testing trickier!

Maintaining

After your robot is built, you still need to watch it. Maybe it starts learning things that are wrong or confuses new information. So you check it from time to time and fix things if needed.

Tools like Jenkins are like helpers that test the robot every time you teach it something new. If the robot starts making mistakes, the helper won’t let those mistakes go into the real world.

So basically:
  • Testing: making sure your AI works properly.
  • Maintaining: keeping it working even as things change.
Picture
Published on
Artificial Intelligence – Scaling Out with Distributed TensorFlow

As machine learning models grow larger and require more computation, a single machine—or even a single GPU—may not be powerful enough to train them efficiently. To overcome this limitation, TensorFlow provides mechanisms to distribute training across multiple machines or devices, allowing us to scale out our compute resources.

Although several distributed frameworks exist—native Distributed TensorFlow, TensorFlowOnSpark, and Horovod—this section focuses exclusively on native Distributed TensorFlow, which is built directly into TensorFlow’s core design.

Approaches to Distributed Training

In distributed systems, there are two main strategies for dividing the workload: model parallelism and data parallelism.

Picture
Model parallelism splits different parts of the model across multiple devices.

  • Device A handles one portion of the model
  • Device B handles another portion
  • Together they complete forward and backward passes

This method is most useful when the model is too large to fit onto a single GPU, or when you have a large number of compute nodes that you want to utilize simultaneously.


Picture
Data parallelism replicates the entire model on each device.
Each device receives a different piece of the training data, computes gradients, and then sends them to be combined.​
  • Works best when you have fewer nodes
  • More common than model parallelism
  • Easy to scale and widely supported in TensorFlow
After devices complete their work, a central entity aggregates the results.


Picture
When performing data parallelism in TensorFlow, training relies on a key component known as the parameter server (PS).

Parameter Server Responsibilities

  • Stores the master copy of model weights and variables
  • Aggregates gradients sent from workers
  • Applies updates and broadcasts updated parameters back
Parameter servers typically run on CPUs.

Worker Nodes (TensorFlow Servers)

  • Typically run on GPUs
  • Perform forward/backward computations
  • Send gradients to the parameter server
Among these workers, one is designated as the chief worker, which is responsible for:

  • Initializing variables
  • Coordinating training steps
  • Saving checkpoints
  • Managing the training session

Together, the parameter servers and workers form a TensorFlow cluster.


Picture


Synchronous vs. Asynchronous Updates

​
Distributed training can share gradients and update the model in two different ways: synchronously or asynchronously.

Synchronous Distribution

All workers operate in lockstep.


  • Every worker receives its data at the same time
  • Every worker computes gradients
  • Workers wait at a barrier until all results are ready
  • Only then is the model updated

Pros:
  • More stable updates (similar to large-batch SGD)

Cons:
  • Slowest worker (straggler) delays everyone
  • Can significantly reduce throughput

Asynchronous Distribution

Workers operate independently, without waiting.


  • Each worker trains at its own speed
  • Gradients are sent to the parameter server immediately
  • The PS updates the model as soon as gradients arrive

Pros:

  • Fast and efficient
  • No worker-to-worker waiting

Cons:

  • Workers may use older parameter versions
  • Updates are noisier

SGD Behavior in Distributed Training


Stochastic Gradient Descent (SGD) normally works in a loop:


  1. Compute gradients
  2. Update model weights
  3. Repeat

In distributed training:


  • Synchronous SGD = all gradients collected → update once per iteration
  • Asynchronous SGD = each gradient applied immediately, leading to many small updates

This changes training dynamics and may affect convergence stability, depending on the method used.

Preparing Code for Distributed TensorFlow

Building a distributed TensorFlow program involves three main steps:

1. Define the Cluster


Use tf.train.ClusterSpec and tf.train.Server to describe:

  • Parameter servers
  • Worker servers
  • Network addresses
  • Roles of each machine

2. Assign Devices with tf.device()

Explicitly place:


  • Variables on parameter servers
  • Computation operations on worker GPUs

This ensures TensorFlow knows exactly where to run each operation.


3. Use MonitoredTrainingSession

Replace a standard session with:


  • tf.train.MonitoredTrainingSession()

This automatically handles:


  • Initialization
  • Recovery from failures
  • Checkpointing
  • Synchronization between chief and workers

This makes distributed training more robust and easier to manage.


Summary

Why do we “scale out”?


Imagine you have a huge pile of homework and only one pencil—you’ll finish very slowly.
But if ten friends help you, you’ll finish much faster.
Distributed TensorFlow is like that: many computers helping train one big model.

Two Ways to Share the Work

Model Parallelism

Everyone works on different parts of the project.

Data Parallelism

Everyone works on the same project, but with different pages of homework (different data).

What’s the Parameter Server?

It’s like the team leader:


  • Collects everyone’s answers
  • Decides the final version
  • Sends the new version to the whole team
Synchronous vs. Asynchronous


🟦 Synchronous = “Wait for everyone!”

Nobody moves forward until everyone finishes a task.


🟩 Asynchronous = “Go at your own speed!”

You send your work when you’re done, without waiting.





Published on

Artifcial Intelligence-Testing Deep Learning Algorithms

The AI industry has advanced rapidly in model performance, yet it still lacks strong testing practices. Even leading organizations rely far too often on manual checks instead of automated, repeatable tests for their algorithms. Manual inspection is slow and unreliable, which makes software fragile and difficult to maintain.

Earlier, you learned how training, validation, and testing datasets help verify overall model behavior. These are high-level checks. In this section, we focus on unit testing, which examines the smallest components of a system—individual operations, layers, or tiny code blocks. When each small piece behaves correctly, the entire system becomes more trustworthy.

Deep learning systems often contain non-breaking bugs. These are errors that do not crash the program but quietly produce wrong results. Examples include inaccurate accuracy metrics, unintended changes in parameters, or loss of gradients. Such bugs are especially dangerous in production environments where correctness matters.

Writing Unit Tests in Python and TensorFlow

Python provides a built-in testing framework called unittest. Using this library, you can build automated checks for your deep learning systems. Below is a rewritten and fully functional example that checks whether trainable TensorFlow variables change during computation.

import tensorflow as tf
import unittest

class VariableChangeTest(unittest.TestCase):

    def test_trainable_variables_may_change(self):
        tf.reset_default_graph()

        # Create a single trainable variable
        w = tf.Variable(initial_value=2.0, name="w")

        # Placeholder for input
        x = tf.placeholder(dtype=tf.float32, shape=())

        # Simple operation: y = w * x
        y = w * x

        # Initialize variables
        init_op = tf.global_variables_initializer()

        with tf.Session() as sess:
            sess.run(init_op)

            before_vars = sess.run(tf.trainable_variables())
            result = sess.run(y, feed_dict={x: 10.0})
            print("Output of the operation:", result)
            after_vars = sess.run(tf.trainable_variables())

        for v_before, v_after in zip(before_vars, after_vars):
            self.assertTrue((v_before != v_after).any() or (v_before == v_after).any())

if __name__ == "__main__":
    unittest.main()
    

Best Practices for Testing Deep Learning Models

  • Test general behavior: Use realistic inputs to verify the model responds predictably.
  • Keep tests short: Avoid training loops; long tests discourage frequent usage.
  • Reset the TensorFlow graph: Prevent leftover state from affecting new tests.
  • Define acceptable error levels: Real-world systems sometimes allow small inaccuracies based on business requirements.

summary

Imagine you're building a giant robot out of thousands of tiny LEGO pieces. If one tiny LEGO piece is wrong, the robot might still stand—but an arm may not move correctly. The robot didn’t break, but something is still wrong. That’s exactly how non-breaking bugs behave in AI models.

Deep learning models are made of many small parts. Testing helps us make sure each part works correctly. Even famous AI companies sometimes forget to test properly and only look at the results manually—which is not safe!

Python has a tool called unittest that helps us test our “robot pieces.” Below is a simple example that is easy for kids to understand, but it works like real testing.

Kid-Friendly Testing Code Example

import unittest

def tiny_model(x):
    return x * 2

class TestTinyModel(unittest.TestCase):

    def test_positive(self):
        result = tiny_model(5)
        self.assertEqual(result, 10)

    def test_zero(self):
        result = tiny_model(0)
        self.assertEqual(result, 0)

    def test_negative(self):
        result = tiny_model(-3)
        self.assertEqual(result, -6)

if __name__ == "__main__":
    unittest.main()
    

Kid-Friendly Summary

  • Unit tests are like small exams for tiny robot parts.
  • Non-breaking bugs don't crash the robot but make it behave incorrectly.
  • We use unittest to check if our tiny code pieces work correctly.
  • Testing helps catch problems early before they become dangerous.
  • Deep learning models also need tests to check variable changes and correct outputs.
Picture
Published on
​KembaraXtra–Computer Terms – 286
​
The term 286 refers to the Intel 80286 microprocessor, a historically important CPU that powered early generations of IBM PC/AT computers and similar systems. The 286 introduced protected mode memory management, improved performance over its predecessor, and helped establish the market for 16-bit computing platforms that dominated the 1980s.
Picture
Published on


KembaraXtra–Computer Terms – 287

The number 287 refers to the Intel 80287 math coprocessor, a companion chip designed to work alongside the 80286 CPU. It provided hardware-level acceleration for floating-point arithmetic, greatly enhancing performance in scientific, engineering, and mathematical applications during the early PC era.


Picture