Thread

Replies (10)

What do you mean I code dumbest thing πŸ˜† that works πŸ˜†? I’m a musician been playing cello for many many years coding for me mean is I have to decrypt what composer wrote hundreds of years ago and then interpreted on my instrument for a modern ear to hear . Yes I can interpret it in a dumb way but also in authentic way like composer intended, Is that what you mean?
That's how I started. All my early projects were messy, but they did exactly what they needed to. It's just matter of making clean projects that do exactly what they need to do. There's no tradeoff. But moreso than software, it was real physical engineering that taught me the value of quality up front. Anything can be made to work, but only a few things can be made to last.
Well that’s different every time I play and every day is not the same. Because unlike visual art which is permanent and cannot be changed over time. Music is elastic. If I don’t like my audience or if there is a person in the audience paying attention to his phone instead of listening skills, I’ll make them pay attention first by playing in the different style licensing ponticello technique and only then please them with my tone or vibrato or a fast finger passage so they enjoy instead of looking at their phone at the concert. Believe me this happens all the time
I flip flop between these extremes. If I'm being paid a salary, i will code "proper". If I am just trying to code something to fix a problem (eg worried about being sensored on meetup.com) then I will do what Vito said and code the dumbest thing to just get something out the door. If it gets adoption or people ask/pay me to I would refactor to something more maintainable and extensible.