DEV Community: James Gibbard

Why I Built Clearminutes: A Privacy-First Meeting Assistant

James Gibbard — Sat, 04 Apr 2026 21:32:57 +0000

Like many developers, I spend hours in meetings every week. And like many developers, I've tried various meeting transcription tools: Otter.ai, Fireflies, Granola. They all share one thing in common: they send your audio to the cloud.

The Problem with Cloud Transcription

Every time a meeting bot joins your call, it's recording everything. Your strategy
discussions. Your 1:1s with reports. Your sales calls with prospect data. All of it uploaded to servers you don't control.

For most meetings, that's probably fine. But what about:

Healthcare professionals discussing patient information (HIPAA)
Lawyers in privileged client conversations
Financial advisors discussing sensitive portfolio details
Startup founders in investor meetings with proprietary information

The "just don't use it for sensitive meetings" argument doesn't hold up. You can't always predict which meeting will discuss something sensitive.

Building Local-First

I built Clearminutes with a simple principle: your audio never leaves your machine.

We use Whisper.cpp running locally on your Mac or Windows PC. The transcription happens entirely on-device, using your GPU (Metal on Mac, CUDA on Windows) or CPU. No cloud services see your audio. Ever.

How It Works

You start a recording in Clearminutes
Audio is captured from your microphone (and optionally system audio)
Whisper processes it locally on your device
The transcript and AI summary stay on your machine
You own everything: no server copies, no training data

The Privacy Advantage

Because processing happens locally:

Healthcare professionals can transcribe patient sessions without HIPAA concerns
Lawyers can use it in privileged conversations
Anyone can transcribe confidential business meetings
No internet required: it works offline

Beyond Privacy: Speed and Cost

Local processing isn't just about privacy. It's also:

Faster: No upload/download latency. Real-time transcription.
Cheaper: No per-minute fees. No subscription for basic features.
More accurate: Use the largest Whisper model without cloud costs.

Try It Free

Clearminutes is free to try with local transcription using Whisper Small. Download it for Mac or Windows and see what private meeting transcription feels like.

Your meetings belong to you. Keep them that way.

MeetUp Overview - Building & Scaling Game Dev in the Cloud

James Gibbard — Fri, 09 Aug 2024 13:00:12 +0000

I recently had the pleasure of presenting at a meet-up where I delved into a topic that's both exciting and challenging: moving AAA game development into the cloud. For those who missed it, I wanted to take this opportunity to share some of the key insights and solutions discussed.

You can catch the recorded session on YouTube here:

The Evolution of Game Development

Game development has come a long way from its early days. Today’s AAA games are akin to blockbuster movies, characterised by their massive budgets, global reach, and complex production processes. The development of these high-profile games typically happens in dedicated studios equipped with cutting-edge hardware. These studios invest heavily in powerful gaming PCs, extensive graphics design tools, and vast amounts of storage.

However, as technology evolves, there’s an increasing push to leverage the cloud for game development. The cloud offers scalability, flexibility, and the potential for significant cost savings. But moving such a complex and resource-intensive process to the cloud presents its own set of challenges.

Current State of AAA Game Development

To set the stage, let’s clarify what a AAA game is. AAA games are high-profile, high-budget titles developed by major studios with the expectation of global success. They require extensive localisation, support for multiple platforms (such as Xbox and PlayStation), and involve large teams working on everything from graphics and coding to complex game logic.

Traditionally, the development of these games occurs in physical studios, where developers use high-spec gaming PCs. These machines come equipped with powerful GPUs, ample RAM, and fast CPUs, necessary to handle the enormous data volumes and intricate processes involved. Game development is often done in silos, with studios working in isolation to create content that eventually gets integrated into the final product. The development cycle is lengthy, sometimes taking years, and involves managing terabytes to petabytes of data.

Challenges & Solutions for Cloud-Based Game Development

Challenge 1 - Handling High Demands of Game Development

The Challenge: Game development requires high-performance, low-latency hardware. Developers, artists, and testers need access to powerful PCs with fast disk speeds, high-end GPUs, and substantial CPU resources. They also need peripherals and controllers to test and interact with the game seamlessly.

