It turns out that senior engineers are more receptive to the agent's output than junior engineers.

It seems like a counter-intuitive conclusion, but it's right.

Let me talk about my own experience: In the first two years as a programmer, my mind was full of local optimality.

I wanted to use the latest and most powerful technology.

This set of xxx was out.

I didn’t care about the whole picture and despised the business.

After a few years, I became more senior and started to lead people.

Both the front and back ends were involved.

I had to arrange the division of labor and wipe people’s butts.

I began to understand the whole system, which ones should not be touched, and understood that what is reasonable is not necessarily optimal, etc.

Later, stability, maturity, effort saving, business value, team combat effectiveness, morale, etc.

Words that seem to have nothing to do with technology have been taken into consideration again and again in a large project that lasted for half a year or even more than a year.

So: The same goes for the use of AI.

1 Do I know its boundaries?

2 Where is it more efficient and where is it fully capable?

3 How to optimize the new working mode?

4 How to consider token consumption, illusion, and gold data?

In my eyes, AI is a real and perceptible task, indicator, and scenario.

I am constantly thinking about how to use the models I am familiar with to connect with the most advanced productivity, without personal emotions, petty thoughts, or avoiding problems.

Because my position will always be challenged, whether by people or AI, it’s just a matter of changing the target.

I hope it's useful to you, please give me a thumbs up.

❤️

Visual summary

Article argument map

Generated from the post's content graph

Mermaid outline

flowchart LR
  format-long_post["longform note"]
  topic-agents["agents"]
  capability-agent-workflow["agent workflow"]
  capability-product-surface["product surface"]
  format-long_post -->|covers| topic-agents
  format-long_post -->|signals| capability-agent-workflow
  format-long_post -->|signals| capability-product-surface

Visual structure

Essay structure map

Built from summary and key paragraph positions

Mermaid outline

flowchart LR
  thesis["It turns out that senior engineers are more receptive to the agent's output than junior engineers. It seems..."]
  signal["It turns out that senior engineers are more receptive to the agent's output than junior engineers."]
  operator["Words that seem to have nothing to do with technology have been taken into consideration again and again in..."]
  implication["❤️"]
  thesis -->|frames| signal
  signal -->|develops| operator
  operator -->|lands in| implication

Source: View the original post