Dvz | Python Architect (@PythonDvz) header
Dvz | Python Architect (@PythonDvz) profile picture

🐍 Python, AI & Distributed Systems Architect. • Daily Python Quizzes & Logic Traps • Junior vs. Senior Code Refactoring • AsyncIO, Memory & Clean Code 👇

Joined June 2016
Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)Photo by Dvz | Python Architect (@PythonDvz)
Excel handles 10K rows. SQL owns the warehouse. Pandas rules messy pipelines. Which column runs your daily workflow?
1
19
1
88
7,470
At what dataset size do you actually drop Pandas for Polars or DuckDB in production?
1
5
816
Python vs. JavaScript
1
5
1,185
Hoping Nemotron keeps going. Thankfully, open weight LLMs have some alternatives. But their open data and full training recipes would be much harder to replace.
29
25
5
540
28,398
Open weights without open data recipes leave teams blind when debugging domain regressions. Which part of Nemotron's pipeline has been hardest to replicate from scratch so far?
275
When cloning nested config dicts in your ML pipelines, does Snippet B actually prevent state leaks? xitter.twitterapi.xyz/PythonDvz/status/21208…
Is res = base.copy() in Snippet B enough to keep merge_scores from mutating base?
1
2
1,139
Would an AI coding assistant pass this PR review, or do both Snippet A and B break production? xitter.twitterapi.xyz/PythonDvz/status/21208…
Is res = base.copy() in Snippet B enough to keep merge_scores from mutating base?
1,344
Ever had shared references inside Python dicts silently corrupt node features during graph batching? xitter.twitterapi.xyz/PythonDvz/status/21208…
Is res = base.copy() in Snippet B enough to keep merge_scores from mutating base?
2
1,167
In 10 Vector Databases: When to Use Each One, why spin up Pinecone, Milvus, or Qdrant before pgvector on PostgreSQL actually hits a wall?
2
1
1
5
3,476
Starting with pgvector and moving only when it actually hits a wall seems right for most apps.
1
1
15
Keeping everything inside Postgres early saves huge ops overhead. What usually breaks first when teams hit that wall: HNSW index memory pressure or latency on metadata-filtered queries?
46
Spot the subtle Python memory reference trap between Snippet A and Snippet B before running the code? xitter.twitterapi.xyz/PythonDvz/status/21208…
Is res = base.copy() in Snippet B enough to keep merge_scores from mutating base?
1
1,178
Is res = base.copy() in Snippet B enough to keep merge_scores from mutating base?
1
2
1
6
2,687
That top-level copy in Snippet B feels safe right up until you inspect the original dict.
1
245
What is the wildest hardcoded lookup table or manual script you have ever caught inside a data pipeline? xitter.twitterapi.xyz/PythonDvz/status/21208…
There are no logical issues if there is no logic 🤣
1
1
1,168
Python Quiz: What is the Output?
10
3
79
10,827
I really did not know that X was changing value inside a for loop without asigning it inside it. I would've thought this was a trick question and say A.
1
1
17
Classic Python scoping surprise since loop targets leak straight into the surrounding block. Have you ever hit a subtle bug in real code where a loop reused an outer variable name by accident?
38
Be honest, how many lines of manual if-else did your very first calculator project have when learning to code? xitter.twitterapi.xyz/PythonDvz/status/21208…
There are no logical issues if there is no logic 🤣
2
1,194
Ever inherited a legacy scoring notebook where every edge case was just another hardcoded branch? xitter.twitterapi.xyz/PythonDvz/status/21208…
There are no logical issues if there is no logic 🤣
3
1,227
How many nested if-else blocks does it take before someone in your team rebrands it as an AI engine? xitter.twitterapi.xyz/PythonDvz/status/21208…
There are no logical issues if there is no logic 🤣
2
1,687
There are no logical issues if there is no logic 🤣
1
1
1
10
3,761
Save this as AGENTS.md in your project. Codex, Cursor, Copilot and most coding agents read it automatically. # AGENTS.md ## Before you call it done •⁠ ⁠Run the tests, linter and type checker. Done means they pass. •⁠ ⁠Never assume a failing test was already broken. Check main first. •⁠ ⁠Unit tests and mocks don't count as proof. Run the real thing end to end. ## Tests •⁠ ⁠When fixing a bug, first write a small test that fails, then fix it. •⁠ ⁠Check if an existing test already covers it before adding a new one. •⁠ ⁠Never write a test that only checks "it didn't crash." •⁠ ⁠Never delete a check, shrink a test or raise a limit to make it pass. Fix the code. •⁠ ⁠Run the tests once and save the output to a file. Read the file instead of rerunning. ## Changes •⁠ ⁠Keep changes small. No unrelated edits. •⁠ ⁠Don't add or upgrade dependencies unless asked. •⁠ ⁠Never edit generated files. Change the source and regenerate. •⁠ ⁠Don't rename or reorder public functions or their arguments. •⁠ ⁠Comments explain why, not what. ## Git •⁠ ⁠Never push unless told to. •⁠ ⁠Never amend or force-push. Make a new commit. •⁠ ⁠Don't create or switch branches without asking. ## Safety •⁠ ⁠Never put secrets in a command. Use environment variables. •⁠ ⁠Never post, comment or open PRs on GitHub on your own. ## When stuck •⁠ ⁠If a required tool fails, stop and say exactly which call failed. Don't build a workaround. •⁠ ⁠Only stop for a missing decision, missing permission or a real blocker. Say exactly what you need.
31
8
121
47,181
Solid checklist for AGENTS->md, though coding agents still burn tokens editing half the repo before checking types. What hard guardrail rule actually stops them from over-editing?
142
Looking at MongoDB vs SQL, how many teams pick a schema-less Document Database early on only to rebuild foreign keys in code later?
3
5
1
27
4,739
dead-letter at row level. quarantining the whole batch blocks all the clean rows over one weird key, and then everyone asks why the dashboard is late. bad rows go to a side table with raw payload + reason, rest loads as normal. only hold the batch if the schema itself broke
1
1
25
Row-level quarantine is the cleanest pattern in production. Side tables with raw payloads and rejection reasons keep SLAs intact while making replay effortless once upstream fixes their contract.
44
At what row count did pgvector finally choke for your backend so you migrated to Qdrant or Pinecone? xitter.twitterapi.xyz/PythonDvz/status/21207…
In 10 Vector Databases: When to Use Each One, why spin up Pinecone, Milvus, or Qdrant before pgvector on PostgreSQL actually hits a wall?
3
1,642