s&t bugs 021216

BUGS!

Features

+

Bugs

-

In 1946 Grace Hopper joined the Computation Laboratory at Harvard where she worked on the Mark II/Mark III electromechanical computers for the US Navy.

Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. Delightfully, the actual bug was carefully removed and taped to the log book.

A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or

unexpected result, or to behave in unintended ways.

- Wikipedia

Something I broke by mistake :-(

- Dan

Our development sprints tend to follow a broad pattern:

A) Lots of features, a couple of bugs

B) Lots of bugs, a couple of features

Our bugs tend towards the visual display side of things.(That’s because front-end development is harder than backend development)

Bugs can be reported to the team by anyone.

If we establish that a reported bug is valid it’ll go into Pivotal with a description, supporting info and, preferably,

a screenshot illustrating the problem.

Bugs don’t usually have user stories. That would be weird.

Bugs can be giant, site-spanning monstrosities…

Make the space between the main content and the device edge consistent

#119625949

HUH?

Bugs can also be tiny oddities that only an unlucky few ever encounter

Content type label wrapping on to 2 lines in Safari

#119625949

Normal browsers - Firefox, Chrome, Edge, IE (IE!)

Safari - Mac & iOS

Bugs get a bum rap but they are a vital part of our workflow. Fixing a bug makes things better for everyone.

BE VIGILANT! REPORT STYLECRIMES!