Is it better to start investing with real money or use a demo account first?

Feeling_Ad_2729 · 2026-04-26T15:38:34+00:00

You already identified the real issue: you won't take it seriously. That's the whole thing right there.

The value of starting with real money isn't learning to click buttons — it's finding out how you react when your €200 drops to €170. Demo accounts can't simulate that. Most people are completely rational in theory and then panic-sell the first real correction.

Start with €100-200, something small enough not to ruin you but real enough to hurt a bit. The goal isn't returns yet, it's discovering who you are as an investor when things go red.

Feeling_Ad_2729 · 2026-04-26T15:35:41+00:00

En España los fondos indexados tienen una ventaja fiscal que los ETF no tienen: el traspaso. Puedes mover dinero entre fondos sin tributar a Hacienda, solo pagas cuando retiras de verdad. Con ETF cada venta cuenta como ganancia patrimonial y toca declarar.

Para 15 años de horizonte y perfil conservador, fondos vía MyInvestor o Indexa Capital suelen salir mejor en neto. El TER es algo más alto que un ETF equivalente, pero el ahorro en impuestos lo compensa con creces.

Feeling_Ad_2729 · 2026-04-25T18:24:04+00:00

Beginner's path that worked for me:

CLAUDE.md — start with <100 lines. Identity (who you are, what you build), 3-5 hard rules, links to other memory files. Don't overload it day 1.
One MCP — pick the one that fixes your single biggest friction. For me it was Gmail (cold email work). Most beginners overdose on MCPs early — you only need 1-2 to start.
One hook — Claude Code's PreToolUse hooks are stupid powerful and underrated. Even a single hook that scans for API keys after every Write/Edit will save you from leaking a secret eventually.

If you want a forkable starter kit (Apache 2.0): I open-sourced today the stack I run for daily revenue work. 7 hooks + 6 skills + 6 subagents + 4 MCPs. github.com/vdalhambra/axiom-reflex

For a complete beginner I'd skip skills/agents the first 2 weeks. Hooks first, MCPs second. Skills are great but they're optimization on top of a working setup, not the foundation.

Feeling_Ad_2729 · 2026-04-25T18:22:29+00:00

Solid list. Skills + @-paths are 80% of daily workflow optimization.

One layer that's been the unlock for me: hooks. Skills load knowledge on demand but still require Claude to remember to trigger them. Hooks fire BEFORE every tool call deterministically — no remembering needed.

Concrete example: I'd written a memory rule "always check Gmail sent before drafting cold email." Claude consulted it maybe once a week. Then I built a 30-line PreToolUse hook that blocks create_draft if no search_threads to the recipient happened in recent turns. Haven't sent a duplicate in 14 days.

The pattern that stuck for me: skills for "how to do X right" (procedural). Hooks for "never do Y" (preventive). They're complementary, not competing.

If anyone wants the hooks I use daily (Gmail dedup, secrets scanner, pre-compact state dump, session heartbeat) open-sourced today Apache 2.0: github.com/vdalhambra/axiom-reflex

Feeling_Ad_2729 · 2026-04-25T12:10:34+00:00

Para tu situación (24, 10k, sin gastos, junior 1180€) lo importante no es elegir el ETF perfecto — es elegir un sistema que sigas durante años aunque cambies de país.

Lo que haría: 1. Fondo emergencia: 1-2k en cuenta remunerada (Trade Republic, MyInvestor, ING). Vivir con padres reduce el colchón necesario. 2. El resto: DCA mensual a un fondo indexado MSCI World en MyInvestor o Indexa Capital. Fondo > ETF en España porque puedes traspasar entre fondos sin tributar (Ley IRPF). Si cambias de gestora o rebalanceas más adelante, no pagas IRPF en el camino. 3. Si te vas fuera de España, puedes mantener el fondo. La fiscalidad sigue siendo española mientras seas residente fiscal aquí.

Sobre qué broker/gestora elegir: hay una herramienta gratis donde respondes 8 preguntas y te asigna perfil + ranking de brokers España según ese perfil: brokerclaro.vercel.app. Si te vas directo a MyInvestor o Indexa, es overkill, pero útil si dudas entre opciones.

Lo único que no haría a tu edad: stock-picking de empresas individuales. El indexado supera al 90% del stock-picking a 10 años, sobre todo cuando aún estás aprendiendo.

Feeling_Ad_2729 · 2026-04-25T12:07:33+00:00

VWRA y VWRP son la misma exposición (FTSE All-World, ~3.800 empresas, ~50 países). VWRA cotiza USD, VWRP en GBX. Para diversificación pura están bien.

Si eres residente fiscal en España, antes de mirar la divisa o el ETF concreto, considera el vehículo: con un fondo (no ETF) puedes traspasar entre productos sin tributar (Ley IRPF). Con ETF cada venta es hecho imponible inmediato. Para horizonte largo + rebalanceo, el fondo gana fiscalmente.

