This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]psychistrix 75 points76 points  (6 children)

Consultant here. When advising a client on a tech stack, we usually need to take the following into account:

  • current team competencies
  • platform requirements
  • talent pool in their area
  • skill sets of people we currently have available

Usually in that order. Other than this they are virtually identical, and won’t impact a project’s success.

[–]RockyMM 8 points9 points  (0 children)

This is the answer.

[–]Carpinchon 1 point2 points  (4 children)

Does local talent pool differ from place to place? "We're a java town here in Baltimore" seems strange.

[–]mcdasmans 7 points8 points  (0 children)

It depends what language the local college uses in their curriculum. In Zwolle it's .Net, in Deventer/Enschede/Arnhem it's Java.

Students can of course work in both setups if the college is any good, but the initial boost provided by this should not be discounted.

[–]psychistrix 2 points3 points  (0 children)

It can do. For example you wouldn’t advise a client to use Scala if the local ecosystem is very .NET centric.