Well, I guess mostly by revising work I've done in the past.
Reviewing it and thinking about how it could be improved if I were to apply methods that my coworkers would use.
I know it could be difficult for you, but consider just asking them for advice on the systems you're building/proposing. If you think they're likely to turn down the ideas you have, you may as well pre-empt that and get down to the business of figuring out a compromise. It may not make you look like some rockstar programmer, but at least you'll be learning something as quickly as possible. Also, depending on how down to earth your employers are, appearing humble before your superiors/more experienced colleagues and wanting of knowledge will only cast a good light on you.
I know it could be difficult for you, but consider just asking them for advice on the systems you're building/proposing. If you think they're likely to turn down the ideas you have, you may as well pre-empt that and get down to the business of figuring out a compromise. It may not make you look like some rockstar programmer, but at least you'll be learning something as quickly as possible. Also, depending on how down to earth your employers are, appearing humble before your superiors/more experienced colleagues and wanting of knowledge will only cast a good light on you.