slysf
Joined 15 years ago
Joined 15 years ago
Obviously you should have a nice balance of both, but I've found many company cultures to lean more one way or another, and the advice on this post seems to divide similarly. If you like option A I'd recommend getting a good overview of a variety of languages, data stores, and tools/frameworks so you can at least have an idea of which one you'd learn more of for a given problem. If you like option B I'd do a deep dive into algorithms and CS fundamentals with one language (C, Java, etc) and target companies that work with that language. They're also more likely to have a well defined intern/junior dev role than the fast paced shops, but a slower pace of learning/advancement.
Location: Seattle, WA or REMOTE or Onsite
Remote: Yes
Technologies: Rails/Ruby, MySQL/Postgres, Redis, Mongo, Erlang, GIS systems, SOLR, massive scale.
Email: sylvain dot niles at gmail dot com
I'm open to many types of engagements from helping with specific problems to large scale projects.
Isn't that the bus/train?