@thickinbrooklyn @dasowth @123pleasant you rocked at broken goblet the other night. Totally went there just to see y'all. So glad I got to see you live!
New episode alert!
Special Guest Tom!
John and Chris have a special guest on today. We are interviewing Tom. Tom is a developer at Miles Technologies and has been developing software using the Breckenridge template ...
@PilgrimSecret@JohnGrahamDev
https://t.co/VBYuAyaBMQ
@BenLesh I've been teaching a technique @milestech where we just use an @angular service with BehaviorSubject (and some helper functions) to do light state management.
Works great honestly, and easy to follow and understand.
Last night I established a mentorship with a budding programmer that "needs" to get out of a bad job in customer service.
I can really relate to that. I spent nearly 17 years in "sales" before being a programmer. For me, it was THE BEST professional decision of my life.
New episode alert!
Component APIs
John and Chris talk about an option for controlling child components from parent components by creating an API for your component.
@JohnGrahamDev@PilgrimSecret@angular
https://t.co/ZE57XJGUSX
Just finished up a pair programming session with @JohnGrahamDev
So glad we have the opportunity for collaboration like that. Always learn something.
... and I get to take a break from my own skull-sized kingdom.
New episode alert!
Practical State Management
John and Chris talk practical state management in Angular applications. Format is a train-me episode where John plays the part of the audience, learning about state management from Chris.
@JohnGrahamDev@PilgrimSecret@angular
@ladyleet I'd love to have that going on ... but I don't think I would survive it. I've had to go low calorie on everything. Guess I'll have to enjoy them vicariously.
@holywolf232 @ngBuildPod Glad you were feeling motivated!
Yea, there are many exiciting ways to really tweek how the modules are loading. The optimization options seem to be near limitless.
TIL: of() and of(null) work differently with pipes
of().pipe(concatMap(...))
*does not* fire concatMap on subscribe
of(null).pipe(concatMap(...))
*does* fire concatMap on subscribe
I am guessing of() is just not a supported concept since its supposed to return something
#rxjs
@holywolf232 so looking closer at it, it's all because this line of code never gets hit, which I guess is the underlying thing to know about this ... if there is nothing in the off, it never says `.next` so it doesn't fire the pipes
https://t.co/xhQyKISJTJ
@holywolf232 I guess asking if it *is* or *is not* "supported" isn't really what I should be asking.
"should the developer expect that of() completes and will not fire subsequent pipes, but of(null) does fire them?"
I mean, I didn't tell it to complete.
What's the reasoning for this?