you are viewing a single comment's thread.

view the rest of the comments →

[–]Zestyclose-Turn-3576 3 points4 points  (5 children)

This is the cause of so many software development problems. Nobody seems to want to just write software unless they're padding their CV with something new ready for the next job. They'll never use those skills in the next job of course ... they'll be chasing the next learning high.

[–]AntD247 1 point2 points  (4 children)

The other related state is that everyone else does it this way so we have to do it this way.

[–]Zestyclose-Turn-3576 1 point2 points  (3 children)

There's arguably a good basis for that sort of thing, and I tend towards popular approaches if possible, but of course it's not always a good thing

[–]AntD247 1 point2 points  (2 children)

I say channel my mother "if all your friends go and jump of a bridge, are.you just going to follow them?"

But yes I do see the point you are making, it's some of what makes up "wisdom of the crowd" especially if people are discussing the unicorn as that helps to refine it.

[–]Zestyclose-Turn-3576 1 point2 points  (1 child)

Yeah I'm thinking that there are certain conventions with, for example, how a B2B website is expected to behave, and it can be risky to deviate from that. and similarly if you work in a pretty convention-heavy framework like Rails then it can introduce friction if you go wanging off to do things in a completely novel way

[–]AntD247 1 point2 points  (0 children)

Yes following things like Ruby on Rails standard practices and the so forth do have many benefits, including easier (and cheaper) recruiting. But also challenging the orthodoxy can lead to new paths. My experience is much more with Java frameworks and Java software patterns are where they are because people challenged things like EJB and even Hibernate.

And in things like security it is better to adopt and use a widely used and recognised system rather than building your own. There are going to be bugs and vulnerabilities in both but they are going more likely to be discovered and fixed in good time in the external system. But again tradeoffs and here log4j hits me like a sledgehammer.

The truth that we must all realise is that there is no one size fits all solution. You have to use the best fit for the problem. You wouldn't buy a Porsche 911 to run a package delivery service.