Ref

@Vonnie_Ivy @grok whats name of series

Oh, Poor Catherine!!!💔 🎥 TV Show: 9-1-1 (S7E7)

@Healer2Hacker OOP everywhere!!!

Day 6 of #100DaysOfSwiftUI ✅Checkpoint 7 complete Today I learned about classes and inheritance in Swift. Lots of similarities to JavaScript classes so felt easier than the previous days

@runliftrunlift 😅😅😅its been so massive this year i love it though. The them is to be on the roof everyday. Poor older guys are always up there in the country side.

Snow clearing here is a Sisyphean task. These poor guys will be back on this roof soon, no doubt.

I’m 54, a physicist, have spent decades using mathematics to study the universe, solve problems, and build things. If your work touches numbers, now or in the future, and you want to learn math properly, this thread shows a from-the-ground-up math you’ll actually need:

@runliftrunlift Ohh! it gets worse for sure, I have small cars are having a hard time. This week alone saw 4 tumbled. But the walks are superb

Short base run this morning. Rough conditions. I’m fine with the cold, but having to run on the Hirafu sidewalks with deep snow makes it a challenge to get into a rhythm. No choice but to lean into it though. It’s awesome that I get to do it at least once (emphasis on once ⛄️)

@runliftrunlift I have seen massive amounts too, reminds me of 2021-22-23. Luckly Japan doesn’t see a lot of days of black eyes. We would be walking like ducks all day.

Easy run:walk just over an hour this morning Comical amounts of snow recently, it piles up everywhere. I suppose you get used it living here. I’m mostly accustomed to running outside now. Today I wore goggles for the first time and feel like my snow running gear is complete.

I have stayed in snowy side of Japan for almost 10+ years, and its only over the last half where my body has gotten used to it. My health suffered for 5-6 months, but I have found the solution to be right clothing. Because I want to maintain more movement, and working towards running a marathon next year, I have resolved to getting to walk as much as possible.

Living in a really cold place is wild. I’m coming up on my first full week in Hokkaido. Most of my time in the US I’ve lived in Northern California (Sacramento & San Francisco) where it never snows and doesn’t ever get very cold. In Tokyo it’s cold for a couple months out of the year, but nothing crazy. The main difference I’ve noticed here is the friction between inside and outside. I’ve always taken frequent short walks throughout the day. Here I need to think twice. Gotta bundle up first, put on my ginormous snow boots. I spent several minutes scraping off my car the other morning. Tough to just go places quickly. It’s an adjustment. I don’t mind it, but I will be happy when the weather gets warmer.

@runliftrunlift Il be in Tokyo in two weeks, do you think leaves will still be beautiful? Anyway, googling the trail. Thanks

Beautiful day for a hike today. Autumn colors starting to come in. Wife and I hiked from Kori to Okutama station. If you visit Tokyo and want a good day trip, going to Ome/Okutama is can’t miss provided the weather is decent. Just a couple hours from Shinjuku station.

@JackUnicyclist 👏🏾👏🏾 wonderful to hear you moved Jack, looking forward to those deep study sessions once you are settled. 💪🏾

FINALLY! We made it! After 6.5 years of being together and 2.5 years in the visa process, I'm finally living with my wife in Colorado! Together at last! Due to spending time with family before I left and getting everything settled in the U.S. I haven't been doing as much software engineering. Still showing up every single day, just not much. The month I've been only putting in a few minutes per day, mostly doing practice problems. Doing some DSA, OOP, and other practice problems. Making this post to keep people up to date. Currently figuring out my finances, driver's license, buying a car, finding a job and more. So I'm a little distracted and busy at the moment. That being said, I want to start getting back into more consistent deep study sessions. Keep you all posted and thank you for your support 👋 🚀 DAYS 720 - 746 OF #1000DaysOfCode

☄️Day 21-32 of 500DaysOfLittlePromise: The heat is something out of this world this year. I travelled from my current work place north of Japan to the south side in Fukuoka. Seriously, I didn't expect the weather to do a number on me like this: Here is a record of how much time was recorded for week 30(21-27): 64.9% was attributed to learning the OOP concepts, covering concepts such as collaborator object, the mechanism of how they fit into an 00P program, thus in week 31(07/28-08/02) I started working on the Rock Paper Scissors and adding more features. The program is in-progress, will report tomorrow on it.. A good time to slow down and zoom in and out as i work through this problem. Also, I have been reading the book to get better at improving my time and this concept of making daily highlights, and scheduling on the calendar as suggested by Jake Knapp and John Zeratsky has been keeping me sane. #productivity, #100DaysOfCode, #selfLearner #TimeManagement

