Dip your toes in!

The water is *just* fine! And what water is that, you might be asking? Why, the Flood Depth exercise on Codility, of course! The exercise, designed to test your ability to manipulate arrays efficiently, proved to be a fascinating journey into algorithmic thinking and problem-solving.

At first glance, the Flood Depth problem seems very… not so very straightforward. We are given an array representing the heights of terrain blocks with the task of calculating the maximum depth of water that could be trapped between the blocks when it rains. It sounds simple, yet the devil lays silently (or not so silently) in the details.

The essence of the exercise lies in identifying the locations where water could be trapped. To do this, I had to analyze the array and discern the boundaries of each potential water basin by traversing from left to right and then back from right to left. How well-versed are you in traversing arrays?

My first approach was a naive one – iterate through each block to the right and then iterate through each block to the left. This involved two separate for-loops (and two separate arrays- a big no-no) that led to a time complexity that most definitely could be improved. And while it may have lacked the efficiency that is often crucial in real-world applications, I’m proud to say that it was pretty readable 😉

As I delved deeper into the problem, I realized the key was to take the minimums of left and right, which are the points where water could start accumulating and subtract that our original array. Not so deep after all, lol! Now, could I employ a stack-based approach? Sure, maybe- as the stack would allow me to keep track of the ascending order of terrain heights. However- for now, I am appending going to the right and then inserting going to the left.

Overall, the elegance of this algorithm lies in its efficiency. Nevertheless, the Flood Depth exercise on Codility wasn’t just about finding an efficient solution though, as it’s prompted me to consider at least one edge case that might break my implementation. But what if there were multiple local minima close to each other? What if the terrain had a single peak with no depressions?

I’m not quite at the place of tweaking my algorithm as of yet because…. I submitted my program into Codility and got a fairly good score (at least to me! And I am stoked about it!) for the very first submission (if you want to know what that is- be sure to watch my YouTube video premiering on Thursday at 8:15PM EST!).

Ultimately, I was able to break it down into five “gears” – iterating to the right, iterating to the left, creating an array of minimums between the left and right, creating an array of “results” and then returning the “max” of that *result*.

As always, there are so many ways you can solve this- the program I wrote (in my video) with my five “gears” is how I chose to do mine. How would you write your program?

_________________________

Thanks for reading! Don’t forget to set an alarm for Thursday at 8:15pm!! Where I break down the whooooole problem and show the results of my test… be there or be square 🙂

Click HERE to visit my channel 3>

It’s not this, it’s that

In the vast landscape of programming challenges, Codility stands tall as a formidable arena where developers showcase their skills and problem-solving prowess. However, nestled within this realm lies the “Longest Password” exercise—a not-so-complex puzzle that not only tests my programming acumen but has also plunged me deep into the treacherous waters of video editing for an explanation on solving it.

The Longest Password exercise on Codility asks it’s students to determine the length of the longest valid password that is given to us in a string. The rules are that the password is to meet specific criteria, including an even number of digits, an odd number of letters, and no other characters other than alphanumeric. And apparently, solving this puzzle requires a delicate dance of algorithms, precision, and a touch of artistry (or so some say).

As if decoding the intricate dance of characters weren’t challenging enough, the true test begins when attempting to document this coding journey in Premiere Pro. Enter stage left, the realm of video editing, where lines of code meet pixels, and the struggle to convey the elegance of a solution takes center stage that eventually wrestles me into a corner of my bed that I don’t want to get out of, lol.

Incoming cheese for my whine! Table for one!

In my feeble attempts at conveying the intricacies of algorithms, loops, and logical structures I’m trying so hard not to lose that sense of storytelling. How does one really capture the essence of problem-solving in a way that is both engaging and educational? But not only that, then comes the unavoidable dilemma of screen real estate; balancing code snippets, explanations, and the occasional witty commentary becomes a juggling act and the canvas of the video editor that starts as a friend becomes mostly foe, offering creative freedom but demanding a meticulous approach to maintain any kind of coherence on my part.

Coherent? Me?

Video editing, much like solving a complex coding problem, is an iterative process and the parallels between coding and video editing has become so painfully apparent recently. Just as one refines and optimizes code for efficiency, so too does a video editor fine-tune the visual narrative to ensure a seamless and engaging viewing experience. And what a process that is! A total paradox of blood, sweat and tears… of joy (when it’s all said and done).

“There is a certain vulnerability in presenting one’s coding journey through video.” <– I didn’t write that, but I feel it all the same. Just as Codility’s code review exposes the intricacies of one’s logic, a video walkthrough lays bare the thought process and communication skills used by me that in turn, inevitably leads to the choice I must make of how I will navigate visually the review my program’s performance. The evolution of that journey eventually morphs into another example of that intimate dance between creator and audience, where every keystroke and every cut is a testament to the journey while at the same time tends to leave my brain smoking from the ears!

