<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://herrickspencer.github.io/</id><title>From the desk of Herrick Spencer</title><subtitle>Blog site for hosting previous blog posts, and new thoughts on technology, Software Development, DIY, Woodworking, Tips of the Week, and parenting.</subtitle> <updated>2026-08-07T11:46:34-07:00</updated> <author> <name>Herrick Spencer</name> <uri>https://herrickspencer.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://herrickspencer.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://herrickspencer.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Herrick Spencer </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Cut AI Credit Usage by 5–20× Without Losing Productivity</title><link href="https://herrickspencer.github.io/posts/AI-Credit-strategies/" rel="alternate" type="text/html" title="Cut AI Credit Usage by 5–20× Without Losing Productivity" /><published>2026-08-06T17:00:00-07:00</published> <updated>2026-08-06T17:00:00-07:00</updated> <id>https://herrickspencer.github.io/posts/AI-Credit-strategies/</id> <content type="text/html" src="https://herrickspencer.github.io/posts/AI-Credit-strategies/" /> <author> <name>Herrick Spencer</name> </author> <category term="Software Development" /> <category term="Technology" /> <category term="Programming" /> <category term="AI" /> <summary>Introduction The problem: AI credit burn is real, especially with frontier models. Since the change in pricing models from a ‘all you can eat buffet’ to a per token or per ‘AI Credit’ plan, there has been a huge worry that the costs of using AI for every task will outweigh the benefits. I recently tracked my usage over a month of unlimited usage in April and found that with the current pricin...</summary> </entry> <entry><title>TOW: Access Commandline from OOBE aka Windows Setup</title><link href="https://herrickspencer.github.io/posts/TOW-OOBE-Commandline/" rel="alternate" type="text/html" title="TOW: Access Commandline from OOBE aka Windows Setup" /><published>2026-08-05T11:31:00-07:00</published> <updated>2026-08-05T11:31:00-07:00</updated> <id>https://herrickspencer.github.io/posts/TOW-OOBE-Commandline/</id> <content type="text/html" src="https://herrickspencer.github.io/posts/TOW-OOBE-Commandline/" /> <author> <name>Herrick Spencer</name> </author> <category term="Tip Of The Week" /> <summary>Access the commandline from the Out-of-the-box Windows Setup When you first install Windows, or start a Windows machine for the first time there is a setup sequence called “OOBE” short for Out-Of-Box-Experience. This helps add your user, name the machine, setup network connections etc. However occationally you are doing something else at this point… maybe you want to shrink partitions or crea...</summary> </entry> <entry><title>Local Models for AI Development</title><link href="https://herrickspencer.github.io/posts/Local-Model-AI-Dev/" rel="alternate" type="text/html" title="Local Models for AI Development" /><published>2026-08-03T17:00:00-07:00</published> <updated>2026-08-07T11:46:09-07:00</updated> <id>https://herrickspencer.github.io/posts/Local-Model-AI-Dev/</id> <content type="text/html" src="https://herrickspencer.github.io/posts/Local-Model-AI-Dev/" /> <author> <name>Herrick Spencer</name> </author> <category term="Software Development" /> <category term="Technology" /> <category term="Programming" /> <category term="AI" /> <summary>I am starting an investigation of how to use local models to substitute for cloud based AI coding agents such as Claude and Copilot CLIs. I am only at the start of this investigation but will report on what I find periodically to keep track of what I discover. Machine Specs Matter First thing that has become apparent, and likely obvious, is that a beefy machine spec is needed for this. I had ...</summary> </entry> <entry><title>AI: The ROI of Hiring Seniors vs CS Grads Has Changed</title><link href="https://herrickspencer.github.io/posts/seniors-with-ai/" rel="alternate" type="text/html" title="AI: The ROI of Hiring Seniors vs CS Grads Has Changed" /><published>2026-06-16T16:50:00-07:00</published> <updated>2026-06-16T16:50:00-07:00</updated> <id>https://herrickspencer.github.io/posts/seniors-with-ai/</id> <content type="text/html" src="https://herrickspencer.github.io/posts/seniors-with-ai/" /> <author> <name>Herrick Spencer</name> </author> <category term="Software Development" /> <category term="Technology" /> <summary>AI: The ROI of Hiring Seniors vs CS Grads Has Changed With this title, you would be forgiven if you thought this post was going to be about elders getting scammed by AI bots. However, I’ve wanted for a while now to express my thoughts on how AI collaborative coding should be changing the workforce in tech. You’ve Been Promoted! As soon as I started using AI in a more deliberate and intentio...</summary> </entry> <entry><title>Building StrikeAlert: An AI-Assisted Options Trading App from Scratch</title><link href="https://herrickspencer.github.io/posts/building-strikealert-options-trading-app/" rel="alternate" type="text/html" title="Building StrikeAlert: An AI-Assisted Options Trading App from Scratch" /><published>2026-04-19T00:00:00-07:00</published> <updated>2026-08-04T14:46:57-07:00</updated> <id>https://herrickspencer.github.io/posts/building-strikealert-options-trading-app/</id> <content type="text/html" src="https://herrickspencer.github.io/posts/building-strikealert-options-trading-app/" /> <author> <name>Herrick Spencer</name> </author> <category term="Programming" /> <summary>The Itch I Had to Scratch So there I was, watching a video from Brandon Powers’ CLT Options methodology — price and volume analysis for timing options spreads — and thinking: “This is great… but what if I didn’t have to stare at charts all day?” What if a system could watch my tickers, recognize the same PV setups Brandon teaches, and just… tap me on the shoulder when it sees something? Push ...</summary> </entry> </feed>
