1) Be helpful. Colleague beating her forehead against her desk debugging something? Go help. Account manager running into a bug? Go help. Sales team encounterin

1) Be helpful. Colleague beating her forehead against her desk debugging something? Go help. Account manager running into a bug? Go help. Sales team encountering pushback from a potential customer? Go help. You'll learn a ton. 2) Learn why you're building something. Not just the technical 'why', but also the business 'why'. Yes, you should understand why you're using RabbitMQ over Redis. You should also try to understand the business case that you're solving – in as much depth as you can get. The stronger you align with what your business needs, the more valuable you become, and the harder problems you will be solving, an the more you'll have the opportunity to learn.