But I did make a promise.

That even though I am currently grappling with the challenges of video editing, I will emerge not only with a solution to the Longest Password that has a score of 100% (I am currently at 30%) but with a renewed sense of wonder for the artistry required to convey the beauty of code. At the end of the day, it’s just a long line of thread weaving a great tapestry of learning, where triumphs and frustrations interweave to create a story that goes beyond the lines of code and pixels on a screen but to the end user who is also struggling to make things happen for themselves in the world of programming.

In the end, the struggle is not just about solving a coding challenge; it is about the transformation of a coding journey into a visual masterpiece that helps others. That is the thread that pulls me and this video will launch tomorrow at 8pm.

Vulnerable thoughts

In the vast landscape of content creation, the journey is often filled with highs and lows, unexpected turns, and, above all, vulnerability. Today, I want to talk about my experience on YouTube, the unanticipated challenges I faced, and the pivot I’m making towards a new chapter with Patreon. Is it a tale of resilience? A tale of self-discovery? Or, is it really about the importance of embracing vulnerability in the pursuit of a greater education in coding?

Like many aspiring content creators, I embarked on my YouTube journey with dreams of not only sharing my passion but also generating a side income. The platform seemed like the perfect space to showcase what I was learning, connect with like-minded individuals, and potentially monetize my content. I delved into creating videos about a variety of topics, hoping to strike a chord with a wide audience.

However, reality hit and the path to success proved wayyyy more challenging than I initially anticipated. Despite pouring my heart and soul into creating engaging content, the anticipated financial returns simply didn’t materialize. Ever. It was disheartening to realize that the YouTube algorithm, unpredictable as it is, wasn’t favoring my content in the way I had hoped. But is that my fault? A robot’s? Nah, we all have aspirations as newbie’s and many, many times those aspirations turn to smoke when the rubber begins to really hit the road.

Rather than succumb to frustration, I’m choosing to embrace vulnerability and share the pause in my journey openly- and in a world where success stories often take center stage, admitting to setbacks and challenges can often be a daunting task. However, I believe that authenticity fosters genuine connections, and by being vulnerable, I hope to resonate with others facing similar struggles.

For me- I simply gave up. Took a long break. Had a hard time.

I want to share that it has to be okay to explore the realities of YouTube experiences as a creator, from the excitement of creating content to the disappointment of financial setbacks (not that there was EVER a “setback” lol!). I feel that the response from my audience was overall very positive, revealing a supportive community and I should have just kept going.

But.

I needed an actual paycheck. And so it was- a crucial turning point in my content creation journey, leading me to reassess my goals and pivot towards a new direction:

A place in Info Tech

~~~~~~

At this point in time, I have officially been in my new role as IT Tech for one year and let me say, I am in looooooove with it! It’s been a wonderful experience. Awesome. Love, love, love.

But.

Ultimately, I am a creator. I cannot and will not let go of that. So, in the process of self-reflection, I am revisiting my roots and renewing that passion that had initially sparked my interest – Codility’s exercises. As a content creator, I had previously created valuable content around coding challenges and problem-solving, attracting an audience who were interested in honing their programming skills in order to land their dream job.

But.

YouTube’s stiff requirements of making content to merely acquire a cup of coffee… well… it sucks.

So after some thought and a renewed sense of purpose, I am making an executive decision to refocus my content on the niche that had initially inspired me by using YouTube as an advertising platform for my new Patreon.

LOW cost Patreon, I might add! Very low, and I want it to be worth every penny someone might want to pay! The goal is to focus on delving deeper into Codility’s exercises, creating tutorials, walkthroughs, and insightful discussions around coding challenges WITH the edutainment my audience has come to experience and enjoy! PLUS, I have more Premiere Pro experience under my belt after producing an Algorithm course for FreeCodeCamp so the editing will be much better! (being on TikTok helped too ;).

The decision to explore Patreon wasn’t without angst, however. In particular, the stigma around monetizing content. In a landscape where some still view creative pursuits as hobbies rather than legitimate sources of income, it can be challenging to assert the value of one’s work.

BUT. I firmly believe that creators deserve fair compensation for their time, effort, and expertise IF IT’S GOOD CONTENT. Now, could I say my content was “good”? Maybe? Maybe not? I know that I tried real hard, but that effort means nothing if it can’t retain watchers. And that is YouTube’s gauge, is it not? So with that in mind- I have a paradox: I want to create WATCHABLE content but I don’t want to wait for YouTube’s algorithm. It’s slow. And… it’s a new age! It’s 2024 people!

The Future: A New Chapter of Growth

The question then becomes: can Patreon provide a direct channel for anyone that will want to support my work? Can I acquire a contribution to the sustainability of the content they love, foster a more equitable relationship between a creator and their audience? How much of this is a gamble of my time, resources and energy? Am I hurting for money? No. I have a plan. It’s selfish, maybe. A plan that will be revealed much, much later…

