https://t.co/CO81QF8gv2

She Can Code! Last night, at 9 PM, I invited my partner to try https://t.co/bf4RLWyK7C. I wanted to see how easy it would be for someone without technical skills to write their first lines of JavaScript... 15 minutes later, she had compiled code with detailed instructions on

https://t.co/bWpbNi5Eqo

@Prathkum I actually think writing code and putting in hours to manually build stuff makes you a better thinker and an engineer. I'm not saying AI-assisted coding is not useful. But just as watching calculus videos is not enough to learn calculus (you actually have to solve problems by

I was learning Rust on https://t.co/iWs6IoD8Iw and was prompted to upgrade to a premium subscription... I pulled my credit card and happily paid the monthly subscription fee: 25 euros. Then realised that I built the tool myself. Yes, I just paid Stripe 0.25 cents for using my

Plan, Create US, Build, Review, Test, Update US, Repeat

Can you become a competent Rust Developer in 1 month? We're making it possible on https://t.co/YgXVC5s1sS If Rust is not your thing, TypeScript and JavaScript are two programming languages you can learn and improve your level in just a few days with your dedicated coach. Give

Ah, you're absolutely right!

@davybuild And not just a dying breed. A nearly obsolete breed

The Real Mindset Shift AI automates typing, not thinking. Skill atrophy only happens if: you stop thinking you stop understanding you stop designing As long as you remain the critical thinker, architect, and reviewer, your skills will not only survive — they will grow faster

9. Use AI as a challenging sparring partner Ask AI to: Critique your design propose alternative implementations Find weaknesses in your approach ask you questions (Socratic method) Now AI becomes the gym — and you get stronger.

8. Teach, write, or explain concepts regularly When you teach something, you maintain mastery. Try: writing short internal docs recording short explanations teaching juniors creating small “architecture notes” summarizing what AI taught you in your own words Explaining

7. Build one project per quarter — but go deep Choose a project where you: design it set up tooling build core modules debug issues write tests deploy it AI can help, but you must make the decisions. If you do one meaningful project every 3 months, you will never lose

6. Keep learning new systems, not just syntax Languages and frameworks matter less now. What matters is whether you understand: distributed systems event-driven architectures caching strategies database modeling concurrency DevOps fundamentals type systems performance

5. Read code — not just generate it Skill atrophy comes from not thinking in code structures. Make it a habit to: Read your teammates' PRs Explore open-source repositories Ask AI to explain unfamiliar patterns Rewrite parts of the generated code in your style Reading keeps

4. Work on real-world complexity (AI can't fully hide it) Even when AI writes code, you must still deal with: architecture scaling decisions debugging weird runtime issues environment setup APIs and integrations performance tuning security data modeling AI helps, but you must

3. Use AI as an “augmentation coach,” not a code factory Instead of asking AI: ❌ “Write this for me.” Ask: ✅ “Check my code for improvements.” ✅ “Explain different ways I could design this.” ✅ “Compare two approaches and tell me the trade-offs.” ✅ “If you were mentoring

2. Regularly code small things from scratch without AI This is like going to the gym. Do short 20–30 minute drills: Implement a caching layer Build a small CRUD API Write a debounce function Create a custom hook in React Implement binary search Turn Cursor off. Use your

1. Stay in the driver’s seat, not the passenger seat AI can write code, but you must remain the architect. How to do it: Before asking AI for code, write a spec yourself. For every suggestion, ask: “Do I understand why this works?” Force yourself to explain the code back to

Do you still need to learn coding in 2025 and beyond? I was demoing https://t.co/bf4RLWyK7C to a good friend of mine this afternoon. Me: I'm building Cursor for Technical Education He: Developers are cooked. Why bother? | | | | After an hour of discussion, we couldn't agree on