They say that gear doesn’t matter, but it does
I do some photography on the side.<p>I think the sentence describe it perfectly.<p>Gear won&#x27;t take good photos. But it sure makes it easier if you know what you are doing. And it also opens new possibilities.<p>It is all good, IF you know how to use it. Probably the best advice I got when I started was to settle on a simple piece of gear, fairly constrained, and learn how to use it creatively. I settled on a Fuji X100s which is prime, non interchangeable lens. I learned everything about it for the next year and I am probably better photographer for it. When you learn everything about your fairly simple camera you can start learning how to use it creatively. The camera itself becomes your tool and you learn to predict what is going to happen and what is&#x2F;not going to work in a particular situation. Those skills, for some reason, transfer when you change to other cameras.<p>Give my full frame with my expensive lenses to my wife and the pictures are worse than she would do on a phone. It is just too complicated for her to be thinking about the photo, not that she pays a lot of attention to the composition anyway.<p>So what is the application?<p>Whatever you do, try to understand different aspects of your craft and maybe figure out which of those aspects you are underutilising and how you could force yourself to learn them better.<p>For example, as a developer, decades ago, I was thrown on a project that required me to write a lot of code in a very constrained environment (embedded C, low memory, etc.) without being able to compile and run it. I was able to run my code once a week.<p>I probably learned more about programming working for 3 years on this project than I learned over the rest of my career before and after. I learned that compile&#x2F;run&#x2F;fix loop is a crutch that most people never wean themselves of because it is just so damn convenient. I learned that you can teach yourself to write code for days and then get it to work correctly on the first try (most of the time). I learned it gives you superpowers.<p>I can now barely stand watching people who can&#x27;t predict what their code does, it feels so amateurish. I know I did the same and I know it was a chance that I learned it, but still.<p>It also makes your code much, much more bug free and reliable. Because QA&#x2F;QC&#x2F;code reviews, etc. only find certain types of problems that manifest themselves fairly easily. To reduce other types of bugs you have to create less bugs in your initial version because nobody will ever find them and fix them for you. Those bugs are still there and will manifest themselves in those rare occasions or when you refactor the software a bit. It also means when you are done coding the application is pretty much production ready -- there is no QA&#x2F;QC phase where bugs are getting fixed.