I want to tell you something about AI-assisted development in 2026.
If you don't understand your programming language deep, your main web framework, HTTP, databases, and concurrency fundamentals, you can't tell when the code generated by Claude or Copilot is subtly wrong - and it will be, often enough to matter in production.
AI amplifies what you already know. The stronger your fundamentals, the better your judgment on what to keep, what to fix, and what to throw away entirely.
The numbers:
→ 60.7% on Finance Agent (SEC filings) — best in market
→ 76% on TaxEval
→ Due diligence tasks that took weeks → dramatically faster
AI isn't replacing finance pros. It's giving them superpowers.
https://t.co/QjBrzseLZP
#AI#FinTech#ClaudeAI
Claude Opus 4.6 just dropped — and it's a massive leap for AI in finance.
+23% improvement on real-world finance benchmarks. State-of-the-art on SEC filing analysis.
Here's what changed 🧵
It now powers 3 key tools:
• Cowork — run multiple financial analyses simultaneously
• Claude in Excel — pivot tables, charts, formatting
• Claude in PowerPoint (NEW) — build decks from your templates
Finance analysts, your workflow just changed.
I wrote my first React code 7-8 years ago. I still remember examples of createElement, the hassle of setting up Webpack, finding the right loader for an svg or a custom font, ejecting CRA and then regretting it, binding methods in class components, debating should you use componentDidMount or componentWillMount to fetch initial data etc.
And I have to say that the current way of working with React (RSC's, Hooks, Server Actions, Framework-based) Is my preferred way.
BUT I do feel like that devs that have gone through what I've written above have an unfair advantage of understanding the new React.
When I first learned about useEffect, I mapped my existing knowledge of class component lifecycles to the dependency array and it's matching behaviour. I have no idea how new developers remember those behaviours.
In my videos, when I explain "use client" as "like the old way of doing it", that makes perfect sense to me - but do new developers have any idea what I mean? How are they supposed to know?
When we dive into next.config.js to change the webpack config - I imidiatelly match this with my experience of modifying webpack config in CRA using react-app-rewired - But do new developers even know what Webpack is? Should they know that at all?
My point is that I feel like there is no official way to learn React as we would use it in the good old days.
Now to be completely fair, I went onto React's, Svelte's and Vue's documentations to see how they handle this. You can find recommendations of using framework-based solution on all three (Next.js, SvelteKit & Nuxt.js)
Both React & Svelte recommend using a framework in their "Start a new project" guide! - And it is pretty clear why, this is the preferred way of building production-grade apps.
Only Vue documentation shows an example of how to setup Vue as a SPA, and then by scrolling down you can find SSR using Nuxt.js - and I absolutely love this. This is how I would want to learn react. Standalone first, and then a framework solution.
Clients on Upwork are easy creatures to understand 🧪
-They’ll likely only read the first 4 words of your job title.
- They’ll likely only read the first 3 sentences of your bio.
Tip: The first few words need to count 🧩
🔮 A 21 Day Upwork Challenge.
A plan of action, checklist, covering all your weak spots.
Working in the hotel lobby to bring this together for you all. Yes it’ll be Free 👀
RT & Comment ‘21days’ if you want access when I release it ⚡️
@JoshBurnsTech I have been struggling for the last 1.5 years to be stable on Upwork but failed. Whenever, i get frustrated, i just visit a few profiles like @topdevfreelance@UpworkSaves@remoteoliver@freelancemvp along with you. That gives me energy back. Thanks a lot guys ❤️