The transformation of one of my 8-years-old kid-students

If properly trained, in an year time even a 7-years-old kid can transform himself vis-a-vis software knowledge. Have a look at the following videos.

- How to find the smallest number in an array - October 2018

-  Singleton Pattern - February 2019

- How to develop a Scramble - Unscramble app in Android - May 2019

-  App store - current

Google Play store profile of Ridit - an 8 years old boy...

Towards the end of 2018, this kid-student was practising some simple Java programs. After 4 months, he transformed himself and discussed about Singleton Design Pattern and after 7 months he started discussing about Android apps. And in October 2019, this kid has his own Google Play Portfolio ( the last link). i know its a long journey to become an ace developer, but proper training is very important for the Indian software engineers. I think people will agree with me about this point.

English is just a language - speaking English is not a skill...

English is just a language to communicate. This cannot be used as a substitute for skill.

This video which explains the Observer Design pattern in Bengali is dedicated to all those Bengali students who despite their Bengali medium schooling background have become bright engineers of India...

Observer Design Pattern in Bengali...

The next video explains the Callback mechanism in an Object-oriented world.

#Enjoy

The Callback mechanism in Bengali...

And the last one...

Factory Design Pattern in Bengali

Providing engineering education in the mother tongue offers a multitude of benefits for students, leading to improved comprehension, stronger analytical skills, enhanced learning environments, wider access, linguistic diversity promotion, and global competitiveness. By valuing and utilizing the mother tongue, we can empower students to excel in engineering while preserving cultural heritage and fostering inclusive learning opportunities.

Engineering college study revisited - the simulation of PID Controller

Here's my story of curiosity - a short speech on PID control...

Back to the Roots — A Tour Through PID Control...

Years after graduating, I found myself staring at lines of C++ code and a bouncing green square on my laptop screen. It felt oddly familiar — like flipping through an old notebook filled with scribbles from those rushed, caffeine-fueled college nights.

Back then, PID control was just another formula — Kp, Ki, Kd — abstract terms scribbled across whiteboards, mixed with equations I barely grasped. We memorized it for exams, solved a few paper problems, and moved on, never fully realizing its power.

But today, that same concept came alive on my screen.

A simple OpenGL simulation — an object floating, falling, recovering — all orchestrated by the same PID logic. And with every tweak of Kp, Ki, and Kd, I could see physics, control theory, and mathematics working in perfect harmony. No longer abstract — this was control in action: balance, stability, correction — everything life taught me after college, now visualized through code.

In that moment, I wasn’t just coding. I was walking the halls of my old college — but this time, with experience as my guide. PID control wasn’t just theory; it was a reminder that the lessons we rushed through back then? They’re the foundation of what we build today.

It turns out, sometimes the most inspiring discoveries happen when you revisit the past — armed with curiosity, patience, and maybe, just a little more coffee.

Here's me...

joining the dots backward...

The below screen recording was an implementation of PID control in Java done many years after graduation.

Android Internals - UI Events...

i know the way we started learning computer science almost three decades ago is absolutely different from the way students learn computer science these days. 

students these days probably start programming keeping AI, Robotics and similar stuffs in mind. 

However, it is also the fact that the basics have remained the same.

For example, the way event-handling works in different UI based OS is almost the same.

I remember when i studied Windows/ Visual C++ in 90's, i was really awed (rather scared)  by the MFC's dreaded 

DECLARE_MESSAGE_MAP

BEGIN_MESSAGE_MAP 

and 

END_MESSAGE_MAP 

macros... 

That's why i have made this video to throw lights on the way UI event handling is done in Android.

The video in the beginning is my investigation on the Android internals vis-a-vis an UI input event. 

i always wanted to get involved in my software job as an inquisitive engineer and not just as a programmer. 

Hence when Google made Android's framework code open-source, it became a boon for me. 

It opened the door for doing in-depth investigation... 

Hope you like the video...

Happy learning

Enjoy...

Here goes the source code of the Simulation Of the Android Button Click Event project.

package com.somitsolutions.java.SimulationOfAndroidButtonClickEvent;

public class View {

static class ListenerInfo {

OnClickListener mClickListener;

OnLongClickListener mLongClickListener;

}

ListenerInfo mListenerInfo;

//Lazy Initialization

ListenerInfo getListenerInfo() {

if (mListenerInfo != null) {

return mListenerInfo;

}

mListenerInfo = new ListenerInfo();

return mListenerInfo;

}

public void performClick() {

mListenerInfo.mClickListener.onClick(this);

}

public interface OnClickListener

{

public void onClick (View view);

}

public interface OnLongClickListener

{

public void onLongClick (View view);

}

public void setOnClickListner(OnClickListener li){

getListenerInfo().mClickListener = li;

}

public void setOnClickListner(OnLongClickListener li){

getListenerInfo().mLongClickListener = li;

}

}

package com.somitsolutions.java.SimulationOfAndroidButtonClickEvent;

public class Button extends View {

private String mButtonText;

public Button ()

{

}

public String getButtonText() {

return mButtonText;

}

public void setButtonText(String buttonText) {

this.mButtonText = buttonText;

}

}

package com.somitsolutions.java.SimulationOfAndroidButtonClickEvent;

public class Activity implements View.OnClickListener{

Button button;

public Activity() {

button = new Button();

button.setOnClickListner(this);

}

@Override

public void onClick(View view) {

// TODO Auto-generated method stub

if(view.equals(button)) {

button.setButtonText("You clicked me...");

System.out.println(button.getButtonText());

}

}

}

package com.somitsolutions.java.SimulationOfAndroidButtonClickEvent;

public class Main {

public static void main(String[] args) {

// TODO Auto-generated method stub

Activity activity = new Activity();

View view = (View)activity.button;

view.performClick();

}

}