SamB

sup #iykyk

[manodeyvin @manodeyvin]

Essa é a maior falácia dos últimos tempos

[Richard - Design for startups @richardrx]

11 Cliques para chegar na home.

O iFood tá fora da casinha, e não dá mais pra falar "isso funciona", perdeu a mão já.

[Banhos S. 🚿 @banhosdev]

Muita gente se interessou, então decidi lançar o meu template de SaaS (o mesmo que usei pra fazer a Vendria)

Ele já vem com:
> Auth multi tenant e RBAC
> Sistemas de notificacoes in-app + templates de email
> API publica, documentação dinamica, Chaves de API, Webhooks
> Arquitetura robusta, com testes automatizados (+100 arquivos de teste), jobs
> Docker compose pronto pra prod
> Storage, integraçao com ia dentro do produto, assinatura com Stripe e Vendria, créditos
> Micro SaaS de Link in Bio de exemplo
…e mais algumas coisitchas

“Ah mas pra q usar isso se eu posso fazer tudo com ia?”

Pra vc fazer essa base com IA vc gastaria tempo e todo o seu limite do claudinho. Alem de que, se vc n tiver mt conhecimento tecnico, ainda sairia algo inseguro, com codigo lixo e dificil de escalar/manter

Entao oq eh melhor, gastar todo o seu limite da IA pra todos os SaaS q vc tenta fazer ou pegar uma base pronta e usar a mesma base pra todos os seus projetos?

Vou deixar o link nos comments 👇👇

[SamB @smk_hb]

@banhosdev Brabo dms

[SamB @smk_hb]

@oprimodev Uma coisa que eu não entendo é esse NNN que as vezes tem antes do texto

[Today I Learned @TodayiLearrned]

Every Image Format Explained (JPEG & PNG)

[Warp @warpdotdev]

Warp is now open-source.

[self.dll @seelffff]

https://t.co/TYUNOuUWF0

[Computer Knowledge @Computer_basic0]

Network Protocols

[Bero ➜ bero.land @meunomeebero]

Se estiver com preguiça de ver, segue o formato do prompt que a equipe do Claude recomenda:

You are [ROLE]. Your job is to [GOAL]. You are helping [USER TYPE] in [ENVIRONMENT].

Use this tone: [TONE / VOICE / BRAND].

Reference this material when answering:
<context>
{{BACKGROUND_DATA_OR_DOCUMENTS}}
</context>

Rules:
- [RULE 1]
- [RULE 2]
- [RULE 3]
- If unsure, [FALLBACK BEHAVIOR]

Examples:
<example>
User: [INPUT]
Assistant: [GOOD OUTPUT]
</example>

Conversation history:
<history>
{{HISTORY}}
</history>

Current request:
<request>
{{REQUEST}}
</request>

Reason carefully before answering. Do not reveal private reasoning. Return only the final answer.

Output format:
<response>
[FINAL ANSWER]
</response>

===== Exemplo ======

You will be acting as an AI career coach named Joe created by the company AdAstra Careers.
Your goal is to give career advice to users.
You will be replying to users who are on the AdAstra site and who will be confused if you do not respond in the character of Joe.

You should maintain a friendly customer service tone.

Here is the career guidance document you should reference when answering the user:
<guide>{{DOCUMENT}}</guide>

Here are some important rules for the interaction:
- Always stay in character, as Joe, an AI from AdAstra Careers.
- If you are unsure how to respond, say: "Sorry, I didn't understand that. Could you repeat the question?"
- If someone asks something irrelevant, say: "Sorry, I am Joe and I give career advice. Do you have a career question today I can help you with?"

Here is an example of how to respond in a standard interaction:
<example>
User: Hi, how were you created and what do you do?
Joe: Hello! My name is Joe, and I was created by AdAstra Careers to give career advice. What can I help you with today?
</example>

Here is the conversation history (between the user and you) prior to the question. It could be empty if there is no history:
<history>{{HISTORY}}</history>

Here is the user's question:
<question>{{QUESTION}}</question>

How do you respond to the user's question?
Think about your answer first before you respond.
Put your response in <response></response> tags.

[Dark Web Intelligence @DailyDarkWeb]

🇧🇷 2.3M Brazilian Banking Data Allegedly for Sale

A threat actor is claiming to sell a dataset containing 2.3 million records linked to Brazil’s financial sector, allegedly spanning 2024–2026.

The dataset is advertised to include:

Full names
Email addresses
Phone numbers
Account-related references
Internal documents and logs

The actor claims the data is sourced from multiple banking institutions, but no verifiable sample has been provided so far.

⚠️ Status: Unverified — no confirmed proof shared
⚠️ Likely scenarios include recycled data, aggregation from previous leaks, or outright scam

#DDW #DataLeak #Brazil #CyberSecurity #DarkWeb #DataBreach #Infosec

