Podcasts about when aj

AJ came from a broken but supportive home.  He didn't know his dad and wasn't part of his life growing up.  He was raised by his grandparents and mother in a 3-bedroom apartment.  At the age of 15, AJ got his record deal with the Backstreet Boys.  His newfound stardom gave AJ the motivation to move out of his house at the age of 17, after getting in a huge fight with his mom. AJ didn't actually start drinking until he was 25.  He started with hard alcohol right off the bat and got worse from there.  Then during an early morning music video shoot, he tried cocaine for the first time.  After that, he was buying large amounts from a friend in Florida.  AJ was up to an 8 ball a day.  Eventually AJ overdosed and was revived with an adrenaline needle, just like the scene with Uma Thurman in Pulp Fiction.  You would think that would be enough for AJ to stop, but it wasn't. In 2001, the Backstreet Boys were supposed to throw out the first pitch at a Boston Red Sox game.  AJ was partying the night before and woke up hungover, and told his manager that he wasn't going.  This prompted a fight with his band members where he quit the band on the spot.  The manager gave him the option of going to rehab, and he accepted. AJ stopped drinking and using drugs for the first time in 2001.  He was able to stay sober for 7 years.  Then in 2008, out of the blue, their friend Shania Twain had a concert coming up in Las Vegas.  Originally, AJ wanted to do a date night with his wife at the show, but she couldn't make it and said to go by himself.  AJ knew his wife wouldn't be there with him, so immediately he called his dealer.  He thought he would be able to sober up before coming back home, but he just couldn't stop.  Then again in 2019, Backstreet Boys had their massive DNA World Reunion Tour.  When AJ got the call to go to Vegas for the residency, his wife called him and told him “Don't even bother coming home” because she knew he was partying too much.  The breaking point for him was when he got home, his daughter came to sit by him on the couch.  Normally she cuddles with him, but this time she said “you don't smell like my dad” and this crushed AJ.  This was the catalyst to get help and begin his sobriety. The pandemic recently was the silver lining for AJ.  None of the temptations from the road were messing with his mental health, so he could really focus on his family and health.  AJ has now been sober for 20 months.  He's traveled twice by himself now, and hasn't relapsed.  Now he's part of the “Pretty Messed Up Podcast” along with Cheryl Burke & Rene Elizondo where they talk about their problems, addictions and how they're dealing with them.  Now with his new podcast, AJ hopes to remove the stigma with mental health by speaking openly about his experiences. This is AJ McLean in his own words, on Knockin' Doorz Down. For Carlos Vieira's autobiography Knockin' Doorz Down https://www.kddmediacompany.com/ For 51FIFTY use the discount code KDD20 for 20% off! https://51fiftyltm.com/ https://www.facebook.com/51FIFTYLTM https://www.instagram.com/51fiftyltm/ https://twitter.com/51fiftyltm For more on the Knockin' Doorz Down podcast and to follow us on social media https://www.kddmediacompany.com/podcast https://www.instagram.com/knockindoorzdown/ https://www.facebook.com/knockingdoorsdown/ https://twitter.com/kddmediacompany https://www.youtube.com/channel/UCUSJ5ooBFqso8lfFiiIM-5g/  For more information on the Carlos Vieira Foundation and the Race 2B Drug-Free, Race to End the Stigma, and Race For Autism programs visit: https://www.carlosvieirafoundation.org/ https://www.facebook.com/CVFoundation/ https://www.instagram.com/carlosvieirafoundation/ For more on AJ McLean: https://www.facebook.com/AJMcLean https://www.instagram.com/aj_mclean/ https://twitter.com/aj_mclean https://www.youtube.com/channel/UCaLkX_Si9eHmSQV30eaX2UA

Claire from Tacoma says her boyfriend AJ is freaking out over a butt-dial call from her ex-boyfriend. She says it was totally just an accident, the Ex left a message saying so, and she thought it was funny and actually showed it to AJ not realizing he would totally obsess over it. Now AJ brings the Ex up all the time and is suspicious of all Claire’s plans and calls, asking her a lot more questions about where she’s going and what she’s doing. When Fitz says sometimes guys just want to “check in” and AJ is right to be nervous, Claire insists she loves AJ and has no interest in the Ex but admits AJ is being a total jerk and she’s not happy with him at the moment. When AJ comes on he says he’s not insecure, he just knows how guys think and thinks the Ex was totally testing the waters and Fitz agrees. But then he spends the rest of his time quizzing Claire on the identities of all the other people in her phone; turns out AJ’s got a little baggage.

