Post 9he3svd93RfVSFEgPA by dax@niu.moe
(DIR) More posts by dax@niu.moe
(DIR) Post #9he3svd93RfVSFEgPA by dax@niu.moe
2019-04-09T22:42:13Z
0 likes, 0 repeats
well, today was quite a dayI was handed a monolothic legacy C# app and a card reader with shitty docs and told, "make this app talk to this reader"I spent most of the day poking around with the docs and API of the reader, so I'll probably spend tomorrow plowing through that ghastly codebase:blobdead: I heard them tell a client "we've got the new guys on it, so give it a month or so", so I guess that's a deadline to work with
(DIR) Post #9he3svmMVB2bupY2ls by dd86k@shelter.moe
2019-04-09T22:44:48Z
0 likes, 0 repeats
@dax C# eh, been a while I didn't touch that. I guess if you need help, I'm around. I think my C# skills may be a little rusty.
(DIR) Post #9he4UNIBAgabxdHj6G by dax@niu.moe
2019-04-09T22:51:34Z
0 likes, 0 repeats
@dd86k half the problem is C#, and half the problem is a convoluted Visual Studio project
(DIR) Post #9he4aV6z0nQHwwy9PE by dd86k@shelter.moe
2019-04-09T22:52:41Z
0 likes, 0 repeats
@dax Oh boy. Today I just finally compiled the biggest thing in our corporation VS solution (has like 40 projects in it, legacy stuff)
(DIR) Post #9he4owOeMcLecv7OhU by dax@niu.moe
2019-04-09T22:55:18Z
0 likes, 0 repeats
@dd86k yeah, I was just given a Microsoft account and an Azure URL, then told to pull it and work on it
(DIR) Post #9he55aUh3ANXcVsnOi by dax@niu.moe
2019-04-09T22:57:50Z
0 likes, 0 repeats
@dd86k apparently one of the ex-devs was REALLY into Microsoft, so the team is now stuck with C#, Visual Studio, Azure, and Microsoft Teams on Windows 10its becoming a problem for clients because their computers keep restarting for long updates during working hours, and we can't defer updates longer than 12h apparently
(DIR) Post #9he55bMZopTqJd5pNw by dd86k@shelter.moe
2019-04-09T22:58:18Z
0 likes, 0 repeats
@dax oof