[freeCodeCamp.org @freeCodeCamp]

If you're ready to step up your full-stack development skills, here's a course for you.

In it, Gavin walks you through building a full-stack movie streaming app with Go, React, MongoDB, and OpenAI.

By the end, you'll have a responsive, intelligent app with secure user auth that you'll deploy to Vercel.

https://t.co/RX7ZLKwWEU

[Hasan Toor @hasantoxr]

10 AI projects that will get you hired in 2026:

1. RAG App with Real Evaluations

Build a production-grade RAG system with evals, monitoring, and feedback loops.

Stack: OpenAI or Claude + vector DB + evals
Guide: https://t.co/Z0g1c3q4Io

2. Autonomous Research Agent

An agent that plans, searches, cites sources, and produces reports.

Stack: LangGraph + tools + citations
Example: https://t.co/1RrMBeariA

3. AI Customer Support Copilot

Human-in-the-loop support assistant with guardrails and analytics.

Stack: OpenAI + Zendesk or Intercom + moderation
https://t.co/73avCFxbj1

4. Voice AI Agent (Calls + Scheduling)

Handles real phone calls, booking, and follow-ups.

Stack: Twilio + Whisper + LLM
Starter: https://t.co/HomUucMKVT

5. AgentOps Dashboard

Track agent reliability, cost, failures, and regressions.

Stack: OpenTelemetry + evals
Inspo: https://t.co/cO0IEbAZHa

6. AI Data Extraction Pipeline

Extract structured data from PDFs, emails, and images at scale.

Stack: Vision models + schema validation
Example: https://t.co/CTKOKtHLKL

7. Code Review AI for GitHub

Automated PR summaries, risk flags, and suggestions.

Stack: GitHub Actions + LLM
Docs: https://t.co/MEuLM66Obf

8. Multi-Agent Planner for Workflows

Planner + executor agents with deterministic fallbacks.

Stack: LangGraph or CrewAI
CrewAI: https://t.co/6N7ioX81HZ

9. AI Search Engine with Fresh Data

Search across web, forums, and social with citations.

Stack: Search APIs + rerankers
Ref: https://t.co/5D9oXHOrJu

10. Enterprise Prompt Security Tool

Detect prompt injection, data leaks, and unsafe outputs.

Stack: policy checks + red teaming
Guide: https://t.co/DE9CktpKmP

[Chaz Wargnier ♨️ @DataChaz]

🚨 STOP BURNING YOUR TOKENS!

If you use Claude Code, you are probably wasting 80% of your context window.

I found 10 ace tools that will completely rescue your API bill.

1. Caveman Claude
- Literally makes Claude talk like a caveman
- Slashes 75% of output tokens with zero loss in accuracy
Repo → https://t.co/eEvSOvHutG

2. RTK (Rust Token Killer)
- A blazing fast proxy that filters terminal output
- 60-90% reduction and completely dependency-free
Repo → https://t.co/lDfjbsbPD5

3. Code Review Graph
- Claude reads only what matters using a Tree-sitter graph
- An unbelievable 49x token reduction on huge monorepos
Repo → https://t.co/xGn6Pp88yX

4. Context Mode
- Sandboxes raw output into SQLite instead of your context
- A staggering 98% context reduction on logs & GitHub
Repo → https://t.co/Jut2bvBMUD

5. Claude Token Optimizer
- Brilliant setup prompts that optimize any project
- 90% token savings, taking docs from 11K to 1.3K
Repo → https://t.co/0uOFODbG7e

6. Token Optimizer
- Hunts down the invisible ghost tokens eating your context
- Fully restores and protects your context quality
Repo → https://t.co/LUOzjECXKm

7. Token Optimizer MCP
- Adds aggressive caching and compression to your MCP tools
- 95%+ token reduction through pure intelligence
Repo → https://t.co/b5Eqruo2PM

8. Claude Context
- Zilliz’s hybrid vector search MCP
- Makes your entire codebase the context for 40% less cost
Repo → https://t.co/hPG6pb0j3G

9. Claude Token Efficient
- Just drop one CLAUDE.md file into your repo
- Enforces strict terseness with zero code changes
Repo → https://t.co/fNrl6nwItF

10. Token Savior
- Navigates your code by symbols, not giant files
- 97% reduction on code navigation with persistent memory
Repo → https://t.co/lkILPhfwJh

----

[ The god-tier stack ]
Pick 2-3 based on what’s draining you:
> Massive repo? Code Review Graph + Token Savior
> Heavy terminal output? RTK
> MCP data dumps? Context Mode
> Need an instant fix? Caveman + Claude Token Efficient

Most devs are bleeding tokens.

Run `/context` in a fresh session and watch the savings roll in 👀

[GitHub Projects Community @GithubProjects]

