Arian Acosta

AI is crossing a real line. Not better answers but a shift from assistance to ownership. We’ve entered an era where AI can take a goal, plan the work, operate across systems, and deliver progress. In wealth management, that matters because the constraint has never been insight; it’s coordination and review. Think of AI as a junior operator: prepping, assembling, maintaining, executing. That doesn’t replace judgment. It lets judgment compound. The question isn’t how to automate tasks. It’s how to safely delegate outcomes. The firms that scale will think in leverage. The mindset shift matters more than the tool.

16

Remix 3 and the End of React-Centric Architectures Remix 3 challenges the idea that React should be the center of our frontend universe. Instead it puts web fundamentals back in the spotlight. For years, React has reigned supreme not just as a UI library, but as the foundation of full-stack JavaScript architecture. But Remix 3 is flipping that script. It challenges the idea that React should be the center of our development universe; and instead, it puts web fundamentals back in the spotlight. Built on progressive enhancement and server-first principles, Remix 3 doesn’t just optimize performance — it redefines how we build. In a world obsessed with client-side everything, this framework asks: what if we stopped treating React like a framework and started using it like a tool? The implications could reshape frontend architecture entirely. https://lnkd.in/e6VdYjzZ Stay Connected to Sidharth Sharma, CPA, CISA, CISM, CFE, CDPSE for content related to Cyber Security. #CyberSecurity #JPMC #Technology #InfoSec #DataProtection #DataPrivacy #ThreatIntelligence #CyberThreats #NetworkSecurity #CyberDefense #SecurityAwareness #ITSecurity #SecuritySolutions #CyberResilience #DigitalSecurity #SecurityBestPractices #CyberRisk #SecurityOperations 

1

Mault will be releasing our multi-agent flow this week. It includes: Does the code work? **Agents operate in scoped sandboxes (worktrees/PIDs) so they never bump into each other. ** Gatekeeper protocol mandates Hexagonal Architecture, SRP, and zero hard-coding. ** Pre-commit hooks enforce testing structure and code quality before it leaves machine. ** CI serves as the ultimate arbiter, utilizing mutation testing and stealth security checks to ensure 'correctness' isn't just a pass/fail metric. The Results: --> 2.6% Code Duplication (industry average is often 10-20% in rapid-growth phases). --> 40+ PRs per day with total architectural consistency. Does the product work? ** Now that code is proven to work, we have a tester agent tasked with proving the product, and user journey to work (will demo that seperately)

11

I've seen this a few times so I wanted to break down that math: at Claude Opus 4.6 $25 per million output tokens, this is 10 𝑩𝒊𝒍𝒍𝒊𝒐𝒏 tokens or Approximately 7.5 𝑩𝒊𝒍𝒍𝒊𝒐𝒏 words Roughly 750 𝑴𝒊𝒍𝒍𝒊𝒐𝒏 lines of code That's an estimated 15 from scratch Windows 11 rewrites Or approximately 50 new Android operating systems Google is estimated to have 2 billion lines of code across all umpteen of their products. 2 1/2 engineers at $250k in tokens could rebuild all of Google in a year. Also, AI engineer pay ranges w/bonus: Senior AI Engineer $222K–$376K Senior Machine Learning Engineer $170K–$270K Principal Machine Learning Engineer $186K–$309K Director of Machine Learning $203K–$325K So, only the top 1% of AI engineers at top tech companies are making $500k and no one person should be spending $250k on tokens unless they are rewriting all of Google solo from scratch. #AI #LLM #Nvidia #JensenHuang #SoftwareEngineering

206

78 Comments

Learn how a strategic partnership between applied research and product management allows Capital One to drive scientific innovation at scale and create a better banking experience for our customers. Read the full blog from Bayan Bruss, VP, Applied AI Research, and Ofer Idan, Sr. Director, Enterprise AI/ML Product, on our strategy-backed applied research. https://bit.ly/4o8oh62

5

