3 ms·
- good solutions are abandoned by no reason other than lack of momentum/popularity - there's a sweet spot between "new, cool but unproven" and "boring but work
by raverbashing 8y ago
- good solutions are abandoned by no reason other than lack of momentum/popularity
- there's a sweet spot between "new, cool but unproven" and "boring but works" and it is different each time
- find the right level of abstraction to work with. Too high and you'll lose flexibly, too low and you're doing work you shouldn't.
- cut the crap and don't waste time with what you don't need. Focus on the product and on shipping the product. Your customers don't care about the latest js lib unless your product is significantly better than the competition for using it.
- TeMPOraL 8y ago> find the right level of abstraction to work with. Too high and you'll lose flexibly, too low and you're doing work you shouldn't. That's a very good point that took me a long time to fully comprehend. The concept of code abstraction is usually introduced with a promise of it increasing flexibility. But the truth is, abstractions increase flexibility along one dimension, by severely constraining you in many others[0]. As long as you only need to move around along the abstraction-favoured dimension, things are fine, but if you find yourself needing flexibility elsewhere, it turns out that rewriting dumber/less abstract code is much easier and faster than digging yourself out of a wrong abstraction. -- [0] - I sometimes feel there is a "law of conservation" kind of thing hiding in there. That abstractions are merely moving complexity around, not destroying it. Someone must have explored this idea before; anyone here knows of such attempts?
- s_m_t 8y agoIts just compression and information theory.
- gugagore 8y agoThat's a bit too reductionist, right? Or perhaps you could elaborate? As it stands it sounds like "it's all just atoms" when someone asks "how does a neuron fire? Someone must have studied that."
- s_m_t 8y agoIn information theory you can't come up with an encoding that will give you more than a bit of information per bit of source on average. Of course, the information we usually care about is usually highly structured, so we use encodings that compress the highly structured parts we care about and dont care if in that same encoding it would take many bits more to encode some other part. Ever used some sort of library or framework where in the beginning you get a ton of progress made in a small amount of time but when it comes to getting it to do exactly what you want you find your code balooning around the corner cases? Same idea in my opinion.