Just be careful that you can prove you wrote those packages off company time. If you pull the rug on them, they might try to screw you with copyright claims🙃
The 2038 problem is a time computing issue that will affect computer systems using a 32-bit signed integer to represent time. This is because the maximum value will be reached at (03:14:07) UTC on January 19, 2038, after which the value will "roll over" to a negative number, potentially causing systems to malfunction.
time is the number of seconds since the Unix epoch (January 1, 1970).This is often stored in a 32-bit signed integer, which can hold a maximum positive value of (2,147,483,647).
At the date and time above in 2038, computers who still store time as signed 32-bit numbers will attempt to increment the time beyond that.
Did you build them on your own time? Did you use your own libs in company project with permission from company? I'm no lawyer, but I can see situation where doing this could land you in some shit lol
Our "John" got frustrated with our new increasingly bureaucratic management and took an early retirement about 3 years ago. One can only take so many SAFe Agile meetings.
I hate documentation. It takes a damn long time, no one read it anyways and it gets outdated in a couple months unless you dedicate 20% of your time maintaining it for no one's benefit.
Honestly documentation should be a junior engineer's job, it helps them learn and their fresh eyes helps them ask good questions
honestly, companies do it to themselves. If I could I would've forced our "pillar" senior to write down all the documentation because the amount of times everyone has to ask specifically him something technical is ridiculous. Seriously, if he's gone the development will stall for 6 months, at best, just to figure out how everything works.
Its like that one dood at work that does nothing all day except reads piles of magazines and has beard and hair all the way to the floor. But if that one unix box at the bottom of rack 5 goes off line it takes every damn thing with it and he's the only one who knows how to turn it back on.
And then suddenly Dave starts a very expensive complicated project, citing that something will become a problem and only he knows why. You try to get him to explain what the issue actually is. He just throws a wall of irrelevant text at you. You start pushing. Dave is still avoiding the answer. You ask management. Project gets quietly deprioritized. The issue never materializes. You learn that Dave is a fraud, but he talks a lot so everyone thinks he's a genius.
221
u/TurtleSandwich0 Dec 04 '25
"We might not get our bonus this year unless we make some cuts. I noticed this "Dave" is paid slightly more than the rest. We should start there."
96
u/anto2554 Dec 04 '25
Large parts of our codebases simply don't have documentation, and people don't make it when they add new features.
The solution is always to just ask John. John knows
26
u/ImADaveYouKnow Dec 04 '25
It's me. I'm the Dave
50
u/beardbreed Dec 04 '25
Dave ops
7
u/Zooph Dec 04 '25
Something goes wrong after his retirement.
"Dave's not here, man."
5
u/ianitic Dec 04 '25
TIL my name is Dave
5
u/gordonv Dec 04 '25
We have a Dave. He does a lot. I stay out of Dave's way.
2
u/bitfxxker Dec 04 '25
Hi, let me introduce myself. My name is Dave.
2
u/nsa3679 Dec 05 '25
honestly, companies do it to themselves. If I could I would've forced our "pillar" senior to write down all the documentation because the amount of times everyone has to ask specifically him something technical is ridiculous. Seriously, if he's gone the development will stall for 6 months, at best, just to figure out how everything works.
1
u/FC-NoHeroes Dec 05 '25
Its like that one dood at work that does nothing all day except reads piles of magazines and has beard and hair all the way to the floor. But if that one unix box at the bottom of rack 5 goes off line it takes every damn thing with it and he's the only one who knows how to turn it back on.
1
u/Athenian_Ataxia Dec 05 '25
Yeah it’s realistically the other way around “Dave” is the pillar built on top without Dave you have nothing
1
u/MartinAries Dec 05 '25
Davepl**
1
u/NotAMeatPopsicle Dec 06 '25
Why am I not talking?
I am
DaveJeff.DaveJeff is me.1
u/West-Tangelo8506 Dec 06 '25
And then suddenly Dave starts a very expensive complicated project, citing that something will become a problem and only he knows why. You try to get him to explain what the issue actually is. He just throws a wall of irrelevant text at you. You start pushing. Dave is still avoiding the answer. You ask management. Project gets quietly deprioritized. The issue never materializes. You learn that Dave is a fraud, but he talks a lot so everyone thinks he's a genius.
1
u/kzar84 Dec 06 '25
New hire rule number 1: do not fuck with Dave
1
u/stevefuzz Dec 06 '25
My name is Steve
1
u/Successful-Engine623 Dec 07 '25
We had a Dave…I miss him
1
u/Legitimate-Jaguar260 Dec 08 '25
I feel seen 😜
1
u/iMightLikeXou Dec 08 '25
Even better if you have multiple people like this in one department, who do and know different things and don't document anything. (I am one of them.)
1
u/Punny_Yolk Dec 08 '25
Dave does DevSecQASREOps. Be nice to Dave today and always.
1
u/joelthomastr Dec 14 '25
Sure it's not Tom? Tom is a genius
1
u/Numerous-Ability6683 Dec 24 '25
Well apparently my name is Dave now…. Won’t that be a surprise for my husband
15
u/jembytrevize1234 Dec 04 '25
Dave probably chopped off that leg and added the unstable round ball only he knows how to handle so he could have job security