התחברות או הרשמה
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת

אפס סיסמה - שכחתי את שם המשתמש

שם משתמש
זכור אותי

he icon   en icon

עליכם להיכנס כמשתמשים רשומים בכדי להשתתף בפעילויות הקהילה - ההרשמה/כניסה מתבצעת מכותרת האתר.


התמונות של shiri malki

אין אלבומים

חדשות מעולם הבדיקות

  • Meme of the day: When you ask a question in stackoverflow

    Source : Reddit The post Meme of the day: When you ask a question in stackoverflow appeared first on The Life Of One Man.

    24.02.2020 | 2:06 קרא עוד...
  • Would Heu-risk it? Part 22: The Contract

    Would Heu-risk it? Part 22: The Contract I feel like I cheated a bit with this tool by using a rhyme that makes it both an asset but also a weapon or weak spot. Judge for yourself: “Mocks, stubs and fakes are all tools we can useTo ease our complexity and dependencies looseBut check all the contracts on which you dependDon´t assume it´s working, leave no loose-end“ So, what does it mean? First of all: I _love_ the idea of mocking out all dependencies. Isolation of concern, speed, ease of debugging – all the best things possible!I see why we want to have small small items with a single/few purposes that can be streamlined, re-used and easily replaced. But: It does not make the _total_ less complex. It just makes the _parts_ less complex and the possibilities for failures between parts endless. And: Communication is incredibly hard. Please remember that.So, back to the card. When we have interfaces between services, systems, applications, apps etc: you have to make sure to test that interface. You have to make sure you agree on every in and out of that interface. And you have to make sure you test the ecosystem with AND without all parts. What happens if one service decides to change from javascript framework 1 to javascript framework 2? What happens when the external service ABC suddenly is taken down for maintenance? What happens when external system 123 is hacked? Or simply when your sister team handling the internal service A12B adds a potential value to their[…]

    24.02.2020 | 11:15 קרא עוד...
  • Shot, Neglect or Train?

    Shot, Neglect or Train? How you treat the bringer of (bad) news tells me a lot about the organisation and potential for business growth. Go Read Accelerate – that book is full of insights. One of the models, is the organisational types from Westrum: [ Screen capture from the Kindle issue of Accelerate ] Andy Kelk has a to-the-point description about Westrum on his blog: To test your organisation, you can run a very simple survey asking the group to rate how well they identify with 6 statements:https://www.andykelk.net/devops/using-the-westrum-typology-to-measure-culture On my team, information is actively sought.On my team, failures are learning opportunities, and messengers of them are not punished.On my team, responsibilities are shared.On my team, cross-functional collaboration is encouraged and rewarded.On my team, failure causes enquiry.On my team, new ideas are welcomed. The respondents rate each statement from a 1 (strongly disagree) to a 7 (strongly agree). By collecting aggregating the results, you can see where your organisation may be falling short and put actions in place to address those areas. These questions come from peer-reviewed research by Nicole Forsgren.https://www.andykelk.net/devops/using-the-westrum-typology-to-measure-culture So when a passionate person comes to you with (bad) news, what do you and your organisation do? Do you reflect, ignore or hide the request? Do you say that it’s not a good idea to bridge the organisation? Do you raise an Non-conformity and set in motion events to bring “justice”? Do you experiment to implement the novel ideas and actively seek information? FAIL = First Attempt In Learning.

    24.02.2020 | 10:10 קרא עוד...


לרשימה המלאה >>