Polyglot polywhat polywhy
Download as ODP, PDF0 likes852 views
The document discusses the term 'polyglot' in the context of recruitment, describing it as someone who excels in multiple programming languages. It emphasizes the importance of side projects as opportunities for skill enhancement and contribution to projects. Additionally, it includes a personal link for further information about the author.
Polyglot polywhat polywhy
- 1. “Polyglot”
- 3. “A polyglot is someone who speaks multiple languages.”
- 4. “someone who regularly codes in multiple languages.”
Editor's Notes
- #3: This lightening talk is about this word, and what I think it means to developers, and why it is important.
- #4: You do see this word used to job adds and bios on the web. Developers don't seem to use it that much themselves maybe its taken for granted in the current eco system? I think it is.
- #5: This is the official definition which relates to spoken languages, you can see how this can relate to computer languages, just change a few words in this statement.
- #6: But I think you have to change some more words to give yourself this title. I'm sure we have all spoken to other developers that have stated or we have stated things such as “I did some Java in a previous job x years ago”, “then moved on to PHP for project x” etc.. These type of conversations normally include negativity towards past languages used, and what they are using now is the favourite. But are we missing out? Has a language or library you used years ago improved? What's the replacement?
- #7: When writing code for fun not profit, its your chance to try a new language, framework or even new style of coding. Even if your usual goto toolset would work fine. You will have a step learning curve (challenges are interesting). Next time you start a side project change at least one of the tools you use, maybe a database for example. Change it for no reason in particular you will benefit for it.
- #8: You will form more opinions and see things you like that are not available in your usual toolset, and definitely things you will hate (which can reaffirm recent tech choices.) This can lead to better tech choices in the future from increased exposure to more tech.
- #9: We we can't keep switching language or stack at the day job because the grass looks or even is greener without major work and planning. Using a different tech might not be as advised. But we can add missing features to modules from other languages
- #10: Quick questions?