I ran into this already on January first. Someone in the last 4 years changed/created a function in a MUD that I now maintain, to convert Unix timestamps into iso8601 strings for MySQL.
They did the math for which year is a leap year incorrectly, which wasn't the bug that bit us, they helpfully added the leap day regardless of where in the year it was. The tests they wrote targeted the middle of the year and missed it. I just pulled in date2j and related match from postgres, added more test cases.
I found this out the hard way as well, at some point since I last logged in they quietly enacted a policy of deleting keys that aren't used for roughly a year.[1] This meant I couldn't use the not so public method of verifying I still had access to various associated keys.
I have a different problem, my name Jensen generally gets said correctly but people looking at the spelling of my name get it wrong (Jenson / Jason) quite frequently.
This is primarily an issue with new contacts / acquaintances which I'm sure looks poorly on both of us, especially when this gets sent to other people on job searches etc.
I've seen enough crosswalks that go from solid red hand to a flashing red hand immediately, that I now ignore the flashing red hand until the street light turns yellow.
Shortening it makes it dangerous for a lot of parties.
My company has the following statement, which basically sais they shouldn't for any purpose outside of breaking non-compete/confidentiality.
Ability for <Company> Employees to Accept Project Work Outside of <Company> Time
It is the policy of <Company> to allow employees to accept and function as independent contractors for other companies/projects while on their own personal time. That being said, the non-compete/confidentiality agreement remains in force at all times and <Company> trusts that this binding agreement will be upheld on the part of all employees and contractors.
It seems like he still wants to make awesome, and is at least well aware of the challenges he faces in selling people on buying into what may be a limited (albeit super dedicated audience)
Use tabs to align stuff on the left. This means putting some_key_1 on the next line. Also move the closing brace to a new line and add a comma after some_var_3.
Added advantage that you can move all of the lines around, :sort them or comment out individual ones without breaking anything.
Use spaces to align anything after the key, I usually align them with a tab stop so that several blocks line up.
They did the math for which year is a leap year incorrectly, which wasn't the bug that bit us, they helpfully added the leap day regardless of where in the year it was. The tests they wrote targeted the middle of the year and missed it. I just pulled in date2j and related match from postgres, added more test cases.