![]() ![]() Then there's the stuff that's "open source" but effectively "look but don't touch" because they are so massive or otherwise locked out in some other way. People not knowing the fundamentals - because the industry doesn't like for it to be widely known that a lot of DRM and other user-hostility can be disabled with changing a single bit, for example - thinking open-source is somehow a panacea, then either wondering why it's so difficult to fix what should really be a simple thing that is "open source", or spending a ton of time trying to do it anyway. With no need to know assembly and how to reverse engineer a binary. and especially on that old OS the message itself can be cryptically short, likely because even a few bytes still cost serious money in the beginning. Most likely because IBM really does not expect you to encounter that error on a mainframe delivered since, say, the Berlin Wall fell.Įven if I wanted to, I doubt IBM wants to sell me a support contract for their 4 decades old last public domain version of their mainframe OS on an emulator. The problem is, the original handbooks are hard to come by, and while another wonderful thing (in some aspects) is that a modern, current mainframe is still compatible with that old code from the 70s, and so you can use their resources, you sometimes encounter error codes where the description is basically just "contact IBM". If you ever used OS/2 you might have seen that, too. Playing around with a mainframe OS from the 70s (I'm weird like that), I realized that IBM has that wonderful thing where nearly every message has a code that you can use for lookup. Now if you'll excuse me, I'll be contacting Atlassian support to help me fix the "Something is wrong" message. And even if I do figure it out, I'm powerless to change the situation. It's much harder to figure out what's going wrong with closed source software. ![]() ![]() Once I do that I can either fix the issue, work around it, or even submit a PR upstream. I've often delved into the source code to understand what's going on. Since software can be a lying devil, I am happy that I can make use of so much open source software. Maybe it's not a misleading error message, but it's certainly an unhelpful one. but I'm the administrator! And I don't know what's wrong. It popped up an error message saying "Something is wrong. After the upgrade I got an error in the administrative section of the app. Recently I upgraded Jira Service Desk (new name: Service Management) to a new version. It's even worse when I have to think "What part of the system is lying to me?" As a software developer, it's bad enough that I have to constantly challenge my assumptions to try to debug something. ![]()
0 Comments
Leave a Reply. |