@beebeezipi
iAccount based inBrazil
About this account
- Account based in
- Brazil
- Connected via
- Brazil App Store
Account-level information from X, not a live location or the device used for a specific post.
Carioca e Desenvolvedor.
Rio de Janeiro, Brasil
Joined August 2010
- Tweets1.6K
- Following2.2K
- Followers77
- Likes8.1K
A AWS liberou 50% de desconto na primeira tentativa para as seguintes certificaƧƵes + 2a tentativa GRATUITA
- Claude/AI Practicioner
- Solutions Architect Associate
- Generative AI Developer Professional
- Data Engineer Associate
- CloudOps Engineer Associate
- Security Speciality
CUPOM: PersonRetake2026 (aplica no checkout do exame no site da AWS, só começa a funcionar amanhã, dia 29)
A primeira tentativa precisa ser do dia 19/9 até 17/11 e o retake grÔtis de 4/1 até 17/11/27 (não vale para todas)
pearsonvue.com/us/en/test-taā¦
beeš retweeted
We have posted the YouTube playlist for "Architecture 1901: From Zero to QEMU" by Antonio Nappa @jeppojeps of Fuzz Society @fuzzsociety_org. Now anyone wishing to download the videos for offline viewing can find all their URLs here:
youtube.com/playlist?list=PLā¦
But as always the best experience is at the full class at ost2.fyi/Arch1901.
beeš retweeted
As an AI Engineer. Please learn:
> Harness engineering, not just prompt engineering
> Context engineering, not just long prompts
> Prompt caching vs. semantic caching tradeoffs
> KV cache management, eviction, reuse, and memory pressure at scale
> Prefill vs. decode latency and why they optimize differently
> Continuous batching, paged attention, and throughput optimization
> Speculative decoding vs. quantization vs. distillation tradeoffs
> INT8, INT4, FP8, AWQ, GPTQ, and when quantization hurts quality
> Structured output failures, schema validation, repair loops, and fallback chains
> Function calling reliability, tool contracts, argument validation, and idempotency
> Agent guardrails, loop budgets, tool budgets, and termination conditions
> Model routing, graceful fallback logic, and degraded-mode UX
> RAG architecture: chunking, embeddings, hybrid search, reranking, and freshness
> Retrieval evals: recall, precision, grounding, attribution, and citation quality
> Evals: golden sets, regression tests, adversarial tests, LLM-as-judge, and human evals
> LLM observability as a first-class discipline: traces, spans, tokens, latency, errors, and drift
> Cost attribution per feature, workflow, tenant, and user journey, not just per model
> Safety engineering: prompt injection defense, data leakage prevention, and permission boundaries
> Multi-tenant isolation, cache safety, and cross-user context contamination prevention
> Fine-tuning vs. in-context learning vs. RAG vs. distillation, and when each is the wrong tool
> Latency, quality, cost, and reliability tradeoffs across the full inference stack
> Production failure modes: hallucinated tool calls, malformed JSON, stale retrieval, runaway agents, and silent eval regressions
> Shipping LLM systems as reliable infrastructure, not demos wrapped around prompts
aiengineeringfromscratch.comā¦
beeš retweeted
Your agent can trade. Your agent can pay.
But who is your agent?
Join us tomorrow, Sept 18 at 3pm ET for a Space on AiFi: Agentic Identity.
w/ @World_ID, @browserbase, @marco_derossi, @programmer & @Coinbase
Set a reminder ā
nitter.cf/i/spaces/1XxygwOZELdGM
Testing Agentic AI + Onchain Infrastructure on an IoT Edge device (2019 Jetson Nano).
Testing completeness, frequency & consistency as primitives for measuring trust in autonomous AI agents.
#AgenticAI #OnchainAI #EdgeAI #Blockchain #DeAI
beeš retweeted
No funding? You can apply.
No revenue? You can apply.
Still building the product? You can apply.
@16vchq is looking for pre-seed and seed founders with deep insight, speed, conviction, and the ambition to build something significant.
$200K SAFE. No program fee.
tiny.cc/16vcapply
beeš retweeted
Download 698-page PDF >> Everything You Always Wanted To Know About Mathematics*
(*But didnāt even know to ask)
A Guided Journey Into the World of Abstract Mathematics and the Writing of Proofs ā”ļø math.cmu.edu/~jmackey/151_12ā¦
beeš retweeted
Principles of Deep Learning TheoryāTheoretical & Mathematical Foundations
[471-page PDF Draft] arxiv.org/abs/2106.10165
-or-
Buy new edition: amzn.to/3qoqmS5
An absolutely brilliant textbook "Foundations of Large Language Models" by Tong Xiao and Jingbo Zhu (2025) is now in @ChapterPal's collection.
This book is a comprehensive, technically grounded treatment of modern generative language models for artificial intelligence researchers, engineers, and advanced students in natural language processing.
Assuming a foundational background in deep learning, probability, and standard neural sequence modeling, the book explains the entire lifecycle of foundation modelsāfrom raw data pre-training and architectural design to alignment, inference acceleration, and system-level scaling.
It's a great in-depth read specifically on Large LMs after my The Hundred-Page Language Models Book that covers neural network and deep learning basics, count-based LMs, RNNs, and transformers.
Read the book with an AI tutor: chapterpal.com/ebook/14fa054ā¦
(All books on ChapterPal are free to read with a free account.)
The book has 76 beautiful illustrations across 277 pages.
Table of contents:
Preface
Notation
1. Pre-training
- 1.1. Pre-training NLP Models
* 1.1.1 Unsupervised, Supervised and Self-supervised Pre-training
* 1.1.2 Adapting Pre-trained Models
- 1.2. Self-supervised Pre-training Tasks
* 1.2.1 Decoder-only Pre-training
* 1.2.2 Encoder-only Pre-training
* 1.2.3 Encoder-Decoder Pre-training
* 1.2.4 Comparison of Pre-training Tasks
- 1.3. Example: BERT
* 1.3.1 The Standard Model
* 1.3.2 More Training and Larger Models
* 1.3.3 More Efficient Models
* 1.3.4 Multi-lingual Models
- 1.4. Applying BERT Models
- 1.5. Summary
- References
2. Generative Models
- 2.1. A Brief Introduction to LLMs
* 2.1.1 Decoder-only Transformers
* 2.1.2 Training LLMs
* 2.1.3 Fine-tuning LLMs
* 2.1.4 Aligning LLMs with the World
* 2.1.5 Prompting LLMs
- 2.2. Training at Scale
* 2.2.1 Data Preparation
* 2.2.2 Model Modifications
* 2.2.3 Distributed Training
* 2.2.4 Scaling Laws
- 2.3. Long Sequence Modeling
* 2.3.1 Optimization from HPC Perspectives
* 2.3.2 Efficient Architectures
* 2.3.3 Cache and Memory
* 2.3.4 Sharing across Heads and Layers
* 2.3.5 Position Extrapolation and Interpolation
* 2.3.6 Remarks
- 2.4. Summary
- References
3. Prompting
- 3.1. General Prompt Design
* 3.1.1 Basics
* 3.1.2 In-context Learning
* 3.1.3 Prompt Engineering Strategies
* 3.1.4 More Examples
- 3.2. Advanced Prompting Methods
* 3.2.1 Chain of Thought
* 3.2.2 Problem Decomposition
* 3.2.3 Self-refinement
* 3.2.4 Ensembling
* 3.2.5 RAG and Tool Use
- 3.3. Learning to Prompt
* 3.3.1 Prompt Optimization
* 3.3.2 Soft Prompts
* 3.3.3 Prompt Length Reduction
- 3.4. Summary
- References
4. Alignment
- 4.1. An Overview of LLM Alignment
- 4.2. Instruction Alignment
* 4.2.1 Supervised Fine-tuning
* 4.2.2 Fine-tuning Data Acquisition
* 4.2.3 Fine-tuning with Less Data
* 4.2.4 Instruction Generalization
* 4.2.5 Using Weak Models to Improve Strong Models
- 4.3. Human Preference Alignment: RLHF
* 4.3.1 Basics of Reinforcement Learning
* 4.3.2 Training Reward Models
* 4.3.3 Training LLMs
- 4.4. Improved Human Preference Alignment
* 4.4.1 Better Reward Modeling
* 4.4.2 Direct Preference Optimization
* 4.4.3 Automatic Preference Data Generation
* 4.4.4 Step-by-step Alignment
* 4.4.5 Inference-time Alignment
- 4.5. Summary
- References
5. Inference
- 5.1. Prefilling and Decoding
* 5.1.1 Preliminaries
* 5.1.2 A Two-phase Framework
* 5.1.3 Decoding Algorithms
* 5.1.4 Evaluation Metrics for LLM Inference
- 5.2. Efficient Inference Techniques
* 5.2.1 More Caching
* 5.2.2 Batching
* 5.2.3 Parallelization
* 5.2.4 Remarks
- 5.3. Inference-time Scaling
* 5.3.1 Context Scaling
* 5.3.2 Search Scaling
* 5.3.3 Output Ensembling
* 5.3.4 Generating and Verifying Thinking Paths
- 5.4. Summary
- Appendix
- References
beeš retweeted
I am absolutely loving this book.
Everyone has struggled to understand tensor calculus (I mean the real "tensors" with Christoffel symbols, metric etc).
Most textbooks just puts out magical definitions for you to memorize without providing any insights or giving you any explanations of where things came from.
On the other hand, pop-sci/pop-math books just tells you how amazing things are but without any details on what exactly those things are.
The gap is so serious that it has haunted me for decades and I have started to take things in my own hand (I mean put it in AI's hand). š§µ
beeš retweeted
AI Agents and Applications: amzn.to/4gH98Y7
[448 pages. From @ManningBooks]
beeš retweeted
As an AI Engineer, you must learn following application layer things as stated by Ankit, inorder to actually be called as AI Engineer.
1) Infrastructure: LLM optimization in terms of latency and cost. Quantization, Flash attention, paged attention, continuous batching, prompt catching, all of these things you need to learn in order to be a great AI Engineer.
2) Finetuning of open source model with Qlora and RLHF.
3) MLOPS: Model Versioning, Model rollback, model deployment, shadow deployment, GPU utilisation, load balancing, logging.
4) Cloud Infrastructure: You don't need to learn 200 services of AWS. Just learn regular 8-10 services which any AI Engineer regularly uses. Learn on the fly by building one solid project.
If you have any query, leave down the comments.
DM for 1:1 paid consultation regarding your career.
beeš retweeted
šµAI Agents in Action: amzn.to/3RiYRqX v/ @ManningBooks
š”New! Updated! 2nd Edition!
š¢ Table of Contents:
Chapters:
1. The rise of AI agents
2. Core components: Large language models, prompting, and agents
3. Actions with Model Context Protocol for AI agents
4. Architecting and building multi-agent systems
5. Agent reasoning and planning
6. Working with memory & knowledge RAG for agents
7. Building robust agents with evaluation and feedback
8. Deploying agents and agentic systems
9. Understanding the agentic loop
10. Exploring the cognitive agent that thinks, monitors, and adapts
11. Tips for building agentic systems
Appendices
A. Setting up the sample code repository
B. Node.js setup for local MCP servers
beeš retweeted
It's possible that a killer app of adversarial governance mechanism design theory will end up being AI safety.
Compare:
vitalik.eth.limo/general/202ā¦
aiprospects.substack.com/p/pā¦
There's a deep duality between the two environments. Both are about a less-sophisticated principal trying to get ideal outcomes from a set of more-sophisticated agents: in the first case, the principal is a static algorithm and the agents are humans, in the second case, the principal is humans plus weaker LLMs and the agents are stronger LLMs.
A key finding was that you can achieve much better outcomes if you can guarantee limits to how much agents can collude (see: Nash equilibria being abundant, vs. cooperative-game-theory "cores" often being empty). That argument should naturally transfer to this new setting.
beeš retweeted
A lot of important progress on Frames (EIP-8141) has been quietly happening over the last few months. Highly recommend reading this, also the updated EIP eips.ethereum.org/EIPS/eip-8ā¦
firefly.social/post/x/209626ā¦
beeš retweeted
If you can build these 12 Agentic AI Engineer projects.
You're hired.
Project 1: Autonomous Ticket Resolution Engine
Agent that reads the ticket, queries the database, applies the fix, and asks a human before anything destructive.
⣠Shows: You build agents that resolve not just reply
Project 2: Deep Research Agent with Citation Graph
Multi-hop research, source grading, contradiction detection, fully cited final report.
⣠Shows: You can orchestrate long-horizon reasoning safely
Project 3: Self-Healing Data Pipeline Agent
Detects schema drift in ETL jobs, drafts transformation fixes, re-runs with rollback.
⣠Shows: You trust agents with production data, carefully
Project 4: CI Triage Agent
Reads failing pipeline logs, reproduces the error, opens a fix PR with tests, waits for approval.
⣠Shows: You can embed agents into engineering workflows
Project 5: Multi-Agent Code Review Desk
Reviewer + security scanner + test writer agents with consensus and conflict resolution.
⣠Shows: You orchestrate teams of agents not toys
Project 6: Computer-Use Back-Office Agent
Browser automation for legacy portals: forms, uploads, extraction, human takeover on CAPTCHA.
⣠Shows: You ship agents in the messy real world
Project 7: Invoice Processing Agent with 3-Way Match
Reads invoices, matches POs and deliveries, flags exceptions, posts to ERP via MCP.
⣠Shows: You automate expensive enterprise workflows
Project 8: Incident Response Agent
Correlates alerts, traces, and logs; drafts the post-mortem; suggests the rollback command.
⣠Shows: You make on-call humans faster not obsolete
Project 9: Real-Time Voice Ops Agent
Sub-second voice with tool calling, interruption handling, escalation paths.
⣠Shows: You can build multimodal agents that feel human
Project 10: Adaptive Tutor Agent with Mastery Memory
Spaced repetition, difficulty routing, long-term memory of learner state.
⣠Shows: You use memory systems that personalize over time
Project 11: Agentic Sales Ops Assistant
Enriches leads, drafts personalized outreach, syncs CRM, tracks replies, updates forecasts.
⣠Shows: You connect agents to revenue not just demos
Project 12: Agent Eval and Regression Platform
Golden trajectories, CI gates that block bad prompts, quality dashboards.
⣠Shows: You ship agents like production software
Most people stay stuck watching tutorials. Builders get hired.
Bookmark & Repost !!!
Which project are you building first?
If I had 6 months to become an Agentic AI Engineer.
I'd do this.
Stage 1: Python and LLM Foundations
Python, async, API design, Anthropic/OpenAI SDKs, tokens, embeddings, structured outputs.
Stage 2: Context Engineering
System prompts, few-shot patterns, chain-of-thought, context budgets, dynamic context assembly.
Stage 3: Tool Calling and Function Schemas
JSON schemas, Pydantic validation, retry logic, dynamic tool discovery, error recovery.
Stage 4: Agent Loop Patterns
ReAct, plan-and-execute, reflection, self-correction, max iteration limits.
Stage 5: One Agent Framework, Deeply
LangGraph state machines, nodes and edges, CrewAI roles, OpenAI Agents SDK handoffs.
Stage 6: Memory Systems
Short-term buffers, long-term vector recall, episodic summaries, context compression.
Stage 7: Agentic RAG
Hybrid search, reranking, parent document retrieval, query rewriting, citation tracking.
Stage 8: MCP and Integrations
MCP servers and clients, tool standardization, API connectors, webhooks, auth.
Stage 9: Multi-Agent Orchestration
Supervisor patterns, typed state handoffs, consensus logic, human-in-the-loop, escalation.
Stage 10: Evals and Observability
Golden datasets, trajectory evals, LLM-as-a-judge, LangSmith/Langfuse tracing, regression gates.
Stage 11: Production Deployment
Docker, CI/CD, guardrails, cost tracking, fallback chains, checkpoint and resume.
Stage 12: Public Portfolio
Ship 3 agents, publish architecture writeups, share benchmarks, record live demos.
Most people stay stuck watching tutorials.
Builders get hired.
(Bookmark & Repost !!!)
beeš retweeted
The Art of Mathematics" by BƩla BollobƔs
A very interesting collection of problems.
Volume 1: cambridge.org/core/books/artā¦
Volume 2: cambridge.org/core/books/artā¦
beeš retweeted
As a backend dev in 2026 , learn these 11 skills to keep yourself relevant in this Job market :
1. API Design - REST/GraphQL/gRPC
2. Authentication & Authorization - OAuth2, JWT, OpenID Connect, Passkeys
3. Databases - SQL, NoSQL, sharding, indexing, query tuning
4. Caching - Redis, CDN, edge caching strategies
5. Event-Driven Systems - Kafka, Pulsar, streaming pipelines
6. Concurrency & Async - reactive programming, structured concurrency
7. Distributed Systems - microservices, service mesh, eventual consistency
8. Security - HTTPS, encryption, zero trust, OWASP top 10
9. Observability - logging, tracing, metrics, OpenTelemetry
10. Cloud & Deployment - Docker, Kubernetes, serverless, GitOps
11. AI Integration - LLM APIs, vector databases, retrieval-augmented systems