‘What hurts today makes you stronger tomorrow.’ – Jay Cutler, pro bodybuilder and four-time Mr. Olympia.
P.S. Visit our website: fitradar.me and join the mailing list. Our app is coming soon.
FitRadar ir jauna mobilo telefonu lietojumprogramma, kas lietotājam ļauj atrast vispiemērotāko personīgo sporta treneri vai sporta pasākumu Jūsu tuvākajā apkārtnē un jebkurā Jūsu izvēlētajā sporta kategorijā. Sports ir tuvāk nekā Jūs domājat.
No Tevis sagaidām:
Pievienojies mūsu komandai un audz kopā ar mums kā uzņēmuma līdzdibinātājs!
Ja Jūs esat ieinteresēts, lūdzu sūtiet savu CV uz:
P.S. Visit our website: https://www.fitradar.me/ and join the mailing list. Our app is coming soon.
The other day I was reviewing my colleagues’ code. It was back-end code written in C#. I noticed that he introduced a class that is very similar to the structure I was quite sure existing in the .NET base library. I found that structure in Microsoft documentation and we agreed that it is better to use .NET type instead of introducing the same type with a different name. After that occasion, I recalled several other cases when I saw the unique solutions for the problems that could have been solved by well-known pattern or practice. My gut feeling was telling me then that it is not a good idea to introduce your own solution for a problem that is already solved by someone else, but I have never really thought what problems such decision can introduce in the project. And so in this article, I wanted to share some thoughts regarding the widely accepted and unique solutions in software development.
First let’s make it clear that any best practice, framework, algorithm or technology was a unique solution in their time. Then when exactly one or another solution became widely accepted?
And still all these criteria are not so reliable as big O for algorithms.
In case of algorithm I think it is quite clear that if there is already an algorithm that solves the problem it is pointless to write your own, unless you can produce better one. In case of frameworks I would follow the same logic – if there is an well known framework that can solve the problem it is much safer to relay on the majorities opinion (although the majority can be wrong) rather than on your own single point of view. Even if the framework or pattern will be rejected in the near future at this moment:
Visit our website: https://www.fitradar.me/ and join the mailing list. Our app is coming soon.
P.S. We are hiring: http://blog.fitradar.me/we-are-hiring/