In episode one of the Making Strides Podcast, we wanted to give you, the listeners, an introduction to who we are and our background. We talk about our schooling and how we got into running. While Adam's is rather traditional, AJ had a very unique experience to open him up to his possibilities as a runner. Having a combined 9 years of experience, we have many patient stories that we can share. In this episode, we each share a story surrounding a success and an experience where we both had to step back and learn from due to a not so great outcome. We hope you enjoy this episode and look forward to sharing more of our thoughts around everything running in the coming episodes!   1:35 Purpose of podcast and how it fits into the podcast world 5:35 Adam's background academically and in running 7:15 AJ's background academically  9:45 AJ's path to running 11:40 Adam's patient success story 13:15 Adam's missed bone stress injury 14:40 AJ's missed bone stress injury 16:15 When AJ feels full-filled in patient care   AJ's website at Up and Running Physical Therapy Adam's website at RunMental   Watch this podcast episode on YouTube!

Valeri Karpov is a maintainer on Mongoose, has started a few companies, and works for a company called Booster Fuels. Today’s topic debugging with Async/Await. The panel talks about some of the challenges of debugging with Async. AJ, however, has never encountered the same problems, so he shares his debugging method.  Valeri differentiates between .catch vs try...catch, and talks about why he prefers .catch. There are two ways to handle all errors in an async function without leading to an unhandled promise rejection. The first is to wrap the entire body of the async function in a try...catch, has some limitations. Calling an async function always returns a promise, so the other approach is calling .catch on the promise to handle any errors that occur in that function body. One of the key differences is if you return a promise within an async function, and that return promise is wrapped in a try...catch, the catch block won’t get called if that promise is rejected, whereas if you call .catch on the promise that the function returns, you’ll actually catch that error. There are rare instances where this can get tricky and unintuitive, such as where you have to call new promise and have resolve and reject, and you can get unexpected behavior. The panel discusses Valeri’s current favorite JS interview question, which is,  “Given a stream, implement a function called ‘stream to promise’ that, given a stream, returns a promise that resolves to the concatenation of all the data chunks emitted by the stream, or rejects if the stream emits an error event.” It’s really simple to get this qustion right, and really simple to get it wrong, and the difference can be catastrophic. AJ cautions listeners to never use the data event except in the cases Val was talking about, only use the readable event. The conversation turns to the function of a readable event. Since data always pushes data, when you get a readable event, it’s up to you to call read inside the function handler, and then you get back a chunk of data, call read again and again until the read returns null. When you use readable, you are in control and you avoid piling functions into RAM. In addition, the right function will return true or false to let you know if the buffer is full or not. This is a way to mix imperative style into a stream. The next discussion topics are the differences between imperative style and reactive style and how a waits and promises work in a normal four loop. A wait suspends the execution of a function until the promise is resolved. Does a wait actually stop the loop or is it just transpiling like a promise and it doesn’t stop the loop. AJ wrote a module called Batch Async to be not as greedy as promise.all but not as limited as other options. The JavaScript panelists talk about different async iterators they’ve used, such as Babel. They discuss the merits of Babel, especially since baseline Android phones (which a significant portion of the population of the world uses) run UC Browser that doesn’t support Babel, and so a significant chunk of the population of the world. On the other hand, if you want to target a large audience, you need to use Babel. Since frameworks in general don’t handle async very well, the panel discusses ways to mitigate this. They talk about different frameworks like Vue, React, and Express and how they support async functions. They discuss why there is no way for you to actually cancel an async option in an actual case, how complex canceling is, and what you are really trying to solve for in the cancellation process.  Canceling something is a complex problem. Valeri talks about his one case where he had a specific bug that required non-generic engineering to solve, and cancelling actually solved something. When AJ has come across cancellation issues, it’s very specific to that use case. The rest of the panelists talk about their experiences with having to cancel something.  Finally, they talk about their experience with async generator functions. A generator is a function that lets you enter into the function later. This makes sense for very large or long running data sets, but when you have a bounded items, don’t complicate your code this way. When an async generator function yields, you explicitly need to call next in order for it to pick up again. If you don’t call ‘next’, it’s essentially cancelled. Remember that object.keys and object.values are your friends.  Panelists Christopher Buecheler AJ O’Neal Charles Max Wood With special guest: Valeri Karpov Sponsors The DevEd Podcast Sentry use the code “devchat” for 2 months free on Sentry’s small plan Adventures in DevOps Links Mongoose Express 5 Node Streams Pull Streams Masteringjs.io MongoDB Babel HTML Webpack Vue Express RxJS Console.log Json.stringify Batchasync.js How to Write Batch Async Functions Follow DevChatTV on Facebook and Twitter Picks AJ O’Neal: Ethan Garofolo YouTube Christopher Buecheler: Functional Design Patterns for Express.js Charles Max Wood: Microsoft Ignite Maxcoders.io Valeri Karpov: Follow Valeri on Twitter @code_barbarian and Github @vkarpov15 Masteringjs.io Jurassic Park: A Novel

