Tim Santeford 
When I’m working with large datasets in PySpark, I often need to know how many records are flowing through my transformations. It’s a simple thing, but being able to log that information at the right time can help me catch issues early—like unexpected filters wiping out rows or joins ballooning in size. What makes it
Commit Quantity vs Quality Balancing commit quantity and quality is a common challenge for software engineers. While some emphasize frequent, incremental commits, others advocate for single, clean commits that ensure a pristine history. In this post, I’ll share my personal approach to navigating this balance, lessons from past experiences, and tips for fostering a team
Welcome to your first day as a software engineer! Whether you’re joining your first tech company or transitioning into a new role, the beginning can feel like a mix of excitement, nerves, and information overload. But don’t worry—there are a few key things you can do on Day One to set the tone for success
Encountering a ModuleNotFoundError while running a PySpark job can be frustrating, especially when the module exists and works perfectly outside of Spark. I recently ran into this exact issue while working with a Spark job that imported a function from a local utils module. Everything seemed fine until I tried to use a PySpark UDF,
When working on a monorepo with multiple packages, getting everything up and running efficiently can be a challenge. I’ve been there—jumping between terminal windows, manually starting different services, and hoping I didn’t forget anything. Fortunately, NPM workspaces provide a great way to manage multiple packages in a single repository, and with the right setup, starting
Handling file uploads in a React app is straightforward, but things get more interesting when you need to filter for specific file types and parse their contents. I needed to create an upload button that only accepted JSON and YAML files, then read and displayed their contents in the browser. Here’s how I did it.
When working with Storybook, I wanted my component previews to take up the entire viewport height. But by default, the preview area doesn’t always stretch to fit the full screen. After trying a few different approaches, I found the simplest and most reliable way to achieve this. Here’s how to make sure your Storybook preview
When I started working with Adaptive Cards in a React app, I wanted a way to dynamically load and style cards while keeping them flexible. Adaptive Cards provide a powerful way to render dynamic UI elements using JSON, but by default, their Markdown support is somewhat limited. To improve this, I decided to integrate markdown-it,
When I first encountered the “The inferred type of ‘meta’ cannot be named without a reference to…” message in Storybook, I was caught off guard. I wanted a quick solution that would keep my TypeScript checks happy and my Storybook setup running smoothly. After a bit of trial and error, I discovered a simple fix
I remember feeling puzzled the first time my TypeScript compiler complained about an imported .module.css file in my React code. Everything worked at runtime, but VSCode kept throwing red squiggles. To avoid confusion, I decided to create a quick fix that put an end to these errors. Cannot find module ‘./MyComponent.module.css’ or its corresponding type
I recently ran into an error in my Storybook environment that read: useNavigate() may be used only in the context of a component. It took me a moment to understand why this was happening, and I want to share how I solved it. Error: useNavigate() may be used only in the context of a component.
Azure Event Hubs are designed as an immutable, append-only store for events. Once events are ingested, they remain available until the retention period expires. This approach is ideal for high-throughput and reliable streaming, but it also means that individual message deletion is not supported. Instead, the available options focus on managing data lifecycle through retention