The next Slay the Spire to be developed on Microsoft Access
Comment on It's a mass extinction event
TheFerrango@lemmy.basedcount.com 1 year agoTime to become a Visual Basic .Net developer
Rentlar@lemmy.ca 1 year ago
Comment on It's a mass extinction event
TheFerrango@lemmy.basedcount.com 1 year agoTime to become a Visual Basic .Net developer
The next Slay the Spire to be developed on Microsoft Access
Wild_Mastic@lemmy.world 1 year ago
Jokes on you, I am already one! (yes my company chosen dev language is really vbnet)
Heavybell@lemmy.world 1 year ago
My old boss loved VB.Net. I still remember a time when I helped him out by solving mysterious bug for him.
He used to have this class he copied about to do database stuff. Not the worst thing of itself, but it was oddly specific in some ways for reused code. E.g. It had a function that took an enum value and returned connection string. And of course what options were in the enum varied.
So I come in one day and two other devs are already peering over his shoulder trying to help. The program is crashing when it tries to connect to the database and they can see for some reason the connection string is a single letter. I ask to see the function that is getting the connection string and see he’s removed the parameter, but the compiler didn’t pick up on it because:
So instead of passing an enum to a function, it was calling the function with no parameter, then using the enum value to index the returned string into a single character, which was then treated as a string and passed to the SqlClient constructor.
Wild_Mastic@lemmy.world 1 year ago
I saw something similar in ancient code I found while refactoring some stuff. It’s between genius and maniac.
amio@kbin.social 1 year ago
I'm so sorry.
TheFerrango@lemmy.basedcount.com 1 year ago
All I’m saying is “AndAlso”
Wild_Mastic@lemmy.world 1 year ago
OrElse
lanbanger@kbin.social 1 year ago
I remember when I turned up to a new C# role, when all the interviews had been about C#, and the system was all VB.Net. Fckmylife.