Independent software · Crypto · Fintech · Engineering · Productivity
Every app here started with the same question — what's the simplest tool that genuinely helps someone do their work better?
Crypto decisioning
A decision engine for crypto traders. Scores every tradable coin on Pionex against nine technical setups — post-pump consolidations, breakouts, momentum continuations, grid-bot candidates — with the exact indicators behind each verdict. Turns hunch-based trades into scored, evidence-backed decisions.
For active Pionex traders who make their own calls.
Open →Organize thoughts, finish tasks
An AI companion for planning, brainstorming, and knocking out the long tail of small tasks — including mine. Built for the way real work actually happens: in bursts, with a lot of small things that need to get done without ceremony.
For people whose focus comes in bursts — ADHD brains included.
Open →Manage money and forecast retirement
Budgeting, net worth, and retirement modeling in one dashboard. Model ACA subsidy cliffs, spousal Social Security timing, Roth conversion ladders, and where retirement actually lands — no advisor required.
For DIY planners modeling retirement without an advisor.
Open →Design open water channels
Open-channel hydraulics calculator. Gradually-varied flow profiles, Manning's equation, critical depth, orifice flow, and rating curves. Originally written in Visual Basic in 1997 to help design the juvenile fish bypass channel at Bonneville Dam on the Columbia River. Still solving the same engineering problems nearly three decades later, used by engineers, students, and water-resource professionals.
For civil and hydraulic engineers sizing open channels.
Open →I've spent three decades solving technical problems from multiple angles — as an engineer, developer, trainer, and enablement leader — and I still enjoy building small, useful tools that make real work easier.
It grew out of Rickysays, a technical blog I started for writing up the tools I was working on and the problems I ran into. A few of those "what if I built this" posts turned into actual apps.
The first one predates the blog by more than twenty years. I wrote the original version of FlowPro in Visual Basic in 1997 as a licensed civil engineer at the U.S. Army Corps of Engineers, to help size the juvenile fish bypass channel at Bonneville Dam on the Columbia River. That project made me realize I liked the software more than the civil engineering.
From there: software developer at STEP Technology in Portland, then a long non-linear arc through engineering, technical training, pre-sales, and partner enablement. Now at Anaplan, designing the Partner Presales Certification Workshop — while shipping these apps on nights and weekends.
How I build
Questions, bug reports, collaboration ideas, or "hey I used FlowPro in the field today" — all welcome.