Thinking and executing is key! I've definitely spent too long on the course/tutorial treadmill at times in my career and expanding and getting out of my comfort zone has been big in combatting that. Also, I am interested in learning another backend language! I've used a bit of Elixir at work and honestly I am not a big fan of it, I think something like Go, Rust, or C++ may be more suitable to me. Do you have a preference for someone interested in diving deeper into CS fundamentals? I've been on the look out for next ways I can level myself up, and that seems pretty important along with data structures + algs. Long term it would be nice to get a deeper understanding into graphics and physics, i.e. game/engine development, so maybe math is a good idea?

hahaha I can only dream of such a thing

yetanothertroll oooo this one looks fun

Hahaha I felt like it would've made it 10x harder to follow the logic of this post if it needed to also be a RegEx introducer. I'm not personally opposed to using it as long as you understand what you're matching for and how to modify it in case that pattern changes in the future I'd actually love to dive further into regex myself so maybe that could be a fun future post! With solving confirm-a-pattern-type problems in BASIC, is using regex super common? I've only ever had to use it a handful of times in ruby/js algos, but that may be because I am spoiled by these languages' built in methods/helpers/etc

Glad to be back :) I never would have thought of using ASCII math, that's a neat tactic. This would be another O(n) solution right? I wonder how long it'll be until I post one of these that you couldn't solve in BASIC, you're quick!

I once asked for and received feedback from a job interview with a lot of reasonably objective points: mistakes I had made, technical issues I ran into issues with, topics that deserved more discussion, etc. Great feedback for this specific project, but as you mentioned, this is only a single glimpse of a candidate and inherently cannot demonstrate all capabilities. Even in a more objective setting like a technical interview, it feels like a lot of it comes down to what the interviewer is looking/aspiring/dreaming for. Taking all of that new information from the feedback and perfectly implementing it does not guarantee that you'll align with the next company. 100% agree that feedback can be an invaluable tool, but it is important to take it with a grain of salt!

Yeah definitely agree that building that common language is important. Unfortunately in my experience lots of teams build no such thing, and instead stumble gracelessly through slogs of language Instead of building a common index of important terms, providing lessons and lectures and communication surrounding our language, we simply hope for learning through osmosis. Lots of unnecessary manual work, repetition, and frustration in that process IMO

I think if you're reaching an O(n^2) solution, something must be going wrong. Good luck though, if it can be done in BASIC, you're the one to figure it out!

Day 106 hahaha you're killing it man! Awesome to watch!

Wattenberger's website is so cool omg I love the diagram changing as you scroll through