---
title: "Coding into the night"
url: "https://osherove.com/blog/2003/3/16/coding-into-the-night.md"
canonical: "https://osherove.com/blog/2003/3/16/coding-into-the-night.html"
published: "2003-03-16T18:35:00"
updated: "2003-03-16T18:35:00"
tags: []
author: "Roy Osherove"
description: "You all know these moments. You worked on something really hard for a serious amount of time, hacking away, discovering errors, finxing bugs, implementing pure cool stuff and then, finally, after all this time, you…"
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/"
---

# Coding into the night

By Roy Osherove March 16, 2003

**Historical article** · Originally published March 16, 2003; technical details may be outdated.

You all know these moments. You worked on something really hard for a serious amount of time, hacking away, discovering errors, finxing bugs, implementing pure cool stuff and then, finally, after all this time, you press "play" and it just runs.

Just like you thought it would look at the end. Your vision has come true. You thought of, designed ,investigated and implemented a cool piece of software, and it just runs. I really love these moments. I even cought myself raising my arms in the air and whispering a quiet "yahhh!" (don't wake the wife...)

There is still lots to do, but from what it looks now my little project is really coming along. I don't wanna give away the ending, as i will be releasing my code as GPL, but just a taste would suffice:

When what i wrote ran, i could write a .Net assembly which does Interop with a VB COM dll and a C++ COM dll, and i could trace through **all** the code (.Net-to-VB-to-C++-to-.Net again) using a simple "Trace.Write" call whenever i needed to and everything showed up on one specific place.

But that's only the beginning of what i have planned....


---

## 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/