732 karma · joined May 3, 2018
the x20 Max plan for Claude gives you way lover limits.
you're not actually spending that money. it's sunk cost, as you already bought the hardware. at least for the big pharmaceutical companies for drug development. then you run your own local model, trained on special data, with special etc, etc... to the end of buying GPUs for what, 3.5-6.5M/rack or so (GB300 NVL72, Google AI summary pricing quote) becomes a bargain (vs the double digit billions you need to spend on a new drug R&D).
(I'm also an IBMer.)
signed: a proud IBMer
WITH raw_data AS (
SELECT * FROM (
VALUES
('S01', 5000.0, 0.45, 120, 5),
('S02', 2400.0, 0.30, 45, 12),
('S03', 15000.0, 0.60, 300, 45),
('S04', 900.0, 0.15, 20, 2),
('S05', 3200.0, 0.50, 85, 8)
) AS t(store_id, revenue, margin, tx_count, returns)),
base_data AS (
SELECT
store_id,
revenue,
margin,
CAST(tx_count AS DOUBLE) AS tx_count,
CAST(returns AS DOUBLE) AS returns
FROM raw_data
)
SELECT
store_id,
revenue,
margin,
CAST(tx_count AS BIGINT) AS tx_count,
CAST(returns AS BIGINT) AS returns,
-- KPI Layer
returns / tx_count AS return_rate,
revenue / tx_count AS avg_order_value,
-- Threshold Layer (matching original alias names)
revenue > 1000.0 AS is_revenueabove1000,
revenue > 5000.0 AS is_revenueabove5000,
revenue > 10000.0 AS is_revenueabove10000,
tx_count > 50 AS is_tx_countabove50,
tx_count > 100 AS is_tx_countabove100,
tx_count > 200 AS is_tx_countabove200,
-- Interaction Layer (preserving exact numeric formula & aliases)
revenue / (margin + 1e-5) AS ratio_revenuepermargin,
revenue / (tx_count + 1e-5) AS ratio_revenuepertx_count,
revenue / (returns + 1e-5) AS ratio_revenueperreturns,
margin / (tx_count + 1e-5) AS ratio_marginpertx_count,
margin / (returns + 1e-5) AS ratio_marginperreturns,
tx_count / (returns + 1e-5) AS ratio_tx_countperreturns,
-- Segmentation Layer
CASE WHEN margin > 0.4 THEN 'High' ELSE 'Low' END AS margin_profile
FROM base_data;Then I read the code but only after it got scrutinized by pr review skills on multiple models and those feedback got marked completed by the author.
He said "ultrafast" which has nothing to do with subagents. It's a new API tier where it runs on a different inference backend to get you faster token/s.
as for the commit message: if it's the usual verbose Claude style, I'm also not going to read it. to be honest, probably if it's not verbose, I'm still not reading it.
I'll ask my review agent anyway to summarize your code. My review agent will read your commit message.
I'm not even sure about the unpaid part.
remember, this is Europe - the coffee is not made the same nor looks or tastes the same as you get in the US. it's mind boggling to me that people get a 16oz "cup of coffee", black.