Code Smell 77 - Timestamps

Timestamps are widely used. They have a central issuing authority and do not go back, do they?

TL;DR: Don't use timestamps for sequence. Centralize and lock your issuer.

Problems

• Bijection Fault.

• Timestamp Collisions.

• Timestamp precision.

• Packet Disorders.

• Bad Accidental Implementation (Timestamp) for an Essential Problem (Sequencing).

Solutions

1. Use a centralizing sequential stamper. (NO, not a Singleton).

2. If you need to model a sequence, model a sequence.

Sample Code

Wrong

# using time module
import time

# ts stores the time in seconds
ts1 = time.time()
ts2 = time.time() #might be the same!!

Right

numbers = range(1, 100000)
#create a sequence of numbers and use them with a hotspot

#or
sequence = nextNumber()

Detection

Timestamps are very popular on many languages and are ubiquitous.

We need to use them just to model... timestamps.

Tags

• Bijection

Conclusion

This smell was inspired by recent Ingenuity software fault.

If we don't follow our MAPPER rules and model sequences with time, we will face trouble.

Luckily, Ingenuity is a sophisticated Autonomous vehicle and has a robust fail-safe landing software.

This video describes the glitch

Relations

Code Smell 39 - new Date()

Maxi Contieri ・ Dec 1 '20

#oop #codenewbie #tutorial #globals

Code Smell 32 - Singletons

Maxi Contieri ・ Nov 23 '20

#codenewbie #tutorial #webdev #programming

More info

• Timestamp proposed changes

• Build a Mapper

• What is wrong with software

---

The most beautiful code, the most beautiful functions, and the most beautiful programs are sometimes not there at all.

Jon Bentley

Software Engineering Great Quotes

Maxi Contieri ・ Dec 28 '20

#codenewbie #programming #quotes #software

---

This article is part of the CodeSmell Series.

How to Find the Stinky parts of your Code

Maxi Contieri ・ May 21 '21

#codenewbie #tutorial #codequality #beginners