The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
So I'm working on this application that creates files according to some early 90's "standard"...
I'm not sure how many applications use this standard, but not a lot.
The only application I've tested with, that can read these files, already made a mess of the standard, as did a sample file I got.
So anyway, the standard has a list of companies and codes, which is a bad idea because companies quit and start and so you have a standard that's constantly moving.
It's only a very specific niche type of company, so it's not like it changes daily, but once every few years at the least.
Judging from the names still in the list and some rather big companies missing, I can only assume this list is changed rather infrequently and code 099 (unknown) is used in a lot of cases.
Now we want our company (with two locations) to be added to the list, so we sent out a mail requesting new codes.
And bam, we got an email back saying that they're now added...
But what about everyone else who uses this standard?
What about the software that has to interpret these values?
You can't just change the standard because Sander send you an email (if only! ).
This is not how a standard works!
How about we use a government issued number that every company in this business is legally required to have?
And then maybe look up that number in some public repository.
Perhaps a CoC number or a number that's specific to this industry (there are actually more than one to choose from)?
Of course it would require considerate effort of all parties involved to implement that now
I'm just very quietly hoping these values are completely ignored by all parties using this standard (we've seen that to be the case for some other mandatory fields as well)
Been working on this for three months and every month I get a little sadder
Luckily this project is in it's final stage and we'll soon start a pilot with some customers.
The next project will not feature any standards except my own
I'm translating from German to Dutch, but it makes no sense...
Google Translate asks me if I meant Luxembourgish
Makes slightly more sense from Luxembourgish though
Playing database in a file, huh?
It's not even a file I'm creating or sending, just a very long string.
I put it in the database, a client asks for it using a SOAP service, I send the string and the client application puts it in a file.
But everyone around this standard keeps talking about files and I kind of stuck with it
I wouldn't be surprised if others actually used files to store this data in a back-end though.
I think even the documentation says I should use files.
Stupid documentation can't tell me how to store my data...
The only file I get is a CSV from a source application, but only because there really is no other way
You should try then with "lerne bayerisch"... It sometimes hurts in the eyes, seeing how it is written
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Standards are attempted by team managers who get tired of fixing the same exact type of bug over and over. So they come into the world through the best of intentions.
The problem with standards is that they can limit creativity, which itself is a critical part of programming.
So, how do you have both? That is the big question we are all still trying to find the answer to. There are lots of ideas and attempts, which means there is a lot to research and a lot more that can be tried.
Last Visit: 31-Dec-99 18:00 Last Update: 13-Jun-21 15:45