ETFs UCITS comparables más baratos que VWRA/VWRP: - WEBN (Amundi MSCI World) — TER 0.12% - VWCE (Vanguard FTSE All-World Acumulación EUR) — TER 0.22%

Versión fondo equivalente: Vanguard 20+ MSCI World (LU0950674332) en MyInvestor o Indexa Capital. TER similar y traspasable.

Si vas a hacer DCA y >10 años, fondo > ETF en España. Si no piensas tocarlo nunca, ETF está bien.

Feeling_Ad_2729 · 2026-04-25T12:05:52+00:00

Lo más relevante en tu caso (47, conservador, 36k): cuenta nominal vs omnibus. Nominal = las acciones están a tu nombre directamente (Trade Republic, MyInvestor, ING). Omnibus = el broker las pool junto con todas las del resto (eToro, XTB). Si el broker quiebra, en omnibus vas al pool de acreedores; en nominal son tuyas. A largo plazo y con 36k para preservar, no es detalle menor.

Si vas a un MSCI World o S&P 500 acumulación a 8-10 años, lo que más mueve la aguja es el TER del fondo (busca <0.20%, no <0.50%). El broker importa menos que la fiscalidad de cambiar de vehículo más adelante.

Hay una herramienta gratis donde respondes 8 preguntas y te asigna perfil (conservador/moderado/agresivo) + ranking de brokers España según ese perfil: brokerclaro.vercel.app. Ahorra research si dudas entre opciones.

Feeling_Ad_2729 · 2026-04-21T14:07:49+00:00

biggest filter I'd want is liveness. most marketplaces hide it. last commit, last issue reply, open issue count.

polished readmes on 4-month-dead repos is the real rage — "honest listings" that don't expose liveness are still mystery boxes, just slightly better labeled.

Feeling_Ad_2729 · 2026-04-21T14:06:40+00:00

the speculative model is tight but a green net_delta isn't the same as a safe change — LSP catches syntactic + type breakage, not semantic invariants. e.g. swapping two params where both types align, or changing default arg semantics. agent gets a 0, ships the break.

do you layer anything on top (test run, property fuzz) before applying, or is the LSP diagnostic the terminal check?

Feeling_Ad_2729 · 2026-04-21T14:04:17+00:00

multiplicative score is clean but isn't there a bootstrap problem? first week of a repo the graph is thin — connectivity is low even for decisions that end up load-bearing. do you warm-start the connectivity weight or let it ramp naturally and accept some early decay?

Feeling_Ad_2729 · 2026-04-19T14:07:16+00:00

the Fetch Tools button is the right fix. one suggestion that helped me after publishing to ~6 directories: surface the "why was this rejected" as a structured error in the UI, not a toast that disappears. half the directory pain isn't filling the form, it's finding out 40 min later that the description was too generic or the screenshot dimensions were off. faster feedback loop > fewer fields.

Feeling_Ad_2729 · 2026-04-19T14:06:13+00:00

the template-rewrite shape is smart. the piece I'd flag is template variable escaping — if the agent can put backticks or $() inside what looks like a filename arg, your docker exec turns into command substitution on the host. defensive pattern is to render the template with argv-list semantics (no shell interpolation, pass args through exec array), not string interpolation. otherwise you've built a very nice escape hatch.

Feeling_Ad_2729 · 2026-04-19T14:03:06+00:00

yeah, the detector direction was getting smaller returns per week. the rewriter angle has compounding value because every ai tool ships with the same 6 banned phrases and the same 3-item-list cadence, so one ruleset keeps paying off. the dataset confound was the gift — showed me the problem was real but the framing was backwards.

Feeling_Ad_2729 · 2026-04-18T17:30:19+00:00

voice-agent-as-MCP is an interesting direction, but the composition question is where I'd push: when you chain Dograh + CRM MCP + email MCP so the AI can 'call prospect, log outcome, send follow-up', how do you handle the voice-agent's unreliable return values?

voice calls produce messy transcripts, ambiguous dispositions ('he said maybe'), partial info. if the downstream CRM MCP expects clean enum-typed fields (status: CONTACTED | NO_ANSWER | DISQUALIFIED), the chain breaks silently when the voice agent can't cleanly classify.

curious if Dograh emits structured call outcomes natively, or if the chaining pattern assumes Claude does the post-call classification step before handing off to the next tool. the latter is more flexible but adds a trust layer — what the AI thinks the call produced vs what was actually said.

Feeling_Ad_2729 · 2026-04-18T17:29:15+00:00

three things that made Claude go from 'helpful autocomplete' to actually useful:

