3 ms·
I definitely agree. I've seen the typical examples of ugly code over the years; over-complicated conditions, piles of IF statements, things that should be in a
by bluedino 9y ago
I definitely agree.
I've seen the typical examples of ugly code over the years; over-complicated conditions, piles of IF statements, things that should be in a database or associative array, all because the person just couldn't solve the problem in a simple, straight-forward way.
These people get stuck on what should be a simple problem and productivity plummets. If you've spent the whole morning on something, taking it from 5 lines to 105, you're probably attacking the problem from the wrong angle.
- dronescanfly 9y agoDefinitely can relate to that... One of my colleague is the type of person who somehow forcibly denies doing the most straightforward things/solutions. Every problem is being 'solved' by pulling in yet another library that somehiw touches the problem. Of course it needs it's own layer of abstraction to be swapped out easliy for yet another library im case the first is deprecated. All that for stuff which can be solved with simple 1-10 lines of code. (not these everlasting functional programming chained to eternity lines. real slim and dumb code)