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

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

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

he icon   en icon

אתר קהילה חדש בשם TEST Huddle

נכתב על ידי 
חמישי, 10 יולי 2014 05:57
דרגו כתבה זו
(1 הצבעה)

אתר קהילה חדש בשם
TEST Huddle
מחליף את אזור המידע באתר של EuroStarConferences.com
מומלץ להרשם




חובה להיות משתמש רשום במערכת בכדי להגיב - ההרשמה/כניסה בכותרת האתר

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

  • TestCamp – a short relation

    TestCamp – a short relation Disclaimer Occasionally I cooperate with TestArmy as Trainer.TestArmy is the main organizer of TestCamp. First thing first I would like to formally Apologise to Damian Szczurek for forgetting his name on stage. I am really sorry it wasn’t intentional. What is TestCamp? TestCamp is Conference addressed mostly for younger testers still trying find their footing in IT world and our profession. At least that was the idea of the first edition looking at the subject on this one I think this year didn’t have as clearly targeted audience. There was still a lot of beginner level subject, but there were a few more advanced ones. Also, there was a lot of experienced testers in the audience. How was the conference? This time I won’t describe a presentation after presentation. I will present my top picks. As far as I am aware they will be available online on testuj.pl youtube channel. So you can watch them yourself. But first few things about the organization. Everything was running smoothly, even better then some other conferences but there are 3 things I didn’t like:THE HUGE PILLAR in the centre of the stage. with poor lighting. That’s why I decided to present outside of the stage. Another thing is there weren’t enough places to leave the plates glasses after taking the snack. And the snack areas basically had choke points at the entrances. So which presentations I liked? Nauka na błędach – root cause analysis w praktyce –  Katarzyna Balcerzak had great keynote about root cause analysis.[…]

    23.09.2018 | 1:02 קרא עוד...
  • Demystifying Machine Learning, Part 6

    Demystifying Machine Learning, Part 6 In the last post, we defined our neural network by providing it some specific hidden layers that will provide the basis for how the neural network model actually works. We were also able to dig in a bit to what’s happening behind the scenes. In this post, we’ll actually execute the neural network by feeding it the data and evaluating what gets produced as output. This will be the final post in the series and much of the points I make here have been covered in some way, shape or form in the previous posts in this series. My goal in this final post is to finish off the neural network we started in the previous post. This will actually be the second implementation of the same neural network you already developed. I did a few steps at the end of the previous post to help you visualize the model that had been created. Those statements weren’t strictly necessary for the operation of the network. Let’s level set and consider what script you should have in place. In your mnist.py, here is what you should have: import numpy as np import matplotlib.pyplot as plt from keras.datasets import mnist from keras.utils import np_utils from keras.models import Sequential from keras.layers import Dense, Activation (train_images, train_labels), (test_images, test_labels) = mnist.load_data() total_pixels = train_images.shape[1] * train_images.shape[2] train_images = train_images.reshape((60000, total_pixels)) test_images = test_images.reshape((10000, total_pixels)) train_images = train_images.astype('float32') test_images = test_images.astype('float32') train_images /= 255 test_images /= 255 train_labels = np_utils.to_categorical(train_labels) test_labels = np_utils.to_categorical(test_labels) total_classes =[…]

    22.09.2018 | 11:31 קרא עוד...
  • The sprint planning meeting that goes on forever | SupremeAgile

    The sprint planning meeting that goes on forever | SupremeAgile The sprint planning meeting is the longest meeting in the scrum framework and based on my experience it also the most exhausting meeting for most teams. The most difficult thing about this meeting is that team members often come to this meeting with the mindset that it will take the exact time written in the book…but it doesn’t! In scrum we have a very important term called timeboxing. A time box is an agreed upon and limited box of time that is used by a person or team to perform a dedicated activity (see here for more information about timeboxing). Everything in scrum is time-boxed, including the scrum planning meeting, so what happens when the meeting time is near the end, and the team hasn’t determined the goal or sprint backlog? Do we end the meeting and continue it next week? Should we extend it? Do we just end it? This scenario happens over and over, especially for new scrum teams that have neither the maturity nor the experience to conduct an effective sprint-planning meeting. So, what should one do in this scenario? To be honest, it really depends on what you want to achieve, but some common solutions that I love to use are: Let the team learn the hard way Let’s say that you have a team that is not willing to change their habits and continuously ignores the meeting’s timeframe. In this case, you can cut the meeting at the end of the time box, which will make the[…]

    22.09.2018 | 10:05 קרא עוד...


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