-
Generative AI is a sustaining innovation for products and a disruptive innovation for costs. Technology moves operational leverage up the business chain. Before the introduction of spreadsheet software, clerks and bookkeepers outnumbered analysts, auditors, and managers by a third in the U.S. Twenty years later, there are two-and-a-half times more analysts and managers than clerks. Generative AI enables every clerk to become an analyst, every writer to become an editor, and every developer to become an architect.
-
To avoid feeling bitter, do two things: start something that’ll be fun to work on (you’ll feel more fulfilled) and do nice things for people in an organised way or just do random nice things. (How to avoid feeling bitter)
-
Don’t use adjectives if you can provide evidence. Why say “made a big impact? “ when you can say drove $40 million of additional revenue?
-
Sail the feature-seas mindfully. Before using a product, people judge its quality based on the number of features it has. They realise the usability issues of too many features are created only after using the product. This incentivises you to build features quickly, but this also means more maintenance, bug fixes, customer support and the resources required to keep the feature running and updated.
-
Build independent products or grow slowly and optimise. If your work product–e.g. codebase, documents, etc.–can be factored into independent modules, do so. The key word there is independent. Slicing your shit up into a hundred microservices will not help you if everyone needs to change ten of them to get anything done. Some problems are not particularly amenable to partition; these are also problems which do not benefit much from additional workers. If the problem is a fixed point, look at ways of optimizing the sequential portion of the work. Know that throwing bodies at that problem will produce a clusterfuck.
-
Great customer service is expensive, but it’s also free. It’s free because delighting a customer who has an issue is the single cheapest way to not only keep that customer but also have them spread the word. (Customer service is a choice)
-
Learn how to create opportunities for others and share the credit. In engineering, seniors should find co-founders for their best ideas, pick a task, delegate it mid to junior engineers and provide necessary air cover. The role of seniors is to create room for juniors to grow and get hands-on experience with a high-impact project. You can create other seniors by creating opportunities and sharing successes or failures.
-
Keep to software lean. Too much code is being shipped, much of it by third parties and uninspected. This creates a large attack surface full of mediocre code. Limiting the amount of code exposed to the world is crucial, as many logic bugs are still not detected.
-
Serverless can refer to many things, but in terms of computing, it usually pertains to Functions. Functions are a more efficient way of managing, scaling, deploying, and understanding this workload. The great thing about Functions is that they have a smaller lifecycle and API footprint than others. This simplicity is ideal for the task of “a request came in, we have to do something.” (@rauchg or Twitter)
Substack edition
Generative AI is a sustaining innovation for products and a disruptive innovation for costs. Technology moves operational leverage up the business chain. Before the introduction of spreadsheet software, clerks and bookkeepers outnumbered analysts, auditors, and managers by a third in the U.S. Twenty years later, there are two-and-a-half times more analysts and managers than clerks. Generative AI enables every clerk to become an analyst, every writer to become an editor, and every developer to become an architect.
To avoid feeling bitter, do two things, start something that'll be fun to work on (you'll feel more fulfilled) and do nice things for people, in a organised way or just do random nice things. (How to avoid feeling bitter)
Don’t use adjectives if you can just provide evidence. Why say “made a big impact? “ when you can say drove $40 million of additional revenue?
Sail the feature-seas mindfully. Before using a product, people judge its quality based on the number of features it has. They realise the usability issues of too many features are created only after using the product. This incentivises you to build features quickly, but this also means more maintenance, bug fixes, customer support and the resources required to keep the feature running and updated.
Build independent products or grow slowly and optimise. If your work product–e.g. codebase, documents, etc.–can be factored into independent modules, do so. The key word there is independent. Slicing your shit up into a hundred microservices will not help you if everyone needs to change ten of them to get anything done. Some problems are not particularly amenable to partition; these are also problems which do not benefit much from additional workers. If the problem is a fixed point, look at ways of optimizing the sequential portion of the work. Know that throwing bodies at that problem will produce a clusterfuck.
Great customer service is expensive, but it’s also free. It’s free because delighting a customer who has an issue is the single cheapest way to not only keep that customer, but also have them spread the word. (Customer service is a choice)
Learn how to create opportunities for others and share the credit. In engineering, seniors should find co-founders for their best ideas, pick a task, delegate it mid to junior engineers and provide necessary air cover. The role of seniors is to create room for juniors to grow and get hands on experience with a high impact project. You can create other seniors by creating opportunities and sharing the success or failure.
Keep to software lean. Too much code is being shipped, much of it by third parties and uninspected. This creates a large attack surface full of mediocre code. Limiting the amount of code exposed to the world is crucial, as there are still many logic bugs that are not being detected.
Serverless can refer to many things, but in terms of computing, it usually pertains to Functions. Functions are a more efficient way of managing, scaling, deploying, and understanding this workload. The great thing about Functions is that they have a smaller footprint in terms of lifecycle and API compared to others. This simplicity is ideal for the task of "a request came in, we have to do something." (@rauchg or Twitter)