3 ms·

> Our jobs will change. We might look more like product managers than code artisans. Or like lead engineers guiding mentoring and nudging robots to build the ri

> Our jobs will change. We might look more like product managers than code artisans. Or like lead engineers guiding mentoring and nudging robots to build the right thing. This is why I repeatedly tell software engineers not to be “ticket takers”. If your job is just pulling well defined stories off the board where the business requirement is already known - which is considered mid level behavior at every tech company where I have seen leveling guidelines - your job may be in danger by AI. But it is definitely in danger of being outsourced to cheaper labor and you’re just commodity and will find it hard to stand out against thousands of other commodities.

godelski 2y ago
Any employee's job is not to follow instructions, rather it is to do the job required to accomplish the company's goals. These are not always aligned. You know more than your manager about certain things and vice versa. You have to interpret. You have to use your expertise. It's easy to do work while creating more work for others. Move fast and break things works when learning but you don't go around breaking everything in the office either. Your expertise is not being glue between stack overflow and your codebase, your expertise is to understand the picture, limitations, failures, knowing there are different types of glutes, tapes, and fasteners. Your experience is seeing failures others don't, the cracks in the system. There's an old joke. There's two types of 10x developers 1) those like Knuth 2) those that complete 10 the number of jira tickets The former will prevent 100x tickets from ever being created, while the latter will be the cause (Yeah jokes aren't perfect. You don't need to nitpick and but actually. You can interpret )
- scarface_74 2y ago
  My day job is a “staff” software architect working at a third party AWS cloud consulting company (coming from working at AWS directly doing the same thing) I am not bragging - I’m just old. I have “expertise” at some level or the other with: 1. Discovery, requirements gathering, creating project plans, etc - 2. project management (not great. But I’m good enough) 3. Tech lead for a software development project or a cloud architecture “DevOps” project 4. Your standard “senior” hands on enterprise software developer. 5. Every database type imaginable. 6. A “cloud engineer”. I can go from an empty AWS account to a completely “Well Architected” infrastructure using IaC and creating pipelines While I can do any of those, as a hands on keyboard person, I can only do 40 hours worth of work and I could never complete a moderately complex project that required me to do all six in an acceptable time period. When doing any of that work, I’m operating at most 2x the average person and that’s being generous. My value add, is that a company can throw me on a conference call or tell me to hop on a plane and deal directly with the client along with sales to close a deal and know I’m not going to embarrass them. On the other end, by being able to lead and coordinate between the customer, sales, and the hand on engineers , I can hopefully get a project across the finish line on time, on budget and that meets requirements.

godelski 2y ago

Any employee's job is not to follow instructions, rather it is to do the job required to accomplish the company's goals. These are not always aligned. You know more than your manager about certain things and vice versa. You have to interpret. You have to use your expertise. It's easy to do work while creating more work for others. Move fast and break things works when learning but you don't go around breaking everything in the office either. Your expertise is not being glue between stack overflow and your codebase, your expertise is to understand the picture, limitations, failures, knowing there are different types of glutes, tapes, and fasteners. Your experience is seeing failures others don't, the cracks in the system. There's an old joke. There's two types of 10x developers 1) those like Knuth 2) those that complete 10 the number of jira tickets The former will prevent 100x tickets from ever being created, while the latter will be the cause (Yeah jokes aren't perfect. You don't need to nitpick and but actually. You can interpret )

scarface_74 2y ago
My day job is a “staff” software architect working at a third party AWS cloud consulting company (coming from working at AWS directly doing the same thing) I am not bragging - I’m just old. I have “expertise” at some level or the other with: 1. Discovery, requirements gathering, creating project plans, etc - 2. project management (not great. But I’m good enough) 3. Tech lead for a software development project or a cloud architecture “DevOps” project 4. Your standard “senior” hands on enterprise software developer. 5. Every database type imaginable. 6. A “cloud engineer”. I can go from an empty AWS account to a completely “Well Architected” infrastructure using IaC and creating pipelines While I can do any of those, as a hands on keyboard person, I can only do 40 hours worth of work and I could never complete a moderately complex project that required me to do all six in an acceptable time period. When doing any of that work, I’m operating at most 2x the average person and that’s being generous. My value add, is that a company can throw me on a conference call or tell me to hop on a plane and deal directly with the client along with sales to close a deal and know I’m not going to embarrass them. On the other end, by being able to lead and coordinate between the customer, sales, and the hand on engineers , I can hopefully get a project across the finish line on time, on budget and that meets requirements.