…it’ll be wise to probably build a basic avatar component and keep in mind that my next PR will likely be adding the user’s chosen border colour around the picture. Anything beyond this would be premature abstraction imo!
…it’ll be wise to probably build a basic avatar component and keep in mind that my next PR will likely be adding the user’s chosen border colour around the picture. Anything beyond this would be premature abstraction imo!
…you’re likely to build? Maybe abstract for that. For example, if I have to build an avatar component, and I know right now I just need to show a profile picture in a circle, I won’t overthink it. But if I know that in the next cycle, we’re going to allow colourful borders…
…you’re likely to build? Maybe abstract for that. For example, if I have to build an avatar component, and I know right now I just need to show a profile picture in a circle, I won’t overthink it. But if I know that in the next cycle, we’re going to allow colourful borders…
1. unless your software demands it, performance/elegance is a *quality* and not a requirement, within reason of course. If the code gets the job done, ship it.
2. Think of the product roadmap. What’s the next feature (1/2)
1. unless your software demands it, performance/elegance is a *quality* and not a requirement, within reason of course. If the code gets the job done, ship it.
2. Think of the product roadmap. What’s the next feature (1/2)