[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.

[devnexus 2026] Maven’s Hidden Secrets to Speed up your Build

Speaker: Ko Turk (@KoTurk77)

See the DevNexus live blog table of contents for more posts


Waiting

  • Showed spring boot app with tests. Took 51 seconds
  • Real builds could even take 30 minutes

General

  • About 75% use Maven, about half use Gradle (so many both) and small percentage Ant.
  • Maven created in 2002
  • Became top level Apache project in 2023
  • Maven 4 is a release candidate – it does parallel building better
  • mvnup check – for migrating to Maven 4
  • Can install through website, brew, sdkman, daemon, wrapper, etc

Daemon

  • JDK background process stays in memory so warm
  • Reuses plugins

Hierarcy

  • Lifecycles – clean, build, etc
  • Phases – clean, process-resources, compile, etc
  • Maven plugins
  • Maven goals

Also showed

  • Profiling plugins such as jcgay/maven-profiler or Gradle develocity
  • Adding echo ot the pre-clean phase
  • Maven clean verify vs mvn clean install
    • failsafe vs surefire. Can run integration tests in profile so control when run

Covered after I left: see deck

My take

I liked that he played music while running a build to show how long a simple build takes. The pirate/treasure map theme was fun. I had to leave this session at the halfway part but I enjoyed the part I saw. Good mix of slides and showing.