Post AFaJS8FtuDR9jnLudc by cincodenada@cybre.space
(DIR) More posts by cincodenada@cybre.space
(DIR) Post #AFaH1vUmWaicj3gnMe by cincodenada@cybre.space
2022-01-19T02:08:07Z
0 likes, 1 repeats
Okay so I thought I had realistic expectations of Atlassian products, but they just keep finding new and appalling ways to surprise me.At least the error message tells you exactly what kind of ass-backwards decisions they've made so you can adjust, I guess.
(DIR) Post #AFaH1vviuQGm4cIJMG by pry@raru.re
2022-01-19T02:24:40Z
0 likes, 0 repeats
@cincodenada this is so incredibly cursed wtf... WHO SIGNED OFF ON THIS??
(DIR) Post #AFaICZjjrasgNjKKzQ by cincodenada@cybre.space
2022-01-19T02:36:04Z
1 likes, 0 repeats
Update: it gets worse!!The placeholder text uses hyphens as separators, but the calendar control inserts slashes.So what happens if you literally type in the suggested placeholder text? Surely they wouldn't suggest an invalid format?If you guessed "of course they would" congratulations! You have the correct amount of faith in Atlassian's quality control! Blisteringly cursed software design, stratospheric levels of dgaf.Bonus: yes, the placeholder dates are in January *2012*, and I would not be surprised in the least if that means this code hasn't been updated in over a decade.
(DIR) Post #AFaJQou8MotfQpXsxs by cincodenada@cybre.space
2022-01-19T02:51:34Z
0 likes, 0 repeats
@pry Oops it got worse: https://cybre.space/@cincodenada/107646796712147250
(DIR) Post #AFaJS8FtuDR9jnLudc by cincodenada@cybre.space
2022-01-19T02:51:49Z
0 likes, 0 repeats
@pry Guess what, it got worse: https://cybre.space/@cincodenada/107646796712147250
(DIR) Post #AFaLG2rMLDq3R6EnGC by 00dani@elekk.xyz
2022-01-19T02:17:59Z
0 likes, 0 repeats
@cincodenada "MMM"? three of them??? what the fuck
(DIR) Post #AFaLG3MCUYVaykfQKe by cinebox@cybre.space
2022-01-19T02:20:46Z
0 likes, 0 repeats
@cincodenada @00dani the forbidden 100th month
(DIR) Post #AFaLG3nqpkcuMVbVQm by Seirdy@pleroma.envs.net
2022-01-19T03:12:01.256600Z
0 likes, 0 repeats
@cinebox @cincodenada @00dani Happy Julianuary.Anyone who understands this reference gets to join my cool kids club.
(DIR) Post #AFaRHDVMqaqcSytQhc by fence@xyzzy.link
2022-01-19T04:19:30.967476Z
0 likes, 0 repeats
@cincodenada what even is that format???
(DIR) Post #AIZ1YIDMtZnbmln9qS by cincodenada@cybre.space
2022-01-19T03:06:48Z
0 likes, 0 repeats
Update: it gets worse!!The placeholder text uses hyphens as separators, but the calendar control inserts slashes.So what happens if you literally type in the suggested placeholder text? Surely they wouldn't suggest an invalid format?If you guessed "of course they would" congratulations! You have the correct amount of faith in Atlassian's quality control! Blisteringly cursed software design, stratospheric levels of dgaf.Bonus: yes, the placeholder dates are in January *2012*, and I would not be surprised in the least if that means this code hasn't been updated in over a decade.
(DIR) Post #AIZ1YJGaz3yV34JFVw by cincodenada@cybre.space
2022-01-19T03:12:12Z
0 likes, 1 repeats
I don't do a lot of criticizing other people's software projects because I'm a developer and, like, software is hard! It's easy to screw stuff up!But the level of inconsistent shoddiness that Atlassian dependably puts out is organizational-level failure. This is not criticism of any of the developers involved, because they don't even have the ability to fail on this level.Atlassian is a company whose priorities are perfectly demonstrated by the fact that they spent engineering and support time implementing and defending a mandatory feature that autocorrects the capitalization of their brand names everywhere across their whole platform, a feature that serves literally no value to end-users: https://community.atlassian.com/t5/Jira-questions/Jira-gt-Deactivate-autocorrect-in-Jira-issues-comments-etc/qaq-p/1186807The end-user experience in their software is literally just not prioritized. Which unfortunately is a viable business model if the people you're selling the product to are not the ones using it.
(DIR) Post #AIZ1YNIVzrt3YBEq3s by cincodenada@cybre.space
2022-01-19T03:37:14Z
0 likes, 0 repeats
Welp, @avocatto couldn't just let this one lie, and observed that with two-digit years, you've got Y2K problems, right?You sure do. So I dug in: I figured they probably implemented the solution you use if for some reason HAVE to deal with two-digit dates (which they don't, but chose to anyway).You just pick a number, and assume any dates before that number are 20xx, and after are 19xx. For something like JIRA where you're not really recording historical data, you can probably get away with this. You're not gonna have tickets opened before, like, 1980, maybe pick 1970 cause it's the epoch, there, you're future proof for 50 years.So I went to test, and was surprised when 50 was interpreted as 1950...and a few astonished trials later: jimminy cricket on a bobsled, they chose nineteen-FORTY-TWO as the first year to assume is 19xx :blobthinkingeyes: :thonking: I really, really wish I were making this up because I am at a loss as to how you even begin to end up here. Stumped.
(DIR) Post #AIZ1YNJZvujnbTjgie by cincodenada@cybre.space
2022-01-19T03:14:11Z
0 likes, 0 repeats
(Apologies to folks who boosted or replied to the original version of this post: I went to redraft the *reply to this post* cause it had a pretty critical typo at the end, but redrafted this one instead, womp womp)
(DIR) Post #AIZ1YPFOkQa9b5nNTs by cincodenada@cybre.space
2022-01-19T03:40:52Z
0 likes, 0 repeats
My only guess, given the placeholder dates, is that this code was also written in 2012, and they decided that 30 years of buffer was good enough. Just bonkers decisionmaking.