That feeling you get when you developed a cool new feature, only to find that it is already been done and even much better! Thanks @NxDevTools you can use these executors to version, build and deploy your packages to an NPM registry, nice https://t.co/NTVTxrnW7a
@greg_radzio Remove the responsibility of data access and management of the request entirely from the component. Keep the component simple - reduce its footprint. This is a mediator/adaptor pattern used commonly in CLEAN architecture.
@greg_radzio The component's responsibiity is to display and collect data...not retrieve it. What if there is an `error` from the request. Where is that handled - again, use the "UIService" to set some readonly Observables for the component to manage its display state.
How would you describe leadership from a technical stand point? Is your current leadership taking you in the right direct. Things are changing fast in IT - we need leadership more than ever, can you follow your leaders?
It might surprise you that there is good technical debt. Are you pushing the envelope? How do you identify debt that needs immediate attention? https://t.co/kiZUWqPWAZ
@scrumtuous @craig_davld There’s no short cut to being a professional, right? If so, we’d all have amazing multimillion dollar contracts… it is a combination of hard work and experience. When you have both of these, the next thing you need is an opportunity!
@scrumtuous Why not both? Take a look at @NxDevTools Workspace…a monorepo that supports Angular, NestJS, React application projects. And wait, there’s more: support for library projects for each tech stack.
@mariofusco The future of software is in a world of hurt. Denying the usefulness of design patterns is immature and wreckless - good luck with your projects. And BTW, stop using things that use these patterns and imagine what your app-life would be like!