Archives for April 2017

  • Restarting The Engine

    Job Change from Innate (2016) to CQ Roll Call (2017)

    Today, I start a new job and adventure – UX developer with CQ Roll Call, a company that has been historically documenting the legislative history of the country for the past 72 years.

    It has been an interesting four months away from full-time work, going through the process of applying and interviewing for jobs – something that I hadn’t done in 10+ years. Obviously, applying for a front-end developer position as changed during this time. Unfortunately, some things haven’t changed since I last went job hunting. [Hint: JavaScript is not Java.]

    That said, there are a number of people that I would like to give thanks to the following:

    • Will Packard for his employment support/advice, especially during the first month
    • Kenneth Joholske reminding me why we’ve been friends for 30+ years (see you next week for opera 🙂 )
    • post-Innate items from Casey Hawkes (thanks for the youGo print) and Brian Schlansky (thanks for the note, keeping in AoRD lecture journal)
    • Owen Shifflet and Devorah Firestone with their support and letting me bent an ear once in a while
    • Alison Farmer for her advice and support in making this job transition one of the smoothest I’ve had
    • Mary Cadden for her support and shoulder to cry on at the right moments
    • Darrin Maule in offering a job literally hours after losing mine (sorry we can’t work together at Fig Leaf but I really appreciate what you did and hope you, your family, and Fig Leaf success and happiness)
    • Jeff Lloyd and Ambrose Ferber for reminding me that I was worth more than I thought
    • Kevin Hewitt and Kelly Mullen for job references
    • my fencing family at Olde Town and DCFC (and other members of the fencing community), who are waiting for me to come back
      (P.S. Wayne would have laughed perversely upon knowing my new employer 😉 R.I.P.)
    • nclud for not just brief employment but allowing me to stay around to get myself (not just work-wise) together. I am grateful to all of your and hope you guys do great things. And finally…
    • To the design/UX/IA/tech community. Many of you I’ve met off and on during the years, at meet-ups, various conferences and online. But during this time, many of you not only offered not just job lead but advice and support. I’m really honored to be part of this community and hope to return the favor.

    Thanks to all of you.

    And now…forward…

  • A Brief Note on Responsive Design and Constraints

    (In response to Adam Silver’s Stop using device breakpoints)

    There are two points that I like to add –

    The relationship between Constraints, Content, and Context

    Content

    Content will always affect Constraints (i.e. breakpoints) and vice versa.

    What I do is a) use the familiar set of breakpoints as initial guesses and b) treat them as assumptions that need to be tested and verified.

    If you’re getting more breakpoints, maybe you need to reconsider your initial ones. Some may just need to be:

    1. Moved or
    2. Removed completely

    Experience

    This is probably more a developer than designer problem(?) but depends on your background. It comes down to hands-on knowledge of various devices.

    1. Don’t assume the device you have on hand is the one [definite] solutions. Just because you have an iPhone doesn’t mean everyone else does…sounds sensible but you’ll be surprised how many people don’t follow that advice. I have experience because most of my work involved non-American clients (more likely to see a Samsung than an iPhone).
    2. Comes back to testing on multiple devices – using BrowserStack (or other simulators) helps testing for both iOS/Android devices or just get a few old/borrowed devices on hand.

    The idea here is to get use to the idea of breakpoints as initial guides, not fixed points.