vk@resume:~$ whoami
Principal Solutions Architect with over 25 years of experience working on large-scale software projects across industries including R&D, Aerospace, Controls & Automation, Power Systems, Telecommunications, Stock Market, and Entertainment.
Currently focused on applied AI and enterprise AI solutions using Python, Azure, and modern AI/LLM technologies. Experienced in designing scalable enterprise systems and bridging software engineering with practical AI applications.
vk@resume:~$ cat about.txt
BigLittleEndian
“BigLittleEndian” comes from the old computer science term endianness — the order in which computers store bytes. When I started working in software, this actually mattered: Intel processors were little-endian, Motorola processors were big-endian, and mixing them up could produce some very surprising results.
For a long time, I thought the names sounded oddly funny for something so technical. Then I discovered the real story: the terms were inspired by Gulliver’s Travels, where the Lilliputians argued over which end of a boiled egg should be cracked first — the big end or the little end.
That mix of serious engineering and playful history is exactly why the name stayed with me. It’s a small tribute to old-school computing, elegant engineering problems, and the strange sense of humor hidden deep inside computer science history.