Edwar Duque

Simplemente Futbol Simply Football / Soccer
La vida es un constante ciclo de aprendizaje / Life is a constant cycle of learning

[Alan Daitch @AlanDaitch]

Señoras y señores: acá tenemos la causa de que tengamos que sufrir hasta el final del partido

[Miguel Ángel Durán @midudev]

¡Nuevo curso oficial gratuito de Claude Code!

✓ CLAUDE.md y Plan Mode
✓ Agent Teams + Subagentes
✓ Skills, MCP, Permisos, Hooks...

2 horas de contenido con subtítulos:
https://t.co/CmO0MvcCeT

[Edwar Duque @eltipinho]

@JobFound5 Interested

[Edwar Duque @eltipinho]

@JobFound5 Interested

[Miguel Ángel Durán @midudev]

Guía visual para aprender ALGORITMOS en programación.
+25 algoritmos explicados paso a paso con pseudo código.
→ visualgo․net

[Edwar Duque @eltipinho]

@JobFound5 Interested

[Edwar Duque @eltipinho]

@JobFound5 Interested

[Edwar Duque @eltipinho]

@JobFound5 Interested

[Miguel Ángel Durán @midudev]

Aprende Patrones de Diseño con ejemplos reales en:
TypeScript, Java, C#, PHP, Python, Rust.
Guías gratuitas y en español:
→ https://t.co/9AdUL2IXSl

[Carlos E. Perez @IntuitMachine]

There will be more jobs in AI that we have yet to imagine!

[Alex Xu @alexxubyte]

AI Vs Machine Learning Vs Deep Learning Vs Generative AI clearly Explained:

[Reza Dorrani @rezadorrani]

⭐ Agent Flows in Copilot Studio | Complete Tutorial

Learn how to build your first Agent flow — including AI actions, Advanced Approvals, and how to trigger flows to create truly autonomous agents.

📽️ Watch here: https://t.co/COw3XCyB5J

#CopilotStudio #Microsoft #AgentFlows

[Python Developer @PythonDvz]

Confused between Data Analyst, Data Engineer, Data Scientist, or ML Engineer?

Here’s a quick breakdown of the key skills each role demands!

Whether you’re a storyteller with numbers or a backend tech builder, there’s a space for you in the data world.
Find your strength, build on your gap, and OWN your data journey.
Because in tech, there’s no one-size-fits-all—only growth paths.

[Miguel Ángel Durán @midudev]

GitHub anuncia un bootcamp para dominar Copilot.
En Español, 2 días de talleres sin coste:
→ https://t.co/pMK1trl7UB

[Brais Moure @MoureDev]

Microsoft ha lanzado un curso para empezar a crear tus propios Agentes con IA

→ 11 lecciones
→ Teoría, código, vídeo y recursos extra
→ Curso de inicio con otras 21 lecciones por si partes de cero

Gratis y en español!

https://t.co/u4sMMC7dga

[Joey👽 @FCBJoeyy]

Scoring a goal from over 40 yards is completely outrageous and spectacular at the same time

Here are 10 of the best long range goals in football

A Thread

1.Roberto Carlos Incredible long Range Freekick (France 1997)

[Dr Milan Milanović @milan_milanovic]

𝗧𝗼𝗽 𝟲 𝗖𝗼𝗺𝗺𝗼𝗻 𝗠𝗶𝘀𝘁𝗮𝗸𝗲𝘀 𝗶𝗻 𝗥𝗘𝗦𝗧𝗳𝘂𝗹 𝗔𝗣𝗜 𝗗𝗲𝘀𝗶𝗴𝗻

Here are the six most consequential mistakes engineers make when designing RESTful APIs.

𝟭. 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗜𝗻𝘀𝗶𝗱𝗲-𝗢𝘂𝘁 𝗜𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗢𝘂𝘁𝘀𝗶𝗱𝗲-𝗜𝗻

Many engineers approach API design by directly exposing their internal data models or service functions, creating what API experts call "implementation leakage." This inside-out approach produces interfaces that force API consumers to understand their internal architecture rather than efficiently solving their use cases.

👉 Example: Stripe's early API versions exposed endpoints like `/accounts/create` that reflected their internal service methods.

Their improved API now uses resource-focused endpoints like `/v1/accounts` with POST requests.

𝟮. 𝗜𝗺𝗽𝗿𝗼𝗽𝗲𝗿 𝗨𝗥𝗜 𝗗𝗲𝘀𝗶𝗴𝗻

URIs should identify resources through nouns, not actions or operations. This fundamental REST principle separates the "what" (resources) from the "how" (HTTP methods).

❌ Poor design: `/api/getUsers` or `/api/deleteUser/123`
✅ Better design: `GET /api/users` or `DELETE /api/users/123`

Well-designed resource naming creates intuitive hierarchies: `/organizations/{id}/teams/{id}/members` clearly expresses the relationship between resources.

𝟯. 𝗠𝗶𝘀𝘂𝘀𝗶𝗻𝗴 𝗛𝗧𝗧𝗣 𝗠𝗲𝘁𝗵𝗼𝗱𝘀

HTTP methods have specific semantics that should be respected to benefit from web infrastructure:

🔹 GET: Retrieves resources (must be idempotent, cacheable, and free of side effects)
🔹 POST: Creates new resources or triggers processes
🔹 PUT: Replaces resources ultimately (must be idempotent)
🔹 DELETE: Removes resources

Tools like RESTful Linters can automatically check API specifications for method usage violations, potentially saving up to 15 hours of debugging time per project.

𝟰. 𝗡𝗲𝗴𝗹𝗲𝗰𝘁𝗶𝗻𝗴 𝗘𝗿𝗿𝗼𝗿 𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴

Studies show that 29% of API integration time is spent handling errors and edge cases. Implementing a consistent error model improves the developer experience.

Stripe's approach to error handling sets the industry standard:

{
"error": {
"code": "resource_missing",
"message": "The requested resource doesn't exist",
"param": "id",
"type": "invalid_request_error"
}
}

Their structured errors include the following:
🔸 HTTP status codes that accurately reflect the error category
🔸 Machine-readable error codes for automated handling
🔸 Human-readable messages for debugging
🔸 References to the specific fields or parameters causing issues

𝟱. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻𝗶𝗻𝗴 𝗼𝘃𝗲𝗿𝘀𝗶𝗴𝗵𝘁

Practical versioning approaches include:

🔹 URI path versioning: `/api/v1/users` (used by Stripe, easy to understand)
🔹 Custom header versioning: `Accept-version: 1.0` (used by AWS, cleaner URIs)
🔹 Content negotiation: `Accept: application/vnd.github.v3+json` (used by GitHub, most technically correct)

Each strategy has tradeoffs, but the absence of any versioning guarantees future pain.

#api #apidesign

[Pablo Giralt @giraltpablo]

Atención. Se probará la LEY WENGER en algunos torneos a partir de la próxima temporada.

El jugador atacante solamente ESTARÁ en OFFSIDE si NINGUNA parte de su cuerpo (con la que pueda hacer un gol) coincide con el rival.

¿Opiniones?

[Virginio Gallardo @virginiog]

La lista de las habilidades más importantes para el próximo 2025 según el WEF