World’s First Computer Bug: It may not has been Sep 9, 1947 but at least September when I came across my closest bug to the original insipiration of calling a defect in system as bug.
The clock is running out, project deadline closing in and you are desperately trying to make sense out of the current situation. You even resort to measures, you know make no sense at all, but yet again no idea. That was were I stand at Sep 2021 where the software kept misbehaving on different places with no easy reproduction or any apparent relation between those. Later on (after many hours of attempts) I got an almost always reproducible setup, and you know what it means, you are just few steps away of figureing out the root cause (or maybe not but here was the good case).
It all comes down to the fact that kernel reuses fd numbers in the process, hence if close(fd) is called on an fd already released, it will cause random fd in the program to close.
It was truely a ferret running amok in the program, chewing on wires and closing fds at will with all weird reprecussions in program. Very similar to the first ever catched bug, no pun intended, in the hardware flying around and causing the hardware to malfunction.
Software development moves at an ever increasing speed, engineers feel always the fear of lagging behind and get laid off. This amplifies by the fact that post corona platue of reality had hit big giants crocked projecty of the branch prospect with desert of disappointment. Thank got in US, hire and fire as you please, leading to waves of lay off from legenedary start-from-garage-of-my-father-in-california company to leave the poor software developer in awe of, if an engineer at google loses his job just like that what about an average employee in an average company.
But looking at technologies like CHAT-GPT and Sora, you can't imagine the the industry will slow down it would speed up, but most provably skill set are evolving rapidly. The highlight of software industry is that wide and bride at your feet,
you can move as you please between tech stacks of Golang/Python/C++/Rust on backend, micro-processor, desktop at any depth, from app level to platform and middleware to kernel and drivers.
I would argue that the nature of every leaving thing is to procreate rather for humans have evolved to different levels. Learning provides the dopamine to the human brain that the animal requires to reach through sex (I guess though swiping instagram is much higher dopamine levles that learning but sill a better incetinvize system than animals), so it-
- bootlin had a good training on yocto, I was fully alien to concept of yocto and building your own distro. Some really good basic and pretty some mid level foundation. It helped me a lot during a solution implementation to a problem of creating container images inside yocto build pipeline which lead to deprecating a full fledges service with its repo and logic and code-base.
- foundation ISAQB: It is definitely not a walk in the park, the exam at the end kind of keep you on your toes during the course to pay attention and stay interactive. It had some pretty obvious concepts and some that at first sound like anti-patter but the more you think about it, it is a very positive pattern. Such as "delay making decision to the last feasible moment" though normally the decision-making speed is a KPI of success in a company, but for architects it is neccessary to iterate as much as possible to learn the problem.
The exam was a bit tough and needed real focus.
- agility
- communication
- domain-driven design
- cloud engineer
Locked Safe
Submarine
And here the yellow submarine song, to conclude myself with music
