When you build something with code or no-code tools, shipping the product matters. But your real job is shipping knowledge. The skills and insights you gain while building let you create higher-value work next time.
Ship knowledge. I think that a, when people are starting their work in technology, whether they're using pro-code or no-code or whatever, they often think their job is to ship the artifact that's going to be the thing that the rest of the organization could use, the customer is going to use, or whatever it might be. And certainly that is important, but it should not be the primary mission. The primary mission should be the growth of the person who's developing. And that's going to be about the knowledge that you get as a result of taking this, this piece and turning it into technology. And the things you learn along the way are what's going to enable you to create the next level of value. So whether you are a builder creating a product, you're someone in customer success who's adding a bit of tech, put a primacy on your own growth and that the initiatives you do are going to make you smarter and help you increase knowledge. If you focus on shipping knowledge along the way, you will deliver value for both yourself and for your work.
