
I hate Subversion, on all of the days that end in merging back to trunk.
It is giving me all of the feels, except the happy.
public static function process($sets, $departmentPeople, $peopleDepartment, $rules) { $membersOnlyDepartments = $rules['membersOnlyDepartments']; if (!is_array($membersOnlyDepartments)) { $membersOnlyDepartments = array($membersOnlyDepartments); } $backdoorUsers = $rules['backdoorUser'];...This, but SQL, and whoa simpler.
Apparently the same rules that apply to Lolita apply to IT. Very well put.
This is exactly why SQL exists. Except some derp face decided SQL wasn’t good enough for directory information, so they had to go and make LDAP. And another derp decided that the best way to populate contacts into a particular “enterprise” version of an open source chat system is by making someone upload a giant spreadsheet mapping every account, to every contact by contact group. Considering our organizational rules about people with multiple departments getting multiple contact entries per account and people with tin-foil hats in groups that should only be visible to people in that group… it generates over 62,000 rows for 250 or so accounts.
This function happens way after all the LDAP mining has been done (and we have to merge contacts from two different Active Directories using LDAP).
Instead of one SQL statement with sub-SELECTs and JOINs that would then INSERT/UPDATE this data into the database, this program has to get all contacts, map the right fields (because they are different in each LDAP), normalize data, nestedly loop a billionty times to map relationships between people and their departments. Then it loops a billionty times again to create this crazy spreadsheet matching every person to every other person.
The complicated AND/OR in this function was a real favorite of mine.
You’d think IT people would be forward-thinking enough to give their brethren clear technical requirements.
No.
This extra logic handles the fact that when we have new people to add, we don’t yet know if we are supposed to dump all the old contacts and submit them all, or only submit the new contacts. Assuming the latter we have to decide who to add and generate only rows giving them a contact for everyone else and everyone else a row for them.
It would have been better to filter out people during the LDAP mining part, but since we didn’t know about this possible extra requirement until well after the fact, it turns out to be much “easier” to filter on output :/
On a related note, someone else left our little career starter a few weeks ago, so my group “inherited” another “application” that had been developed outside of IT proper.
Not only did they take SQL and treat it like a spreadsheet, they made it a very bad spreadsheet. I kid you not, it’s like someone decided to make a performance art project out how badly you could misuse SQL.
I think after we finish Will and Grace Brian and I will have to watch Dr. Who. I at least know what these creepy fuckers are all about.
Yeah, we all got wooden nails, we’re tongue tied to a hate factory
So glad this week is over. People have been working my ever-fucking-last-nerve. I didn’t even punch them in their stupid face.
Rewarded myself with an Adventure Time hoody. Maybe next week that’ll be my GPOYW.
BRB, going to enjoy the weekend. Next week is also going to suck.
OK, this one is sarcastic enough that I’ll actually post it.
This is the first and last thing I’ll ever say about this meme on here. Srsly.

gpoy
fffffffffff. need to get lunch.
Not complaining. I leave at the same time of day regardless.
The correct syntactical use of GROUP_CONCAT still escapes me :[
It’s super effective :[

gpoyw: not even three full days back from break and I’m sick of Java already.
I don’t mean to be such a hater, but really. It isn’t the language I was hired to program in, and JSP is pretty dang crappy. If PHP is smoke and mirrors, then JSP is just a farty sauna.
Just saying.







