If I understood correctly, you're effectively saying that the priority of a software engineer is the success of the business, and that their value is directly correlated to the amount of value they add to the business, and that it's on them to prove and justify this.
The main concept for me is how software engineering is a vehicle for increasing value to any business, since it's about information technology, which is based on automation.
> In a way, it's inconsistent of you to be concerned that any of these problems is going to cost the business money.
I don't see this as inconsistent because an engineer's value to the company should be implicit by the definition of the role.
I guess this is where my disconnect is. I don't see engineering like any other role, i.e. management. I see it as something that should inherently add value if done properly because of its very nature. This may sound like I'm glorifying engineering over other roles, but we're now talking about the possibility of AGI and *replacing* engineers with software made by other engineers, so there's something inherently different about it.
The original context of this was 10x engineers, and how they need to add value to the company, but what better way than to leverage the limitless automation of software to do so (as oppose to having them worry about the direction and details of the business)?
The main concept for me is how software engineering is a vehicle for increasing value to any business, since it's about information technology, which is based on automation.
> In a way, it's inconsistent of you to be concerned that any of these problems is going to cost the business money.
I don't see this as inconsistent because an engineer's value to the company should be implicit by the definition of the role.
I guess this is where my disconnect is. I don't see engineering like any other role, i.e. management. I see it as something that should inherently add value if done properly because of its very nature. This may sound like I'm glorifying engineering over other roles, but we're now talking about the possibility of AGI and *replacing* engineers with software made by other engineers, so there's something inherently different about it.
The original context of this was 10x engineers, and how they need to add value to the company, but what better way than to leverage the limitless automation of software to do so (as oppose to having them worry about the direction and details of the business)?