I often see web apps with separate frontend and backend dev teams.
This front/back developer split leads to a common problem: Frontend devs become victims of backend problems that they can't fix.
Common backend problems:
🚩Instability
🚩Performance
🚩Clunky API design
🚩Poorly structured JSON
A frontend team can't fix these issues alone. They can only try to mitigate them via client-side caching, optimistic UI, etc.
The backend team holds the political power in this relationship, because the frontend team relies upon the backend.
Three solutions I've seen work:
1. If the backend is for a single frontend, consider merging the teams.
2. Consider a monorepo to foster collaboration. This also allows the frontend devs to open PRs for simple backend changes.
3. A single manager over the frontend and backend can assure the backend team is responsive to frontend concerns.
🔥 VS Code Tip 🔥
Did you know you can add section headers to the minimap of @code?
Use "MARK:" in the comment, and the designation will be clearly visible in the minimap, which will help you quickly scan and navigate your files.
Did you know `color-mix` is already available in all browsers? We can finally use #CSS variables and add transparency to them when we need to, without introducing extra variable or jumping through hoops of using separate variables for RGB channels:
https://t.co/QGusmTj2nP
🧐 the most common cases when I reviewed #Angular code
Combine the Input and HostBinding decorators to set the value of an input parameter as a class to the component's host element.
#AngularCodeReview
Can You Read the Code You Wrote Last Week? How to Do Better
@John_Papa: The positive impact of readable code on your career can be huge as devs spend far more time reading code than writing.
#softwaredevelopment#readablecode#codereadability#coding
https://t.co/F6QNQZio87
@joshuamorony Ah I see thanks, I just set up an NX workspace for the first time and I see library tsconfig paths are by src/index.ts not dist/*, which is what I'm working with currently.
Thanks for your help :)
@joshuamorony Hi Josh, when you are working on multiple libraries at the same time within a workspace, do you 'ng watch' each of them in sequence or is there a better way?
@joshuamorony Do you build the libs after each edit or does nx serve watch those files for you? I'm trying to migrate from a custom local dev webserver to nx serve, currently I watch the apps and any libraries I'm editing, think I've misconfigured something somewhere
#Angular dependency injection is way more powerful than one might think. We can, for example, use it to choose which implementation of a service to use. Here is an example of using a `console.log` logger in development and another one in production:
I strongly identify as a Product Engineer.
Not as:
- Developer (I only like building user-facing things)
- Full stack (I want to help with shaping, roll-out, strategy)
- Entrepreneur (not interested in company building)
- Indie hacker (like working with team, not into quick and dirty stuff)
- Design/Dev unicorn (my design taste > my skill)
I really like going from a customer problem into "potential solution mode" and then taking it all the way to code on production.
I'm having trouble finding (...and hiring) people like me. Who should I be talking to?
#FrontendSnack 18💡You can reduce the amount of Change Detection cycles in #Angular with the ngZone property called ngZoneEventCoalescing. Note! It might have some side effects, so test it well. Also...👇
💁🏼♂️ I publish advanced Angular video tutorials here https://t.co/SKNyeL1bkB
#AngularTip of the day! Make a very simple #Angular component for ticker/running text to show full overflown text upon hover/tap.
Live demo:
https://t.co/bzV6gb9gC9