We are launching the largest open-source initiative in @rootlyhq's history: On-Call Health
It helps engineering teams ensure their on-call responders aren't overworked or at risk of burnout.
Try it right now at https://t.co/Cxu20mdVJ2. We provide mock data, no setup required.
Man... I am getting misty thinking about everyone I have met over 10 years of going to #ngconf and all the friends I have made along the way. @angular has been so much more than a framework to me. much, much more...
Speaking of great friends... I would have never guessed the miles that @jeffwhelpley and I would experience together. What started out as "I'm stuck" conversation has turned into a deep, collaborative friendship. To this day, he challenges me to be my best. 🫶
Just thinking about people have had a HUGE impact on my career and @donnfelker is at the top of the list. From first five minutes I saw him speak, I knew I wanted to be like him. He graciously gave me his playbook and encouraged me the entire way. No one succeeds in a vacuum.
I love everything that @ManfredSteyer does... not at all embarrassed to admit that he has deeply informed the way I think about frontend architecture. Oh! And he is super nice as well!
I proudly announce: The 6th edition of our free eBook on #AngularArchitecture
☑️ 20 chapters, PDF & epub
☑️ Strategic Design w/ Nx and Sheriff
☑️ Native Federation & esbuild
☑️ The new NGRX Signal Store
⬇️ Download it now!
https://t.co/qE3dMGUIR2
The problem with this article is that is inflammatory by nature (classic Crockford modus operandi) and yet the supporting argument is a single, anemic example that fails to establish context and nuance. It is amusing/fitting that he used the three stooges to make his point.
“The DOM is much less deficient and much more portable and reliable. That is why I now recommend abandoning the libraries, which have grown into bloated platforms, and instead using the DOM and plain old JavaScript together.” https://t.co/nHLcm9PerR
@allingeek Your wording shows that you are thinking about this at a project level. We are buddies so I have the luxury of historical context and I agree. Change the abstraction level to the component layer and code duplication is the devil i.e. nested logic and SRP violations.
@allingeek Sure,but that requires a conversation to establish logical boundaries. "DRY is important as long as..." You need a conceptual framework to know when and why.
@bahmutov And suddenly that bike would look like a JavaScript framework! 🤣 What teamwork! WE just made the point I was trying to make by myself. LOLOLOL
"Bicycles are so much more portable and reliable, and so I recommend we abandon cars entirely. I am going to prove this by riding my bicycle around the block."
“The DOM is much less deficient and much more portable and reliable. That is why I now recommend abandoning the libraries, which have grown into bloated platforms, and instead using the DOM and plain old JavaScript together.” https://t.co/nHLcm9PerR
@bahmutov Context matters which is what our friend Mr. Crockford failed to provide when he made his "point." Also, I was waiting for you to push back on bikes. HAHAHAHA
@bahmutov Agreed! Bicycles ARE awesome, and depending on the situation should be preferred over cars. But we should not abandon cars wholesale or even stop trying to build a better car. I don't think you would want to come and visit me all the way across the country on a bike.
The Coding Bootcamp in Prison mini-documentary from @FrontendMasters is so profound and yet so consistent with what I have seen from @1Marc and crew from day one. I ♥️💯 the legacy that FEM is creating by changing lives through coding.
https://t.co/Jlcm4NhhQS