DEV Community: Leon mckenzie (rowan turner)

Engineers, PLEASE STOP WITH THE FKIN' VIBE CODING

Leon mckenzie (rowan turner) — Thu, 03 Apr 2025 11:30:24 +0000

Look, I get it. We're all excited about AI. As the CEO of an audio AI startup and a principal SWE myself, I'm knee-deep in this stuff. I'm constantly exploring the potential of these tools. But what I'm seeing lately is just... infuriating. It's this goddamn "vibe coding" trend, and it needs to stop.

What is "vibe coding," you ask? It's when engineers rely entirely on AI to generate code, without understanding what the hell that code is actually doing. They're just throwing prompts at a chatbot, crossing their fingers, and hoping for the best. It's like trying to build a house by telling a robot to "make it look cool." You end up with a structurally unsound mess.

I'd Rather Pay a Human to Code

Seriously. I'd rather pay a competent human to write code from scratch than try to debug the Frankensteinian creations these AI tools are spitting out. At least with a human, I know they understand the underlying logic. They can explain their decisions. They can fix their mistakes.

Don't get me wrong, I'm not anti-AI. Using AI as a coding assistant can be incredibly powerful. It can help with boilerplate code, suggest optimizations, and even catch errors. That's fantastic. But it's a tool, not a replacement for actual engineering skill.

AI Is NOT Gonna Replace SWEs

Let's be clear: AI is not going to replace software engineers anytime soon. Anyone who tells you otherwise is selling snake oil. Coding is a complex, nuanced process that requires critical thinking, problem-solving, and a deep understanding of systems. These are things that AI, in its current state, simply cannot replicate.

We need to stop treating AI like a magic black box. We need to stop pretending that it can solve all our problems with a few vague prompts. We need to get back to the fundamentals of software engineering: understanding the problem, designing a solution, and writing clean, efficient code.

Do the Fkin' Work

So, here's my plea to all the engineers out there: stop with the vibe coding. Stop relying on AI to do all the heavy lifting. Learn the fundamentals. Understand the code you're writing. Do the f**kin' work.

We're building the future here. Let's build it with intelligence, not blind faith in a glorified autocomplete.

The True Test of a Software Engineer: Building Without Libraries or Frameworks

Leon mckenzie (rowan turner) — Wed, 13 Nov 2024 14:25:20 +0000

I come from the days of yore, where BASIC was still used, 256MB of storage was like 2TB, and 64KB of ram was like 32GB. There's a quiet arrogance in the tech world today. You see it on social media profiles, in job titles, and echoing through open offices: "Software Engineer." But what does it mean to be a software engineer today, when most of the tools we rely on have already been built by someone else? When the libraries are just a package away, and frameworks do the heavy lifting for us, the label starts to feel a bit hollow.

Imagine this: the internet goes down, your package manager is acting up, or you're in a restricted environment. You need to write something as simple as a command-line interface or maybe even a basic web server. Suddenly, the comforting blanket of frameworks and libraries falls away, and you're left with just your wits, the language's raw capabilities, and your hardware knowledge. The feeling can be humbling, disorienting even. You start to understand what software engineering really is: not just using tools but knowing how they work, and how they interact with the hardware beneath.

To build without libraries or frameworks, you need to know more than syntax—you need to understand the why behind the code. You need to understand data structures, algorithms, and design principles. You need to see the bigger picture, to know what problems you're actually solving and how to solve them from first principles. It's like being a mechanic who doesn't just change parts but understands how every piece in the engine contributes to motion.

Take building a web server, for instance. With a framework like Flask or Express, it's a few lines of code to get a simple endpoint running. Without them, you have to dive into the fundamentals of HTTP, handle incoming byte streams, and manage sockets. The beauty here is that, once you do this, you realize why frameworks do what they do—why certain abstractions exist and how they save time. But this knowledge gives you something more valuable: it gives you choice. It gives you the ability to know when to use a framework and when not to, and how to fix things when they inevitably break.

The truth is, many people today are far more library users than they are software engineers. There is nothing wrong with this—libraries and frameworks are incredible tools that speed up development and allow us to focus on solving new problems rather than reinventing the wheel. But there is a difference between knowing how to use the tools and understanding how to craft them. There is value in rolling up your sleeves and learning to work without a crutch—not because you have to, but because the insight you gain will make you a stronger, more capable engineer.

Building without libraries or frameworks isn't a hypothetical exercise. It's the reality behind every new invention and optimization. It's how breakthroughs happen. The next time you find yourself thinking that all software engineering is just gluing APIs together, remember that there's a deeper level to this work. There's a world where you write the API, design the database engine, and implement the communication protocols—a world where "engineer" means understanding the full stack, not just relying on what’s already been stacked for you.

So, the next time you're feeling comfortable in your IDE, challenge yourself: build something with no imports, no dependencies, nothing but the core language. Implement your own sorting algorithm, build a simple UI with raw JavaScript, or write a CLI tool in pure Python. You might be surprised at how much you learn and how different it feels to call yourself a software engineer afterward.

Engineering starts where the libraries end.

Optimize for What You Can Do: A Coder's Guide to Customization and Inclusivity

Leon mckenzie (rowan turner) — Fri, 01 Mar 2024 00:20:26 +0000

Introduction: Crafting an Efficient Coding Symphony

In the realm of software development, efficiency is not just about speed; it's about creating an environment that echoes our individual needs and breaks down barriers to innovation. My own journey from a coder with a love for music to a champion of inclusivity in technology has been underpinned by this very principle: optimizing for what I can do, not for what others expect.

My path has been unconventional, marked by a transition from game/web development to DJing, to digital audio engineering, and now to a PhD focusing on audio AI and ASR for dysarthria. Each step has been guided by a commitment to creating spaces and tools that are accessible to all, reflecting a belief in the transformative power of technology.

The Genesis of My Setup

The keyboard is the coder's instrument, and in my case, it needed to be more than just functional—it had to be intuitive and inclusive. My custom keyboard layout, which I call the "QWERTY Functional," is designed to cater to my left-hand dominance due to my unique abilities. While the image may suggest a grid, my actual keyboard is staggered, matching the natural finger reach and enhancing typing comfort and speed. This layout is my statement in the need for inclusivity in the tools we use.

