Skip to main content

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 isn't payable on a minimum-wage job. Since I need to be available all day (the child works at night), this eliminated the possibility of moving. Working for some of the work-from-home companies didn't pay well: a low bid normally got the job.

Programming had always been part of  my life, when a computer was available. But finding a full scholarship to a boot camp (which are rare), and hoping to get placed quickly enough that the financial crunch this would put the family in - I had doubts. Yes, places say they have placement rates over 75%, but even that figure (take off the rose-colored lenses!) made it more risky than I wanted.

My son, a current student at the college, started taking - through edX - the CS50 class and working through Free Code Camp, and, after a few weeks of him asking me how to do things - I gave up and joined him in both of them.

Why do I always decide to start a project during the holidays - when I know I have no time?

Making the Jump

All right, let's do this!

The child is working on homework for his classes at the college, and I'm at the kitchen table on the second day of Free Code Camp. The night before, we watched the first lecture, and I'm trying to ignore the fact that both it and the Free Code Camp stuff feel like they are too easy, and I'm not being challenged. I go in to ask the child where he's at on Free Code camp, so we can work together on it - maybe I'm missing something?

I'm on lesson 50 in two days, the child, who has been working on this for months, is on 75.

Wait - what?

Okay, I guess he doesn't like the front end stuff much. This is simple, other than a couple of points where I literally go back one lesson to make sure I didn't miss something. At least he is more familiar with the C language, and can help me there - he's already watched the second lecture while I slept, and is started on the homework.

Until the first project. And then finding out exactly how different our coding styles are, as he tries to help me with  CS50.

A week later, we aren't watching the lectures together, much less coding alongside each other. We occasionally ask advice, but it's rare - and usually get a "Why are you doing it that way?" expression along with an answer.

This doesn't bode well.

So, maybe I need some more-expert feedback: or at least ones that I can break down the answer, and get a reason as to why something is done in a particular manner. A quick course in C++ helps (two days to finish the introductory lecture and finish all the problems) with a 87% rate (with the lowest tossed out, it was 100% - but I claim the lower number), and finding Slack helped me move beyond the isolation, the table, and much of the confusion.

Popular posts from this blog

30 Days of Postman - for Testers!

  https://www.pexels.com/photo/white-and-brown-cat-lying-beside-a-laptop-and-toys-5468268/ Photo by Karolina Grabowska from Pexels   Working with developer- focused tools can be a challenge for some testers: we may know what the words mean, but haven't used those skills recently enough to make the tasks simple. Or we may not have ever used them, other than at a quick glance to make sure that what we are getting matches what it should be sending. And some give results that require us to go find another team member to help interpret the results. Being a more-independent tester has always been one of my goals - being able to use the tools that are common in the team, and be able to do at least basic tasks that support my tests with them. Our team used Postman for many of the API tasks that we had, so exploring this tool was a natural fit. There are alternatives it there, both graphical and command line, so feel free to explore! The items that you can do, and tools that ...

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:...