Home / Companies / Sleuth / Blog / July 2024

July 2024 Summaries

2 posts from Sleuth

Filter
Month: Year:
Post Summaries Back to Blog
The text highlights three anti-patterns in implementing AI in engineering management: replacing team members with AI, augmenting junior developers with AI, and automating recruitment with AI. These patterns can lead to negative consequences such as a drop in quality, over-reliance on coding assistants, and overlooking human interaction in the hiring process. The article suggests using AI to generate content, uncover patterns and insights, and automate tasks and workflows instead, which can help improve productivity, reduce manual work, and provide team members with more focus time. Ultimately, the goal is to use AI in a way that empowers people and improves their experience, rather than just focusing on short-term gains.
Jul 31, 2024 2,479 words in the original blog post.
You're in the middle of a productive work session when a new meeting invite pops up, but it doesn't have to be a draining experience; the problem lies not with meetings themselves, but how we approach them. Traditional meetings often lack clear outcomes, right stakeholders, and necessary data to drive meaningful decisions, instead focusing on status updates or unproductive discussions. However, having identified what makes a bad meeting makes it easy to understand how to improve, and good meetings should involve the right stakeholders at the right times, have clear outcomes, and be data-informed. To turn your meetings into effective reviews, invest in collaborative pre-work, involve the right mix of quantitative and qualitative data, task the right individuals to collect and interpret the data, provide time and space for collaboration, clearly define a time before the review, and involve the right stakeholders. By doing so, you can transform aimless talking to an outcome-driven collaboration, focusing on meaningful discussions rather than status updates, and making your meetings more productive and efficient.
Jul 31, 2024 859 words in the original blog post.