Had a talk with a QA guy that sh0wed me how much I rely on making things break

So I was banging my head against a layout bug all morning at work. The dropdown menu kept overlapping the header on mobile, classic z-index mess. My buddy from QA walks by, sees me cursing, and says 'you know you only find these because you assume the CSS will break, right? Users never expect it to be broken until it is.' That hit different. I realized half my debugging habit is just me pre-blaming the browser or the framework before I even look at my own code. Since then I started asking 'what did I write that could cause this' first, not 'what's wrong with Chrome today.' Has anyone else caught themselves doing the same thing, or am I the only one who skips the obvious self-check?

1 comments

1 Comment

avery7212d ago

Man I felt this in my soul. I literally spent two hours yesterday blaming Safari for a flexbox issue only to find out I forgot to close a div. QA guy probably watched me lose my mind and was just laughing inside. My brain goes straight to 'this framework is garbage' before it ever considers 'maybe I cant count my own HTML tags.' I've started screenshotting my broken layouts and asking what a dumb person would do, then remembering I'm the dumb person writing the CSS. Still blame the browser first sometimes though, old habits die hard.