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 help

Where Is It? Part 1 - Inputs

Photo by Pixabay from Pexels     I am job-searching, and running into some coding challenges. Most of them are simple - some seem to want one-line solutions that require two cups of coffee and a half-hour to figure out what they want. Others are far above where my skills lie, and these I give a try for, and learn. And then there are the ones that offer, seemingly randomly, a challenge - within my skills (or at least my research skills) - that could be used as part of a larger project that I want to work on. This was the case last week, when I tried for a position that was a bit above what I felt I could do comfortably. The challenge was to let someone enter items, and then give back their location. In a language I am just familiar enough to be a danger to myself in. Happily, and thinking forward about how I could use this as a part of a larger program that would  use something like this to interact with the user. And also, this is command line, and thinking of how to set this up to

Do Your Tests Wobble?

Image by delo from Pixabay “The green reed which bends in the wind is stronger than the mighty oak which breaks in a storm.”  ― Confucius  I was asked to pair Blog with Lena Weiberg - much to my shock and delight. This was the perfect opportunity to hear another point of view on something, and share it with the wider community.  ~ Part of being a good tester, to me, is making sure I stay aware of the trends in development. Knowing  how the team is working can help get comments and questions to them at the proper times, and has  the information that can be acted on. In this quest, I attended a recent online conversation where the  topic was primarily on the size of 'steps' taken in software development: making sure each step takes  a reasonable amount of time, that it leaves the system in a state that isn't worse than it was before the  change, and that could - if needed - be deployed at this point.  The concept of “wobble”  (I'm not sure