The Official Status Thread
-
-
Status: This is used in every single AJAX error handler in a table control used all through the application. Verbatim.
function OnFault() { alert('fault'); }
-
Aww, I kinda hoped it was a "we made it purrty!" remake of the original. Oh well, not like the original is ugly, I just hoped for a polished version.
Also, maybe I should give up on my chronological plan thing and just play some damned Zelda?
-
Daewoo? Daewoo makes microwaves now?
Daewoo makes all sorts of stuff, from microwaves to cars to oil tankers. And firearms, apparently…
-
Status: LOL'd because GNU Hurd turned v0.6 this week.
No rush, guys. The world is gonna wait on you.
-
STATUS: A bunch of Pakistanis suddenly decided to add me on LinkedIn today.
Umm.... I'm flattered? CIA please don't assassinate me?
-
Slight headache still present. Really want a smoke right now. Fuck me, that makes no sense.
I agree, it doesn't make any sense. You are only going to get soaked in the rain and won't be able to light your tar-stick.
-
####Status:
Deleting a group of users makes the users in that group inaccessible (because the group gets
DELETE
d from the database and the Users don't get touched).I was told to just disable the deletion buttons for groups with users in them and not adjust the deletion procedure to do such checks / delete affected users.
I guess that ... uh ... works? Doesn't feel safe, though.
-
Deleting a group of users makes the users in that group inaccessible (because the group gets DELETEd from the database and the Users don't get touched).
I was told to just disable the deletion buttons for groups with users in them and not adjust the deletion procedure to do such checks / delete affected users.
I guess that ... uh ... works? Doesn't feel safe, though.
That's a frontend fix for a backend problem. Bad!
-
I was told to just disable the deletion buttons for groups with users in them and not adjust the deletion procedure to do such checks / delete affected users.
Hey, stupid idea... Ummm... Get the DBA people to put actual constraints on the tables so the data integrity gets checked by the, you know, the thing that is supposed to care about data integrity? Not fucking disabled buttons?
EDIT: FUCK YOUR RATE LIMITS! I LIKED A SINGLE POSTS AND YOU COCKBLOCK ME FOR 10 MINUTES? FUCK YOU JEFF!
-
Deleting a group of users makes the users in that group inaccessible (because the group gets DELETEd from the database and the Users don't get touched).
So there isn't an FK relationship fromUser
toGroup
? Because having one would stop the deletions long before they break anything (guessing at table names btw).
@aliceif said:I was told to just disable the deletion buttons for groups with users in them and not adjust the deletion procedure to do such checks / delete affected users.
The front-end fix is OK, but it should really be fixed in the back-end too.
@aliceif said:I guess that ... uh ... works? Doesn't feel safe, though.
It isn't safe; the UI can't guarantee the integrity of the back-end.
@Onyx said:EDIT: FUCK YOUR RATE LIMITS! I LIKED A SINGLE POSTS AND YOU COCKBLOCK ME FOR 10 MINUTES? FUCK YOU JEFF!
I swear something's up; I've asked PJ if the upgrade fucked the Like limit.
-
So there isn't an FK relationship from
User
toGroup
? Because having one would stop the deletions long before they break anything (guessing at table names btw).Not necessarily. Constraints do allow you to specify
ON DELETE NO ACTION
.It isn't safe; the UI can't guarantee the integrity of the back-end.
Bonus points if it were a web UI and buttons disabled by JS.
I know it's not in this case, but I'm honestly waiting for something like that on the frontpage, any day now.
-
Bonus points if it were a web UI and buttons disabled by JS.
Oh, there's an ASP.NET WebForms thingie for it.
Don't worry, I'll disable the buttons server-side there.
-
Not necessarily. Constraints do allow you to specify
ON DELETE NO ACTION
.
Constraints allow you to turn off referential integrity?
-
Status: Nice try
That actually got through the Outlook.com spam filter. About which I'm alsoYes, that's my real first name. No, it's not the first time I've posted it here; that's why I didn't bother censoring it. Besides, it's piss easy to find my real name elsewhere; I don't exactly hide it.
-
Don't worry, I'll disable the buttons server-side there.
Well, that's an option, I guess. Maybe make them not even render?
I'd still feel better if DBAs just did their job.
Constraints allow you to turn off referential integrity?
Yes. There are edge cases where it's useful. Note the edge bit.
-
I'd still feel better if DBAs just did their job.
We don't have one, though.
So there isn't an FK relationship from User to Group? Because having one would stop the deletions long before they break anything (guessing at table names btw).
They're associated via a table.
-
We don't have one, though.
Oh... okay. Who takes care of the DB then? Please tell me someone takes care of it?
They're associated via a table.
You can still set constraints.
-
@RaceProUK said:
So there isn't an FK relationship from User to Group? Because having one would stop the deletions long before they break anything (guessing at table names btw).
They're associated via a table.
But wh- oh, many-to-many. Still, as @Onyx said, you can still set constraints on the relationships.
-
Yes, that's my real first name.
-
WHAT THE EVERLOVING FUCK?!?!
If oNode.Tag.GetType().ToString().Contains("Organisation") Then
-
Seriously, the whole codebase already doesn't use types properly.
But this takes the cake.
-
But this takes the cake.
Just the cake? Looks more like it's taking the whole bakery to me…
-
But this takes the cake.
To be fair, it does check that it is indeed the cake (or something called "Cake") before it takes it.
-
Status:
Bullshit.
No, sweetheart, daily means once a day. This is like the 14th one of those today. It's wonderful, really. We're worried about square avatars being dehumanizing. Yet, we don't know what the words mean. Don't we,
childrenDiscodevs?
-
Since I'm the only one not up on the level of horror above: can poor old non .NET-speaking me get a bit of an explanation?
Tag.GetType().ToString()
is the worst offender I presume? It looks ugly but I have no idea whatTag
is... XML?
-
In this case,
Tag
looks like it's just a property of whatever type of objectoNode
is; there isn't enough info in that snippet to work out anything more than that.
-
A Windows-Forms-ism: You can add an Object as a tag to a control. In this case, some nodes in a treeview (like potentially
oNode
) have a group as their Tag.
-
Since I'm the only one not up on the level of horror above: can poor old non .NET-speaking me get a bit of an explanation?
Tag.GetType().ToString() is the worst offender I presume? It looks ugly but I have no idea what Tag is... XML?
The root of the WTF is using reflection. Examining type metadata. Slow as hell.
-
I will guarantee you that percentage is dodgy. If you have a 1100w microwave and set it to 50%, I would be willing to wager that it is not even within 15% of 550w cooking power.
Microwave controllers are binary. It's either on or off. The percentage doesn't change the amount of cooking power, but the amount of time the magnetron is turned on.
-
So it's getting the type of the object... casting to a string...
The root of the WTF is using reflection. Examining type metadata. Slow as hell.
Ah, Hanzo'd. So I got that right-ish. Didn't know it actually needs reflection for that.
I join your brigade of -faced people proper now. Cheers.
-
Status: This is used in every single AJAX error handler in a table control used all through the application. Verbatim.
function OnFault() { alert('fault'); } ```</blockquote> Maybe the guy who wrote that misunderstood "de-fault error message"? :rimshot:
-
Didn't know it actually needs reflection for that.
Well, it doesn't if you don't write idiotic code.
You can just sayIf TypeOf oNode.Tag Is OrganisationThingYouActuallyWantItToBe Then
instead.
But I replaced it with aTryCast
thing.
-
casting to a string
Not casting; given aType
object in .NET, callingToString()
returns the fully-qualified type name as a… well, as a string
-
Bingo. Have a cigar!
Oh. right! Have some lukewarm candy then.
-
Status:
Reading the above post while doing pretty much this:
Just without the cool poster. And the cool mug.
The expression fits, though.
-
Status:
Checking some IVR recordings I just got, that the client insisted on recording in-house. The quality is good enough, I guess, but then...
... send an email or SMS ...
No, I did not translate that, that's the English version. So... umm... AFAIK, English speakers refer to those as "texts" or "text messages". So while not wrong, your translation might confuse people not familiar with the fact that "texting" means using "Short Message Service"...
You know what? I don't care any more. They keep rejecting my advices anyway, they are not getting any more.
-
-
-
The cake is a like?
-
Status: after about 36 microwave-related posts I just hit the "scroll to bottom" button. Goddamned you morons talk about boring shit.
-
Nooo, you missed the best part!
STATUS: My new LinkedIn buddies: Malaysians.
My effort to keep myself off the Axes of Evil were in vain.
-
Everyone calls them SMS in Germany, FWIW.
-
My effort to keep myself off the Axes of Evil were in vain.
You could try shoving them into your microwave? How many Watts is it rated?
-
####Status:
Undermotivated. Probably due to it being Friday afternoon.
Also, I'm going to have another coworker next Monday. I really hope he knows what he's doing.
-
Microwave controllers are binary. It's either on or off. The percentage doesn't change the amount of cooking power, but the amount of time the magnetron is turned on.
I know this. They control it through PWM. Due to the dwell of magnetrons, the non-linear relationship to input voltage and cooking power, and the fact that I seriously doubt that any manufacturers make accurate maps of that relationship and then derive algorithms from them and also the wide variance given to cheap parts...I still seriously doubt that 50% on the display is 50% less cooking power. ;)
-
Also, I'm going to have another coworker next Monday. I really hope he knows what he's doing.
-
You could try shoving them into your microwave?
Better use a counter top model for that. I doubt that a wall mount microwave is going to be able to support the weight.
-
Former coworker who did Database and backendy stuff made real messes.
Other coworker that was here when I started (and who still works here) writes completely shit code but he mostly does reports and such, so his code isn't really dangerous. And he is the one of the team who gets along the best with the boss.
Coworker who got here in the 4th quarter of last year is actually competent but only works half-days.
-