internationally approved symbol for a glitch?
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
Not sure how you are collecting data but this actually sounds to me as though a bug has been exposed. If the application/system has the assumption that once a write is issued the data has been saved - this 'glitch' has exposed that as a bug within the system. It sounds like the bug that has been exposed is that a save is not saved until it has been checked. A great opportunity for a unit test!
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
First thing to come to mind when you say "Glitch" is The Matrix, so perhaps a pictuer of Neo's head (complete with cool sunglasses) will do the job :cool:
Nah, the black cat was the glitch. So a drawing of a cat.
-
Nah, the black cat was the glitch. So a drawing of a cat.
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
Many moons ago, we referred to an anomaly seen in an oscilloscope display as a glitch. "look at the output of that flip-flop, it's not steady, there is a glitch in it". I would suggest a lightening bolt kind of icon. Maybe with a beard. :)
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
-
Many moons ago, we referred to an anomaly seen in an oscilloscope display as a glitch. "look at the output of that flip-flop, it's not steady, there is a glitch in it". I would suggest a lightening bolt kind of icon. Maybe with a beard. :)
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
- Large & in color: a banana peel. - Small: a reversed box with a this side up arrow at the bottom.
-
Not sure how you are collecting data but this actually sounds to me as though a bug has been exposed. If the application/system has the assumption that once a write is issued the data has been saved - this 'glitch' has exposed that as a bug within the system. It sounds like the bug that has been exposed is that a save is not saved until it has been checked. A great opportunity for a unit test!
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
All very true and happily planning a minor update to make it more robust. Still a glitch at root cause though.
-
CodeWraith wrote:
Daniel Pfeffer wrote:
vibrating
rotation != vibration
The vibrations refer to the starquake, not the rotation.
CodeWraith wrote:
And where are the two death rays it emits at the poles?
I also don't show the electro-magnetic field, the gravitational field, and the [Cheela](https://en.wikipedia.org/wiki/Dragon's\_Egg) living on the neutron star. This is a suggestion for a glyph, not a peer-reviewed article on Relativistic Physics!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
Daniel Pfeffer wrote:
the Cheela living on the neutron star
+5 nerd points to Daniel! :-D (excellent novel, BTW)
Software Zen:
delete this; -
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
A picture of the universe with it's middle finger pointing towards you ? For the religiously oriented, use a cloud, instead, in the form of a one-finger salute.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
How about a wall power socket, with one socket looking burnt out? A more emoji-esque version of this. href="https://i.stack.imgur.com/1UgVd.jpg Money makes the world go round ... but documentation moves the money.
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
---------------^v----------------------
-
I am sure many of is have a whiteboard for informally recording significant events for quick visual reference. For fun (mainly) but also because its really handy we add a simple little emoji style graphic to show what kind of event it is. So a bug gets a nice little picture of a bug, a piece of software with a sunset date gets a setting sun and so on. Means we can tell whats what, and waste five minutes drawing it. Yesterday I found a data issue caused not by a bug but by a glitch. A power cut had thrown some data out. We should record this but we don't know what a glitch looks like :~. We can't possibly put it on the board without a picture. Please help with your suggestions.
This is simple. Glitch: order disrupted by unexpected disorder. - Sign of order: sinus - Sign of disorder: noise Intuitive symbol for glitch could be a sine turning into noise. Quick illustration: https://i.imgur.com/OsQuZ9V.png
