[devnexus 2026] Code Your Way to Quantum-Safe Development by Solving Tomorrow’s Encryption Crisis

Speaker: Barry Burd

See the DevNexus live blog table of contents for more posts


Shor’s algorithm

  • Quantum algorithm to factor large numbers
  • Divides very large numbers
  • Cracks RSA
  • 100K qubits
  • Harvest now; decrypt later. While can’t implement algorithm efficiently now, will be able to decrypt the data in the future. Lots of data will be stale by then, but lots won’t be (ex: social security number)

Programming quantum computers

  • Languages – OpenQASM, Qiskit (IBM), Circ (Google), Q# (Microsoft),, Strange (Johan Vos)

JEPS

  • 496 – Quantum resistant module lattice based key encapsulation mechanism – way to send a secret key. Based on difficulty in finding relationships between vectors in a lattice (grid). Generally when vectors are close to parallel (but not parallel), the more dimensions and the larger the vector is, the harder it is to subtract them
  • 497 – Quantum resistant module lattice based digital signature algorithms
  • 510 – Key Derivation Functional API
  • 527 – Post-quantum hybrid key exchanged for TLS 1.3

Qubits

  • Either 0 or 1
  • Hadamard gate turns a bit into a superposition (unresolved state)
  • Even nature doesn’t know the value until receiver reads it.
  • Unmeasured qubit has 50% chance of becoming 0 or 1 when measure it. In this example, it’s for sending a secret key which is random data.
  • An even number of Hadamard gate cancel each other out so you wind up with the initial value.

Defenses

  • Post quantum cryptography – better classical algorithms. Can run on computer have today in Java.
  • Quantum key distribution (QKD) – key exchange with quantum hardware. We know how to do this on short distances, like within a city. Experimenting at long distance, but not practical yet. Have sender hadamard some bits and each party say some information about what is hadarmard’d. Then having sender receive; confirms nobody eavesdropped on message which would change the value.

My take

Nice diagrams and code. Barry explained well. Especially the concepts that were new to me and therefore not intuitive like quantum key distribution. A little glad this wasn’t immediately applicable because my brain is full.

[devnexus 2026] Stop Fighting Your AI: Engineering Prompts That Actually Work

Speaker: Martin Rojas (@martinrojas)

See the DevNexus live blog table of contents for more posts


Slides online

General

  • Prompting is the new code switching [it took me a minute to realize he meant the ENglish language one]

Components

  • System Message – sets behavior and role
  • Instruction – what to do
  • Context – background data
  • Examples – pattern demonstration
  • Constraints – output limits
  • Delimiters – section separation

Markdown

  • Most common prompting language. Still text but gives structure
  • Headings, bold, list, code

Prompt types

  • Zero shot – direct instruction – simple/fast but inconsistent quality
  • One shot – format setting – consistent format, but limited pattern learning
  • Few shot – pattern learning – adapts to context, but token intesive
  • Role based – behavioral framing – consistent voice, but might override other instructions

Techniques

  • Clarity and specificity. Need to define assumptions
  • Chain of thought -make the model think like an analyst
  • Format constraints – specify what want for output
  • Prompt compression – use less tokens to say equivalent thing. Drop filler words like please. Use lists instead of sentences. Use a little quality, but worth it if minimal effect on output. Engineering tradeoffs.
  • Progressive enhancement – Naked prompt (vagye, add role, add specificity, add chanin of thought, add constraints, add validation

AI as Coach

  • Ask AI to improve your prompt; both with why and to rpdouce and improved prompt
  • Ask AI to compress to make shorter

More notes

  • Build prompt library that works for you – uses Obsidian and in the AI tools themselves (aka skills)
  • Measure for your use cases

Advanced Patterns

  • Tree of Thought (ToT) – explore multiple analytical approaches simultaneously then evaluate which version reals the most insight. This is why AI goes off for an hour; it is doing this behind the scenes
  • Self consistency – try different approaches and then majority vote for accuracy
  • ReAct pattern – Iterative reason > Act > Observe loops for multi step investigations

My take

Good start by defining vocabulary/components and good example. I’m really glad he shared the slides. The contrast between the text and background made the examples hard to read so I pulled up the deck on my computer for reading those.

[devnexus 2026] Sociotechnical Platform Engineering

Speaker: Chris Corriere (@ecology_chris)

See the DevNexus live blog table of contents for more posts


Garden analogy

  • Continuous delivery of fish and vegetables
  • The structure defines the system

Platform

  • Abstraction of complexity
  • 2 sided networks (sometimes n sided)
  • Opportunities for business to serve customers (ex: airport or shopping mall)
  • Business isn’t responsible for handling restroom, etc

DevOps

  • Reduce friction to prod
  • ICE CALMS acronym. Integration, Continuous Deployment, Experimentation, Culture, Automation, Lean, Measurement, Sharing

SRE

  • Production stability
  • Must have all four of these:
  • SLA (Service level agreements)
  • SLO (Service level objectives)
  • SLI (Service level indicators)
  • Error budgets

Maps

  • Value stream map – horizontal through organization
  • Social practice – decenter process
  • Wardley map – source vertical dependencies for each process
  • A security patch can’t go faster than a trivial change.

Useful to graph

  • Duration
  • CI/CD wait time

Comparison

  • DevOps – SLIs, version control, bronze, python notebooks
  • Shared Social Practices – SLOs, integration testing, silver, databricks/snowflake
  • SRE – SLAs, response time, gold, Apache Spark (powers databricks under the hood)

Shared between DevOps and SRE

  • ML Ops – vector embedding, model selection, Ralph Wiggum, unstructured data
  • Shared Social Practices – RAG, agents, evals, semistructured data
  • SRE – rate limits, humans guard rails, structured data

Maps

  • Point of a map is to facilitate a conversation
  • All maps are wrong
  • Some are useful

My take

Lots of information. Some I knew; some I did not. A cookie analogy before lunch made me hungry, but it was a good map. Good visuals for the maps I wasn’t familiar with.