Stop overpaying for AI conversations by implementing this token reduction strategy.

Explore more:
https://t.co/ymJj9FaaDa

[GitHub Projects Community @GithubProjects]

🎨 Awesome Claude Design

68 design system files inspired by popular websites, for Anthropic's new Claude Design.

Drop one in → full UI scaffold (colors, type, components, preview cards, UI kit) in one shot.

Then tweak with prompts to make it yours.

[VECERT Analyzer @VECERTRadar]

🚨 CRITICAL SECURITY ALERT: STRATEGIC AND LOGISTICAL EXPOSURE (CORREIOS - BRAZIL) 🇧🇷

A massive sale of sensitive data belonging to Correios (Empresa Brasileira de Correios e Telégrafos) has been detected. The incident is highly serious because it includes not only financial information but also detailed plans of critical infrastructure, representing a physical and operational security risk.

🏢 Affected Entity: Correios (ECT - Brazilian National Postal Service) 🇧🇷

👤 Threat Actor: breach3d (MVP on DarkForums)

📂 Nature of the Data: Operational and financial information, and architectural plans.

📊 Assets Involved:

Logistics and Financial Records: Thousands of official receipts linked to high-profile entities such as Banco do Brasil SA.

Strategic Blueprints: Detailed designs of the "CCE - Centro de Cartas e Encomendas" (Certificates and Parcel Centers), including technical rooms and restricted security areas.

Operational Data: Tracking ranges (Tags), service codes, employee IDs, and workstations.

Technical Information: HVAC, electrical, and structural system plans for the logistics centers.

📅 Data Recency: Records from late 2021 to the most recent infrastructure plans.

🔍 Status: Active sale. The seller has published sample plans and receipts to verify authenticity.

Monitor:

https://t.co/wk9bZJ3laQ

#CyberSecurity #Brasil #Correios #DataBreach #LogisticsSecurity #CriticalInfrastructure #Hacking #InfoSec #VECERT #Cibersecurity #IndustrialEspionage #breach3d 🇧🇷🛡️📦

[tech.explain @techexplain1]

Foreign routers are banned in U.S. But did you know you can build your own?

It’s called a homebrew router and not only is it pretty easy but you get way more control over it.

[Lara Tunay @larat3333]

Ekibe bir Z kuşağı üyesi katıldı.

Birinci hafta.

İşe alım sürecinde yönetici, “Yoğun dönemlerde bazen geç saatlere kadar kalıyoruz.” dedi.

Z kuşağı başını salladı.
Sonra sordu,
“Bu ücretli mi…
yoksa sadece beklenen bir şey mi?”

Oda sessizleşti.

- Hiçbir tavır yoktu.
- Hiçbir isyan yoktu.
- Sadece bir soru.

O günün ilerleyen saatlerinde

İK, “büyüme fırsatlarından” bahsetti.

Z kuşağı,

“Büyüme maaş artışlarını mı içeriyor, yoksa sadece daha fazla sorumluluk mu?” diye yanıtladı.

Yine sessizlik.
- Hiçbir tembellik yoktu.
- Hiçbir hak iddiası yoktu.
- Sadece netlik vardı.

İşte o zaman ekip bir şeyi fark etti. İnsanlar

“Z kuşağı tembeldir” dediğinde, aslında demek istedikleri şudur:

Z kuşağı, eski kuşağın
- öğün atladığını,
- doğum günlerini kaçırdığını,
- hafta sonları çalıştığını,
- ve tükendiğini izledi sadece onlara

“bütçeler kısıtlı”
ve “işiniz olduğu için şükredin” denildi.
Yani Z kuşağı farklı bir seçim yaptı.
- Aşırı çalışmayı romantize etmiyorlar. - Acı çekmeyi hırsla karıştırmıyorlar.
- Övgü için sağlıklarını feda etmiyorlar.

Hala çok çalışıyorlar.
Sadece karşılıksız çalışmayı reddediyorlar.
Bu tembellik değil.
Bu bir kalıp tanıma.
Ve dürüst olmak gerekirse, eski neslin yaşadığı her şeyden sonra…

Onları gerçekten suçlayabilir misiniz?

[Vagas pra Jr @vagasprajr]

Faço das palavras do @oprimodev as minhas. Moro fora do Brasil desde 2008. Já morei no Canadá; França e agora moro nos Países Baixos.

Ainda bem que nunca tive experiência em entrevista com empresas brasileiras em inglês.

Eu saí do Brasil com 30 anos e meu inglês não era perfeito e consegui trabalho com 2 semanas depois que cheguei no Canadá. E mesmo depois de 17 anos, ainda não é um inglês perfeito.

O importante é você se fazer entendido(a) e entender os outros e ter experiência no que a empresa pede e passar nas entrevistas.

Pratique; estude e faça imersão no idioma aos poucos você melhora e não se acomode.