samhatoum

4 ms·

1.
Federated Design Systems with Storybook(medium.com)
1 points by samhatoum 6y ago|0 comments
2.
AHow to Design and Build a Hyper-Fast Test Automation Stack(medium.com)
1 points by samhatoum 10y ago|0 comments
3.
Olympic Proof That Drag Beats Thrust in the Longer Term – Software Quality(medium.com)
4 points by samhatoum 10y ago|0 comments
4.
Is Your Testing Strategy Back-To-Front?(medium.com)
1 points by samhatoum 10y ago|0 comments
5.
by samhatoum 10y ago
Thanks for the clarification and totally agree. I have seen project managers turn their gantt-chart sideways, have 1 hour standup meetings and call themselves Scrum Masters! So I know exactly what you mean. Nowadays I never say the A word i
6.
by samhatoum 10y ago
It's not just about critical bugs though. Those are "stop what you're doing and get on it". ANY bug that is not critical gets worked on next no matter what. So it's about all bugs getting priority over other work. I
7.
by samhatoum 10y ago
I don't think the world has an agreed definition of a bug, or at least I've not seen it! I understand that the issue people have is with the wording of the zero-bug. As I've mentioned elsewhere it's still true that it is
8.
by samhatoum 10y ago
FYI, I'm not a project management type. I've build numerous continuous delivery pipelines for enterprise clients and helped them deliver multiple features per week. I have current skills in writing Java, C# and Node.js. I've
9.
by samhatoum 10y ago
I like you're reasoning! There is no situation where zero latency actually means a latency of zero, whereas in the description I've provided there is a situation where you end up with zero bugs. Out of interest, what would you cal
10.
by samhatoum 10y ago
Actually this is where you can be flexible with a specification. If the ticket was initially specified as embedding the fonts, then technically it's an implementation defect since it was already specified. However, as a team you might
11.
by samhatoum 10y ago
As gshulegaard has mentioned, I think you're taking the name Zero-Bug to mean something different than what I intended. Zero-Bug does not mean writing software without defects - that's impossible, instead it means correctly classi
12.
by samhatoum 10y ago
It's not really a lie when you think about it. It's very true to its name. It's saying, after you've classified the bugs, you're not to do any other work until the bug list is cleared. This will lead you to zero-b
13.
by samhatoum 10y ago
You missed the part about making them the top priority after you reclassify them. After that, you are right, it's that simple. I even state that in the article that it's not complicated. Yet, not many seem to do it. Click-bait? No
14.
The Zero-Bug Policy in Software Development(medium.com)
9 points by samhatoum 10y ago|24 comments
15.
The Zero-Bug Policy(medium.com)
2 points by samhatoum 10y ago|0 comments
16.
by samhatoum 11y ago
Hey, this is the author. The article is not at all marketing our services. It contains a ton of links that are intended to help you adopt BDD and TDD practices. Tweets like this one back my response up: https://twitter.com/C
17.
Preventing Software Bugs from Ever Occuring(medium.com)
8 points by samhatoum 11y ago|2 comments
18.
What is Quality?(medium.com)
1 points by samhatoum 11y ago|0 comments
19.
The Forgotten First Principle of Software Delivery(medium.com)
6 points by samhatoum 11y ago|0 comments
20.
Super-fast reactive acceptance testing with Chimp(xolv.io)
1 points by samhatoum 11y ago|0 comments
21.
by samhatoum 11y ago
Try this https://github.com/xolvio/Letterpress/tree/master/app/tests/... ES6 modules will change this approach somewhat, FYI
22.
Meteor Testing in Ghana(twitter.com)
2 points by samhatoum 12y ago|0 comments
23.
The Meteor Testing Manual book is now available
5 points by samhatoum 12y ago|1 comments
24.
New Book: The Meteor Testing Manual(meteortesting.com)
3 points by samhatoum 12y ago|0 comments