r/ClaudeHomies

I recently got Claude Pro mainly because I wanted to see if I could use it for something beyond just asking questions and helping with college/work.
I’m interested in actually making money with it, but I’m not looking for the usual “start a faceless YouTube channel” or “generate AI blog posts” advice.
I’m curious about what people here are actually doing with Claude Pro that brings in money.
For example:
Freelancing

Building websites/apps

Digital products

Automation

Content creation

Design

Research

Selling services

Anything else

I’m open to learning new skills too. I’m mainly looking for ideas where Claude genuinely makes you more productive or lets you provide a service/product that people are willing to pay for.
If you're already making money with Claude Pro, what are you doing, how did you get your first customers, and roughly how much are you making?
Would love to hear some real experiences rather than generic AI side-hustle lists. 🙏

Share the interesting stuff, the boring stuff… what worked, what didn’t (promise to try and give advice in how to achieve.

If you worked on an interesting product, feel free to self promote.

Hey everyone, I’m a student studying AI & Data Science and I really want to use Claude for studying, coding and projects, but the subscription is a bit too expensive for me right now.

Is there any student program, free option, or anyone who could help me get Claude Pro free, I’d genuinely appreciate any suggestions.

Thanks ❤️

The clanker deleted my last post as an "a c ( 0 u n t issue".

It's not. It's a product question.

So... is it true? Chat and Claude Code only when on subscription? API only with pay for usage?

Do you guys know that you don't need to pay for the pro plan for claude upto a week

Ok, so there's a new watermark on text that supposedly survives copy & paste, and editing? Not that I'm trying to pass any writing off as non-AI generated, but couldn't you literally just retype the exact text on a word processor? Or am I not understanding this correctly?

Ideally avoid Claude code stuff. But we’re not picky.

Feel free to self promote!

Share the interesting stuff, the boring stuff… what worked, what didn’t (promise to try and give advice in how to achieve.

If you worked on an interesting product, feel free to self promote.

Updated set of impactful things i actually do with Claude professionally and personally. Inspired by this post:

1. Edit, don’t correct. If Claude gives a bad answer, go back and edit the prompt before it. The sh*t answer disappears from the conversation instead of influencing (and poluting) what comes next.
2. Use screenshots NOT descriptions. For designs, bugs, layouts or inspiration, upload what you mean rather than spending five paragraphs explaining it
3. Dictate messy context. Talk through the goal, constraints, what failed and what you’re unsure about. Save time, energy and often give more context. Tip. end with: These are messy voice notes, ask questions if anything is unclear
4. Use Projects for repeated work. Add your reference files, examples and templates once, then reuse that context across related chats. Tip. Organise your chats like this
5. Turn repeated prompts into Artifacts. If you keep asking Claude to do the same task, ask it to build a reusable mini-app instead: a tracker, calculator, dashboard, planner or comparison tool

Has anyone made money using claude? Have you made a trading bot or an app? If so, how was your experience? What would you advice on others who may want to do the same?

# Three Math Ideas Hiding in a Dollar-Store Calculator

There is a calculator in your kitchen drawer. It cost about a dollar, it has no battery you ever replaced, and it has worked flawlessly since the Clinton administration. You have never thanked it, because it seems too trivial to deserve thanks — a plastic rectangle that does what a second-grader does, only faster.

This essay is an attempt to correct that injustice. That rectangle is a museum of mathematical ideas, three in particular, each of which took serious minds decades to work out, and each of which quietly contradicts something you were probably taught to assume about numbers. One idea concerns what a number even *is* once it lives inside a machine. One concerns a discovery so useful it navigated a supersonic bomber before it fit in your pocket. And one is a lesson about the nature of difficulty itself — a lesson the calculator teaches better than almost any object you own.

One honest note before we open the case. The 99-cent four-function model in your drawer holds the first and third ideas fully. The second idea — the beautiful one about trigonometry — lives in its slightly fancier cousin, the cheap scientific calculator with the SIN and COS keys, which today costs less than a sandwich. The fact that the plain model *can't* do trigonometry, and the reason the fancy one *can*, turns out to be part of the story. Popular accounts blur the two together. We won't.

---

## Idea One: A number is not a thing. It is a costume.

Ask a mathematician what the number one-tenth is, and you'll get something serene and eternal: a point on the number line, existing independently of any notation. Ask an engineer, and you'll get a more unsettling answer: one-tenth is whatever pattern of switches we decide will *represent* one-tenth — and every choice of costume has consequences.

Here is the famous embarrassment. Ask a modern desktop computer to add 0.1 and 0.2 and, under the hood, it computes 0.30000000000000004. This is not a bug. Computers store numbers in binary — base two — and in base two, one-tenth is an infinite repeating fraction, the way one-third is in our decimal system (0.3333... forever). The computer must chop that infinite tail somewhere, and the chopped stump is *almost* one-tenth but not quite. Two stumps added together miss three-tenths by a whisper, and occasionally the whisper leaks onto the screen. For scientific work this is a manageable nuisance. For a device that adds up grocery bills, it is unacceptable. Nobody will trust a calculator that thinks a dime plus two dimes is thirty cents and a ghost.

So calculator designers, particularly in the classic era, reached for a different costume: binary-coded decimal, or BCD. Instead of translating a whole number into one long binary string, BCD keeps each *decimal digit* separate and encodes it in its own little four-bit packet. The number 125 isn't converted to binary as a whole; the 1, the 2, and the 5 each get their own packet, standing in a row exactly as you typed them. The machine is still made of two-state switches — it can't help that — but it has been organized to *think in tens*, the way its human owner does. Type 0.1, and the machine holds precisely the digit one, one place right of the decimal point. No infinite tail, no stump, no ghost. Your dime is exactly a dime.

This costs something: BCD wastes a little storage (four bits can count to fifteen, but we only use them to count to nine) and requires fussier arithmetic circuitry. The designers paid gladly, because they understood their customer. The costume was chosen to fit the wearer's expectations.

But — and here is where the idea gets its depth — no costume fits everything. Ask that same honest calculator for one divided by three, and it displays 0.3333333333 and stops, because *decimal* notation cannot hold one-third exactly, any more than binary could hold one-tenth. The tables have precisely turned. Every representation makes some numbers exact and exiles others to approximation; the choice of base decides which numbers get citizenship. And beyond fractions lies a further frontier: the sine of an angle, the logarithm of a number — these are almost never expressible in *any* finite string of digits. Every transcendental result your calculator has ever shown you was an approximation, engineered to be wrong only past the last digit of the display, where you cannot catch it.

So the first idea hiding in the drawer is this: exactness is not a property of machines, it is a *negotiated treaty* between a machine and its users, and the treaty's terms are written in the choice of representation. The calculator doesn't know what a number is. It knows what costume you asked for, and it wears it with total commitment.

---

## Idea Two: When you can't afford the math, rewrite the math.

Now pick up the cousin — the cheap scientific calculator — and press SIN. The answer appears faster than your finger lifts. To understand why that is astonishing, you need to know what the button is asking for, and what the chip has to give.

What sine *is*, mathematically, involves the machinery of calculus. The classical recipe for computing it is an infinite polynomial: take the angle, subtract its cube divided by six, add its fifth power divided by 120, and continue until the corrections become negligible. Notice the verbs. Powers mean multiplication upon multiplication; the recipe is drenched in the stuff. And multiplication is exactly what primitive digital hardware is poorest at. A bare-bones chip does three things cheaply: add, subtract, and *shift* — slide a binary number's digits sideways, which doubles or halves it for free, the way sliding decimal digits multiplies by ten. General multiplication must be built out of many additions, or out of large, hungry, expensive circuitry. In the 1950s that circuitry meant cabinets, watts, and pounds; even now it means silicon area someone has to pay for.

In 1956, this collision landed on the desk of an engineer named Jack Volder at Convair, in Fort Worth. His employer was building the B-58 Hustler, the first Mach-2 bomber, and the Air Force wanted its analog navigation computer — accurate but drifting — replaced with a digital one. Navigation at twice the speed of sound is continuous trigonometry in real time, and the affordable digital hardware of 1956 could add, subtract, and shift. That's all.

Volder's response is one of the great moves in the history of problem-solving. He did not ask how to make the machine strong enough for the mathematics. He asked whether the mathematics could be rewritten in the machine's dialect. Rummaging through the trigonometric identities in his 1946 *CRC Handbook of Chemistry and Physics* — the fat reference every engineer of that era kept at arm's reach — he found, by what he later called "massaging" the angle-addition formulas, a back door.

Here it is without a single equation. Picture a clock hand of length one, pointing at zero degrees. The coordinates of its tip *are* the cosine and sine of whatever angle it points at — so computing sine becomes a steering problem: rotate the hand to the angle you want, then read the tip. Rotation normally requires multiplication, which seems circular in the useless sense. But the rotation formulas can be rearranged so the only multiplier left standing is the *tangent* of each swing — and nobody said the hand must reach its target in one swing. Volder restricted the machine to a fixed menu of swing sizes, chosen with perfect cunning so that each swing's tangent is a power of one-half: first 45 degrees (tangent 1), then about 26.6 (tangent ½), then 14.0 (tangent ¼), then 7.1 (tangent ⅛), each half the last. Multiplying by ½ or ¼ or ⅛ in binary is *nothing but a shift*. The expensive operation was not sped up. It was chosen out of existence.

The algorithm then plays warmer-colder. Want 52 degrees? Swing 45 — too little. Add 26.6 — overshot. Subtract 14.0, subtract 7.1, add the next... The hand whips back and forth in shrinking arcs, every swing costing only shifts and additions, each oscillation roughly halving the error, guided by a tiny stored table of the menu angles. Volder named it CORDIC — Coordinate Rotation Digital Computer — and published it in 1959.

Two honest footnotes the legend omits. The hand never lands *exactly*: each swing buys about one binary digit of accuracy, so the machine simply runs enough swings that the leftover error hides past the last digit of the display — recall the treaty from Idea One. And the rearranged formula has a side effect: every swing slightly stretches the hand, by a factor that is fixed and known in advance because the menu of swings never changes — about 1.6468 in total. The designers' answer is a click of pure elegance: start the hand at length 0.6073, the reciprocal, so that after all the swelling it arrives at length exactly one. The error is not corrected. It is *pre-paid*.

The afterlife is a comedy of near-misses. Volder left Convair before his navigation computer flew, built a desktop calculator prototype with a partner, and pitched it to Hewlett-Packard in 1965. HP said no — then absorbed the idea anyway through engineer David Cochran, who by 1966 was corresponding with Volder about running CORDIC on decimal digits (BCD again — the two ideas in this essay shook hands in a private letter sixty years ago). HP's 9100A desktop machine used the algorithm in 1968; John Walther then generalized it so the same shift-and-add engine could produce logarithms, exponentials, and square roots; and in 1972 the HP-35, the first pocket scientific calculator, put the whole arsenal in a shirt pocket for $395 and killed the slide rule within a few years. The transistors had shrunk a thousandfold since 1956, but nobody had made multiplication fundamentally cheap. The pocket calculator became possible because the *mathematics had already been translated* into the dialect that cheap silicon speaks. Half a century later, CORDIC still runs inside signal processors, GPS receivers, and graphics chips — anywhere shifting is cheaper than multiplying, which is to say nearly everywhere small.

---

## Idea Three: Difficulty is not in the problem. It is between the problem and the machine.

The third idea is the one the other two have been secretly demonstrating, and the dollar-store calculator states it more plainly than any textbook.

We are taught to assume that mathematical tasks have inherent difficulty rankings — that computing a sine simply *is* harder than adding, the way granite is harder than chalk. Volder's story breaks that picture. Sine-by-power-series is a multiplication-hungry aristocrat; sine-by-rigged-rotations is a pauper's dance of shifts. Same function, same answers, wildly different cost — depending entirely on which machine must do the work. Likewise, one-tenth is trivial or impossible to store exactly depending on nothing but the base you chose. Difficulty, it turns out, is not a property of problems. It is a *relationship* between a problem and a substrate, and changing the substrate reshuffles the entire ranking of easy and hard.

Once you accept that, the calculator reveals itself as something stranger than a small computer. A general-purpose computer's philosophy is: give me a flexible machine and I'll implement any mathematics in software later. The calculator's philosophy is the reverse: *we know in advance exactly what humans will ask* — arithmetic, a handful of functions, ten digits of display — so let us bake those questions into the architecture itself and throw away everything else. Generality is deliberately sacrificed, and the payment received is efficiency so extreme it looks like magic: a device performing thousands of logic operations per keystroke, powered by the ambient light of your kitchen.

Look at how many layers had to be negotiated to hit that price. The *mathematics* was reformulated until only cheap operations remained (Idea Two). The *representation* was chosen to honor human decimal expectations within a binary machine (Idea One). The *logic* was pared to adders, shifters, and small lookup tables. The *silicon* uses CMOS transistor pairs that draw essentially no current except at the instant they switch — a chip that mostly sits at zero watts, waiting. The *display* refuses to generate light at all; liquid crystals merely twist the room's existing light into the shapes of digits, because emitting photons is an extravagance the power budget cannot bear. And the *solar cell* on the face closes the loop: the machine computes using a sliver of the same light it borrows to show you the answer. No single layer is the miracle. The miracle is that every layer was designed while staring hard at the poverty of the layers around it — mathematics bent around transistor budgets, hardware bent around human habits, decades of mutual accommodation compressed into an object that costs less than the coffee you drank while reading this.

And the pattern did not retire with the calculator. The reason the current era of artificial intelligence exists at all is that researchers pulled the same maneuver at colossal scale: they reformulated *learning itself* into vast batches of the one operation that graphics chips happened to perform spectacularly well, and the substrate, once listened to, delivered. The lineage runs further back, too — logarithm tables were performing the same trick four hundred years ago, converting multiplication (hard for humans) into addition (easy for humans); Henry Briggs was publishing shift-and-add-flavored methods in 1624. It is one idea wearing different centuries: when you cannot afford the tools the problem demands, rebuild the problem around the tools you have.

---

## Closing the drawer

So: three ideas, one plastic rectangle. A number is a costume, and every costume makes some truths exact and others approximate — exactness is a treaty, not a fact. Mathematics is negotiable — the same function can be an aristocrat or a pauper, and the deepest engineering skill is translating it into the dialect your machine speaks for free. And difficulty lives in the relationship between problems and substrates, which means constraint is not the enemy of elegance but its most reliable manufacturer.

Jack Volder spent the Second World War keeping B-24 bombers in the air as a flight engineer, spent 1956 teaching a machine to find angles without multiplying, and died in 2013 having watched his warmer-colder game spread into a billion pockets. The hand he set swinging has never once landed exactly on its target. It zig-zags forever, each arc smaller than the last, and stops only when the error slips beneath the treaty line where no one can see it. Close enough, engineered honestly, turns out to be one of the most beautiful things human beings know how to build — and there is one in your drawer, waiting, at zero watts, for a question.

*— About 2,300 words of essay proper. Historical claims verified against Jack Volder's retrospective "The Birth of CORDIC" (Journal of VLSI Signal Processing, 2000) and standard histories of the HP 9100A and HP-35.*