This is honestly exactly what programming is: breaking down big problems into step by step simple problems. If you’ve never considered taking up programming before, I’d suggest you try it sometime and see where it takes you. It’s not hard to learn, it just takes time.
We call that pseudocode and it looks fine to me. No computer will run it natively (AI meat grinders aside), but most devs will be able to pick up on the logic and convert it to actual code.
My favorite is the fact that Microsoft intentionally left a bug in Excel that treats 1900 as a leap year when it wasn’t so they could maintain compatability with Lotus 1-2-3. And at this point fixing it would cause nearly every date value in excel files to display as off by one day and break a bunch of date formulas.
Wow I’ve seen some really weird backwards compatibility issues, but this takes the cake. I would have imagined that in the move to XLSX they could have addressed this and sorted it out when saving, but nope, I guess having all days off by one and maintaining a support page explaining Lotus123 backwards compatibility for forever is earlier?
What is this? Some sort of COBOL or something.
deleted by creator
COBOL is an old language Internet to make programs look a bit like English descriptions of what was needed.
I don’t really know it, but your code reminded me of the idea of it.
Don’t worry if your code is incorrect, just make random changes until you hit on something that no longer results in errors :)
This is honestly exactly what programming is: breaking down big problems into step by step simple problems. If you’ve never considered taking up programming before, I’d suggest you try it sometime and see where it takes you. It’s not hard to learn, it just takes time.
You should program
We call that pseudocode and it looks fine to me. No computer will run it natively (AI meat grinders aside), but most devs will be able to pick up on the logic and convert it to actual code.
Disclaimer: am a programmer
My favorite is the fact that Microsoft intentionally left a bug in Excel that treats 1900 as a leap year when it wasn’t so they could maintain compatability with Lotus 1-2-3. And at this point fixing it would cause nearly every date value in excel files to display as off by one day and break a bunch of date formulas.
https://learn.microsoft.com/en-us/office/troubleshoot/excel/wrongly-assumes-1900-is-leap-year
Wow I’ve seen some really weird backwards compatibility issues, but this takes the cake. I would have imagined that in the move to XLSX they could have addressed this and sorted it out when saving, but nope, I guess having all days off by one and maintaining a support page explaining Lotus123 backwards compatibility for forever is earlier?
Can confirm Source: am a grammerpro