Tailoring for Strength: The "QWERTY Functional"

The "QWERTY Functional" is a deliberate composition that plays to the strengths of my left hand, allowing me to perform the majority of typing actions with the hand that operates most effectively. The strategic distribution of keys means less cross-hand movement, which translates to quicker, more fluid coding sessions and reduces the physical toll on my right hand. This keyboard layout is a testament to the philosophy of inclusive design, a system that caters to individual user needs without compromise.

Redefining Ability: The Construct of Disability

The term 'disability' implies limitation, but my journey has taught me to see it as a different set of abilities. This perspective has been the source of my greatest innovations, leading me to customize my tools and approach problems with fresh eyes. Embracing our differences and unique strengths is not just beneficial; it's necessary for innovation and growth.

Living Up to Your Own Standards

In a world that often measures success with a universal yardstick, setting personal benchmarks for success that align with my capabilities and values has been an act of courage and self-awareness. It has allowed me to prioritize my own expectations over societal ones, motivating me to innovate and redefine what's possible.

Conclusion: The Symphony of Self-Optimization

As we conclude, it's clear that optimization is a deeply personal symphony composed of our individual abilities, passions, and the unique ways we interact with the world. It is an ongoing pursuit that challenges us to refine our tools, our environments, and ourselves. As I continue my journey through the realms of audio AI and beyond, my commitment to this philosophy remains steadfast, and I invite you to join me in this endeavor—to optimize, to redefine, and to live up to your own extraordinary standards.

Why i quit my job as a staff engineer

Leon mckenzie (rowan turner) — Fri, 09 Feb 2024 18:30:52 +0000

disclaimer: I am just sharing my experiences, I'm by no way looking to shame anyone, I have intentionally not named companies or people for this reason enjoy!

1: From Startup Hell to PhD Pursuit: My Journey Begins

