Patyk (@Paty_Go) header
Patyk (@Paty_Go) profile picture
Joined August 2009
Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)Photo by Patyk (@Paty_Go)
Quem é programador precisa assistir isso aqui até o final. Na verdade qualquer pessoa que curta tecnologia. Esse vídeo tá viralizando absurdamente, nós só traduzimos.
106
787
80
5,312
235,816
It's been nearly 6 months since I posted a 'watch me work' deep dive on my skills. Since then, they've become the most-starred skills repo in the world. So, here's 70 minutes of me building a 21,000-line PR, especially focusing on: - DDD with /grill-with-docs - Improving your codebase with /retro - How to do human review effectively Enjoy!
115
311
36
5,021
333,132
Which Claude model should you build with? Our new guide breaks down when to use Fable 5.2, Opus 5.5, Sonnet or Haiku. It also covers when to adjust effort instead of switching models, and how to save cost by putting subagents on smaller models. claude.dev/blog/which-claude…
372
1,222
305
16,209
2,606,532
PARE DE PERGUNTAR AO SEU FILHO "COMO FOI A ESCOLA." Ele vai dizer "foi legal" toda vez. Uma psicóloga infantil me disse pra trocar por uma dessas 4 perguntas:
34
261
14
1,967
1,763,921
Patyk retweeted
THIS IS ACTUAL F*CKING GOLD Anthropic just shared one of the best tricks for Claude Code. The idea: run Sonnet, Haiku and Opus 5.5 together, each one doing only the job it's best at. Opus-level judgment on every big call, without paying Opus rates for every routine turn. You just launch Claude Code like this: claude --model sonnet --advisor opus here's the split: → Sonnet 5.5 runs the session and writes the code → Haiku 5.5 explores files and docs in parallel → Opus 5.5 stays on call as advisor for the big calls → you stop spending Opus on work that doesn't need it Opus only steps in at three moments: → before a plan locks → when the same error shows up twice → before calling it done Sonnet builds. Haiku explores. Opus reviews. JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split the full tree > Sonnet 5.5 runs the main session and edits code > search maps the repo on Haiku 5.5 > grep finds call sites on Haiku 5.5 > docs pulls the API reference on Haiku 5.5 > Opus 5.5 on call as advisor, reads the whole transcript when consulted > JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Run the main session on Sonnet 5.5 with Opus 5.5 as advisor. 2. Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference). 3. Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error twice, and before calling a task done. 4. Route fast deterministic forks (tool choice, path selection, retries) through JEV. Show me every change as a diff first. No edits until I say go." ↳ code.claude.com/docs/en/advi… save it, you'll use this every single day.
stop using grok bot like a chatbot the people getting crazy results don't have one smart bot. they have a f*cking org chart. how to build your first agent team from scratch: → chief of staff → specialists → skills + routines save this ↓
36
110
7
1,303
195,601
Patyk retweeted
Glm legal trabalhando..
See GLM-Legal in action
1
2
7
1,032
Patyk retweeted
UN INGENIERO DE ANTHROPIC ACABA DE SOLTAR EL MEJOR TRUCO PARA OPUS 5.5 Abre Claude Code y escribe: /claude-api prompt-audit → Audita tus skills, CLAUDE.md y prompts → Borra todo lo que frena al modelo → Lo reescribe con la guía oficial de Opus 5.5 Tus prompts están escritos para modelos viejos. Esto lo arregla en 5 minutos. Guárdalo. Por: @RLanceMartin
58
539
30
4,728
872,753
Meu sistema de skills tá mais robusto do que nunca, e atingiu um estágio onde eu não preciso mais saber o que tem nele. Antes, eu precisava saber alguns comandos, algumas skills e referenciar quando queria. Agora, meu claude code descobre tudo sozinho, on demand, sem encher o contexto de lixo e instrução desnecessária.
4
8
144
11,553
👨🏻 Candidato: "¿Cuánto se le pagó a la persona anterior por este mismo rol?" 👩🏽‍🦱 RRHH: "120,000, pero estuvieron aquí por un tiempo considerable" 👨🏻 Candidato: "Pero el alcance del trabajo, los KPIs y la carga laboral siguen siendo los mismos, ¿verdad?" 👩🏽‍🦱 RRHH: "Sí, eso es correcto" 👨🏻 Candidato: "Entonces, ¿por qué el valor de un nuevo contratado es de repente menor, cuando la empresa espera los mismos resultados?" 👩🏽‍🦱😢 RRHH: .......... A veces, no es que no estés calificado, solo no negociaste con confianza. Conoce tu valor antes de decir "sí".
23
15
1
698
509,175
Vivemos numa cultura que diz “seja você mesmo” como slogan, mas pune quem realmente faz isso.
7
Make the AI do the work, so you do the intelligence!
5
Patyk retweeted
draw.io diagrams now stream into Claude as they're generated. Shape by shape, edge by edge. github.com/jgraph/drawio-mcp…
87
664
189
5,815
1,611,138
Fiquei sabendo hj só Mas tem novo OWASP Top 10 no forno hein #bolhasec
5
22
175
4,811
Nossa espécie é muito violenta, será que somos bons vizinhos interestelares?
13
A IA é boa pra quem já é bom.
30
46
7
624
22,715
Patyk retweeted
Dica pra vc que lança SAAS disruptivos e não sabe o que caralhos está fazendo eai dois segundos depois vazam todos seus dados e vc acha que tem razão em alguma coisa mas não tem. - Peça a IA pra validar se as rotas estão bloqueadas/privadas - Peça a IA pra validar se você sanitiza dados sensiveis dos retornos de API - Peça a IA pra evitar IDs incrementais com dados sensveis - Peça pra IA criptografar dados sensiveis e pra usar algum algoritmo de mercado (não vale salvar em base64 e falar que ta criptografado) - Coloque um caralho de um Shield no seu servidor - Use CORS restritivo e Headers de Segurança, use Helmet se for Node - Evite logs no front end
30
54
8
1,122
57,874
Usar dinheiro é uma forma de escravidão.
9
There are two core pillars in software work: thinking and mechanics. Spec, design, architecture, trade-offs, decisions... that’s the real job. Coding was always the mechanical part. We just used to do it by hand because we had no other option.
24
Você não sabe fazer boas perguntas.
6