You should be tech-agnostic in every development project
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
In an ideal world, it would be nice to be capable of developing on every platform/language/technology. In practice, this should be tempered by the skill set of developers available. There's no point adopting a technology without the skills to use it.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
So - an uncomfortable high risk route is beneficial because...? (I agree we should try to be tech-agnostic using things like repositories, micro-services and interfaces etc. but it is not the case that "language agnostic" is a component of "technology agnostic" and it is not always the case that newer means better)
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
But of course! After all all we do is for fun and learning and passing the time...It has nothing to do with earning money, deploying applications or all those real-word bullocks...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
The article sounds like a rant directed towards executives and not developers. The projects with serious problems due to a bad tech stack choice are the exception and not the normal case. By saying "You should be tech-agnostic in every development project", he actually means "Hey, executives, don't make us use a wimpy development technology like PhoneGap when we need something more substantial. Be flexible and do things my way." And he's diplomatic enough to make his point with a positive-sounding over-generalization that we developers should ignore.
-
The article sounds like a rant directed towards executives and not developers. The projects with serious problems due to a bad tech stack choice are the exception and not the normal case. By saying "You should be tech-agnostic in every development project", he actually means "Hey, executives, don't make us use a wimpy development technology like PhoneGap when we need something more substantial. Be flexible and do things my way." And he's diplomatic enough to make his point with a positive-sounding over-generalization that we developers should ignore.
In my experience, I've found that the wrong tech stack occurs more frequently than it should. The main problem points to non-technical managers (or washed-up engineers) who insist on using some outdated piece of s*** framework, stack or tool that cripples future functionality.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Marcus Brigstocke, British Comedian
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
-
We gravitate toward familiar tech because it's the comfortable, low-risk route.
"Any one who thinks is an agnostic about something, otherwise he must believe that he is possessed of all knowledge."
There's so many things that are ridiculous about that article, I can only say that he sure nailed it on the head when he prefaced the title with "Opinion". Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
In my experience, I've found that the wrong tech stack occurs more frequently than it should. The main problem points to non-technical managers (or washed-up engineers) who insist on using some outdated piece of s*** framework, stack or tool that cripples future functionality.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Marcus Brigstocke, British Comedian
I agree with your first sentence, but have just as often observed developers doing just what the opinion piece suggested. Rather than using outdated stuff, I've found they tend to steer toward cutting edge (with managers often being worse than engineers.) This results in projects being worked on by novices (who are often experts in what they abandoned) that stall when they can't hire anyone to take over (or the "new" think turns out to be a turkey.)
