4 ms·
>Many were newbies in the language, and some were newbies to programming. I wouldn't join this project, no matter what the language is. Imagine it's a popular
by flavio81 9y ago
>Many were newbies in the language, and some were newbies to programming.
I wouldn't join this project, no matter what the language is.
Imagine it's a popular languae. Javascript or C code, for example. There are no true namespacing / packages and modules facilities in JS or C. It would be even worse than the theoretical nightmare you think Lisp would be. (Lisp has extensive namespacing facilities; code can be contained within modules that don't clash.)
If it was Java, you will see wrongly applied Design Patterns, leading to over-complicated, hard to mantain code.
No, thanks. I wouldn't accept no matter the languages.
Newbies to programming should be educated and trained, not incorporated directly into an important project.
- JetSpiegel 9y ago>>Many were newbies in the language, and some were newbies to programming. >I wouldn't join this project, no matter what the language is. Then you will never be employed, because that describes virtually every software project at a for-profit company.
- flavio81 9y ago>Then you will never be employed, because that describes virtually every software project at a for-profit company. I have had 8 years doing software dev (at a for-profit company) most of them as software development director in command of a 15+ people team, thus, I reaffirm what I said: Newbies should be trained first, and only afterwards included in the projects, and that's what I made sure happened on the team, under my command. They deserve to be trained first, in an environment where they can make mistakes freely until they feel confident.