☄️Day 14-20 of 500DaysOfLittlePromise A super quick update on 1️⃣ Technical Learning I ended up committing 13hrs 32min this week compared to the 16hrs planned. But it's no sweat, I realise that I have also done a few other activities that are related to my overral progress in covering and establishing a solid foundation for OOP concepts like: ª Inheritance: which discusses the inheritance of state and behaviors between classes. ᴮ Collaborator Objects: perhaps the toughest one that I am still trying to develop a mental model on: but in a nutshell, it describes the ability of an object's state to be stored in another. There are some key principles and some design considerations to implement this in code, and perhaps thats exactly what's keeping my head focused. ｃ. Module in Ruby: a different form of inheritance, important to Ruby because Ruby's inheritance is mostly single-class inheritance; therefore ,to allow more methods to be shared between classes, we do mixin with modules. - I followed these with a lot of practice problems, and I find myself doing a lot more mind mapping in this course than in the previous 🧘🏽. 2️⃣ Non-technical Strengthening my focus - We are distracted with a lot of things, and sometimes when we want to work on our goals, its like the world wants to work against us, trying to get fit and cut sugar, suddenly you brain cant stop thinking about the soda, oh goodness and the vending machines every 200meters in Japan don't make it easy. - For this, my target is to implement a strategy: Ⓐ Keeping a scoreboard for time spent to my learning session(target for week 30 is 16hrs). Ⓑ Allocate specific time to make this a deliberate intention.

@runliftrunlift How long was this @runliftrunlift ? Just from observation were you already coming from some sort of training prior?

My first year of running, I was very green. I didn’t have a watch for a while, didn’t know anything about heart rate or “zones” But after my first two marathons which were duds, I figured out two important things 1- If I ran intentionally slow, like a purposeful shuffle, I was able to get 1-2 hours time on feet almost every morning. It wasn’t exciting, so I’d listen to podcasts and pick different routes to explore Tokyo. I did this the entire summer. 2- If I rested an extra day or two, my legs felt springy, I was able to run much faster on less effort. This came by happenstance a couple times, getting food poisoning or mild plantar fasciitis that kept me out longer than I wanted. But that extra rest (plus carbs) was like rocket fuel. Those two things - getting a lot of mileage over several months and periodic deloads - made a huge difference in me going from a 4 hour to a sub 3 hour marathon. 1) Run easy so you can run a lot 2) Give your body rest when it needs it There’s more to running, but if you can get down the basics, you’ll improve a lot 🏃🏼‍♂️

Recap Way forward for #500DaysOfLittlePromises 🧘🏽Non-Technical - I have been thinking a lot about discipline and focus concepts. - Why does my discipline wane when I have to do important things? Can I force myself to focus through discipline? I think discipline has its limits when it comes to focus, even worse when one's mental model has been bruised, when discipline has been scared by not achieving or getting rewarded for what was thought might have bring rewards after a disciplined endeavour. I say this as someone who had to send their technical papers to journals after many months of disciplined hard work, and then getting rejected during my graduate studies. So for this, here are my plans to bring a different idea to stay focused on my endeavours, particularly upskilling in programming, working full time and maintaining important parts of my life. 1️⃣ Designing my environment: - What are my external and internal distractions? - Last week I recorded time spent on the phone, shocking, so i am going to put some constraints on this during the day, especially afternoon. This is where I find myself wanting to scroll on it the most, leaving me drained. 2️⃣ Constructing the right internal scripts: - Here, I intend to allocate 90 minutes per session for my work and personal projects, thereby making explicit limits. Often it gets very difficult, especially when I have to work in the morning and then rush for my commute. 3️⃣ Lastly, following my internal scripts; I want to be more intentional about my routines: my record shows commitments to my current long project of upskilling in programming, but its sessions have been sporadic. I am also hoping that by allocating specific times to this work and designating it as a package for its intent, I can be able to let go and take care of other things. That being said. This is likely to end up as a two-week sprint of testing these frameworks. I will report back.

