Azmat

[Shravani @shrav_10]

lol this is fun -> https://t.co/cM64EJfqPl

[Azmat @dotslashAzm]

Devcon 8 & OpenTechSummit proved one thing: open-source software is the backbone of decentralized infrastructure.

#FOSSASIA
#Devcon8
#Ethereum
#OpenTechSummit

[Gaurav @gaurav_ships]

A datacenter is RAM Mandir.

[Azmat @dotslashAzm]

Take this slop back to linkedin please

[Raj kr @raj_4_69]

Recruiter:
Please share your resume via mail.

Normal candidate:
attaches resume on email and send it .

Strong Candidate:

[dinos @din0s_]

are we for fucking real right now 😭

[Azmat @dotslashAzm]

@codinzhubcom @SarveshPatil62

[メ @BjaySwag]

bananas don’t give a fuck about any other fruit in a smoothie.

[Azmat @dotslashAzm]

Uhh, Are you guys hiring

[Umbrella Corp. Official @UmbCorOfficial]

Stop blaming everything on us.

[Azmat @dotslashAzm]

ATP Just print and post it to recruiter so they can physically reject your resume

[Ritesh @riteshpatel1884]

Never upload your resume as a PDF.

There is a reason.

• DOCX is easier for ATS systems to parse
• Recruiters can quickly edit or add notes
• Text extraction is generally easier
• Some hiring portals process DOCX more reliably
• Recruiters can copy your information directly into their systems

So if the application says "Upload Resume", don’t upload a PDF just because it looks better. Always try to upload DOCX format.

[Azmat @dotslashAzm]

@pnyk05 Great, can you share how you made it ?

[Azmat @dotslashAzm]

@vineeth_agi Intrested, can you mention the company name ?

[that_techboy @JoshuaIsreal01]

I'm the API between Claude and my manager

[Suraj Sharma @suraj_sharma14]

As a Backend Engineer in the AI era, you must build these projects.

1.) High-Concurrency HTTP Server
Build: Go or Rust server handling 10k+ concurrent connections with graceful shutdown and backpressure.

Why: Concurrency architecture is the one thing AI cannot design for you.

2.) Multi-Tenant Hybrid Search Database
Build: Postgres with Row-Level Security + pgvector + BM25 hybrid ranking across isolated tenants.

Why: Structured data and semantic embeddings now share one query engine.

3.) Event-Sourced Order Pipeline
Build: Kafka or NATS pipeline with immutable events, dead-letter queues, exactly-once semantics.

Why: AI workloads are slow and async. The main thread must never block.

4.) Durable Onboarding Workflow
Build: 3-day Temporal workflow with checkpoints, retries and human approval steps.

Why: Background jobs are for emails. Durable execution is for multi-step agents.

5.) AI Gateway with Semantic Cache
Build: Proxy that caches similar prompts via embeddings, enforces token budgets and fails over to a cheaper model on 503s.

Why: The gateway protects your margins and your uptime from flaky, expensive LLM APIs.

6.) PII-Redacting Auth Middleware
Build: OAuth2/OIDC provider plus middleware that masks PII before logging and restricts AI agents to read-only DB roles.

Why: When agents can write to your database, a prompt injection is a data breach.

7.) Real-Time Streaming Dashboard
Build: SSE/WebSocket dashboard streaming LLM tokens and database updates simultaneously with backpressure.

Why: Time-To-First-Token and perceived latency are the new UX standards.

8.) Correlated Tracing Pipeline
Build: OpenTelemetry + Langfuse pipeline linking each HTTP request to the exact LLM prompt and DB query it triggered.

Why: You cannot debug a hallucination without replaying the exact context the model saw.

9.) Ephemeral Environment Provisioner
Build: Terraform or Pulumi scripts spinning up a complete isolated staging environment for every pull request.

Why: Manual deployments are a liability. Infrastructure must be version-controlled and reproducible.

10.) Queue-Based Autoscaler
Build: KEDA autoscaler spinning nodes up on Kafka queue depth and down when empty with spot-instance fallback.

Why: Backend engineers now own the cloud bill. Idle resources burn runway.

11.) Globally Distributed Rate Limiter
Build: Redis-backed distributed rate limiter that survives network partitions gracefully.

Why: Architecture must degrade gracefully not cascade into total outage.

12.) Chaos Engineering Suite
Build: Fault-injection harness (latency, replica kills, partitions) with SLO burn dashboards.

Why: Resiliency is proven under failure not in diagrams.

13.) Webhook Reconciliation Engine
Build: Idempotent event processor with exponential backoff, dead-letter queues and replay tooling.

Why: Real integrations fail constantly. Reconciliation is what makes them trustworthy.

14.) Cost-per-Request FinOps Dashboard
Build: Per-tenant, per-endpoint, per-LLM-call cost rollups with anomaly alerts.

Why: Visibility is control. You cannot optimize what you cannot attribute.

15.) Public Architecture Teardown
Build: 3 published deep-dives with system diagrams, ADRs and latency/cost benchmarks.

Why: Senior engineers are hired for their judgment not their syntax.

Systems that prove you can scale, secure & ship when agents touch your stack.

Most people watch tutorials. Builders ship systems.

Bookmark & Repost.

[monolith𓆩❒𓆪 @0xMonolith]

CAN YOU FUCKING STUPID AI REVERSE ENGINEERING NERDS JUST DECOMPILE PHOTOSHOP INSTEAD OF ALL THIS GAME CRAP

[Azmat @dotslashAzm]

Uhh what

[Google Japan @googlejapan]

ユーザーのみなさまへ
Gboard チームからの新しいご提案です。

キーが指先まで流れてくるキーボード
『Gboard くるくるバージョン』を開発しました。

フルバージョンはリプライでご確認ください↓

[Azmat @dotslashAzm]

@EcomExpress_Ofc hey @EcomExpress_Ofc
shipment awb number is :2697315434
pin code mentioned on the package is 481666 which is incorrect , the correct pin code is 481661

please resolve this issue so that I can get delivery of my package

thanks

[⛩️ Sumito ⛩️ @sumitomedia]

e v o l v e

[shidbot420 @shidbot420]

Avg 4 years of university

[⛩️ Sumito ⛩️ @sumitomedia]

morning gamers