Plans gone Astray

Sometimes, things happen. We look at the situation with the best of intentions, and it simply doesn't work. This short post has taken me well over three hours to produce.

After catching a box that was sliding (heavier than expected) directly on the shoulder joint, my typing has been severely limited, and hand- writing and -drawing even more so. And this is driving me insane.

I want to say I've done a lot of study, and moving forward - but I haven't. I've been hyper-focused on a series of interviews, and attempting to tease out usable information given to me by those that are using another computer language, or a different framework. One of those folks is super-helpful: and makes me wish to go to the keyboard and type - but I can't. And it frustrates her and I.

I have a longer post I've been working on, so I hope the next post is more informative!

100 Days of Code Retrospective: Finding options

Thanks for the image, brainyquote.com ! Warning: this section has some details you may not wish to know - skip it if desired. So why, with a child and parent(s) that need attention, would anyone start on a learn-it-yourself path? This has been the best of a list of options, some of which weren't healthy. I'm not skinny enough to strip or work in a gym, I've lost my patience for call center work (the bosses, not most of the customers and co-workers), and damaged a shoulder working food service. I have to make plans for the future - parent isn't going to live forever, and the child is both working full-time, and looking for someone to start a long-term relationship with. The relationships I've had left me with not only bills, but a distrust of someone who isn't willing to work as hard as I do. My college degree is mostly worthless, with the changes in technology - by stopping to care for the family, I found myself behind. And the student loan ...

Drop-down values for injection

cover_image: https://www.pexels.com/photo/flat-lay-photography-of-gold-iphone-on-opened-notebook-beside-pen-583847/ canonical_url: --- Photo by Jessica Lewis 🦋 thepaintedsquare Learning in public is grand, and when you have a team that is willing to help with something that seems simple, but you fall into overthink for the wrong items, it can really help to type out your thoughts, actions, and what the program does to frustrate you. And in this case, getting a value I could see in the debugger was the issue The automation needs to check for page elements – and the drop-down selector triggers potentially different elements. Plus, depending on the user logged in, there may well be different options available in that drop-down. Then, I can get the options available for the user on the drop down, get their values, cycle through them, and verify each set of elements on the page. My test account for this has four options on the drop-down, so I budgeted a couple of hours to get ...

Redefining my Role

Confession: I am a nice person. I'm the one that will check on people - and be concerned if someone is acting off. Or donate money to make sure the potluck I can't attend has everything it needs. This has had an effect on my career: I was less willing to point out 'in public' errors in the code or things that just felt off to me while testing. And this stopped me from being the best tester I could be. Trying to be kind to someone that was having a rough patch, or simply not wanting to expose them to a potential attack was both me trying to get things correct, but care for them. I've decided to embrace this aspect of myself, and shift my focus. Being 'nice' to the product, or company must include being the voice for both end users and the team. Finding things that will be difficult for them, confusing, or flat-out wrong is a major part of my job. And this was also one reason I don't 'delight', at first, when something doesn't work as expected:...

Distorted Rovings

Search This Blog