RmDen
Joined 11 years ago
Joined 11 years ago
Was testing code and pushed a file to FTP 2 days early... vendor picked up, processed file.. the people who signed up in the next 2 days were in the file pushed later... but the vendor already processed the earlier file so they didn't get their metro cards that month
Somehow managed to rebalance underlying components for a Trendpilot ETF monthly instead of quarterly... daily audit that compares the values on NYSE vs in our DB caught it.. lucky for me there was no money in it yet
dropped a table once at lunch time right before taking a bite of my sandwich... did restore table within 10 minutes , didn't eat lunch that day ... lost appetite...
In ETL tool hardcoded something to test.... left it there when running for real
Not out of the ordinary to see a SQL Server query using 20+ cores for a query with a parallelized plan
if null = null print 'true' else print 'false'
Also a null is no equal to anything.. not even another null
This will print false in SQL Server
if null = null print 'true' else print 'false'
If you get the measurements wrong, your end product will be 'wrong' Cooking gives you ways to fix your mistakes.. (add water, cook it more, add spices etc etc)