Days 11-13 of #500DaysOfLittlePromises 🧑🏽‍💻 Technical Reviews - Programming OOP This week, I completed reading the OOP book from @LaunchSchool. The material from them is beginner-friendly and a good way to advance in this apprenticeship in programming. My key takeaways for understanding OOP are that we have three major concepts: 1. Encapsulation: which deals with the bundling of states and behaviours of objects. It is also a concept that describes the privacy of interfaces. 2. Polymorphism describes the ability for different data to respond to a behaviour. 3. Inheritance deals with the sharing of behaviours between classes. But what makes it possible for the implementation of these major concepts/frameworks? How do we see them in action? - This is where we have tools such as instance variables and methods, and class variables and methods to implement these frameworks. ⚙️How do they work? - Instance methods and variables can be thought of as a mechanism that helps achieve encapsulation by bundling object-specific state and behaviour: I found the demonstration of this encapsulation implementation through a problem that required me to parse a method that can modify and change the `name=`. - For this,I also learnt that the constructor only serves one purpose, at initialisation... lazy much... - Class methods and variables provide some class-level functionality that can be shared across all instances. - There is a lot that has gone on and obviously can't fit into this post, here is a diagram of my current mental mapping of the material.

💭 I have been thinking a lot about why I am taking this journey of programming, having to forgo other opportunities that seem great at this point. It may be the frustration of having to deal with productivity dragons that lingers, as I must budget and use my time wisely. Today, I came across an interesting research study that offers a different point of view on why we might procrastinate in the moment and wait until the 11th hour to do the work. 💡Prof. Piers Steel suggests that the culprit could be impulsiveness instead of the widely held belief that perfectionism is why we procrastinate. 👀Checking the phone at the first instance of discomfort when having to work on intellectually challenging things is an act of impulsiveness. It's an ongoing read as I am deeply interested in the topic of focus and how it plays to mastery. ☄️Day 9-10 of #500DaysOfLittlePromise Anyway, today I had a session with one of the students who is taking the Ruby intermediate course that I just completed at @LaunchSchool. It's those sessions that I'm always happy to be in, as they help me keep my fundamentals in check, and it's a way for me to give back my two cents. Speaking of two cents, I also had another session with a student ahead of me who quizzed me on the OOP concepts I just completed from the OOP book. While I haven't covered some sections, such as the difference between Namespacing as a concept under modules compared to namespacing in the context of constant variable scoping across classes, my current approach to the material is suggesting that by being engaged in every sessions I create for my self, I can see slightly in to the near future, or make sense before I even get to the material. That's motivating 😁! In the end, I completed all the end-of-chapter questions for the introduction to OOP. I now understand WHAT and WHY I need to understand these concepts. It's moving forward to HOW. 🔂Of course, this will be a circular approach to the material whenever I get stuck on some question, but my coverage is good enough for me to know what to look for when I reach that point of revisit. Also, I must admit that this summer, I am so exhausted in the evenings that I can barely keep my eyes open. Any remedies?

@JackUnicyclist @launchschool ☄️☄️☄️☄️☄️☄️ congratulations 🎉 @Jack, cant wait for our meet up. And a quick reflection to this last test! You did it!!

I PASSED!! I passed the DSA interview exam at @launchschool 🎉🥳 This was by far the hardest course out of the entire Launch School curriculum and I was happy to get it done after spending so much time on studying DSA. The interview went well, but I got some incredibly valuable feedback from the interviewer on areas I could improve on. Here are some reflection on that feedback and my experience: Hoping this helps others avoid some common interviewing mistakes 👇 1️⃣ Stay calm and don't panic At one point I felt like I was running out of time (the time limit for solving the problem was 45 minutes), so I began to rush a bit and for a brief period started to hack 'n' slash a solution. Turns out, I had waaay more time than I felt like I had. I skipped some testing because of this slight stress and I could've mitigated an "off-by-1" error that lead to a less efficient solve time and got me into hacking 'n' slashing. Panic leads to you not communicating as clear and working less logically. Luckily, I didn't hack 'n' slash for long, which leads me to my next point (something I did well, but could've done better): 2️⃣ When in doubt, go back to the logic Soon enough, I recognized this internal stress and decided to take a deep breath and go back to the logical part of the problem. The problem isn't your coding skills, it's the logic. I communicated that I needed to revisit the logic and did so. Running through the pseudo-code algorithm I had written up, I caught the error in my logic, edited my algorithm and then implemented that change in code. 3️⃣ Test Frequently It's tempting to not test when you think you don't have the time. In reality, you have more time than you think AND the fact that you're staying in control of your code is a lot more valuable than solving a problem with the MOST efficient time. When I got panicked about the time I skipped a few valuable tests I should've done while writing the code for my solution. This lead to having to debug more and using up even more time. There's more value in you being thorough and testing frequently for a few reasons: - It demonstrates a calm demeanour when faced with a challenge - It mitigates bugs that could use up even more time in solving the problem - It shows that you're in control of the code you're writing - It shows good due-diligence in your coding practice ----- Other than these points, I did good on the rest of the problem. The solution passed all test cases, I wrote up the correct test cases, and my break down and inquiry towards the problem was good. Super thankful to have passed this assessment! Thanks to everyone who helped me study DSA and who encouraged me throughout, this was a hard course and I needed it! 😅 Also, shoutout to Zane (an LS student who's in the Capstone program right now) for frequently helping me prep for this assessment and taking the time to give me solid feedback and motivation. Now I'm moving onto the Object Oriented JavaScript course at Launch School, getting me 1 step closer to my goal of becoming a Capstone grad 👊 🚀 DAYS 695 & 696 OF #1000DaysOfCode ⏰ 2.5 Hours #DSA #100DaysOfCode #LearnInPublic

