Braunschweig, Niedersachsen, Deutschland
Kontaktinformationen
244 Follower:innen
188 Kontakte
Beiträge
-
You're struggling with software problems. What's the first thing you should do?
Put the problem into a broader context. Don't report 3+2 is not 5, but try to look at he function or functional area as a whole. Otherwise, by just providing fixes to isolated problem instances, you may miss the moment where it would be appropriate to think over whole part of the solution.
-
You're struggling with software problems. What's the first thing you should do?
The reproduction sequence is important to make it comparable. Try to reduce it to the minimal set of action. Not because of elegance but because it minimises the contact area for other interferences. For sporadicaly occuring problems it helps me to remember that the software never exists in isolation. There are many many layers between the powerplug and the screen. Not to mention the user itself. And every of this layers is full of bugs. Working software is just a coincidence of happy paths. When analysing intermittent problems try to look at the broader action context: what was the intention of the user, not what exactly the user did.
-
You're struggling with software problems. What's the first thing you should do?
Even before you define the problem you have to become aware that the problem exists. Since many problems are just overlooked, ignored or suppressed. Then you have to remember what the problem was, and what were the circumstances of its occurence. For this you have to be self-observant. Typically users new to the system see problems more clearly, before they get used to the application. Don't miss the opportunity to get in contact with new users and ask for their experience. For the problem definition don't miss to state how this behaviour affects the user. This opens up a wider area to look for solutions. Sometimes a change in the application may not be required, and you can solve the problem by providing guidance to the user.
Aktivitäten
-
Was sich nach solidem Deployment-Prozess anhört: 1. Dediziertes Test-Team 2. Change Advisory Board 3. Manuelles Deployment 4. Seltene Deployments 5.…
Was sich nach solidem Deployment-Prozess anhört: 1. Dediziertes Test-Team 2. Change Advisory Board 3. Manuelles Deployment 4. Seltene Deployments 5.…
Beliebt bei Alexej Simakov
-
I'm a real code kata enthusiast, and I genuinely think you can learn a lot and improve as a software developer by working on these seemingly simple…
I'm a real code kata enthusiast, and I genuinely think you can learn a lot and improve as a software developer by working on these seemingly simple…
Beliebt bei Alexej Simakov
Berufserfahrung und Ausbildung
-
Volkswagen Group IT Solutions GmbH
Gesamte Berufserfahrung von Alexej Simakov anzeigen
Jobbezeichnung, Beschäftigungsdauer und mehr ansehen.
oder
Bescheinigungen und Zertifikate
-
ISTQB - Foundation Level
ISTQB - International Software Testing Qualifications Board
Ausgestellt:Zertifikats-ID: 5013199.20260272 -
-
Sprachen
-
Russisch
Muttersprache oder zweisprachig
-
Englisch
Gute Kenntnisse
-
Deutsch
Verhandlungssicher