---
title: "Guess that conference"
url: "https://osherove.com/blog/2006/1/19/guess-that-conference.md"
canonical: "https://osherove.com/blog/2006/1/19/guess-that-conference.html"
published: "2006-01-19T15:02:00"
updated: "2006-01-19T15:02:00"
tags: ["Off Topic"]
author: "Roy Osherove"
description: "Update: Dale got it in the comments. That's the author guidelines for submitting a research article to the \"Agile 2006\" conference, no less. It's following IEEE guidelines for submissions. I'll let you ponder the irony…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Guess that conference

By Roy Osherove January 19, 2006 In [Off Topic](https://osherove.com/blog/category/off-topic)

**Historical article** · Originally published January 19, 2006; technical details may be outdated.

_**Update:**_

_Dale got it in the comments._

_That's the author guidelines for submitting a research article to the "Agile 2006" conference, no less. It's following IEEE guidelines for submissions.
I'll let you ponder the irony in that situation.._

Can you guess what conference (or type of conference) the following piece of guidance document for submitting papers is taken from?

"

# 7\. Main text

Type your main text in 10-point Times, single-spaced. Do **not** use double-spacing. All paragraphs should be indented 1/4 inch (approximately 0.5 cm). Be sure your text is fully justified—that is, flush left and flush right. Please do not place any additional blank lines between paragraphs.

**Figure and table captions** should be 10-point boldface Helvetica (or a similar sans-serif font). Callouts should be 9-point non-boldface Helvetica. Initially capitalize only the first word of each figure caption and table title. Figures and tables must be numbered separately. For example: “Figure 1. Database contexts”, “Table 1. Input data”. Figure captions are to be centered _below_ the figures. Table titles are to be centered _above_ the tables.

# 8\. First-order headings

For example, “1. Introduction”, should be Times 12-point boldface, initially capitalized, flush left, with one blank line before, and one blank line after. Use a period (“.”) after the heading number, not a colon."

## More in Off Topic

[All posts in Off Topic](https://osherove.com/blog/category/off-topic)

- Feb 11, 2006

    ### [The future of interaction](https://osherove.com/blog/2006/2/11/the-future-of-interaction.html)

- Feb 10, 2006

    ### [VB6 Migration pains - captured as a conversation](https://osherove.com/blog/2006/2/10/vb6-migration-pains-captured-as-a-conversation.html)

- Jan 19, 2006

    ### [FYI: "v7ndotcom elursrebmem"](https://osherove.com/blog/2006/1/19/fyi-quotv7ndotcom-elursrebmemquot.html)

- Jan 16, 2006

    ### [Cool Outlook Trick: Sync schedules with multiple computers, without using Exchange](https://osherove.com/blog/2006/1/16/cool-outlook-trick-sync-schedules-with-multiple-computers-wi.html)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/