jadenlemmon

Joined 8 years ago

Karma
49
Submissions
5
Member since
Jul 16
I solve problems with valuable products and tools. In reality, no product is ever unique. It’s already been done. Success is created from execution not ideas. Competitors are a signal of market validation.

I’m a software engineer at heart. I’ve been coding since 4th grade. I recognize the importance and balance of writing the best code vs managing timely expectations during product early stages.

I build successful teams around products ready to execute. Some of my product success includes some of these products.

Voyage - https://voyageapp.io/ Voyage automatically generates an isolated environment and a unique URL you can send to the entire team.

Actovos - https://actovos.com/ Actovos streamlines messages and responses for important events such as an emergency foster care placement or important notifications within the DOD.

Oyster - http://oysterapp.io/ A location-based mingling app that helps you find nearby singles in real time and initiate conversations in real life.

Oh and if you ever catch me out of work you may find me playing 18 holes on the golf course, riding my bike along the Oklahoma river, or capturing some drone footage of downtown Oklahoma City.

View on Hacker News

Recent submissions

Comment · 18 days ago
For an individual, mostly yes. Unactivated will just keep running with a watermark & some minor restrictions.
Comment · 18 days ago
it depends on where you are running it. If using a cloud provider, license is typically built into hourly price.
Comment · 18 days ago
I work at QA Wolf and lead the development of automated testing for Windows desktop apps. I wanted to share what we did and how we did it.

This post covers how we added Windows to a test infrastructure built around Linux runners. The central problem was giving each test a clean, logged-in Windows desktop without waiting 2–3 minutes for a VM to boot.

We extended the device scheduler we already use for mobile testing. It maintains warm pools of Windows VMs on GCE. Each test claims a ready VM, uses it once, and releases it. The VM is then destroyed and replaced, rather than cleaned up for the next test.

The test code stays in a Linux pod. Playwright connects to browsers on the Windows machine over CDP, while WebdriverIO and Appium handle native apps through WinAppDriver. A small Go agent captures the desktop with FFmpeg and streams it over WebRTC for live viewing and recordings.

That separation lets a single test move between a browser and a native Windows app without requiring a separate Windows runner pipeline.

The trade-off is that we keep idle Windows VMs ready and install the app under test on every run. In exchange, tests don’t inherit another run’s files, registry changes, or saved sessions.

I’d love to answer any questions!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton