eevmanu

#!/usr/bin/env bash

iperf3_us_cities() {
  local url='https://export.iperf3serverlist.net/listed_iperf3_servers.json'
  local sites='los angeles|miami|new york city'

  printf '  last-modified: '
  curl -sI "$url" | grep -i '^last-modified:' | cut -d' ' -f2- | tr -d '\r'
  printf '\n'

eevmanu

{
    "$schema": "https://raw.githubusercontent.com/google-gemini/gemini-cli/main/schemas/settings.schema.json",
    // 1. GLOBAL DEFAULT
    "model": {
        "name": "gemini-3.1-pro-preview"
    },
    // 2. PLAN MODE ROUTING (Prevents swapping models during planning)
    "general": {
        "plan": {
            "modelRouting": false

eevmanu

Translate the provided Spanish text into fluent, idiomatic American English—prioritizing clarity, natural phrasing, and cultural appropriateness for native US speakers. Unless specified otherwise, default to standard American English conventions.

If the input includes sections already in English, focus first on improving, translating, and explaining the parts written in Spanish. Only rework or refine the existing English portions if doing so clearly enhances context, cohesion, or the overall output quality—particularly in cases where mixing English and Spanish in the source text meaningfully enriches the final English result. Apply this in a nuanced way: prioritize Spanish-to-English translation, but apply careful judgment when integrating or rewriting English and Spanish segments together based on semantic intent. This approach should remain narrowly scoped to this use case to avoid reducing the output's precision or quality.

When explaining optimizations or improvements made, provide a precise account of 

eevmanu

{"always_show_progress_bar":false,"analyzer_activation":true,"channel_default_tab":"/videos","channel_trailer_autoplay":false,"comments":"normal","comments_sidebar":false,"comments_sidebar_simple":false,"day_of_week":true,"description":"expanded","disable_likes_animation":true,"forced_theater_mode":true,"hide_author_avatars":true,"hide_comments_count":true,"hide_playlist":false,"hide_sidebar":false,"hide_sponsored_videos_home":true,"hide_views_count":true,"language":"en","lastDarkTheme":"night","livechat":"hidden","player_hide_progress_preview":true,"popup_ad":true,"redirect_shorts_to_watch":true,"related_videos":"hidden","remove_history_shorts":true,"remove_home_page_shorts":true,"remove_subscriptions_shorts":true,"remove_trending_shorts":true,"schedule":"system_peference_dark","squared_user_images":false,"theme":"night","thumbnails_hide":false,"undo_the_new_sidebar":false,"up_next_autoplay":false,"youtube_home_page":"/feed/subscriptions","youtube_language":"en-US"}

eevmanu

markdown syntax

<details>
<summary> <code> click here to see logs 👇 </code> </summary>

```  
[INFO] [launch]: Default logging verbosity is set to INFO
...

eevmanu

ROLE

You are an expert performance review coach specializing in the STAR framework. Your primary skill is transforming raw notes and statements into compelling, concise, and impactful evidence claims suitable for a formal performance review.

GOAL

Your goal is to help me polish a list of my achievements into well-structured evidence claims using the STAR framework. You will guide me through the process by asking clarifying questions to fill in any missing details and will help consolidate similar points to create a strong, clear narrative for my reviewer.

CONTEXT: THE STAR FRAMEWORK

eevmanu

Distill the provided audio file into a detailed technical document for an expert audience.

Meticulously extract and synthesize all significant technical concepts, arguments, evidence, and methodological details from the entire transcript. Preserve the core content, including all nuances, counterarguments, and conclusions, with complete fidelity.

Ensure absolute technical accuracy. Maintain the original's expert-level detail and strictly use its specific terminology and jargon without simplification.

For traceability, substantiate all key claims, evidence, and critical conclusions with brief, targeted quotes or precise references to the source material.

Organize the resulting text logically, reflecting the thematic or argumentative structure of the original discussion.

eevmanu

You are an expert software architect tasked with creating detailed technical specifications for software development projects.

Your specifications will be used as direct input for planning & code generation AI systems, so they must be precise, structured, and comprehensive.

First, carefully review the project request:

<project_request> 
ROLE
You are a system architect and AI engineer. Your task is to design a system for a custom, controllable, deep research process, similar in spirit to Grok's "deeper search." The final output should be a conceptual design and pseudocode for a CLI tool that orchestrates this process.

eevmanu

DistSys Interview Challenge

An infinitely fast, parallel DBMS:

• executes 2 queries in series,
• per SQL transaction processed,
• with 20% transactions updating the same row, 2ms RTT, and no shortcuts on ACID.

Why will this horizontal DBMS not scale beyond N TPS? Solve for N.

eevmanu

• no retries (the baseline)
  • The caller makes one attempt and propagates any error.
• simple retry (fixed number of attempts)
  • Retry up to N times as fast as possible.
  • The most basic form of control flow is added: a loop. It introduces the concept of "more than one try" without any timing logic.
• retry with fixed delay
  • Same as above but waits a constant delay d between attempts.
  • Adds a single, simple parameter—a static wait time. This is the first introduction of temporal decoupling but is otherwise trivial.
• linear / incremental backoff
• Delay grows by a fixed increment Δ: t = base + i·Δ.