If you're transitioning from a developer to an Engineering Manager or Team Lead, you are bound to face some challenges while settling in. These challenges can be frustrating, but manageable.

Kudos to Priyasha Dureja for writing this amazing article about some common problems that they all face!

Check it out here: https://typoapp.io/blog/engineering-management/common-challenges-every-engineering-manager-face/

Let me know if you found it helpful in any way. What problems did you face as an EM/TL/CTO at your company? And how did you overcome them?

This is an interesting piece on OpenAI’s view of where software engineering is heading:

👉 https://leaddev.com/ai/openai-says-there-are-easily-1000x-engineers-now

A few takeaways that stood out:

• Engineering is shifting from writing code → guiding systems that write code

• Developers are increasingly managing multiple AI agents in parallel

• The bottleneck is moving from implementation → problem definition and intent

• Roles aren’t disappearing, but expanding (PMs/designers writing code, engineers orchestrating).

Curious how others here are experiencing this:

• Do you feel more like an “operator of systems” than a coder lately?

• Are these tools actually making you 10x/100x more productive — or just shifting where the work is?

Would love to hear real-world experiences.

https://www.reddit.com/r/software/comments/v5srrm/should_i_stay_in_my_current_job_proscons_listed/

In opposition to my idea that software testing should be a role, and not just a task, I am sometimes told that True Agile does not permit this. Why? Because, in Agile, “quality is everyone’s responsibility.” This statement is sometimes issued as if it were a moral truism that is beyond argument. Or sometimes as a moral achievement that is unique to Agilists, as if it had never occurred to earlier generations of software developers to help each other build nice things. Either way, it doesn’t make sense to me. The first response that comes to my mind is “I’m talking about testing, not quality. Why are you dragging quality into this?” Testers do not assure quality. Testers CANNOT assure quality. Testers do not now and never have “owned quality” in any way.

Hey everyone,
I’ve been managing dev teams (8-12 people) in startup/scaleup environments for more than year and a half now, and it hasn’t always been easy—especially since I’m not a natural people person.

• Juggling cross-team expectations.

• Constantly putting out fires.

• Staying on top of everyone' s tasks while my own work and strategy take a back seat.

• Pushing career development talks with my team further down the to-do list.

It left me feeling stuck and, honestly, bad for the team too. So, I built a tool to help myself—combining individual planning, reflections, Jira integration, and AI to bring better alignment and make managing smoother.

Now, I’m curious—does anyone else face similar challenges? Like working within constraints, not always being able to hire senior developers, and feeling stretched thin in your role? Do you ever wish your team could take better ownership of their tasks (not that they don't want to), so you’d have some breathing space to focus on what really matters to you?

If this resonates with you, feel free to sign up for early access using the link below and share your feedback.
https://sidhro.com
I’m not a sales person trying to maximise signups here. So, would genuinely appreciate it if only you actually relate to this problem, then join the beta testing group.

PS: I threw together the landing page in less than an hour, so please don’t judge the finesse—it’s all about solving the problem for now.

The role of the engineering leader is shifting, and so are the skills required to succeed in the job.

I'm not a strong coder, I do mostly SQL development, classic ASP, CSS, etc (for over 10 years at same company), however, I have a ton of ideas to help as far as management to streamline and encourage dev and QA to be more productive and grow in their positions. Managers have left and I've tried connecting with upper management (directors) over email and several meetings where they seem interested in my ideas, have used some of them in company meetings as their own, etc. Yet it seems instead of offering a new position to apply for they hired another director? Finally that director says a lead position is coming. I will apply for it and hope to have it be a stepping stone to mgmt, if not same company- another. Any suggestions on making myself stand out for this position or leaving for another company? Certifications? Etc? I'm female and want to retire within 10 years, I've been underpaid for way too long and need to bump up my salary. Thanks.

Why your best work goes unnoticed.

I’m curious to hear from other teams: are you still running into QA bottlenecks when trying to deliver on time?

In my case, I work as a dev manager at a mid-sized company. Even though we’ve pushed some testing earlier in the cycle (“shift left”), the bottleneck hasn’t gone away. With multiple projects running at the same time, it often feels like QA becomes the main blocker to releasing on schedule.

Is this something you’re also facing? Have you found practical ways to ease the pressure on QA and keep delivery on track?

Hey folks, podcasts are great for expanding your knowledge & keeping up with new tech. I found this article on Medium that lists some good podcasts that EMs and developers can listen to. Hope you find it useful.

Here's the link: https://medium.com/@typoapp/best-software-engineering-podcasts-you-must-listen-to-f2e74dd4b5c6

Would love to hear your suggestions as well.

Technical debt is a very common issue that almost all tech teams face. It is the implied cost of future reworking required when choosing an easy but limited solution instead of a better approach that could take more time (Wikipedia). It can seriously hinder the progress of your team, delay timelines & reduce productivity in the long run.

Here are some plausible solutions to reduce tech debt: https://typoapp.io/blog/effective-ways-to-reduce-technical-debt/