Junilu Lacar wrote:Here's how I might do it in Kotlin
Lou Hamers wrote:I see the same kind of messiness in personal experience from actual business supporting projects. You rarely see a project that doesn't have a large number of messy warnings that the devs simply ignore. Projects I have the lead on are the only ones that come close to being "clean", and even then, they still aren't. (I always lecture my developers a little, "Warnings sometimes turn out to be bad errors in disguise, but there isn't any value in warnings if there's so many of them that they're ALL ignored.") If so many devs won't even pay attention to a simple thing like a javac warning or an IDE warning
Campbell Ritchie wrote:I never knew that rounding mode was called banker's rrounding.
Junilu Lacar wrote:It's a little surprising for me when I get that kind of reaction; it's as though people have never heard of top-down design vs bottom-up design. Is that something that only folks from older generations know about now? I don't get it. I grew up in the Structured Analysis and Design era and starting top-down seems more sensible to me.
Mark Sando wrote:Not sure if it's of any relevance, I use postman to hit the endpoints
Piet Souris wrote:rot13, rot17, ...: that somehow reminds me of Advent of Code 2022, day 11!
Mark Roberge wrote:Then how do I make it executable?
Earlier, I wrote:And no, I did not modify any of the actual code.
Paul Clapham wrote:Some of which have 4 characters which are all different.
Stephan van Hulst wrote:..it took me a few minutes to trim the answer down to 4 characters