So, here we are using postgres in production with the fancy feature of UPSERT. We’ve got loads of request popping in, both new and updates - so the UPSERT getting triggered alot. Today we faced a problem with integer within our app stating that the number is too high. We were like «WTF? Already?!»! After looking in to the features of UPSERT, we came to realize that any sequence will be incremented regardless of an insert being handled. This results then in an ID field being defined with ids such as:
1
2
5
19
222
73377
282828282
Etc. You get the point..
This design is so WTF and I have absolutely no idea why anyone would like their IDs to be generated and incremended even though there is no insert. I hope it is due to my naivity that I cannot comprhend it. Oh well. UPSERT, you’re forever gone 👍🔥

Some stats on what I've been doing all 2020:
222 working days.
60% of the days, working on dev stuff.
80% of the days, working on 2nd responsibility (legal documentation for clients).
From April, 60% of the 222 days working on the 3rd responsibility I got assigned in, you guessed it, April (KPI making).
So basically 70% of my job is no longer what I signed up for.
That's what I want to change this year.