“𝘞𝘦 𝘢𝘳𝘦 𝘢𝘭𝘭 '𝘴𝘦𝘭𝘦𝘤𝘵𝘪𝘷𝘦 𝘴𝘪𝘯𝘯𝘦𝘳𝘴'. 𝘞𝘦 𝘤𝘩𝘰𝘰𝘴𝘦 𝘵𝘩𝘦 𝘴𝘪𝘯𝘴 𝘸𝘦 𝘢𝘳𝘦 𝘤𝘰𝘮𝘧𝘰𝘳𝘵𝘢𝘣𝘭𝘦 𝘸𝘪𝘵𝘩 𝘢𝘯𝘥 𝘫𝘶𝘥𝘨𝘦 𝘰𝘵𝘩𝘦𝘳𝘴 𝘧𝘰𝘳 𝘵𝘩𝘦 𝘰𝘯𝘦𝘴 𝘸𝘦 𝘤𝘢𝘯'𝘵 𝘢𝘤𝘤𝘦𝘱𝘵.” — 𝘚𝘩𝘢𝘮𝘴 𝘛𝘢𝘣𝘳𝘪𝘻𝘪 Just read this somewhere from a post today !

Growing up with financial struggles, in a village or town, with mostly regional-language education shaped my confidence. My school called itself English medium, but hardly anyone taught in English. My parents worked hard to support me. But I was also taught not to question them or any elder, teacher, police officer, rich person, or city person. I grew up feeling like I should always obey and never speak up. That followed me into engineering and work. Struggling to express myself, stumbling over words during presentations, sweating, finding it hard to say no. Being the obedient “nice guy” comes at a cost. Many people around the world grow up this way, constantly worrying about how others see them, afraid of humiliation or awkwardness, and holding themselves back from taking risks. I’m learning to push myself out of my comfort zone, speak up, and stand up for myself. It’s okay to express your thoughts and clarify what you mean when someone misunderstands you. You don’t have to silently accept their version of you. Let yourself be awkward while you practise. Trust me, people care far less about your awkward moments than you think. They have their own lives and worries. That’s how you grow and build confidence. With practice, you can communicate more clearly, feel more comfortable during presentations, and perform better at work. You don’t have to keep holding yourself back. Ask questions. Say no. Make mistakes. Express yourself. Just be mindful of your words and be kind.

The trick to learning fast is to put your ego aside, accept that you don’t understand something yet, and ask “stupid” questions.

Modern SoCs have so many power optimizations. Working in performance engineering exposes us to so many interesting topics :) P-states, DVFS, AMU, PMU, feedback loops... there’s always more to learn.

Brilliant article !

A stolen website key puts one site at risk. eMudhra’s weak CA keys could let attackers forge HTTPS certificates for any domain. If they intercept your connection and your client still trusts those CAs, they could impersonate your bank and read or modify traffic.

Awesome:)

Thank you!!

Can't wait 👀

The best article!

"Do even threads require in os dev." If not threads then what? Also, you're talking about Kernel to usermode boundary. Not about threads

FSMs are used everywhere. For example in OS, it's used in thread life cycle tracking, when threads move from ready->running or any other state.

Is AI good at multi threading? Personal experience is that I had to clean up a lot of mess it created. It's not bad but it increases the chances of race conditions by a lot.

Thanks!

Touched some grass this weekend :)

I always wondered what Priority, Preemption, QoS, CPU Affinity and NUMA actually mean when it comes to scheduling. We hear these terms separately, but they all somehow meet when the OS has to answer a simple question: “this thread is ready, where and when should I run it?” I’m going down this rabbit hole now :)

Thank you! I still need to learn more about scheduling with affinity, QoS, NUMA etc.

Is it still the same case with real time priority?

It’s crazy how advanced modern OS schedulers are. When a thread is ready, the scheduler doesn’t just find a free CPU and run it. It has to think about priority, CPU load, affinity, which core the thread ran on before, cache locality, CPU topology, and on heterogeneous systems, which type of core is a better fit. Move the thread too much and you can lose cache locality. Keep it on one busy core and you lose performance. Put background work on a high-performance core and you may waste power. And these decisions happen continuously while hundreds or thousands of threads are waking, sleeping, blocking and competing for CPU time. Scheduling today is as much about power and hardware topology as it is about sharing CPU time.

Windows NT 3.1 had an interesting bug where starting an application with "START /REALTIME" could make the OS appear to hang. "/REALTIME" put the process in the real-time priority class, where its threads could run above normal dynamic-priority threads and potentially starve lower-priority work. Microsoft documented this as Q103475: “Starting Applications with /REALTIME May Hang Windows NT.” Interestingly, "REALTIME_PRIORITY_CLASS" still exists in Windows today, and Microsoft still warns that misuse can interfere with important system work.