3 ms·

I'd say local code quality is generally good but overall it's a big hodge podge of small features duct-taped together, so the whole app becomes a tangled mess.

• Dwolb 4y ago
  How would you measure impact?
  • zhengyi13 4y ago
    At first guess, landing/launching a new feature, and then possibly feature adoption.
  • haney 4y ago
    A change you made moved some metric a measurable amount (usually aligned with a team or product goal). You put these little nuggets of impact on your performance review.
• bombolo 4y ago
  > I'd say local code quality is generally good Have you ever used facebook.com? At least the frontend is incredibly slow (on a thousands of € machine), so that's not synonym with quality in my experience.
  • KaoruAoiShiho 4y ago
    From reading the comment thread I would say the front end would be macro, local would be like a specific function on the front end, like the friends list, that by itself could have "good code".
    • bombolo 4y ago
      Like when I have a red number indicating I have a notification and then I click and it just loops forever on some grey animation because it doesn't manage to load the list of notification on my fiber connection?
      • Quikinterp 4y ago
        You're thinking of features when the other person is thinking in code. Maybe some overcomplicated bloat is involved with whatever goes into clicking that. They mean locally as in code scope and not necessarily client sided or the size of a feature
      • linuxftw 4y ago
        The little red dot is one microservers, message previews is another, 'load profile picture of message sender id' is probably another, etc.