DEVXA GLOSSARY

What is a Call on Devxa?

A Call on Devxa is a public, timestamped prediction about software development, architectural choices, or market milestones made with an explicit confidence percentage. Once the target deadline arrives, the author resolves the Call with verifiable public evidence, establishing an objective hit rate that demonstrates forecasting judgment and technical honesty.

How Calls Work in Practice

Unlike casual social media opinions that disappear down a feed, a Call on Devxa is a structured, accountable commitment. When a builder publishes a Call, three core data points are recorded:

  • The Claim: A clear, testable assertion (e.g., reaching an open-source milestone, launching a specific feature, or API benchmark).
  • The Target Date: The deadline by which the prediction will be evaluated.
  • Confidence Level: A percentage rating (e.g., 60%, 80%, 95%) indicating how sure the builder is of the forecast.

By fixing these parameters at creation, Devxa eliminates hindsight bias and creates an authentic log of your technical forecasting.

A Concrete Example of a Call

Example Builder Call
Target Date: March 31, 2027 · Confidence: 70%
"Our open-source developer tooling library will reach 1,000 GitHub stars before Q2 2027."

When March 31 arrives, the author resolves the Call by submitting a link to the GitHub repository. If the star count is 1,000+, the Call resolves as Correct. If not, it resolves as Missed. Devxa logs this outcome directly to the builder's Builder Record.

Why Calls Matter for Technical Reputation

Software engineering requires sound judgment and realistic architectural estimation. When founders, investors, or collaborators review an engineer's track record, a documented history of calibrated Calls demonstrates intellectual honesty, realistic roadmapping, and genuine foresight.

Calls pair naturally with Ships and can be exported as shareable Proof Cards or shared across the Devxa developer network.

Call Questions & Answers

Can I edit a Call after publishing it on Devxa?
No. To preserve historical integrity, prediction statements, target dates, and confidence percentages are locked once published. You can only resolve the Call with evidence once the outcome is known.
What happens if a Call outcome cannot be proven?
Calls must be resolved with objective, verifiable proof—such as public URLs, GitHub star charts, or documentation. If sufficient proof cannot be provided, the community or resolving system flags the Call accordingly.
How is my Call hit rate calculated?
Devxa calculates hit rates by comparing your resolved Calls (Correct vs Missed) weighted against your calibrated confidence levels, displaying an accuracy metric on your public Builder Record.

Publish your first Call

Make a public prediction on Devxa and start establishing your verified technical hit rate today.

Join Devxa Free