• 5 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 28th, 2023

help-circle













  • I agree with this, and I think it may be fairly easy to catch most of this with some simple conventions:

    1. If the post is primarily about a specific language, it belongs in that respective community.
    2. Posts about frameworks, libraries, tools, etc. should either go to their respective communities, or if none exists, the nearest language community.

    This would create some gray area for things like the last link in your list, but it should catch the majority of problems. I wonder if this could be resolved with a (new?) Q&A community for people to ask questions that are specific to their situation. That would enable c/programming to focus more on conversational topics.



  • A lot of organizations seem to focus on tailing indicators such as lines of code written, or the number of bugs found, and I think that’s part of what fuels the perception that being an engineering leader is one of the most difficult roles in modern companies because they don’t paint an accurate picture of how things are today.

    The first thing is to get data that tracks key performance metrics. Many organizations often start with DORA metrics to create “slides for the board” that show the overall health of the engineering organization. This is a great place to start, but you can take this further by incorporating your project tracking into the data to measure how you allocate resources across the engineering function and whether or not that allocation is enough to meet product delivery timelines. There are a handful of tools out there that make this easy, like Sleuth and LinearB. A quick search should surface other solutions for this too.