With the launch of Opus 4.5 and the higher capabilities of coding agents, we started to question our workflows and created our new SDLC from scratch.

We actually expected the biggest impact on engineering, but actually our pms benefit the most and our devs are also happier. The main reason: Tools like Claude code are already boosting devs so we only improved their workflow. But PMs can only use dev tools like Claude Code or vibe coding tools like Lovable. None of them were really made to boost their abilities.

I thought it would be cool to share how our product teams are working now:

1. Ideation:

Our PMs dump in ideas, notes, emails, call recordings, screenshots. The idea agent sorts this and helps PMs curate.

2. Planning:

Based on ideas, the PMs + idea agent can start planning features based on the memory layer (which is basically the codebase translated markdown files). The planner is a collaborative doc where PMs, devs and the planning agent work in real time on the plan and iterate. Our flow: agent drafts plan -> humans make edits and add comments -> agent iterates on changes -> human review again -> this loop will continue till the plan is finished.

planning doc + planning agent

3. Issues:

When the plan is ready, the agent breaks down the plan into sub tickets with detailed descriptions about what and how to build. In addition, the agent recommends implementer and priority. The human must assign the tasks (or activate agent auto mode).

issue kanban overview

4. Implementation:

Based on assignments, humans, agents, or both together process issues through this flow: Backlog → ToDo → In Implementation → Agent Review → in Review. Agent tickets will be done by the agents in the background. If devs are assigned, they can pull their tickets using MCP into their terminal session and work from there. The status of these tickets is updated automatically via MCP.

5. Review & testing:

After implementation, a new review environment will spin up the branch for the product engineer to test what was built. Product review by PM, code review by our devs and agents.

https://preview.redd.it/s30v6ob0pusg1.png?width=2208&format=png&auto=webp&s=764df63db7e2caeb05fe645291cae9bb022845f5

6. Merge:

Once everything was reviewed, the branches will be merged into one final feature branch, that can be checked in another preview as well and then be pushed to staging. After that, it gets deployed in production through our Github releases.

_______

What our teams loves most:

• the planning mode is better than claude code, because its finally possibile to work together with multiple people in one place. the terminal session is only ok if you are a single person.
• the requirements are now clearer. It's happening less often that stuff was built differently than intended by the PM, bc the requirements now include exact frontend mockups and deeper technical planning thanks to AI.
• pms can handle simple changes, like padding adjustments by themselves. our devs dont get pulled out of their task for simple stuff. Instead, the devs can focus on the real problems that need their expertise & attention
• ticket status updates itself, when devs are pulling tickets via mcp into their local terminal session. no more pms pinging and asking about the status

This is how we are building software right now! Would love to hear what you are thinking about our current workflow and if your processes also changed that much in the last months!

I Finished bachelors on software engineering but i feel like i havent learned anything during uni. I do know some basics ofc but thats it. I wanna start an internship on something easy as a start, cuz i dont wanna go in a difficult one and embarrass myself by how little i know. Does anyone have any recommendations?

It’s been 3 months since I started my internship as a software engineer. My manager has been assigning me technical topics to learn, but I haven’t been included in stand-up calls, and she doesn’t really check in on what I’m working on. The only updates I provide are short biweekly summaries of my work.

Initially, I was on a data engineering track, but now she has asked me to switch and work on Java backend and Angular frontend as well.

please tell me what should I do?

Hi everyone,

I’m currently working as an intern at a software company, and my conversion to a full-time role depends heavily on my performance during this internship. I still have about 3 months left.

The challenge I’m facing is that I’m not being assigned major or high-impact tasks. Most of the work I receive is relatively small, and sometimes I feel like I’m not being closely evaluated. Because of this, I’m worried that I won’t get enough visibility to demonstrate my true potential.

I genuinely believe I’m capable of handling more responsibility. I’m comfortable working on real features, debugging complex issues, and contributing meaningfully to the codebase. I’m eager to learn, take ownership, and deliver impact — but I’m unsure how to position myself when bigger opportunities aren’t naturally coming my way.

I don’t want to appear pushy, but I also don’t want to miss my chance due to a lack of visibility.

For those who have successfully converted from intern to full-time in software companies:

• How did you create visibility for your work?

• How did you proactively ask for bigger tasks without sounding desperate?

• What specific actions helped you stand out in the final 2–3 months?

• How can I demonstrate ownership even with smaller tasks?

I would truly appreciate any advice, strategies, or mindset shifts that helped you secure your return offer.

Thanks in advance!

Anyone here can make YouTube without shorts? I am unable to focus because of that.

Hi I am looking some guidance in matter of code snippet manager.

Does code snippet manager still holds any values considering LLM is generating code for us?

Does developers really pay for code snippet managers?