Our Solutions:

AWS EC2 GPU-Based Machines: We utilised powerful EC2 instances like G4 and G5, which provide the necessary computing power and graphics capabilities. These instances help deliver a desktop-like experience for game developers and artists working remotely.
Parsec: This technology enables low-latency remote desktop access by creating a peer-to-peer network between the host PC and the remote machine. Using UDP traffic, it streams data efficiently, minimising latency.
Architecture Design: We set up a Virtual Private Cloud (VPC) in AWS, with GPU EC2 machines and Parsec High Performance Relay integrated into the architecture. This setup ensures secure and efficient routing of traffic to minimise latency for users across different regions.

Challenge 2 - Data Transfer and Bandwidth

The Challenge: AAA games generate vast amounts of data. Managing this data, providing fast access to shared storage, and dealing with high CPU demands for compilation are crucial. Additionally, accessing physical gaming consoles for remote testing poses a significant challenge.

Our Solutions:

EC2s & SN DBS: We employed SN DBS technology to allow for distributed compilation by sharing CPU resources across multiple machines. This reduces build times significantly.
FSx for Cache: AWS FSx provides high-speed, managed storage that can be mounted to EC2 instances. This solution addresses the need for fast data access and cache management.
Site-to-Site VPN: To integrate with physical studios and consoles, we used a VPN to connect AWS infrastructure with on-premises systems, allowing remote access and testing.
Global Network Setup: AWS Transit Gateway with inter-region peering was used to create a global network. This setup enabled us to connect distributed development teams and studios effectively.

Challenge 3 - Building the Game

The Challenge: Building a game involves several time-consuming steps, including checking out the source code, compiling the Unreal Engine, cooking data assets, and packaging the game for distribution. Each step requires significant computational power and speed.

Our Solutions:

SN DBS with Autoscaling: We leveraged SN DBS for distributed compilation and autoscaling to dynamically adjust the number of machines based on the workload. This setup ensures efficient resource utilization and cost-effectiveness.
FSx for Shared Storage: Fast access to storage is critical for game builds. FSx provided high-speed cache and storage solutions to support the compilation and packaging processes.
TeamCity CI System: We used TeamCity for continuous integration and orchestration of the build process, enabling automated scaling and management of build resources.
Cost Optimisation: To manage costs effectively, we utilised EBS gp3 volumes with storage-optimised machines. By stripping multiple volumes together, we achieved high IO performance at a lower cost.

Conclusion

Transitioning AAA game development to the cloud is a complex but rewarding endeavour. The benefits include dynamic scaling, global distribution, and overcoming physical limitations of traditional studios. However, challenges such as high data volumes, demanding hardware requirements, and the need for physical console access remain significant hurdles.

Our approach involved a combination of advanced AWS technologies, strategic architectural design, and careful cost management to address these challenges. The result is a scalable, efficient cloud-based game development environment that can support multiple teams and global distribution.

For those interested in exploring cloud-based game development or discussing these solutions further, feel free to reach out. I’m always happy to share more insights and experiences.

Thank you for reading!

Currency Converter using Python 🐍 & Steamlit

James Gibbard — Fri, 09 Aug 2024 09:02:58 +0000

Recently had reason to create a little currency converter app. I decided to do it it Python as I've not had the chance to use the language for a while.

I didn’t want to have to build a whole UI or access a fully blown db as it was just overkill.

After some research I decided on the following tech stack:

Python 3.10
Poetry - for dependency management
Streamlit - for the UI framework
CVS & Pandas - for data storage
APILayer.io - for the currency convert API

I certainly had fun solving this little challenge.

Decided to spit the code architecture into sections to keep things neat and tidy.

. └── currency-converter/ ├── api.py -- remote api cal related functions ├── audit_log.py -- read/write from audit log ├── common.py -- common lists, etc └── currency_converter.py -- main python file

There is a live demo of the app available here: https://jgibbarduk-currency-converter-currency-converter-v6ohj8.streamlit.app

Check out the source here: https://github.com/jgibbarduk/currency-converter

If you like the tech stack used or you have some suggestions, let me know in the comments.