CSS, Filemaker from PHP, Javascript DOM and on* events, and other miscellaneous web development torture.
Of those, the thing that's giving me the most grief is definitely Filemaker. Access has better UI design, and the benefit of Real SQL Underneath. One of the long-term goals for the school is migrating away from Filemaker. I'm hoping it'll become a medium or even short-term goal. What a noxious piece of ass that software is. It's so ugly only its programmers could love it.
Ran into my first Javascript incompatibility within 15 minutes of writing my first line of Javascript. Apple released an update to Safari the next day that fixed it. Rock ON Mr Jobs.
I rocked up to the office today and Pam said "thanks".
I frowned. "What?"
"Thanks," she said. "I figured you were the only one who didn't get thanked last night, so ... thanks."
Everyone's a comedian.
--Nat
(now playing: Touch Me (I Want Your Body) by Samantha Fox)
For some values of "Real"Access has better UI design, and the benefit of Real SQL Underneath
When he arrived, state officials were relying on a bizarre conglomeration of FileMaker and Access database scattered all over the place. (With that kind of IT architecture, it's amazing that anything ever got done.) So, among his first projects when he started working for the RI's Secretary of State was to consolidate (and harmonize) all of these databases using MySQL and the rest of the LAMP stack.
Realistically, the benefit was in consolidating everything on a single SQL-based database server. That they didn't have to pay licensing or lock themselves into a single platform didn't suck.
The result? The Secretary's office can focus on doing real work. Quickly. And effectively. Without paying through the nose.