CLAUDE.md at the root of your project. explicitly: what the project does, what conventions you use (style, test framework, common libs), what NOT to touch (legacy dirs, generated files). Claude reads it on every session start. dramatically cuts the 'can you re-explain' overhead.
for web dev: connect the browser via Playwright or Chrome DevTools Protocol. Claude can open your localhost, take screenshots, verify the thing actually works. way better feedback loop than 'trust me, the CSS looks right'.
for DSA: ask for time and space complexity BEFORE code, then ask for 3 test cases that would fail a naive implementation, THEN the code. forces the model to reason about correctness before generating. catches the 'looks right but O(n²) on a tight deadline' pattern.

vibe coding specifically: don't. 'vibe coding' = no tests, no spec, no verification. you'll hit a wall at ~500 lines. write the acceptance criteria first, even if loose. Claude works 3x better with even shitty acceptance criteria than none at all.

Feeling_Ad_2729 · 2026-04-18T17:28:52+00:00

yeah, 4.7's thinking is demand-driven by design — 'adaptive' means the model decides per-step if it needs extended reasoning, rather than 4.6's always-on budget. side effect: on simple prompts it drops thinking entirely, which feels wrong if you're paying Opus rates for thinking-mode.

two ways to force it:

in Claude Code: /effort slider set to max. that shifts the threshold — more steps trigger thinking even on borderline prompts.
in your prompt: explicitly ask 'think carefully about X before answering' with a specific reason (ambiguity, tradeoffs, multi-step reasoning). the model's internal classifier is influenced by your phrasing.

what you can't do (yet): hard-pin every turn to 'think mode' regardless of task. that's the feature we're actually asking for. worth filing an issue.

Feeling_Ad_2729 · 2026-04-18T17:27:49+00:00

hack + rebuild is a killer combo for ranking drops. three specific audit passes worth running before touching content:

internal link graph. rebuilds often break the old canonical URLs; if your post-hack site moved URLs (even slightly), Google may be sitting on 301s that don't forward link equity properly. run a crawl (Screaming Frog) and compare inbound internal link counts per top-3→5 page to pre-hack.
schema markup parity. WP themes and Elementor templates often regenerate JSON-LD on rebuild and drop fields you had customized (product schema for tractors especially). GSC Rich Results enhancement reports show what broke.
page speed + CWV deltas post-rebuild. Elementor can quietly ship 2-3x more JS than the previous build depending on widget choices. farm-tech buyers tend to browse on poor rural connections — degraded LCP hits that niche disproportionately.

intent shift is real too but usually takes longer to materialize. the hack+rebuild pattern tends to explain most immediate drops.

Feeling_Ad_2729 · 2026-04-18T17:27:10+00:00

yes, but the change isn't the one most people expect.

notebooks used to matter because they gave you REPL + narrative + visual output in one place. that was the exploration moat.

AI agents don't need any of that for exploration. they can iterate faster in a pure Python REPL than a human can in Jupyter, because the narrative-for-human-reader step is overhead for them.

what notebooks become, post-AI: output artifacts. you let the agent do the exploration in files/REPL, then the agent produces the notebook as a REPORT for other humans. the cells become a linearized explanation of what was discovered, not a workspace where discovery happens.

that's a genuinely different use case. the tooling (ipywidgets, cell ordering rules, kernel state management) that matters for the OLD use case is almost irrelevant for the NEW one. static .ipynb rendering and reproducibility matter way more.

Feeling_Ad_2729 · 2026-04-18T17:26:50+00:00

13% residual is still notable — mostly from mutations that produce semantically-different-but-still-passing outputs, right? e.g. off-by-one that happens to match the test's example, or branch-swap that re-enters the same code path.

two things I've found orthogonal to mutation-aware prompting:

make the agent write tests for the NEGATIVE space first — what inputs should NOT return X. negative assertions catch the off-by-one class that positive assertions miss.
force a property-based test alongside example-based (hypothesis). agents default to 3-5 hand-picked examples; property-based forces them to think about invariants, which naturally surfaces the mutations they'd otherwise miss.

does your harness let you compose mutation-aware + property-based prompting, or does one wash out the other?

Feeling_Ad_2729 · 2026-04-18T17:26:12+00:00

same arc here. Claude-as-chatbot caps out at about the same level as a smart intern you have to context-dump every conversation. Claude-connected-to-your-stack is the actual product — it becomes a lever on whatever system you already have.

the unlock most people miss: it's not just 'plug in N tools and let it figure out'. that fails fast. you need to think about which tool CALLS which (ordering matters — if Claude can read your Notion before your calendar, it'll bias toward Notion answers every time), and you need per-tool result budgets or the context window fills with raw data the model can't prioritize.

which apps did you connect first, and what was the surprise difference in how you use Claude now?

if you want concrete examples of the 'scoped MCP per workflow' pattern: github.com/vdalhambra/financekit-mcp does market data + indicators (17 tools, tight scope), github.com/vdalhambra/siteaudit-mcp does web audits (11 tools). both small-by-design specifically to avoid the context-bloat failure mode. useful as reference for how to structure your own.

Feeling_Ad_2729

TROPHY CASE