Valeri Karpov is a maintainer on Mongoose, has started a few companies, and works for a company called Booster Fuels. Today’s topic debugging with Async/Await. The panel talks about some of the challenges of debugging with Async. AJ, however, has never encountered the same problems, so he shares his debugging method.  Valeri differentiates between .catch vs try...catch, and talks about why he prefers .catch. There are two ways to handle all errors in an async function without leading to an unhandled promise rejection. The first is to wrap the entire body of the async function in a try...catch, has some limitations. Calling an async function always returns a promise, so the other approach is calling .catch on the promise to handle any errors that occur in that function body. One of the key differences is if you return a promise within an async function, and that return promise is wrapped in a try...catch, the catch block won’t get called if that promise is rejected, whereas if you call .catch on the promise that the function returns, you’ll actually catch that error. There are rare instances where this can get tricky and unintuitive, such as where you have to call new promise and have resolve and reject, and you can get unexpected behavior. The panel discusses Valeri’s current favorite JS interview question, which is,  “Given a stream, implement a function called ‘stream to promise’ that, given a stream, returns a promise that resolves to the concatenation of all the data chunks emitted by the stream, or rejects if the stream emits an error event.” It’s really simple to get this qustion right, and really simple to get it wrong, and the difference can be catastrophic. AJ cautions listeners to never use the data event except in the cases Val was talking about, only use the readable event. The conversation turns to the function of a readable event. Since data always pushes data, when you get a readable event, it’s up to you to call read inside the function handler, and then you get back a chunk of data, call read again and again until the read returns null. When you use readable, you are in control and you avoid piling functions into RAM. In addition, the right function will return true or false to let you know if the buffer is full or not. This is a way to mix imperative style into a stream. The next discussion topics are the differences between imperative style and reactive style and how a waits and promises work in a normal four loop. A wait suspends the execution of a function until the promise is resolved. Does a wait actually stop the loop or is it just transpiling like a promise and it doesn’t stop the loop. AJ wrote a module called Batch Async to be not as greedy as promise.all but not as limited as other options. The JavaScript panelists talk about different async iterators they’ve used, such as Babel. They discuss the merits of Babel, especially since baseline Android phones (which a significant portion of the population of the world uses) run UC Browser that doesn’t support Babel, and so a significant chunk of the population of the world. On the other hand, if you want to target a large audience, you need to use Babel. Since frameworks in general don’t handle async very well, the panel discusses ways to mitigate this. They talk about different frameworks like Vue, React, and Express and how they support async functions. They discuss why there is no way for you to actually cancel an async option in an actual case, how complex canceling is, and what you are really trying to solve for in the cancellation process.  Canceling something is a complex problem. Valeri talks about his one case where he had a specific bug that required non-generic engineering to solve, and cancelling actually solved something. When AJ has come across cancellation issues, it’s very specific to that use case. The rest of the panelists talk about their experiences with having to cancel something.  Finally, they talk about their experience with async generator functions. A generator is a function that lets you enter into the function later. This makes sense for very large or long running data sets, but when you have a bounded items, don’t complicate your code this way. When an async generator function yields, you explicitly need to call next in order for it to pick up again. If you don’t call ‘next’, it’s essentially cancelled. Remember that object.keys and object.values are your friends.  Panelists Christopher Buecheler AJ O’Neal Charles Max Wood With special guest: Valeri Karpov Sponsors The DevEd Podcast Sentry use the code “devchat” for 2 months free on Sentry’s small plan Adventures in DevOps Links Mongoose Express 5 Node Streams Pull Streams Masteringjs.io MongoDB Babel HTML Webpack Vue Express RxJS Console.log Json.stringify Batchasync.js How to Write Batch Async Functions Follow DevChatTV on Facebook and Twitter Picks AJ O’Neal: Ethan Garofolo YouTube Christopher Buecheler: Functional Design Patterns for Express.js Charles Max Wood: Microsoft Ignite Maxcoders.io Valeri Karpov: Follow Valeri on Twitter @code_barbarian and Github @vkarpov15 Masteringjs.io Jurassic Park: A Novel