Regardless, I am choosing to be positive (lol!) and as I embark on this new chapter, I really am filled with a sense of excitement and optimism. Through Patreon, I hope to rise to the challenge of building a much more sustainable future for my content creation endeavors, allowing me to continue sharing my passion for coding challenges, problem-solving and helping people gain jobs in the field they are passionate about!

In this new chapter for 2024, as I move forward, I invite you to join me on this new adventure, where openness and passion will hopefully pave the way for meaningful connections, sustainable growth and advancing others in their pursuits of programming (and advancing my pursuit at the same time).

Cheers!

~~~~~~

My goal is to start with Codility’s Exercise 1 (2015 Contest) that contains 3 challenges that I will perform using Python:

Longest Password, Flood Depth, and Shalom Skiing.

When it is ready, I will launch the channel (and my true goal for this (in its own time)). Stay tuned!

Is this the branch?

That’s “out”?

You know, the old saying-

I’m branching out.

–A person that identifies as a tree

So, yeah. That’s what I’m attempting to do.

You see, I have an idea. An idea of “branching out” into another realm. Will it work?

Click HERE (…if you dare, muahahaha!)

Life in Info tech

See that face? It’s a little bit Mona Lisa, little bit not. She’s got something under the hood, sometimes not a lot… hey, that rhymes! But that is an accurate pictorial of life in the IT world over the last 8 months.

The pros: so many! I wanted to be in an office setting again (I am), I wanted to learn a lot (I am), I wanted mentoring (I am getting that), and I wanted part-time (got that too).

The cons: it’s a two person team (one of them is me) for 75ish employees. Needless to say, some days are high pressure and it’s a law firm so there are legal/court proceedings that need to take place.

If they don’t due to tech issues, it can have terrible repercussions. As we all know, the legal system is a slow turning cog and if you miss certain things, it can take some deal of time to get back on the wheel. Lawyers and clients don’t like that.

BUT, I thrive under pressure- so, it’s not really a con 😉

Everybody is very nice and I have ample opportunity for training/documentation/troubleshooting on a variety of software and maintenance/upgrading on hardware and other equipment.

I haven’t had a whole lot of extra time to continue my education during this process… But now that I feel more comfortable in this role, things are brewing in my noggin’! I’m working on building up my Fiverr to offer some on-the-side services and will be adding to my YT channel shortly.

Oh! And I got a TikTok account for my brand, found HERE. So follow me over there where I’ll have more updates and quality content.

See you soon!

It’s BIG!

RealToughCandy.io brought me on to teach their Introduction to Algorithms course! AHHHH! That’s where I’ve been over the past couple months as it has sucked the lifeforce right out of me, lol!

It was soooo much fun, though.

It’s over two hours of lessons and coding, with a little twist of my crazy sense of humor.

Best part? It’s FREE!!

Check it out!

LINK HERE

-Jb

But it’s okayyy…

Because I’m on vacaaaaaation!

Remember that song from Rhett & Link?

Record highs in Lakeland, FL ♥️

But I’m still coding like a trooper because I love it. I even signed up for the “Daily Coding Problem” email program as posted by that Techlead(?) guy on YouTube.

It’s pretty cool!

Talk to you later ~

-Jb

DEAD.

You guys.

I’m creating a YouTube video on Leetcode problem 21 and I had this funny idea to create a “love story” between a dummy and myself in reference to the “dummy” node so often used for this problem.

It turned out so funny!

I made a joke about whether my husband was jealous over my love for the dummy and after showing him the video, I think he kind of was! LOL!

He wasn’t sure why it had to be so serious, but he doesn’t understand what nodes are so the joke is lost on him…

Anyway, he’ll get over it.

But I wanted to share it here with you guys so you could see it. The full video will be out tomorrow, but in the meantime, if you know about dummy nodes, this should make you smile.

Hopefully 😉

WordPress doesn’t allow vids to play on the page unless you have a premium account, so click the link below and use the password: dummy

Link here: https://dai.ly/x88ey8f

(don’t forget to put the sound on :))

Enjoy!!

-Jb

Yee-hawwww

I’m trying to be a bit more active on YouTube in an effort to break up the monotony of schooling. So, for the past few days I’ve worked on uploading a video about the probability calculator that I blogged about a little over a month ago (HERE).

I tried to make it a little bit of fun… breaking out some hats since this is a ball sum without replacement project featuring a hat with several color balls. It’s a little cute, I don’t know. You’ll have to tell me your thoughts: link HERE.

I’ve just been feeling blahhhhh with school. Not sure if it’s the super cold temps we’ve been enduring or what, but my energy is just GONE for learning. Maybe I sprained my brain muscle, who knows.

What y’all working on?

-Jb