How to spend the last months of a CS postdoc usefully before leaving academia? My current computer science postdoc ends in the summer. I'm planning to leave academia after that. For the purpose of this question, because reasons I won't go into, we may assume I will never return to academia.

One of the peculiarities of the field of computer science is that research has not really happened if one doesn't travel to present it in a conference over 4 months after the paper has been submitted.

For all relevant conferences that take place before my contract ends, the paper submission deadlines have already passed. Since I don't know what my next job will be or in what continent I'll be living, I cannot commit to traveling to a conference after my contract ends. (And also even if I could, I would not because no matter what people say, I don't want to endorse such a practice.)

I currently have one ongoing project that I've been working on with my advisor. However, it is uncertain how much time is required to finish it. In addition, there are some ongoing projects in our group that I perhaps could join, but I don't know how much I actually could contribute to those projects.

Anyway, I'd like to spend the remaining work time of my contract doing something that's worth doing, when I'm at work working. It seems that there are no good solutions in my situation. But certainly many CS postdocs have had a similar problem before. Is there a solution to this that I'm missing?
Perhaps your advisor has one or more students that could benefit from more mentoring than the advisor can supply?

Helping young graduate students learning to do research and write papers would be worth doing in its own right. If you are going on to an industry career mentoring junior programmers would be a valuable skill. It would be a different sort of experience to put on your resume when job hunting, not just more of the same.