Devagnostic

Finally is there! My first paper book has been printed out. The "Decommission Analysis Guide" is ready to be picked up from the Amazon bookshelf and read. If you have been asked to analyze tens (or more) systems in your organization,  and you're whole in tears now,  this book is for you. That's a practical guide, that will help you to rationalize the task, and embrace a massive number of existing systems you don't know and have no chance to understand. [ Amazon store ] What is system decommission analysis ? A life cycle of all IT systems ends up with plugging out of the power supply.  Before it happens, we need to make sure we understand what is the real scope of the system, and what actually happes once the last led-light goes out. It's not usually a big deal if we have a single system to analyze and an existing support/developer team  already that is up to speed, with an insight into the product.  The problem becomes more interesting once you realize you hav...

While preparing for the Azure exam, I've noticed a supportive initiative on Facebook to help a little girl collect money for her surgery.  A number of my colleagues have already participated in that action, so I've decided to join as well. The challenge was to prepare any "program" staying in 16 lines codes, sharing it publicly on the FB, and add the #code16challenge hashtag. Playing a bit recently with Azure, I've decided to use this opportunity to create a small web app   (nodej.js/npm), set up all required Azure resources ,   and deploy the app to the cloud  - all in 16 lines of code. web= "code16challenge-siepomaga" asp= "wa2021asp" rg= "code16challengeRg" npm init -y  # Webapp setup echo  $(jq '.scripts.start="node index.js"' package.json)  > package.json echo \ "const http = require('http');\  http.createServer((req, res) => {\   res.writeHead(200,...

Test case automation may bring many benefits for the application/system QA process, but it's not always obvious how to introduce an implementation of the test cases into SCRUM flow.  The SCRUM methodology defines the number of PBIs (product increments) for prioritization and planning, as a part of the SCRUM process. Those could be user stories or enablers , sometimes bugs . Each of the PBIs needs to be estimated and confirmed by a scrum team before it's added into a sprint scope (sprint backlog). The question would be: How to plan the effort for the implementation of automation tests, as those are not the PBIs per se? Test Case is not a PBI In the strategy proven in one of my projects, a test case is an output (product) of the delivery, just like an ordinary artifact. Typically, it's a part of a testing suite. It needs to be created, maintained, and placed into a repository (see: Azure DevOps ). Once prepared, we can start working on the automation of the test case. Bo...

"Let's imagine it's 1994" Sometime ago I was looking for a FPS game engine for JavaScript, to implement Doom-like game. And here it is . I was looking something really simple to adopt to my idea. I wanted to create first person shooter game that could let players to run on 6th floor of my office. Sounds scary, isn't it? :) http://wasztemborski.github.io/pandadoom/index.html In fact my goal was to check if I'm capable to do this and what technical issues it will bring. I was surprised how easy it was to adjust the current core engine for my needs. But the most important is that apart from the game the map editor was also available. Both - game and map editor - require html browser and standard technical stack: npm, grunt and web server. The most tricky part was the Map Editor. I've spent the whole week to figure out how to create my map and don't loose my work. Using map editor was so painful, especially when some part for map w...

This week I took part in the UX Poland conference. I was positively suprised, bearing in mind the previous edition in 2015. I was very glad to participate in Masterclass Workshop: ''Lean Ux in the Enterprise''. This training was conducted by Jeff Gothelf, author of the book " LEAN UX Applying Lean Principles to Improve User Experience ".  Some participants tried to challenge the possibility of changing their organisations.  Usualy most are too petrified and prefer dwelling into the past. But even those, want to be like Apple and realize that they can not keep a cake and eat a cake. I was realy under impression of the Microsoft's concept team , who tried to predict the S-F future. When I was watching the movie (from 2011). I realised that nothing special have happened since then but some ideas already have been materialized. The bottom line of the (so ancient) presentation was that all interfaces will still relay on screens. It could be...

Recently I've noticed that I changed the main in direction of my blog . It became more personal and focused on non-technical aspects. In fact It's difficult for me to keep all the things consistent wihin a single blog, as there're a plenty of completely different things that drive my thoughts away from the programing. I'm grateful for people who decided to put their valuable contents into Internet and share their knowledge and experience. I've already spent thousands of hours, trying to solve the problems that are already solved by somebody before. I hope that somebody will find this blog valuable in return. See you soon.. :)