
Software & Telecom Eng | Tech Mentor | Creator contato: [email protected]
Florianópolis
Joined May 2021
- Tweets31.7K
- Following703
- Followers40.4K
- Likes19.3K
Pinned Tweet
HELLO !
💁🏻♀️Para mentoria, contato por email: [email protected]
💻 Trago discussões e perguntas técnicas.
😍 Palestrante, escritora, mentora, criadora de conteúdo, administradora de comunidades para inclusão de mulheres e PCDs.
FOLLOW THE RABBIT 🐰
Engenheira Coelho retweeted
Software engineers, you have 5 days left.
14 March 2025. Amodei said that AI would write all the software in 12 months. That's five days from now. Prepare to disappear.
businessinsider.com/anthropi…
Dario Amodei just told software engineers exactly how long they have.
Six to twelve months.
Amodei: “I have engineers within Anthropic who say I don’t write any code anymore. I just let the model write the code, I edit it, I do the things around it.”
The people building the most powerful AI in history have already stopped writing code.
That is not a forecast. That is the current working condition inside the lab closest to the frontier.
Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.”
The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now.
When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists.
Amodei: “And then it’s a question of how fast does that loop close.”
That is the sentence everyone skipped.
The code was never the hard part.
The hard part was everything around it.
The model just learned everything around it.
Writing the code is already nearly gone.
Testing is next.
Deployment is next.
When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all.
The corporation or sovereign state that closes that loop first does not gain a competitive advantage.
It gains a category of speed that biological engineers cannot match, track, or reverse.
That is not disruption.
That is replacement at a systems level.
Amodei is not describing a future disruption. He is describing the current state of his own building.
The loop is already closing. The only question is whether you are inside it or outside it when it seals.
Engenheira Coelho retweeted
System Design becomes EASY when you follow these:
1. Fundamentals
youtube.com/playlist?list=PL…
2. API Design
youtube.com/watch?v=DQ57zYed…
3. Load Balancing
youtube.com/watch?v=xg7Dj2AX…
4. Message Queues
youtube.com/watch?v=DYFocSiP…
5. Rate Limiting
youtube.com/watch?v=MIJFyUPG…
6. Caching
youtube.com/watch?v=1NngTUYP…
7. Sharding & Partitioning
youtube.com/watch?v=wXvljefX…
8. Database Replication
youtube.com/watch?v=oh8GvLf4…
9. Consistent Hashing
youtube.com/watch?v=vccwdhfq…
10. CAP Theorem
youtube.com/watch?v=RexrINtV…
11. Microservices
youtube.com/watch?v=vTjeDWhj…
12. Fault Tolerance
youtube.com/watch?v=3Lis4w4_…
13. Scalability
youtube.com/watch?v=tjubQ97l…
14. Event-Driven Architecture
youtube.com/watch?v=Fb_0UOD2…
15. Service Discovery
youtube.com/watch?v=v4u7m2Im…
Engenheira Coelho retweeted
If you're a software engineer who wants to upskill in system design, read these 14 articles (links below):
Engenheira Coelho retweeted
VAGA PARA DEV FULLSTACK REACT/C# SENIOR
- React;
- C#/Net Core;
- Typescript;
- Mobx;
- MQTT ou Rest.
100% Home Office
12K CLT + Beneficios
Chama na DM!
O Google mudou mesmo o jeito de estudar línguas. O novo learnLM é literalmente um professor que evolui com o aluno. A proposta é muito boa, vou testar ele :)
labs.google/lll/en
Engenheira Coelho retweeted
Se vc é dev frontend e não sabe isso aqui, desiste, a IA ja tomou seu emprego!!!!
Hydration
Partial hydration
Islands architecture
Streaming SSR
Concurrent rendering
Time slicing
Reconciliation algorithm
Fiber architecture
Virtual DOM diffing complexity
Structural sharing
Immutable data patterns
Referential equality
Memoization pitfalls
Stale closure problem
Event loop (macro vs microtasks)
Task starvation
Layout thrashing
Critical rendering path
Render blocking resources
Tree shaking internals
Code splitting strategies
Dynamic import chunking
Module federation
Shadow DOM
Custom Elements lifecycle
Web Components interoperability
Web Workers vs Service Workers
SharedArrayBuffer
Transferable objects
OffscreenCanvas
WebAssembly integration
Browser compositing layers
Paint vs composite vs layout
GPU acceleration in CSS
CSS containment
Subpixel rendering
IntersectionObserver internals
ResizeObserver loop limits
MutationObserver cost
IndexedDB
Service Worker lifecycle traps
Cache invalidation strategies
Stale-while-revalidate
ETag vs Cache-Control
HTTP/3 and QUIC
Priority hints
Preload vs Prefetch vs Preconnect
CORS preflight
SameSite cookie modes
CSRF vs XSS mitigation
Content Security Policy (CSP)
Trusted Types
DOM clobbering
Prototype pollution
Race conditions in UI state
Tearing in concurrent UI
Scheduler priorities
Render waterfalls
Suspense boundaries
Selective hydration
Server components
Edge rendering
Micro-frontend orchestration
Finite state modeling
Event sourcing in frontend
Optimistic UI rollback strategy
Offline conflict resolution
CRDT basics for collaboration
WebRTC
Backpressure in streams API
AbortController
Streaming fetch response handling
Browser memory leak detection
Detached DOM nodes
Garbage collection timing
PerformanceObserver API
Long tasks API
First Input Delay (FID)
Interaction to Next Paint (INP)
Cumulative Layout Shift (CLS)
Largest Contentful Paint (LCP)
Speculative prerendering
Priority inversion in async code
Deterministic rendering
Idempotent UI actions
Accessibility tree
ARIA live regions internals
Pointer events
Boa referência sobre a diferença entre context engineering VS prompt engineering.
O termo é bem novo, mas eu acho que pega.
airops.com/blog/prompt-vs-co…
Qualquer um que te prometer indicar um caminho de sucesso em tech agora, seja por mentoria e afins, está prometendo algo que não vai conseguir cumprir.
O mercado está ainda em transição, ninguém sabe direito como tudo vai se comportar.
Engenheira Coelho retweeted
Replying to @EngineerRabbit
Um dos antídotos para ansioso, é pensar a longo prazo. A final de contas, a gente quer controlar tudo. Mas existe outro exercício também, que é ABRAÇAR O CAOS ! Tem um vídeo muito bom sobre isso do Ludo youtube.com/watch?v=45u2eqAB…
Sobre ansiedade
Impossível o cenário de mudança na área não gerar o mínimo se ansiedade. O que eu gosto de fazer quando algo me incomoda (e me ajuda muito) é pensar em planos de ação que eu teria caso surgisse um imprevisto.
Por exemplo, caso você perca seu emprego, o que você poderia fazer. Quanto tempo de reserva financeira possui. Quais os caminhos pra encontrar um novo emprego. Quanto tempo você iria esperar até iniciar a busca.
Na verdade, eu gosto de fazer isso pra assuntos diversos.
IA Não vai acabar com o papel de dev, mas vai ser transformar ele, e é importante pensar de forma pragmática quando a gente precisa de um emprego pra pagar as contas.
Tópicos que acredito que serão essenciais e estou investindo meu tempo de estudo:
- Negócios e ciclos de produção.
- Produto
- Arquitetura em geral
- Produto e estratégia
- testando projetos como o lovable e afins
Ele disse que vai acabar. Só não disse quando 💁🏻♀️














