Lynn Hardy

... has a low tolerance for high latency.

[Lynn Hardy @webprodigy]

Do you remember when you joined X? I do! #MyXAnniversary

lol...I actually don't remember. That was a long time ago.

[Lynn Hardy @webprodigy]

I was recently told that I wasn't "obsessed enough with programming" but here I am on a Saturday digging into optimizing recursive functions in javascript. How dare they.

[Lynn Hardy @webprodigy]

I'm building a serverless app from scratch using a cloudformation template. FYI, AWS and medium and the rest of ya, update yo kb. chatgpt knows best.

[Lynn Hardy @webprodigy]

AWS Cloudformation Template Rule #1: Your template is not valid if you don't have any resources to build. How did I test this? I tried commenting out all of the resources in an old crap stack. Fail! The solution? Delete the stack in the console instead...sweaty palms an all.

[Lynn Hardy @webprodigy]

CodeBuild, you have one job to do.

[Lynn Hardy @webprodigy]

About AWS cloudformation templates, I have a new goal of being able to create them from scratch. Why are they important? You know, infrastructure as code is kinda sexy.

[Lynn Hardy @webprodigy]

@rhappe I wonder if "lord" is thinking, now people are tweeting their prayers.

[Lynn Hardy @webprodigy]

@sussmansa @AWS Which aws codebuild image are you using for node 18?

[Lynn Hardy @webprodigy]

@libsoftiktok stop judging!

[Lynn Hardy @webprodigy]

@chezsmithy yeah, thanks for that reminder. one step at a time. and "hi shawn :) "

[Lynn Hardy @webprodigy]

Work Rant: Upgrading from node 12 to 16 is no fun! The new Linux image that we use for Lambdas doesn't play nice with the old yaml syntax in our cloudformation templates and node 16 doesn't like old reactJS code. And then there is a GPG problem inherent in the Linux image itself.

[Lynn Hardy @webprodigy]

Big O Notation Series #1: Big O For Software Engineering https://t.co/LUGqJad8uU via @YouTube

I am not going to underestimate the value of simplicity. This series gives a great visual to better understand how to determine Big O.

[Lynn Hardy @webprodigy]

What do you do when you see an obstacle in your path? Do you focus on it or do you focus on where you want to go?

[Lynn Hardy @webprodigy]

I'm getting ready to build a serverless react native app. I planned on building it from scratch. Then I went down a rabbit hole and was tempted by a blueprint to start coding right away. That takes away half the fun.

[Lynn Hardy @webprodigy]

Still working my way through the Big O logic of determining how runtime scales.

[Lynn Hardy @webprodigy]

Make your program more simple and easy to read. Get rid of promises and promise chaining. Start using async/await. It's so much easier to read and you don't need to control every event.

[Lynn Hardy @webprodigy]

I spend a lot of time extracting values from API payloads to make something else happen. One of my favorite native JavaScript methods is .map to create a new array from the values I need and apply a new key if needed. If I just need a list of values, I'll use Object.values

[Lynn Hardy @webprodigy]

Day 13: Big O, it's about time we get to know each other a little better. When describing how runtime scales, the most commonly used descriptions are O(A+B) and O(A*B) for multi-part, O(log N), and O(N) for recursive.
#100DaysofCode

[Lynn Hardy @webprodigy]

Day 12: When faced with checking whether or not an update happened via a 3rd party API call, instead of writing another API call to get the record and interrogating the data, I used a flag and if/then to determine that the call was successful.
#100DaysofCode

[Lynn Hardy @webprodigy]

Day 12: DYNAMO DB in AWS
Build a single table database using a cloudformation template to adhere to infrastructure as code. Use the DynamoDB class that's natively available in the aws-sdk and build a NodeJS object to query the database.
#100DaysofCode