I have a strong track record for delivering commercial vsts as a DSP engineer, working at several startups over the past 5 years. This audio startup had promised innovation, excitement, and cutting-edge technology. Instead, I found myself drowning in a sea of disappointment. My role as a staff software engineer quickly morphed into a soul-crushing experience. A "promotion" landed me on a project teetering on the brink of collapse, and my efforts to salvage it in a week (as per the CEO's impossible demands) were met with nothing but belittlement.

Desperate for a break and a chance to rediscover my passion, I requested a month of leave to finish my Master's degree. Returning with a renewed sense of purpose, I was faced with another surprise: an invitation to apply for to do my PhD in a doctoral researcher, researching AI in speech recognition.

But taking the leap wasn't easy. Unsure of the path ahead, I embarked on this new adventure. This blog chronicles my journey – from the disillusionment of the startup world to the exciting, yet uncertain, world of PhD research. Join me as I navigate the challenges, celebrate the victories, and ultimately, share my story of transformation.

2: From Dream Project to Startup Disillusionment

Before the chaos of the "promotion" and the PhD opportunity, my days were filled with the exciting challenge I'd always dreamed of developing a VST plugin that was emulating a rare piece of gear. Yes, you read that right – a Virtual Studio Technology plugin, the very technology that allows musicians and producers to create digital instruments and effects. As a passionate audio enthusiast and DSP Engineer myself, working on this project felt like hitting the jackpot.

Building this VST wasn't just another task; it was an opportunity to pour my creativity and technical skills into crafting a tool that could empower artists. Every line of code was a brushstroke, shaping the sonic possibilities for others. It allowed me to tap into a creative flow I never knew existed, a far cry from the disillusionment I later encountered.

While the VST had no direct connection to my current PhD path in AI, it represented a time when I was driven by passion and the joy of creation. It served as a stark reminder of how much satisfaction I derived from working on projects that resonated with my deeper interests. This realization became crucial later on, when I had to decide whether to chase the "safe" option within the startup or pursue the unknown but captivating world of research.

However, as the excitement of the VST project faded, the cracks in the startup's culture began to widen. The initial promise of innovation gave way to unrealistic expectations and a toxic work environment. This shift made me question the true value of my work and ultimately pushed me towards seeking a more fulfilling path.

3: The Promised Land Turns Toxic - A Plugin Nightmare

Remember those impressive VST plugins I mentioned, the ones that landed me this dream job? Well, buckle up, because things were about to get messy. Turns out, the company that hired me based on my proven track record had a little secret of their own: they didn't exactly prioritize honesty or transparency.

My initial project, the one I poured my heart and soul into, was making solid progress. I was genuinely excited about pushing the boundaries of DSP. But then, the rug was pulled out from under me. My "promotion" wasn't a promotion at all; it was a one-way ticket to a different project – a project that was already a raging dumpster fire.

Here's the kicker: the "tech lead" before me on this other VST was... let's just say, less than qualified. His code was riddled with bugs, his vision was hazy at best, and his leadership skills were nonexistent. And guess who was tasked with cleaning up his mess in a week? Yours truly.

It was a recipe for disaster. Deadlines were unrealistic, expectations were sky-high, and the support was nonexistent. I poured in countless hours, trying to salvage something from the wreckage, only to be met with constant criticism and belittlement from the very person who created the mess in the first place. The CEO, who initially promised me full support, suddenly seemed to vanish, leaving me to navigate this toxic environment alone.

This experience was a stark wake-up call. It exposed the ugly truth behind the company's facade of innovation and revealed the consequences of trusting a company that values hype over honesty. It was a turning point, pushing me to question everything I thought I knew about work culture and the importance of genuine talent.

4: From Breakdown to Breakthrough - Leaving Startup Chaos Behind

The pressure cooker had reached its boiling point. The constant stress, the toxic work environment, and the financial strain were taking their toll. Dark thoughts started creeping in, anger became my default response, and the joy of creating faded fast. I was drowning, and the "promotion" had become a suffocating anchor.

But amidst the chaos, a glimmer of hope emerged. My boss, seeing my struggle, surprisingly allowed me a month's leave to finish my Master's thesis. With renewed focus, I poured myself into my studies and emerged with a distinction – a testament to my resilience and determination. This achievement sparked a sense of self-belief, urging me to consider my next move.

I was already juggling my day job with the launch of my own startup – a venture I was passionate about but unsure of its long-term sustainability. Simultaneously, I was exploring various job opportunities, including the doctoral researcher position at my university. I was at a crossroads, unsure of the right path forward.

Then, upon returning from my leave, the rug was pulled out from under me again. My boss, in a cruel twist of fate, questioned my abilities and claimed I wasn't "senior level" material. His words, steeped in condescension and negativity, were the final push I needed. Without a second thought, I walked out.

It was a leap of faith, a jump into the unknown. My startup was still in its early stages, and the research position wasn't yet secured. But the fear of the toxic environment I left behind fueled my determination. I knew I deserved better, and I was ready to chase my true potential.

This wasn't just about quitting a job; it was about reclaiming my self-worth and taking control of my future. It was a defining moment, a turning point that led me to the exciting world of PhD research in AI, but that's a story for another day.

5: From Leap of Faith to Hopeful Horizon - A New Chapter Begins

Just days before Christmas, a beacon of hope pierced the uncertainty: the offer letter for the doctoral researcher position arrived. I couldn't believe my eyes – a wave of relief and joy washed over me, erupting in a triumphant scream that probably scared the neighbors! Starting in a week, I was ready to embark on a new adventure, one driven by intellectual curiosity and a thirst for knowledge.

But the story doesn't end there. My passion project, the startup I launched despite the chaos, also flourished. We launched 4 VSTs, each one met with positive feedback and growing user base. We even have a special project brewing, fueled by our collective creativity and determination.

Yes, the PhD takes priority unless my tasks for that day are done i will refuse to do startup task. It represents a commitment to pushing boundaries and contributing to the world of AI. Yet, my entrepreneurial spirit won't be silenced. My journey with the startup continues, albeit with a different balance – I work on it 4 to 8 hrs/wk. I may not dedicate every waking hour, but my heart and dedication remain unwavering.

The path ahead is undoubtedly challenging. Juggling a demanding research program with an evolving startup might seem like a recipe for madness. But here's the thing: I'm no stranger to challenges. The dark days at the startup, the emotional breakdown, and the leap of faith I took have equipped me with resilience, resourcefulness, and a newfound appreciation for time management.

This is more than just pursuing two passions; it's about defying limitations and proving that ambition doesn't require sacrifice. I plan to document my journey, sharing the triumphs and tribulations, the late nights fueled by coffee and code, and the exhilarating moments of discovery. Perhaps it will inspire others to chase their own dreams, embrace the unknown, and carve their unique path even amidst the chaos.

So, the adventure continues. Join me as I navigate the uncharted territory of AI research, nurture my entrepreneurial endeavor, and strive to strike a balance between ambition and wellbeing. Who knows what the future holds, but one thing's for sure: it will be anything but ordinary.

Conclusion: From Broken Wings to Soaring High - Reflections and Encouragement

It all started with a dream: crafting cutting-edge audio tools and pushing the boundaries of innovation. But the dream turned sour, leaving me disillusioned and questioning my path. The "promotion" became a nightmare, the toxic environment stifled my creativity, and the lack of support crushed my spirit. Yet, amidst the ashes of disappointment, a spark ignited. It was the spark of self-belief, fueled by academic achievement and the tenacity of my own entrepreneurial spirit.

Taking a leap of faith, I walked away from the chaos, embracing the unknown with open arms. The doctoral researcher position was a beacon of hope, an opportunity to delve into the fascinating world of AI research. But my passion for creating didn't vanish. My startup, born amidst the turmoil, continued to thrive, reminding me that the power of imagination knows no bounds.

Today, I stand at a crossroads, juggling the demands of the PhD program with the exciting challenges of growing my startup. It's a balancing act, one that requires meticulous planning, unwavering dedication, and a healthy dose of caffeine. But the challenges pale in comparison to the satisfaction of pursuing both paths, nurturing my intellectual curiosities while building something meaningful.

This journey isn't just about me; it's about you too. If you're feeling stuck, disillusioned, or unsure of your next step, let my story be a testament to the power of resilience and the courage to chase your dreams. Don't be afraid to step outside your comfort zone, embrace the unknown, and carve your own path, even if it means juggling multiple passions.

Remember, the road ahead might be bumpy, but the view from the top is worth it. So, join me on this adventure, share your own stories, and let's inspire each other to reach for the stars, one step at a time. After all, sometimes, the most extraordinary journeys begin with taking a leap of faith and refusing to let your wings clip your dreams.

Why I Chose Linux: A Journey To Development Freedom

Leon mckenzie (rowan turner) — Sat, 27 Jan 2024 01:16:33 +0000

Introduction:

As a software engineer and music producer, the essence of my digital existence hinges on one critical principle: full control. In the sprawling universe of development environments and music production tools, this mantra has led me down a path less traveled, a journey punctuated by love, loathe, and a relentless quest for the perfect setup.

My relationship with development tools is intense, to say the least. Xcode? I've given it a try, but let's just say it wasn't a match made in heaven. Enter Neovim – a beacon of hope in a sea of bloated IDEs. It's not just a tool; it's a statement. A statement that says, "I know what I'm doing, and I need the freedom to do it my way." Neovim has been a game-changer for me, stripping away the unnecessary and leaving a sleek, powerful interface that bends to my will, not the other way around.

But let's not forget the other side of the coin – my passion for music production. Here, the narrative takes a different turn. The Mac, often seen as the antithesis of customization and control, paradoxically, becomes the hero. Why? Because, in the domain of music production, it simply excels. The seamless integration of hardware and software creates a symbiotic ecosystem where creativity flows unimpeded. In this world, the Mac is not just a tool; it's a partner in the creative process.

And then there's Windows – the operating system that tries to be everything to everyone and ends up being a master of none, at least in my eyes. My heart belongs to Unix. Its philosophy, its power, and its flexibility resonate with me on a fundamental level. It's the underpinning of my chosen platforms, a testament to my desire for a computing experience that feels like an extension of myself, not a constraint to be wrestled with.

In this blog, I embark on a candid exploration of my journey through the landscapes of software engineering and music production. It's a tale of two worlds – one where Neovim reigns supreme in a Linux-dominated realm, and another where the Mac becomes the linchpin of musical creativity. Join me as I delve into the reasons behind my choices, the challenges I've faced, and why, despite the dichotomies, I've found a setup that feels like home.

My Ultimate Development and Production Setup:

At the heart of my technological domain lies Garuda Linux Dragonized, enhanced with KWin for a tiling window manager experience that merges aesthetic appeal with efficiency. This choice isn't just about the look; it's about creating a fluid, distraction-free environment where my ideas can soar unfettered. Neovim, my trusted sidekick in the realm of code, is the cornerstone of this setup, its extensibility and speed harmonizing with the Linux foundation to cut through development tasks like a knife through butter.

For my diverse project needs, I oscillate between a suite of powerful languages and frameworks. CMake, JUCE, and Qt lay the groundwork for my desktop applications, with the choice of Rust, Go, or C++ depending on the project's demands. When the web calls, JavaScript, TypeScript, Node.js, and Svelte are my go-to tools, weaving together the frontend and backend with finesse. And yes, I admit to the occasional foray into VS Code for certain tasks— a cardinal sin in the eyes of some purists, but a pragmatic choice for its unparalleled ecosystem and integrations.

For my day job, Python along with PyTorch serves as the backbone of my endeavors into the realms of data science and machine learning, where the manipulation of vast datasets and the training of sophisticated models demand both flexibility and power.

The physical manifestation of my digital workspace is just as critical. My ThinkPad P14s Gen 1, boasting 32GB RAM and a 2TB SSD powered by an i7 processor, is the engine driving my endeavors. This powerhouse is complemented by a triple monitor setup, extending my digital canvas and enhancing my ability to multitask and visualize complex projects. A split keyboard with a custom layout sits at my fingertips, an ergonomic choice that keeps me coding and producing music for hours without strain.

This setup is not just a collection of tools and hardware; it's a carefully curated ecosystem that reflects my identity as a developer and artist. It's where functionality meets personal expression, enabling me to transcend the ordinary and venture into realms of unparalleled creativity and productivity.

Embracing Cross-Platform Development and the Power of CI

The journey towards embracing Linux as my primary development environment wasn't just a personal preference; it was a strategic move underpinned by years of cross-platform development experience. True, I navigated the ecosystems of macOS and Windows for five years, a period that not only broadened my technical expertise but also deepened my understanding of the unique challenges and opportunities each platform presents. At my startup—which I proudly founded and lead—we've crafted a complex yet elegant continuous integration (CI) system that stands as a testament to our commitment to developer freedom and efficiency.

Building across platforms is no small feat, especially within a lean team of three. The key to our agility and adaptability lies in our CI system, a setup that allows us to compile, test, and deploy our applications irrespective of the individual development environments. This autonomy is crucial for a startup where innovation and speed are of the essence. We believe strongly that any company, particularly those with a focus on technology, should invest in a robust build pipeline and cloud-based development practices. For those unable to make this leap, providing developers with the necessary hardware, like laptops, is a fundamental responsibility.

Our CI system enabled a significant transition for me personally—it allowed me to switch back to Linux without compromising our workflow or productivity. This move was more than a change of operating systems; it represented a strategic decision to align our development practices with the most efficient, flexible, and scalable solutions available. In doing so, we not only enhance our capabilities but also set a standard for what good leadership and foresight can achieve in the tech industry. By advocating for and implementing these practices, we empower our team to work in environments that best suit their skills and preferences, all while maintaining a high standard of quality and collaboration across our projects.

Navigating Between AI Research, Startup Ventures, and Linux:

My professional journey straddles two distinct yet complementary worlds: by day, I immerse myself in the cutting-edge realm of AI research within a lab setting, where Python and PyTorch are my tools of choice in pushing the boundaries of machine learning and data science. This work, while challenging, offers a unique perspective on the potential and complexities of AI technologies. By contrast, my entrepreneurial spirit finds its outlet in Synergy DSP, a startup I founded to explore the innovative frontiers of digital signal processing. Here, our commitment to agile development and robust software practices is embodied in our sophisticated CI system, ensuring our small team can deliver high-quality, cross-platform solutions with remarkable efficiency.

This dual engagement presents a fascinating dichotomy:
the structured, research-oriented environment of my day job versus the dynamic, fast-paced world of a tech startup. Bridging these two is my unwavering preference for Linux as my development environment. The choice of Linux is not incidental but a deliberate preference for its open-source ethos, versatility, and the unparalleled control it offers over the development process. Linux, with its rich ecosystem of tools and languages—from Neovim for code editing to the use of CMake, JUCE/Qt for desktop development, and JavaScript frameworks for web projects—provides the perfect foundation for both my AI research and startup projects.

The decision to pivot back to Linux for my development work, even as I navigate the complexities of AI research and lead a startup, stems from a simple truth: Linux aligns with my need for a highly customizable, efficient, and open development environment. It caters to the diverse technological demands of my professional and personal projects, enabling a seamless integration of my coding practices across different contexts. The CI infrastructure at Synergy DSP, designed to support cross-platform development, underscores this philosophy by allowing us the freedom to choose our development environments without compromising on productivity or collaboration. This setup not only reflects our startup's adaptability but also my personal ethos as a developer and entrepreneur: embracing the tools and platforms that foster innovation, efficiency, and creativity.

In essence, the choice to prefer Linux is more than a matter of personal taste; it's a strategic decision that enhances my effectiveness across my roles in AI research and as a startup founder. It signifies a broader commitment to leveraging the best tools and practices available, ensuring that whether I'm delving into AI algorithms or building the next generation of digital signal processing software, I'm doing so on a platform that maximizes my potential.

Conclusion: Embracing Linux in a World of Diverse Tech Challenges

My journey through the realms of AI research and startup leadership has been a testament to the power of choosing the right tools and environments that not only cater to immediate project needs but also align with broader personal and professional goals. The transition back to Linux, a deliberate choice in my development arsenal, underscores a philosophy that has guided me through both areas of my life: the pursuit of efficiency, flexibility, and control in the technology I use.

Linux, with its open-source nature and robust community support, has proven to be an invaluable asset in tackling the diverse and complex challenges I face daily. Whether it's developing cutting-edge AI algorithms in the lab or steering Synergy DSP towards innovative digital signal processing solutions, Linux offers the stability, performance, and adaptability necessary to navigate these tasks with confidence and creativity.

The CI system we've implemented at Synergy DSP is not just a tool for facilitating cross-platform development; it's a reflection of our commitment to creating an environment where innovation thrives, free from the constraints of proprietary platforms. This system, coupled with my preference for Linux, represents a broader ethos: that the freedom to choose how and where we build our technology is fundamental to driving progress in the tech industry.

In conclusion, my return to Linux is more than a mere preference for an operating system; it's a strategic alignment with a platform that embodies the principles of openness, innovation, and control. It's a choice that has empowered me to excel in the highly technical field of AI research and navigate the entrepreneurial challenges of running a tech startup. As the tech landscape continues to evolve, I remain convinced that Linux will continue to be a pivotal force in my development journey, enabling me and my team at Synergy DSP to push the boundaries of what's possible.

Data Spark #002 - Digital Signal Processing: A Comprehensive Guide

Leon mckenzie (rowan turner) — Sun, 09 Jul 2023 23:00:00 +0000

In the world of technology, there are several unsung heroes. Digital Signal Processing (DSP) is one of them. It's a behind-the-scenes star powering a plethora of technologies we use daily, yet many of us know little about it. So, what is DSP?

DSP involves the mathematical manipulation of an information signal - such as sound, temperature, images, etc. - to modify or enhance it. In layman's terms, DSP is about taking signals like sounds and images and manipulating them to improve their quality or extract useful information.

Take, for example, the clarity of a phone call. It's more than just two devices communicating; it's DSP working to reduce noise and enhance sound quality. Similarly, the accuracy of your weather app hinges on DSP's ability to process and interpret a myriad of signals from various sources.

This post will introduce you to the core principles of DSP, giving you a solid foundation to understand this crucial field. We'll look at:

Sampling: This is the process of converting a continuous signal (like an image or sound) into a discrete sequence. It's like taking snapshots at regular intervals.

Quantization: Once the signal is sampled, each sample is then quantized into a digital value, effectively turning analog signals into digital ones.

Frequency Domain Representation: This is where the fun starts. We take our time-based signal and determine what frequencies make up the signal. This is crucial for understanding the signal's properties and behavior.

A crucial part of DSP is the Fourier Transform, a mathematical technique used in many DSP applications. It transforms a function of time, a signal, into a function of frequency. This allows us to analyze each frequency component of the signal individually.

DSP plays a critical role across a wide range of applications and industries. It forms the backbone of audio and video processing, enabling us to listen to clear, noise-free phone calls, watch high-definition movies, and stream music. In telecommunication systems, DSP is used for encoding, decoding, transmitting, and compressing signals. It powers the functioning of our radios, televisions, and mobile phones. In medical imaging, such as MRI and CT scans, DSP techniques help enhance image quality and extract critical diagnostic features. It's instrumental in seismology, helping interpret signals from seismic detectors to predict and monitor earthquakes. DSP also plays a pivotal role in control systems, such as those found in appliances, automobiles, and even aircraft. More recently, DSP has found application in the field of machine learning and AI, aiding in voice recognition, image analysis, and natural language processing. As technology continues to evolve, the applications of DSP are set to increase, further revolutionizing how we interact with the digital world.

Understanding DSP isn't just about comprehending modern technology; it's also about envisioning the possibilities for future advancements. In the upcoming posts, we will delve into the intriguing intersection of DSP and AI, offering a lens to look at how these two fields can converge to amplify the power of information processing and analysis. Stay tuned as we unravel the fascinating world of signals and systems.

Data Spark #001 - an Introduction to Artificial Intelligence: Current Trends and Future Predictions

Leon mckenzie (rowan turner) — Sat, 08 Jul 2023 00:47:08 +0000

The science fiction of yesteryears is today's reality, as Artificial Intelligence (AI) has transcended from the realm of academic curiosity to a cornerstone of modern society. AI has woven itself into the fabric of our daily lives, transforming sectors ranging from entertainment to finance, transportation to healthcare.

The magic of AI lies in its ability to mimic human intelligence. This intelligence isn't merely about executing tasks, but about learning from the environment and experiences, reasoning with the information gathered, solving problems based on that reasoning, perceiving real-world nuances, and understanding language intricacies. The very essence of AI is its capability to analyze the environment and take actions that maximize its chance of achieving specific goals.

One of the most prominent trends in AI today is the rise of Machine Learning (ML) and Deep Learning (DL) models. Machine Learning is an AI subset that allows computers to learn from data, improving their performance without being explicitly programmed to do so. Deep Learning, on the other hand, is a subset of ML, modeling high-level abstractions in data using artificial neural networks.

These models have made possible what was unthinkable a decade ago. Your streaming platform's recommendations? That's ML algorithms at work. The facial recognition feature on your smartphone? Credit goes to DL models.

Natural Language Processing (NLP), another facet of AI, has shown tremendous promise. NLP deals with the interaction between computers and human language. It enables machines to understand, interpret, and generate human language, leading to groundbreaking applications in customer service, entertainment, and more.

As we look forward to the future, it's clear that AI is set to play an even bigger role in our lives. 'Explainable AI' is an emerging field seeking to make the decision-making processes of AI transparent and understandable. This will foster greater trust in AI systems and pave the way for wider acceptance.

In our upcoming posts, we will delve deeper into various aspects of AI, exploring its applications and potential in transforming our future. So, stay with us as we embark on this exciting journey of discovery together.

HI.
My name is leon, a multifaceted tech professional based in London, thriving at the intersection of innovation, research, and practical application. I'm a passionate Machine Learning (ML) researcher and a Digital Signal Processing (DSP) Tech Lead, who navigates the challenges of Autism Spectrum Disorder (ASD) and physical disability with determination and resilience.

Presently, I am deepening my academic understanding by pursuing a Master's degree in DSP. This academic venture enables me to delve into complex theoretical concepts and sharpen practical skills, providing a platform for continuous learning and development.

One of my key research areas is the application of Automatic Speech Recognition (ASR) for individuals with dysarthria, a condition that can make speech difficult to understand. Through this research, I aim to make voice-activated technologies more accessible and functional for those who might struggle with speech.

Professionally, I'm associated with an up-and-coming audio tech startup, pushing the boundaries of how audio technology can redefine our interactions with the world. My role as a Tech Lead involves guiding a team of devoted engineers and maintaining our position at the forefront of the rapidly evolving tech industry.

Additionally, I champion inclusivity in the tech industry, advocating for more accessible and diverse environments. I strongly believe that diversity fuels innovation and that everyone should have equal opportunities in the tech world, regardless of their abilities.

In this blog, I plan to share my insights, learnings, and observations in the fields of AI and DSP. I hope to provide cutting-edge information, trends, and discussions around these transformative technologies. As we embark on this journey together, I invite you to explore, learn, and engage in these fascinating areas of tech.

the tech leads grind

Leon mckenzie (rowan turner) — Tue, 18 Apr 2023 22:37:40 +0000

As a staff software engineer and tech lead on a flagship audio app and pursuing an MSc in DSP (backend audio) and AI, you have a unique perspective on the challenges of being a tech lead. You likely have experience managing teams, resolving conflicts, and staying up-to-date with emerging technologies, and you may have had to balance technical work and management responsibilities. Drawing on your experience, you can offer valuable insights into the things that you may not be prepared for when taking on a tech lead role.

Saying No:

As a tech lead, you'll need to learn how to say no, especially when your team or stakeholders request something that is not feasible or realistic. Saying no can be difficult, but it's essential to set realistic expectations and avoid overcommitting yourself or your team. You'll need to weigh the risks and benefits of taking on a new task or project, and communicate transparently with your team and stakeholders about the reasons behind your decision. Saying no can be challenging, but it's a necessary skill to develop as a tech lead to ensure your team's success and avoid burnout.

Managing People:

As a tech lead, you'll be responsible for managing people, which can be a daunting task, especially if you haven't had prior experience. To be an effective manager, you'll need to be able to communicate effectively, delegate tasks, provide guidance and feedback, and motivate and support your team members. Developing strong leadership and communication skills is essential for managing people successfully. You'll also need to create a positive work environment that fosters collaboration, creativity, and innovation. Encouraging your team members to share their ideas and opinions can help create a sense of ownership and investment in their work, resulting in better performance and outcomes.

In addition to managing your team, you'll also need to manage relationships with other stakeholders, such as project managers, product owners, and other department heads. Building strong relationships with stakeholders can help you better understand their needs, goals, and expectations, enabling you to manage projects more effectively and deliver better results.

Prepare to Drink Lots of Coffee and Have Sleepless Nights:

Being a tech lead is a demanding role, and there may be times when you'll need to work long hours or face tight deadlines. This can be challenging, especially if you're not used to working under pressure. You may find yourself drinking more coffee or energy drinks than usual to stay awake, and you may have to sacrifice some of your free time to keep up with your workload.

To cope with the demands of your role, it's essential to develop effective time management skills and prioritize your tasks. This will help you ensure that you're making the most of your time and avoiding unnecessary stress. It's also important to take breaks regularly, get enough sleep, and maintain a healthy work-life balance to avoid burnout.

In addition, it's crucial to communicate transparently with your team members and stakeholders about the challenges you're facing. Letting them know that you're working hard and doing your best can help build trust and confidence in your leadership. It can also help them understand the constraints you're facing and enable them to support you more effectively.

While drinking lots of coffee and having sleepless nights may be unavoidable at times, it's important to take care of yourself and prioritize your health and well-being. This will help you stay focused, motivated, and energized, enabling you to perform at your best and lead your team to success.

Balancing Technical Work and Management Responsibilities:

As a tech lead, you'll need to balance technical work and management responsibilities. On one hand, you'll be responsible for hands-on development work, such as writing code, testing, and debugging. On the other hand, you'll need to manage your team, plan and prioritize work, track progress, and communicate with stakeholders. To balance these responsibilities effectively, you'll need to delegate tasks and responsibilities to your team members, so you have time to focus on high-level tasks.

It's essential to develop time management skills, prioritize tasks, and maintain a clear line of communication with your team members to ensure that you're making the most of your time. You'll also need to continually update your technical knowledge to stay up-to-date with new technologies and tools. This will help you make informed decisions about project requirements, resource allocation, and timelines.

Dealing with Conflicts:

Conflicts are a natural part of any workplace, and as a tech lead, it's your job to resolve them effectively. Conflict resolution is a challenging skill to develop, but it's essential for building strong relationships with your team members and stakeholders. The first step in conflict resolution is to identify conflicts early and listen to all parties involved. You'll need to create a safe and open environment where people feel comfortable expressing their concerns and opinions.

Next, you'll need to work collaboratively with your team members and stakeholders to find a solution that satisfies everyone. This may involve compromise, negotiation, or finding a creative solution that meets everyone's needs. It's also essential to document the resolution to avoid any misunderstandings and follow up with the parties involved to ensure that the solution is working effectively.

Staying Up-to-Date with New Technologies:

As a tech lead, it's essential to stay up-to-date with the latest trends and technologies. Technology is constantly evolving, and keeping up with emerging technologies can help you make informed decisions about project requirements, resource allocation, and timelines. To stay up-to-date with new technologies, you'll need to attend conferences, read industry publications, and participate in online forums.

It's also crucial to evaluate the potential impact of new technologies on your projects and team members' skillsets. This will help you identify any training needs and ensure that your team has the necessary skills and knowledge to work effectively with new technologies. Staying up-to-date with new technologies can also help you identify new opportunities for innovation and improvement, enabling

Be Prepared to Wear Many Hats:

As a tech lead, you'll be expected to wear many hats and take on multiple roles beyond just technical work. You'll need to be a project manager, a mentor, a communicator, a mediator, a problem solver, and more. This can be overwhelming, especially if you're used to focusing primarily on technical work.

To be an effective tech lead, you'll need to learn how to prioritize your tasks and switch between different roles seamlessly. You'll also need to develop excellent communication skills to collaborate with your team members, stakeholders, and other departments. Being a mentor to junior developers on your team can also help you improve your leadership skills and develop a more well-rounded perspective.

It's also essential to be adaptable and open to learning new skills as you take on different roles. You may need to take on responsibilities outside of your comfort zone, such as public speaking, leading meetings, or creating presentations. While this can be challenging, it can also be an opportunity to grow and develop new skills that can benefit you both personally and professionally.

In summary, being a tech lead requires wearing many hats and taking on multiple roles beyond just technical work. By prioritizing your tasks, developing excellent communication skills, being a mentor to your team, and being adaptable and open to learning new skills, you can excel in your role as a tech lead and lead your team to success.

In conclusion, becoming a tech lead is a challenging but rewarding step in your career. Along with your technical expertise, you'll need to develop strong leadership, communication, conflict resolution, time management, and technology evaluation skills. You'll also need to be prepared to manage people, balance technical work and management responsibilities, deal with conflicts, stay up-to-date with new technologies, and, at times, work long hours or face tight deadlines.

However, with the right mindset and skills, you can excel as a tech lead and lead your team to success. Remember to prioritize your team's needs, communicate transparently with your team members and stakeholders, and take care of yourself to avoid burnout. Embracing the challenges of your role and continually learning and growing can help you become an effective tech lead who drives innovation and delivers results.

why we should diversify tech

Leon mckenzie (rowan turner) — Tue, 14 Mar 2023 21:47:35 +0000

As technology continues to play an increasingly important role in our lives, it's crucial that the industry reflects the diversity of the people it serves. Unfortunately, tech has a long way to go in terms of diversity and inclusion. The good news is that progress is being made, and there are steps we can take to make tech more accessible and inclusive for everyone.

As someone with Aspergers and physical disabilities who has achieved a degree, a leadership position in tech, and is working towards a masters I understand firsthand the challenges and opportunities that exist in this space. In this blog post, I'll be sharing my experiences and insights on how we can make tech more diverse and inclusive, and why it's so important to do so.

Here are some of the key talking points I'll be covering:

-The benefits of diversity in tech, both in terms of innovation and social responsibility

-The barriers that exist for people with disabilities and underrepresented groups in tech, and how we can overcome them

-The role of mentorship and community in supporting diverse talent in tech

-The importance of advocating for change within the industry
and holding companies accountable for their diversity and
inclusion efforts

Through my own experiences and research, I'm confident that we can make meaningful progress in creating a more inclusive and diverse tech industry. So let's dive in and explore how we can work together to achieve this important goal.

The benefits of diversity in tech, both in terms of innovation and social responsibility

Diversity in tech has been proven time and time again to drive innovation and creativity. When people with different backgrounds, perspectives, and experiences come together, they can bring a wealth of unique ideas and solutions to the table. This leads to more diverse and effective products and services that can better serve the needs of a wider range of users. By embracing diversity in tech, companies can also tap into new markets and increase their competitive advantage.

In addition to fostering innovation, promoting diversity in tech is also a matter of social responsibility. Technology plays a critical role in shaping our society and impacting the lives of people around the world. By creating technology that reflects the diversity of its users and includes a wide range of perspectives, we can build a more equitable and inclusive future. This means addressing the biases that exist within technology and working to overcome the systemic barriers that have historically excluded underrepresented groups from participating in tech.

Ultimately, promoting diversity in tech is not only a matter of improving the industry's bottom line, but also of creating a more just and equitable world. By promoting diversity and inclusion in tech, we can empower a wider range of voices and perspectives to shape the technology that shapes our lives. This requires a concerted effort from individuals, companies, and the industry as a whole, but the benefits are clear. By embracing diversity and inclusion, we can create technology that truly serves the needs of everyone.

The barriers that exist for people with disabilities and underrepresented groups in tech, and how we can overcome them

Despite the numerous benefits of diversity in tech, there are still significant barriers that prevent people with disabilities and underrepresented groups from fully participating in the industry. One major barrier is a lack of access to education and training. Without proper education and training, individuals from underrepresented groups may lack the necessary skills to enter and succeed in the tech industry. Similarly, people with disabilities may face additional challenges due to inaccessible education and training programs. To overcome this barrier, we need to invest in educational programs that are accessible and inclusive, and actively work to create pathways for underrepresented groups to enter the tech industry.

Another major barrier to diversity in tech is the prevalence of bias and discrimination. Studies have shown that people from underrepresented groups often face bias and discrimination in the hiring process, as well as on the job. This can include everything from unconscious bias in resume screening to outright discrimination in hiring and promotion decisions. Similarly, people with disabilities may face stigma and discrimination due to misconceptions about their abilities. To overcome this barrier, we need to actively work to address bias and discrimination in the industry, and create inclusive environments where everyone can thrive.

Finally, another major barrier to diversity in tech is a lack of representation in leadership positions. Without diverse representation in leadership, companies may not prioritize diversity and inclusion in their hiring and business practices. This lack of representation can also create a lack of role models for underrepresented groups, making it more difficult for them to envision themselves succeeding in the industry. To overcome this barrier, we need to actively work to promote diversity in leadership positions, and create opportunities for underrepresented groups to develop their skills and advance in their careers.

As someone who has not personally encountered barriers to education or faced discrimination in my last two jobs, I feel fortunate to have had the opportunities to succeed in the tech industry. However, I am acutely aware of the challenges that others may face and the importance of promoting diversity and inclusion in tech. As a tech lead, I recognize that it is my responsibility to prioritize inclusion in every aspect of my work, from hiring and team building to product development and company culture.

Even though I have been lucky to not experience barriers myself, I know that this is not the case for everyone. I have seen firsthand how a lack of diversity can lead to homogenous thinking and missed opportunities for innovation. This is why I am committed to creating an inclusive environment where everyone can thrive and bring their unique perspectives to the table. I recognize that this is an ongoing process that requires constant effort and attention, but I believe that it is necessary to create a better future for the tech industry and society as a whole.

Overall, while there are significant barriers to diversity in tech, there are also concrete steps we can take to overcome them. By investing in accessible education and training, addressing bias and discrimination, and promoting diversity in leadership, we can create a more inclusive and equitable tech industry.

In conclusion, while I have not personally faced barriers to education or discrimination in my last two jobs, I am committed to promoting diversity and inclusion in tech. As a tech lead, I recognize the importance of creating an inclusive environment where everyone can thrive, and I will continue to prioritize inclusion in every aspect of my work. By working together to overcome barriers and promote diversity, we can create a more equitable and innovative tech industry for everyone.

The role of mentorship and community in supporting diverse talent in tech

Mentorship and community play an important role in supporting diverse talent in tech. For underrepresented groups, finding mentors who can provide guidance and support can be crucial for success in the industry. Mentors can offer insights into the industry, help build networks, and provide feedback and advice on career development. They can also serve as role models and sources of inspiration, helping individuals from underrepresented groups envision themselves succeeding in the tech industry.

In addition to mentorship, community is also important for supporting diverse talent in tech. Communities provide a space for individuals to connect with others who share similar experiences and challenges. This can be especially valuable for people with disabilities, who may face unique challenges in the industry. By connecting with others who understand these challenges, individuals can feel more supported and empowered to succeed. Communities can also provide opportunities for learning and growth, whether through online forums, local meetups, or industry events.

Overall, mentorship and community are critical components of supporting diverse talent in tech. By providing guidance, support, and a sense of belonging, these resources can help underrepresented groups succeed in the industry. As someone who has benefited from mentorship and community in my own career, I recognize the importance of giving back and supporting others. I am committed to serving as a mentor and connecting with communities that support diversity in tech, and I encourage others to do the same. By working together, we can create a more inclusive and supportive tech industry for everyone.

The importance of advocating for change within the industry

and holding companies accountable for their diversity and
inclusion efforts

Advocating for change within the tech industry and holding companies accountable for their diversity and inclusion efforts is crucial for creating a more equitable and inclusive industry. While there have been some efforts towards promoting diversity and inclusion in tech, progress has been slow and there is still much work to be done. By advocating for change and holding companies accountable, we can push for more meaningful action and create real change.

One important way to advocate for change is by using our voices to speak out about the importance of diversity and inclusion in tech. This can include sharing our own experiences, calling out bias and discrimination when we see it, and advocating for policies and practices that promote diversity and inclusion. By speaking out and raising awareness, we can help to shift the conversation around diversity in tech and create a sense of urgency for change.

In addition to advocacy, holding companies accountable for their diversity and inclusion efforts is also important. This can include calling out companies that are not living up to their commitments, pushing for transparency around hiring and promotion practices, and advocating for more equitable policies and practices. By holding companies accountable, we can create pressure for change and help to ensure that diversity and inclusion are taken seriously within the industry.

In conclusion, advocating for change within the tech industry and holding companies accountable for their diversity and inclusion efforts is critical for creating a more equitable and inclusive industry. By using our voices to speak out and holding companies accountable, we can push for more meaningful action and create real change. As someone who is committed to promoting diversity and inclusion in tech, I will continue to advocate for change and hold companies accountable for their efforts. I encourage others to do the same, and to work together to create a more inclusive and equitable tech industry for everyone.

the game and web dev turned dj/audio engineer turned senior audio software engineer - why i went back to engineering

Leon mckenzie (rowan turner) — Mon, 13 Mar 2023 01:21:49 +0000

Making career changes is not uncommon, but going back to a field you previously abandoned can be quite a challenge. However, in my case, returning to engineering was a natural progression that made sense to me.

I started coding at a young age and enjoyed game development and web development in high school. However, I decided to pursue my passion for music and became a DJ and audio engineer. This led me to a job at Sony Music, but I soon realized that my dream job was not as fulfilling as I had hoped.

As a result, I started to explore other avenues that would allow me to merge my love for music and audio with programming. I began to create my own plug-ins and software using Max MSP and even built my own hardware on breadboards. My interest in audio engineering research and development grew, and I pursued a degree in audio engineering.

Although I had prior experience in programming, it had been ten years since I last worked with it. However, I was not deterred, and I knew that I could apply my knowledge to the field of digital signal processing (DSP), which I found fascinating.

After launching my own music technology start-up, Synergy DSP, I ported my prototype plug-in from Max MSP to VST format using JUCE and C++. I am currently pursuing a Master's degree in Digital audio engineering learning about DSP & AI.
Pursuing a Master's degree in Digital audio engineering has been an incredibly fulfilling experience for me. The program has provided me with a deep understanding of the theory behind audio engineering and has equipped me with the technical skills needed to excel in the field.

In addition to my studies, I am also working as a tech lead at another start-up, where I lead the development of audio software.
Furthermore, being a tech lead has given me the opportunity to hone my leadership and communication skills. I have learned how to manage a dev cycle effectively and to communicate technical concepts to non-technical stakeholders.

In addition to pursuing a Master's degree and becoming
a tech lead, I have also received recognition for my work in audio engineering. When I graduated from my undergraduate program in audio engineering, I was honored with the Millmar Award for Excellence in Audio Engineering for my final project. It was a proud moment for me to be recognized for my hard work and dedication to the field.

Winning honors and awards can be a significant achievement for professionals and can provide them with a sense of accomplishment and recognition for their work. It can also help to build credibility and enhance their professional reputation, which can lead to new opportunities and career advancements.

I believe that my award for Excellence in Audio Engineering has opened doors for me and has helped me gain recognition for my work. It has been an important milestone in my career, and I hope to achieve many more in the future.

Overall, pursuing a Master's degree and becoming a tech lead has allowed me to take my career to the next level. It has provided me with the skills and knowledge needed to excel in my field, and I am excited to see where this journey takes me.
Returning to engineering has allowed me to merge my passions for music and audio with programming, and I feel that I am contributing to a field that has a significant impact across various industries. Moreover, it has given me a sense of fulfilment that I was unable to find in my previous career.

In conclusion, going back to engineering was the best decision for me, and I am grateful for the opportunities that it has presented me. If you are considering a career change, don't be afraid to explore different avenues and pursue what truly makes you happy.