4 ms·
That's an interesting approach! I tried more or less the opposite: wrote a patch replacing hundreds of lines of Java with dozens of lines of Clojure, then show
by willismichael 13y ago
That's an interesting approach! I tried more or less the opposite: wrote a patch replacing hundreds of lines of Java with dozens of lines of Clojure, then showed it to the team. It didn't work out so well. Here's an allegory that more or less parallels my experience: http://hack-tastic.blogspot.com/2013/04/most-people-who-graduate-with-cs.html http://hack-tastic.blogspot.com/2013/04/most-people-who-grad...
- michaelochurch 13y agoOverperformance is dangerous in the workplace.That's a real risk of using high-productivity tools (e.g. functional programming languages). You're introducing gunpowder to horse-riding swordsmen. Usually, they'll lynch you for witchcraft. "Clojure doesn't have the latest despondency infarction frameworks! Burn it! It's a witch!" I think the trick is to fail up into a better company (or team, if your firm isn't one of those where a bad start renders you immobile) when that happens. Hard to tell how good a company is before you join, though.