Ok, I know this is a joke, but... in all seriousness, I recently moved FreeBSD releases to a quarterly calendar. The first month of the quarter, people are encouraged to finish up their works in progress and get them into the tree; the second month, we have BETA/RC builds every week; and in the third month (usually at the start but not always) I do the final RELEASE build.
This wasn't for any corporatey reason though; it just happened that "every 3 months" is a natural cadence for doing releases. (In a sense it's a 6-month cadence, like e.g. Ubuntu, but we support two major versions at any given time, and their schedules interleave.)
Sometimes a calendar quarter is just a calendar quarter.
hey, author here - I want to get on record that I don't think this is silly at all. I think there is something truthful and useful in dividing and conquering time, it's just that generally the bar is so low right now and we should do better!
Feature request: Please add an endpoint that is by stock ticker (e.g. "https://corporate.watch/AAPL", as some companies do their financial reporting on a different calendar, and it would be nice to reference with respect to their "datetime zone".
Yeah some publicly traded companies have a different 'beginning of the year' but good luck with finding and making one for each (even with some elaborate on-the-fly scripting).
I think the whole effort was to make a funny landing page that would prompt visitors to check the bread-maker objectivetrackr.
It's reasonably easy to get that information from their SEC filings (for public companies), which are all in similar formats, if not exactly the same format. It wouldn't be as hard as you're implying.
Please add an offset functionality to your free solution immediately, as it has now become a core component of our operation, or we will be forced to take legal action.
Also, we appreciate if you could sign a retroactive NDA with our legal team ASAP.
Hello!? No response yet is this project dead or something it has been 30 minutes since the last question. This is very important to a major customer project of ours please get on this.
Real World aside: The other day I tried to 3D print small text. (Not super small, just the usual 0.4 nozzle size.) Comic Sans worked out best for this due to pretty constant line width.
Nothing more corporate / enterprise than deciding the year starts at any point other than January 1st :) (yeah I know all about the fiscal year, which I also find hilarious)
Some of them don't even start on a month boundary, or even on the same day every year. Cisco, for instance, has a fiscal year based on a retail calendar[0]; their fiscal year ends on the last full week in July.
not to be THAT NERD but in the UK at least, the financial year (April 6th - April 5th) was aligned with the start of the new year which was March 25th.
The old financial year started on 25th March, which was also new year's day (and also the point that the year incremented, so if you were knocking around on March 24th 1300 the next day would be March 25th 1301.
But when everyone changed to the Gregorian Calendar - which added 11 days to the calendar to make up for some sloppy Papal mathematicians who didn't believe in things like astronomy or leap years - the tax year had to be shifted to be April 6th, because while everyone else was happy to work around things, the tax office was NOT going to have a tax year that was 11 days shorter because that would have meant less money.
So basically, when the calendar changed happened, new year was set as 1st January (yawn, stupid time to have new year!) at which point the year count incremented up by one year, and the tax year stayed (and still stays) as April 6th, which was really March 25th but with some days tacked on.
ISO 8601 allowing week-based year numbering is even more insane. E.g. In 2007-12-31 (in RFC 3339 format) is allowed to be notated as 2008-W01-1 in ISO 8601. RFC 3339 is superior, partly because it prevents this bullshit.
ISO week numbering is actually sort of neat, because instead of leap days it has entire leap weeks since the 400-year Gregorian cycle has a whole number of weeks in it, but for some reason they decided that a week's year is the Gregorian year in which the Thursday of that week occurs.
We have a P0 to add calendar 445/ 544/ 454. This critical oversight is causing us to lose sales, as our sales folks never know when those companies fiscal year ends, and end up missing budgetary deadlines.
Also, my legal team says your color choices aren't compliant with Section 508, so regrettably, we do have to take legal action.
Edit: EMEA has questions I couldn't answer about GDPR, PII & data governance. Can you please hope on a quick call to see if they also want to sue you?
Offset financial years mean your finance people aren’t working furiously between Christmas and New Years getting the EoY stuff done. I feel bad for the ones in my company every year.
This is fun. Seems like you got several comments here trying to "improve" it's "usefulness". I like it as is, a piece of art on how corporate speak is unrealistically obtuse.
They would have had to add a leap week every five or six years to keep that in sync with the normal calendar - did they do that, or did they just let the calendar drift?
It's been... almost 20 years since I looked at that.
I believe that it had a slightly floating start date.
NetApp fiscal quarters are:
Quarter Three: October 28, 2024 through January 24, 2025
Quarter Four: January 28, 2025 through April 25, 2025
Quarter One: April 28, 2025 through July 25, 2025
Quarter Two: July 27, 2024 through October 23, 2025
And from Wayback (adjusted to fit same ordering)
Quarter Three: October 29, 2018 through January 27, 2019
Quarter Four: January 28, 2019 through April 26, 2019
Quarter One: April 30, 2018 through July 27, 2018
Quarter Two: July 30, 2018 through October 26, 2018
I remember the 4-4-5 from back then (started in '98, was laid off in '09) because we had the old style BIG releases where it was a weekend of things changing (and that was ok). The last weekend of the first month was infrastructure major changes, the last weekend of the second month was software major changes, and the last two weeks of the third month were hard frozen for accounting to not have changes.
You know what is really wild and caused a few bugs in corporate reporting apps? Every 5 or 6 years you need to account for a 14 week quarter. 13 * 7 is 364 so four 13 week quarters will not add up to a calendar year.
6-week December threw off a bunch of reporting last year for my company. The reporting group was not aware of the 6-week fiscal month, and the date dimension table didn't reflect it.
Based on previous discussions during a review with higher ups, there need to be some options as to how the week numbers are counted. Can you action that by KW10.3 and report back. I will create a JIRA ticket for tracking.
Many thanks for your support.
Readit News
This wasn't for any corporatey reason though; it just happened that "every 3 months" is a natural cadence for doing releases. (In a sense it's a 6-month cadence, like e.g. Ubuntu, but we support two major versions at any given time, and their schedules interleave.)
Sometimes a calendar quarter is just a calendar quarter.
I think the whole effort was to make a funny landing page that would prompt visitors to check the bread-maker objectivetrackr.
This is going to push things back to NBD
Are we really still doing the "-r" branding (brandr)? It is so tiresome.
Please add an offset functionality to your free solution immediately, as it has now become a core component of our operation, or we will be forced to take legal action.
Also, we appreciate if you could sign a retroactive NDA with our legal team ASAP.
Thank you.
0 - https://nrf.com/resources/4-5-4-calendar
The old financial year started on 25th March, which was also new year's day (and also the point that the year incremented, so if you were knocking around on March 24th 1300 the next day would be March 25th 1301.
But when everyone changed to the Gregorian Calendar - which added 11 days to the calendar to make up for some sloppy Papal mathematicians who didn't believe in things like astronomy or leap years - the tax year had to be shifted to be April 6th, because while everyone else was happy to work around things, the tax office was NOT going to have a tax year that was 11 days shorter because that would have meant less money.
So basically, when the calendar changed happened, new year was set as 1st January (yawn, stupid time to have new year!) at which point the year count incremented up by one year, and the tax year stayed (and still stays) as April 6th, which was really March 25th but with some days tacked on.
1752 must have been a pretty confusing year.
ISO week numbering is actually sort of neat, because instead of leap days it has entire leap weeks since the 400-year Gregorian cycle has a whole number of weeks in it, but for some reason they decided that a week's year is the Gregorian year in which the Thursday of that week occurs.
Deleted Comment
Also, my legal team says your color choices aren't compliant with Section 508, so regrettably, we do have to take legal action.
Edit: EMEA has questions I couldn't answer about GDPR, PII & data governance. Can you please hope on a quick call to see if they also want to sue you?
No need to appreciate. Signing the retroactive NDA is a non negotiable.
Deleted Comment
Definitely obtuse. Why unrealistic though?
When I worked at Network Appliance (Q1 earnings call is August 27th), they used a strict 4-4-5 calendar. https://en.wikipedia.org/wiki/4–4–5_calendar
This meant that it wasn't "about" 13 weeks for each quarter, the quarter was defined as 13 weeks (91 days).
I believe that it had a slightly floating start date.
And from Wayback (adjusted to fit same ordering) 2018-19: https://web.archive.org/web/20180626150216/https://investors...2019-20: https://web.archive.org/web/20200430103748/http://investors....
2021-22: https://web.archive.org/web/20210802092405/https://investors...
2022-23: https://web.archive.org/web/20221001020458/https://investors...
2023-24: https://web.archive.org/web/20230607023812/https://investors...
It appears that it floats a little bit.
I remember the 4-4-5 from back then (started in '98, was laid off in '09) because we had the old style BIG releases where it was a weekend of things changing (and that was ok). The last weekend of the first month was infrastructure major changes, the last weekend of the second month was software major changes, and the last two weeks of the third month were hard frozen for accounting to not have changes.
Thankfully no particular harm was caused by it.
Sounds easy, right? Just something like:
https://aakashkh.github.io/python/2019/05/30/Business-Days-C...
But then a wild Holiday appears:
https://fastercapital.com/content/Business-Day--Business-Day...