Valeri Karpov is a maintainer on Mongoose, has started a few companies, and works for a company called Booster Fuels. Today’s topic debugging with Async/Await. The panel talks about some of the challenges of debugging with Async. AJ, however, has never encountered the same problems, so he shares his debugging method.  Valeri differentiates between .catch vs try...catch, and talks about why he prefers .catch. There are two ways to handle all errors in an async function without leading to an unhandled promise rejection. The first is to wrap the entire body of the async function in a try...catch, has some limitations. Calling an async function always returns a promise, so the other approach is calling .catch on the promise to handle any errors that occur in that function body. One of the key differences is if you return a promise within an async function, and that return promise is wrapped in a try...catch, the catch block won’t get called if that promise is rejected, whereas if you call .catch on the promise that the function returns, you’ll actually catch that error. There are rare instances where this can get tricky and unintuitive, such as where you have to call new promise and have resolve and reject, and you can get unexpected behavior. The panel discusses Valeri’s current favorite JS interview question, which is,  “Given a stream, implement a function called ‘stream to promise’ that, given a stream, returns a promise that resolves to the concatenation of all the data chunks emitted by the stream, or rejects if the stream emits an error event.” It’s really simple to get this qustion right, and really simple to get it wrong, and the difference can be catastrophic. AJ cautions listeners to never use the data event except in the cases Val was talking about, only use the readable event. The conversation turns to the function of a readable event. Since data always pushes data, when you get a readable event, it’s up to you to call read inside the function handler, and then you get back a chunk of data, call read again and again until the read returns null. When you use readable, you are in control and you avoid piling functions into RAM. In addition, the right function will return true or false to let you know if the buffer is full or not. This is a way to mix imperative style into a stream. The next discussion topics are the differences between imperative style and reactive style and how a waits and promises work in a normal four loop. A wait suspends the execution of a function until the promise is resolved. Does a wait actually stop the loop or is it just transpiling like a promise and it doesn’t stop the loop. AJ wrote a module called Batch Async to be not as greedy as promise.all but not as limited as other options. The JavaScript panelists talk about different async iterators they’ve used, such as Babel. They discuss the merits of Babel, especially since baseline Android phones (which a significant portion of the population of the world uses) run UC Browser that doesn’t support Babel, and so a significant chunk of the population of the world. On the other hand, if you want to target a large audience, you need to use Babel. Since frameworks in general don’t handle async very well, the panel discusses ways to mitigate this. They talk about different frameworks like Vue, React, and Express and how they support async functions. They discuss why there is no way for you to actually cancel an async option in an actual case, how complex canceling is, and what you are really trying to solve for in the cancellation process.  Canceling something is a complex problem. Valeri talks about his one case where he had a specific bug that required non-generic engineering to solve, and cancelling actually solved something. When AJ has come across cancellation issues, it’s very specific to that use case. The rest of the panelists talk about their experiences with having to cancel something.  Finally, they talk about their experience with async generator functions. A generator is a function that lets you enter into the function later. This makes sense for very large or long running data sets, but when you have a bounded items, don’t complicate your code this way. When an async generator function yields, you explicitly need to call next in order for it to pick up again. If you don’t call ‘next’, it’s essentially cancelled. Remember that object.keys and object.values are your friends.  Panelists Christopher Buecheler AJ O’Neal Charles Max Wood With special guest: Valeri Karpov Sponsors The DevEd Podcast Sentry use the code “devchat” for 2 months free on Sentry’s small plan Adventures in DevOps Links Mongoose Express 5 Node Streams Pull Streams Masteringjs.io MongoDB Babel HTML Webpack Vue Express RxJS Console.log Json.stringify Batchasync.js How to Write Batch Async Functions Follow DevChatTV on Facebook and Twitter Picks AJ O’Neal: Ethan Garofolo YouTube Christopher Buecheler: Functional Design Patterns for Express.js Charles Max Wood: Microsoft Ignite Maxcoders.io Valeri Karpov: Follow Valeri on Twitter @code_barbarian and Github @vkarpov15 Masteringjs.io Jurassic Park: A Novel

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money?

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money?

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money?

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money?

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money?

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money? 

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money? 

It can get a little dicey, and of course depend on each situation, but what is the policy for lending family money? When AJ was a kid he believed that it was unquestioned and you let them borrow for the Debate At 8, but life can be a harsh teacher. McCall has a much stricter policy across the board, no for everyone. When it comes to borrowing, what is too much to ask for? Would you lend AJ & McCall money? 