@JackUnicyclist @launchschool I knew you would 🙌🏾🙌🏾🙌🏾🙌🏾,

@refSandie @launchschool Thank you for the encouragement @refSandie 🙌 Happy to say I passed the interview 😁

Tomorrow's the big interview... Tomorrow I take @launchschool's DSA interview exam. It'll test me on the basics of DSA with a practice problem in a live interview where I'm expected to effectively communicate my implementations, logic and problem-solving process. I'm a little nervous because I'm not sure how I'll do. I'm tired of giving boring posts telling you that "I'm grinding DSA problems", so I thought I'd take the plunge and schedule it for tomorrow 😅 I like to think that the Launch School exercise problem sets becoming boring is a good sign, but I've been humbled too many times by my own ego and illusion of competency that I'm open to the concept of failing. Which is also okay, because a failing grade will teach me something valuable I'm sure. Ultimately, things will be good. The past few days AI has come in handy for generating similar practice problems based off Launch School's exercise problems which has helped give me some variety and an added challenge. Wish me luck 🤞 🚀 DAYS 692 - 694 OF #1000DaysOfCode ⏰ 2.75 Hours #100DaysOfCode #dsa #ai

@runliftrunlift A few weeks ago, i asked for your help in getting into running, im in my 30’s and it’s definitely true that letting it be personal is best approach. Still working on getting into some consistency into between learning , fulltime job in a Japanese company💪🏾

Starting to run in your late 30s-40s is a whole different ballgame than someone who started running in high school or college. Accordingly, your expectations should line up with your training/sports background. Don’t worry about anyone but yourself. Some runners might be your same age, but they’ve been in the game a long time, and have thousands of miles on their legs. Wherever you are now, you still have a lot of room for improvement. Stay consistent and enjoy the ride 🏃🏼‍♂️

It has been a while since my #100DaysOfCode logs. I haven't been slacking, in that time I have passed the @LaunchScohool Ruby Intermediate assessment and have moved on to OOP programming. 💪🏽 Because of the 100 Days of Coding, I have found it to be a generally good accountability partner, so in that spirit, I am moving on to 500-days challenge. But with a twist, this is going to be #500DaysofPromises. 📶 The reality is that, while this career transition is my first and most important priority, there are other parts of life that I must maintain to make sure I attain this goal. In the spirit of what these days📅/weeks/months🗓️ will look like, I will give 2-3 focus points for each week (I only provide 1 for this week for brevity🙏🏽) 1️⃣A daily highlight to mark the most important thing that needs to be taken care of. -- I am using this system to ensure that I keep track of my focus on the most important things that need to be taken off each day of the week. And the highlight for today, Day 8 of #500DaysofPromises, was to complete the reading in the OOP book. Here are the key takeaways: - 3 major key concepts make up the foundation for an Object Model in OOP. These include: ✉️ Encapsulation: describes the bundling of data and its behaviors. These bundling properties control what can be shown to the public and what can be hidden during implementation. - Polymorphism: explains the common behaviors that different data types share. - Inheritance: describes a property in which classes inherit from other classes. - Interestingly, in this concept, we learn that there are other ways in which inheritance occurs, and that is through interface inheritance, which is described by utilising the mixin of a module into a class. - I get why OOP was created because dealing with so many features needs some thoughtful design as programs grow larger. I am honing my skills and will focus on practising problems using @launchschool material.