Noah Sussman RSS

simplex sigillum veri

Archives

OneMoreBug.com

@noahsussman

@snarkmeat

Blog Roll

Oct
4th
Sat
permalink
I like to think of this as a visualization of the maximum number of possible frantic late-night IM conversations during an outage. The more paths of communication, the more potential for miscommunication and misunderstanding.

I like to think of this as a visualization of the maximum number of possible frantic late-night IM conversations during an outage. The more paths of communication, the more potential for miscommunication and misunderstanding.

Oct
3rd
Fri
permalink
permalink
Sep
24th
Wed
permalink
permalink
Jul
18th
Fri
permalink

Please stop trying to sell me for management positions while offering an “QA Engineer” title and salary

Recently I was sent a job posting that embodied what I will call the Pernicious Myth of the QA Automation Engineer. Here’s just one line:

Own automated testing capabilities across Web, mobile and production processes.

Um.

An engineer cannot by definition take responsibility (that’s what “ownership” means — right?) for features that cut across multiple groups. In all but the smallest companies, Web and mobile would be managed by different teams. With different MANAGERS.

Engineers don’t take responsibility for the behavior of MULTIPLE managers across different teams.

This is a Director’s job.

Managing software capabilities across multiple teams is the job of a mid-level Engineering manager such as a director or (in larger organizations) a VP.

Why not? Because decades of computer engineering experience show that it never works.

Management (with all its wondrous hierarchical levels) is responsible for behavior of people within and across teams. Engineers and designers are responsible for the behavior and organization of the product. Not the people. People are a management problem. Especially at scale. Organizations that forget this fail.

Takeaway: do not sign on for a director’s job at an engineer’s salary

I’m not saying no one should take responsibilty for the “tests and testability” of an application or service.

What I am saying is that someone should be explicity responsible for testing across the whole organizaiton and that person should be at the director or executive level. Never at the team lead level. Ever.

Jun
1st
Sun
permalink
permalink
May
30th
Fri
permalink
Static analysis is a good replacement for 100% [test] coverage… not that you shouldn’t get to 100% coverage.
— Rasmus Lerdorf
permalink
May
29th
Thu
permalink
May
27th
Tue
permalink
May
24th
Sat
permalink
permalink
If you fits, you sits.

If you fits, you sits.

(Source: cheezburger.com)

May
22nd
Thu
permalink