Loved the epidsode! My name is Jeff True and we have had problems with computers and the name "True". If someone use something like an Excel spreadsheet to store names, it will change True to the formula expression True/False. We have had diplomas, sports jerseys, etc printed incorrectly because the computer was confused. I really resonated with this one!
@@hyretech I'm not in direct contact with code that handles customer records, but in a recent role, I found code to write out config records that converted the special Pandas value called nan to the string "nan". (nan means "not a number", but it's basically Pandas' version of NULL). I changed it to convert nan to an empty string, and the code started failing. I discovered we had code that was expecting empty fields to be represented by the string "nan," but treated empty strings like actual values. When I told the team about this, I was told "It's not a bug, it's a design decision" and got yelled at for breaking the expectation. I was like "you did that on purpose?" In order to support legacy records, we ended up using a test for empty fields that included any of the following: Python's None, the string "None", the empty string, and the string "nan". I was pretty sure we didn't need to do that because we could easily update all the records, but the rest of the team viewed change as riskier than living with bad code, so it stayed that way. I left that role, but my new role at the same company involves dealing with equally ridiculous code.
I know someone name Null, he is always having to like spell it wrong just ti sign up for an app. Said he has seen entire screens pop cover over his page, full of computer jargon/code stuff.
Loved the epidsode! My name is Jeff True and we have had problems with computers and the name "True". If someone use something like an Excel spreadsheet to store names, it will change True to the formula expression True/False. We have had diplomas, sports jerseys, etc printed incorrectly because the computer was confused. I really resonated with this one!
i bet you're not looking forward to legal sentencing being done by computer ;p
I listened to this last night. Sharing widely at the financial organization where I work as a developer... ;)
Let us know what % of your company's code fails the test.
@@hyretech I'm not in direct contact with code that handles customer records, but in a recent role, I found code to write out config records that converted the special Pandas value called nan to the string "nan". (nan means "not a number", but it's basically Pandas' version of NULL). I changed it to convert nan to an empty string, and the code started failing. I discovered we had code that was expecting empty fields to be represented by the string "nan," but treated empty strings like actual values. When I told the team about this, I was told "It's not a bug, it's a design decision" and got yelled at for breaking the expectation. I was like "you did that on purpose?"
In order to support legacy records, we ended up using a test for empty fields that included any of the following: Python's None, the string "None", the empty string, and the string "nan". I was pretty sure we didn't need to do that because we could easily update all the records, but the rest of the team viewed change as riskier than living with bad code, so it stayed that way. I left that role, but my new role at the same company involves dealing with equally ridiculous code.
Very happy to see that it’s still a radio program ☺️ I was worried abouut finding out that it became a youtube “tv show”. Miss Jad
I would automatically assume that someone is an arch user if they had a license plate saying "RTFM"
I know someone name Null, he is always having to like spell it wrong just ti sign up for an app.
Said he has seen entire screens pop cover over his page, full of computer jargon/code stuff.
This is a good one🥰👍
People's first name #
X Æ A-Xii