Comment by funnyfoobar

17 hours ago

What you are saying may have made sense at the start of 2025 where people were still using github copilot tab auto completes(atleast I did) and was just toying with things like cursor, but unsure.

Things have changed drastically now, engineers with these tools(like claude code) have become unstoppable.

Atleast for me, I have been able to contribute to the codebases i was unfamiliar with, even with different tech stacks. No, I am not talking about generating ai slop, but I have been enabled to write principal engineer level code unlike before.

So i don't agree with the above statement, it's actually generating real value and I have become valuable because of the tools available to me.

4 comments

funnyfoobar

Reply
d675  6 hours ago

These are definitely valuable but how much idk.

I've just spent some time with Opus to extend basic metrics in a static language, with guides, where to look, what set of metrics etc, it's making quite a few mistakes for not a hard task...

  • funnyfoobar  2 hours ago

    I have replied to a comment adjacent to yours, for my parent comment. Please check i think if you follow the "process", it is avoidable.

sjsizjhaha  9 hours ago

> Things have changed drastically now, engineers with these tools(like claude code) have become unstoppable

I’ve spent the last week unwinding my coworkers slop who said the same thing.

  • funnyfoobar  2 hours ago

    To be honest, what you have described only shows lack of process.

    I am not talking about vibe coding here, which is totally different and understandable. But I am talking about the professional context where the structure is already in place.

    Here is my workflow, if it helps:

    1. I have a system level prompt i execute(command/skill) before I start anything which says things like

        i) follow SOLID principles
    ii) follow TDD
    iii) follow these testing principles like, don't test the implementation details etc
    and 20 other things

    2. I give it the context of what I need to accomplish, and toggle the plan mode ask it follow the above things I have set at system level, and generate me a document to review step by step

    3. I review everything, add feedback to the generated plan, prompt again, and finally finalize the plan

    4. now that the plan is finalized, I would have a small alignment with co-workers and ask it implement step by step, and then before proceeding with next step, i will tell it to ask me for feedback

    each steps code is reviewed and commited, before proceeding to next step

    5. once all steps are done, manual testing is done, i do a local review

    6. I have a specific skill which reviews everything, and gives me feedback

    7. we have human reviewers who will review the code, and coderabbit

    8. then we take it to the staging and uat before taking to prod

    so see we have not skipped any process of "software engineering", claude code is just an accelrant

    but if you are not doing most of the above steps, i see what you are saying would happen by default