|
My choosing order is the following:
1st - Pick the right technology for the job
2nd - Validate the Team Velocity on that technology against your available time
3rd - Validate the team ramp-up (if needed) against cost/benefits and available time
Ideally you should be given time to ramp-up your team before the project starts but that never happens, so choosing the right tool for the job often depends heavily on the available time.
P.S.: "Whatever I already know" should never be the main criteria.
|
|
|
|
|
So I do all of them according to what best for me and for that project...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
...and that is Windows API. Powerful, flexible, fast, and basically the very same thing that does the dirty work under the bloated .NET.
Wherever I can I use libraries and APIs because they do not force me to design according to the framework, I am free to design as my problem domain needs and to use only the feature I need with no overhead.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
"When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
|
|
|
|
|
|
From my experience, I would say that using/forcing a technology just because it's the one you know will bring you more problems than benefits in the long run.
|
|
|
|
|
Agreed, and I never said you should.
But building a Windows App with a Node.js back-end using Maven to manage your Clojure packages because ReactJS is the popular kid on the block will end in tears 
Ok, that's not even possible, but you get my drift.
New project, new frameworks. Old projects, be very careful.
Don't experiment too much, because each new framework has it quirks and you're going to make mistakes learning and implementing it.
If you're going to use AngularJS use AngularJS and don't use Ember for another page and Knockout for yet another page.
|
|
|
|
|
Sure, that's like the other edge of the problem:
Using everything you can just because you can. 
Anyway, when I wrote that I was more thinking about the common problem between core technologies like .Net vs. Java or things alike. So-called "Architects" tend to stick with their own tribe instead of actually designing a proper performant and logic system.
I'll not even go into details related to product fanboys like SharePoint or CRM where at some point it looks like everything should be religiously stuffed into these resource eating monsters.
Just because one is used to a certain stack it doesn't mean that everything has to fit into that stack.
If one is serious about computer science, one should be as open minded as possible and include different stacks into his toolbelt.
Sure different stacks come with integration challenges but often integration is much easier to abstract (usually even at infrastructure level) when compared to force-fit a technology where it's not meant to be.
|
|
|
|
|
AlexCode wrote: So-called "Architects" tend to stick with their own tribe instead of actually designing a proper performant and logic system
Yeah, I worked for such a company.
Well, they did call themselves a Microsoft company.
If you wanted our software you had to have Microsoft systems.
Nothing wrong with that, as long as you know it.
We never tried to run WinForms on Apple 
Anyway, mentioning anything besides MS was a sin in the company, that's really the only thing that bothered me about it 
|
|
|
|
|
Sander Rossel wrote: If you're going to use AngularJS use AngularJS and don't use Ember for another page and Knockout for yet another page.
Jeremy Falcon
|
|
|
|
|
So I guess "all of the above"?
|
|
|
|
|
And a hearty 'none of the above' would also be nice.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Actually, faaaark them all would be the nicest option!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
