Apparently JSON wasn't enterprisey enough.
Husky
@Husky
Best posts made by Husky
-
IBM's JSONx, or how to represent JSON in XML
-
RE: IBM's JSONx, or how to represent JSON in XML
I'm not sure if you can make an application that speaks JSON be understood by an application that speaks XML using this. From what I gathered, you can represent JSON in XML, not translate.
But I agree, it can have some real, practical uses. Though everything I can imagine that might need this is very probably a WTF by itself...
-
RE: TempleOS and HolyC (Again. I think there's already a thread. Oh well.)
As for metadata - it seems like a cool debugging feature (you have a fluctuating value and you hint the debugger to keep the maximum somewhere without coding a separate variable in).
In 1980, Ada was invented. This is an example of a data type in it:
type Temperature is range 0 .. 100;
Whenever you either try to assign a value outside the range or an operation on it leaves it outside the range, something akin to an exception happens. Not too sure on the actual word and exact functionality, but the idea is the same.
Not sure if that's what you meant, but it sounded like.
Also, you wouldn't believe how much energy a person with mental problems has until you've seen it. Seriously. A girl I know did physically taxing work nearly non-stop for 20 hours, because she believed God had told her to do so. -
RE: Representative jQuery; or Appendicitis
I'd agree completely with you, but jQuery is easy to refactor and doesn't allows nearly as many awesome 1337 tricks that I prefer to fix a jQuery mess than pure JS.
-
RE: Linus RAID failure: suspense / horror thriller for IT professionals (video)
does not allow any deletions, except with a 7 day waiting period or something.
I've once made
rm
superuser-only in a server I was helping my school set up. It broke about a thousand different things and made admin stuff a hassle, but it honestly saved a few man-months of taking it offline to recover some file someone put in the desktop and another teacher thought it was fine to delete.
Don't judge me too much, I was 14 at the time. -
Representative jQuery; or Appendicitis
$myBoss: "Hey, you know that thing you did in the $websitePart, that 'clearbox' thing?"
$me: "Yeah, what about the lightbox?"
$myBoss: "You could add that to the comment system? We got complaints it's not too clear where one should type."
$me: "Uh, sure. It'll be done by monday."Mini-WTF: I added a transparent background to a dialog screen and since a designer called it a lightbox (which is the name of a bunch of jQuery plugins) the name stuck.
Ok, whatever, I decided to look how the HTML of the comment system was done. When I saw it was dynamically generated, I expected something terrible, but not... This.
Comments.html = $('<div>').attr('id', 'lightbox').append( $('<div>').addClass('Comments').append( $('<h1>') .append('COMMENTS - ') .append(Comments.dynamicHtml.title) .append(Comments.dynamicHtml.closeButton) ) .append(Comments.dynamicHtml.listComments) .append( Comments.dynamicHtml.form.append(Comments.dynamicHtml.inputMessage) ) ); // Which was presented to me like this: Comments.html = $('<div>').attr('id', 'lightbox').append($('<div>').addClass('Comments').append($('<h1>').append('COMMENTS - ').append(Comments.dynamicHtml.title).append(Comments.dynamicHtml.closeButton)).append(Comments.dynamicHtml.listComments).append(Comments.dynamicHtml.form.append(Comments.dynamicHtml.inputMessage)));
My best wishes go to whoever is employing this guy right now.
-
RE: Pretty Aggressive Code
Not allowing
SELECT *
in any circumstances is as bad as allowing it freely to my eyes.I mean, the idea is good and I'm considering doing a few ctrl+f's in my codebase to have a talk with the junior developers, but pretty much every project that doesn't has a big focus on performance might have a pair of
SELECT *
to simplify code.Or I might be completely wrong and people will derail this topic because of me.
-
Typecast string to int inside query string
Ran across this today. git blames a new developer, fresh out of college.
Cringed harder than that time he tried to make a SQL query inside Javascript by embedding PHP tags inside the JS file.$db->query("SELECT association FROM UserClasses WHERE codClass=(int)'$this->codClass' AND codUser=(int)'$this->codUser'");
For non-PHP guys, the following is correct, as you can't typecast inside a string:
$db->query("SELECT association FROM UserClasses WHERE codClass='".(int) $this->codClass."' AND codUser='".(int) $this->codUser."'");
Latest posts made by Husky
-
RE: Linus RAID failure: suspense / horror thriller for IT professionals (video)
does not allow any deletions, except with a 7 day waiting period or something.
I've once made
rm
superuser-only in a server I was helping my school set up. It broke about a thousand different things and made admin stuff a hassle, but it honestly saved a few man-months of taking it offline to recover some file someone put in the desktop and another teacher thought it was fine to delete.
Don't judge me too much, I was 14 at the time. -
RE: $40 for a career
Hell, PSP 7 still works fine. Tried 8 once, but it took a slight delay to load while 7 was instantaneous.
-
RE: TempleOS and HolyC (Again. I think there's already a thread. Oh well.)
As for metadata - it seems like a cool debugging feature (you have a fluctuating value and you hint the debugger to keep the maximum somewhere without coding a separate variable in).
In 1980, Ada was invented. This is an example of a data type in it:
type Temperature is range 0 .. 100;
Whenever you either try to assign a value outside the range or an operation on it leaves it outside the range, something akin to an exception happens. Not too sure on the actual word and exact functionality, but the idea is the same.
Not sure if that's what you meant, but it sounded like.
Also, you wouldn't believe how much energy a person with mental problems has until you've seen it. Seriously. A girl I know did physically taxing work nearly non-stop for 20 hours, because she believed God had told her to do so. -
RE: Pretty Aggressive Code
I think the primary reason that he didn't like it is that only looking at the query doesn't tell you what fields the query returns.
This and the code smell are the main problems I see.How frequently do you need all columns in the table, though? In all my projects, that ratio was around 20% of all queries, up to nearly 90% in reports. We're probably doing something very wrong in the database design according to this topic.
Boomzilla's method makes a lot of sense though.
-
RE: Pretty Aggressive Code
Not allowing
SELECT *
in any circumstances is as bad as allowing it freely to my eyes.I mean, the idea is good and I'm considering doing a few ctrl+f's in my codebase to have a talk with the junior developers, but pretty much every project that doesn't has a big focus on performance might have a pair of
SELECT *
to simplify code.Or I might be completely wrong and people will derail this topic because of me.
-
RE: IBM's JSONx, or how to represent JSON in XML
I'm not sure if you can make an application that speaks JSON be understood by an application that speaks XML using this. From what I gathered, you can represent JSON in XML, not translate.
But I agree, it can have some real, practical uses. Though everything I can imagine that might need this is very probably a WTF by itself...
-
IBM's JSONx, or how to represent JSON in XML
Apparently JSON wasn't enterprisey enough.
-
RE: Check out our BRAND NEW ISO specification for $138 ONLY! ORDER NOW!!!
But the real question is whether ".porn" would be for pictures or movies.
Container format, allows a whole range of codecs, from text-only for stories and ASCII porn to images and videos. Duh.
-
RE: Representative jQuery; or Appendicitis
I'd agree completely with you, but jQuery is easy to refactor and doesn't allows nearly as many awesome 1337 tricks that I prefer to fix a jQuery mess than pure JS.
-
Representative jQuery; or Appendicitis
$myBoss: "Hey, you know that thing you did in the $websitePart, that 'clearbox' thing?"
$me: "Yeah, what about the lightbox?"
$myBoss: "You could add that to the comment system? We got complaints it's not too clear where one should type."
$me: "Uh, sure. It'll be done by monday."Mini-WTF: I added a transparent background to a dialog screen and since a designer called it a lightbox (which is the name of a bunch of jQuery plugins) the name stuck.
Ok, whatever, I decided to look how the HTML of the comment system was done. When I saw it was dynamically generated, I expected something terrible, but not... This.
Comments.html = $('<div>').attr('id', 'lightbox').append( $('<div>').addClass('Comments').append( $('<h1>') .append('COMMENTS - ') .append(Comments.dynamicHtml.title) .append(Comments.dynamicHtml.closeButton) ) .append(Comments.dynamicHtml.listComments) .append( Comments.dynamicHtml.form.append(Comments.dynamicHtml.inputMessage) ) ); // Which was presented to me like this: Comments.html = $('<div>').attr('id', 'lightbox').append($('<div>').addClass('Comments').append($('<h1>').append('COMMENTS - ').append(Comments.dynamicHtml.title).append(Comments.dynamicHtml.closeButton)).append(Comments.dynamicHtml.listComments).append(Comments.dynamicHtml.form.append(Comments.dynamicHtml.inputMessage)));
My best wishes go to whoever is employing this guy right now.