Can you imagine the no win situation of mosh pitting with Shaq? Also, the Area 51 invasion has gotten way out of hand, even the creator of the event say so. When AJ & McCall did the Ginger Ale trying video the Radio Ranch ghost looks like it made an appearance. How far does McCall go to avoid germs? Where are the worst public restrooms? Who did chores this weekend, like dishes? Did you clean out the spoiled food or just throw the container out for the Debate At 8? If you had to put together a power point presentation to get your friend a date, how would it go? AJ is excited for 90s cartoons coming back but McCall doesn't really have the same tie to it. 

Week 2 of our no guest run. When will it end? When AJ remembers to check in with one before recording day lol. On this week's episode, AJ & Logan talk about the plausibility of the alleged Bandai Namco developed Metroid Prime 4's multiplayer, our thoughts on clickbait and the resulting backlash, our thoughts on the videos for the week, what we've been playing, and our thoughts on Monster Hunter's eventual 1st full fledged Switch game, and then we do Q&A! TIMESTAMPS 0:58 - Metroid Prime 4 Multiplayer 9:21 - Clickbait & Fan outrage 17:00 - Logans video 32:16 - Aj Video 53:01 - What have we been playing 55:13 - Monster Hunter Switch 59:27 - Q&A 59:59 - Being a guest on "DTY" 1:02:12 - Will Nintendo Do Mario Odyssey 2 or 2D Mario again? 1:04:26 - DL times for games on Switch/Network speeds Join our Discord server here ➡️ https://discord.gg/PXyeUQv Logan's last video: https://www.youtube.com/watch?v=6edWy... AJ's last video: https://www.youtube.com/watch?v=6edWy... RATE US ON iTUNES! --- Send in a voice message: https://anchor.fm/dty/message Support this podcast: https://anchor.fm/dty/support

AJ is a professional baseball player.  AJ will talk about how to be patient during difficult seasons of life. Group Questions: AJ talked about patience during his baseball career and shared about the moments of frustration, bitterness and feeling upset. Why is patience so unnatural for us? Would you consider yourself a patient person? Do the people around you add fuel to the fire when you are complaining? Do they agree with your thoughts of unfairness and entitlement?   Or do the people around you encourage you when you’re down? Are they people who are going to help you make wise decisions? Walk with the wise and you’ll grow wise. Are you being that kind of friend to any guys in your life? Who is it? AJ talked a lot about the company that you keep. When AJ’s friend Travis reminded him “You don’t write your story. Your job is to serve”, it became a turning point in his life. How does the idea of entitlement: “ I deserve, I deserve, I deserve” fight against the mentality of “I’m here to serve”? Read and discuss 1 Peter 5:6-10 How can we practically improve/grow in our patience? Are the things around us helping us or hurting us in that pursuit?

AJ Wilcox is a digital marketing master and performance marketing entrepreneur. He's the founder of B2Linked, a company that specializes in helping companies acquire customers from LinkedIn. He spent the early part of his career learning PPC and working for large enterprises and then transitioned into entrepreneurship. Though the beginning was rough, AJ persisted, and today his company is one of the leading agencies in customer acquisition. He and his team use proprietary marketing strategies to ensure that their clients get the highest ROI possible for every $1 spent on ads. When AJ is not helping companies fuel growth, he is a frequent guest/contributor on podcasts, social media conferences, and blogs. In this episode, we discuss AJ entrepreneurial journey and success habits and discuss practical applications of LinkedIn Advertising. What you'll learn about in this episode: Why LinkedIn marketing offers high ROI on advertising for B2B The best way to craft a LinkedIn marketing campaign The mindset, strategy, and tactics of a winning campaign And lots more. I hope you listen, learn and take plenty of notes. Resources: Twitter: @WilcoxAJ Website: www.b2linked.com

AJ Harmon was blessed with a village in her very own family. Born in Perth, Western Australia to English parents, AJ grew up on the beaches in the summer and studiously studying English, music and languages during the school year. Reading, dancing and cooking filled the rest of her time. Moving to the United States as a teenager opened her up to not only a new culture, but a faster paced life and eventually to her own Prince Charming as well. Now married for 29 years to her sweetheart, AJ is still perfecting their own happy ending, and loving every minute of it. When AJ came home one day from her accounting job and announced to her husband that she was writing a book–after the initial shock wore off–he immediately went to work on preparing marketing plans and strategies. As a small business marketing strategist, he was excited at the prospect of playing in the ‘big league’ with the giants of the publishing industry. Never shying away from a challenge, he was up to the task and took AJ on as his number one client. Turning to her son next, AJ has come to rely on him for most everything else.  Credits: A joint project with www.SexyBooksBlog.net   Music, Song for My Father, courtesy of www.AnnaFisher.com