I think the marginal cost of learning to code just dropped to (almost) zero. Ollama just added Anthropic Messages API compatibility, which means you can run Claude Code (the terminal-based coding agent) against local, open-weight models instead of paying per-token for a hosted proprietary model. What this changes in practice: No token bill while you experiment, learn, and iterate (assuming you already have a machine to run a model). Same “agent in the terminal” workflow: navigate a repo, make edits, refactor, write tests. Better privacy / data residency: your prompts + code can stay on localhost. You can still switch to cloud models when you need more horsepower. If you’re mentoring juniors (or you’re one yourself), this is a big deal: you can practice real workflows - reading codebases, fixing bugs, adding features - without that constant “every mistake costs money” feeling. The key idea is simple: keep the Claude Code experience, swap the model backend. https://lnkd.in/dFxucrBa #ollama #claudecode #opensource #localLLM #aidevtools #learntocode #developerproductivity #privacy #selfhosted

1

🚀 NgRx 21 — 10 Years of State Management, Now Signals-First NgRx 21 celebrates a decade of NgRx while taking a big step toward Angular’s Signals-based future with the introduction of @ngrx/signals/events. 🔍 What’s technically significant in NgRx 21? 🧩 @ngrx/signals/events A new primitive focused on event-driven architecture using Angular Signals: • Explicit event modeling instead of action overload • Clear separation of events → side effects → state updates • Reduced boilerplate compared to traditional Actions + Effects • Fine-grained reactivity with Signals (no unnecessary stream emissions) This makes complex flows easier to reason about while keeping NgRx’s core principles intact. ⸻ ⚡ Signals-First Reactive Model • Moves away from RxJS-heavy patterns where they aren’t required • Enables synchronous, predictable state transitions • Better performance via fine-grained dependency tracking • Ideal for modern Angular apps using signal(), computed(), and effect() ⸻ 🧠 Improved Architecture & DX • Cleaner APIs across NgRx packages • More composable building blocks • Easier onboarding for teams new to NgRx • Stronger alignment with Angular’s recommended direction ⸻ 🏗️ Why this matters for real-world apps For large-scale Angular applications: • Less cognitive overhead in complex workflows • More maintainable state and side-effect management • Better testability (events and state updates are easier to isolate) • Smooth migration path from classic NgRx to Signals-based patterns NgRx 21 proves that enterprise-grade state management doesn’t have to be verbose — and that Signals can coexist cleanly with proven NgRx patterns.

10

📯With 𝗦𝗽𝗿𝗶𝗻𝗴 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝟳.𝟬 set to release by end of 2025, one of the major excepted feature is improved native image support for 𝗚𝗿𝗮𝗮𝗹𝗩𝗠. While Spring started supporting native images from version 6.x via Spring AOT hints, version 7.0 pushes this further by deepening support for:  • Spring AOT contributions, making native image builds more robust and reliable.  • Removing deprecated methods and aligning more cleanly with GraalVM expectations. The key to choosing 𝗚𝗿𝗮𝗮𝗹𝗩𝗠 𝗼𝘃𝗲𝗿 𝗢𝗽𝗲𝗻𝗝𝗗𝗞 however depends on understanding 𝘄𝗼𝗿𝗸𝗹𝗼𝗮𝗱, 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲 𝗮𝗻𝗱 𝘁𝗿𝗮𝗱𝗲-𝗼𝗳𝗳𝘀 - which I have documented in this post to best of my knowledge. ⚖️ Key Trade-offs ✅ Choose GraalVM Native if:  • Cold start speed is business-critical (serverless, on-demand scaling).  • Memory footprint must be minimized (edge devices, containers with hard limits).  • You’re building batch/CLI tools that should run instantly.  • You can tolerate longer build times in CI/CD. ✅ Choose JVM (HotSpot/OpenJDK) if:  • App runs 24/7 and throughput > startup time (e.g., APIs, Kafka, banking apps).  • Heavy runtime reflection, proxies, or dynamic class loading.  • Developer productivity (fast builds, hot reload, live debugging) is a priority.  • You need mature monitoring, profiling, and ops tooling. Hope this helps! Which are the use cases where you think GraalVM would prove better over OpenJDK? #OpenJDK #GraalVM #AOT #SpringFramework #Java #SoftwareDevelopment #JavaEngineering

5