Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
On the other it is an opportunity to force everyone to learn a new language in an idiomatic way. Everyone would need to watch the same videos that tell them how to do it right. Which may not have happened with Java the first time.
-
donuts238503y@Demolishun I'm not the boss... And forcing them to watch videos will never happen unless it's mandated by compliance (aka you will get fired if you don't complete it)
-
@donuts People don't listen to the boss? Your boss doesn't accept feedback or suggestions? This sounds like that might be the bigger issue.
-
donuts238503y@Demolishun feedback or suggestion, I tried.. Answer is only if I can implement it myself.
Learning things off company time is optional. All that self improvement stuff...
On the job no time... Thats the feedback I've given him for years... Nothing changed. And well if I say I have no time... Then the script kiddies probably have less and somehow they're writing the important apps... So....
Best way I can think of is just leave me out of it... But 1 day in gonna get pulled into it anyway... -
Hell no. Doesn't matter if the language is better or not, it's a bad call.
Switching languages mid way through a project is a recipe for disaster. You won't have people writing code in a more idiomatic way, you'll have a bunch of script kiddies bodging things while they try to learn the language, and using your codebase as a sandbox to try out things that may or may not be a good idea.
If these people can't write decent in language X, then switching language is never the solution. The solution is either training them up, or hiring better engineers. -
If a smith hits his hand constantly with his hammer... Another hammer wouldn't solve the problem.
He should change the job....
Was recently asked if our team wanted to change from Java to Kotlin so I looked over the feature lists but don't see much that's impressive.
One argument was less boilerplate code but I think they're are libraries like Lomboq that can write that stuff for you.
The other was smart type casting and type inference and to that I'm like this sounds like giving monkeys a hammer.
Our JS codebase looks like shit... And our Java app just crashed in prod.
Getting a ton of text messages this morning and thankfully I'm on vacation still...
The error is not caused by NPE... but how some or logic spammed the db..
A new language isn't going to fix this.... And a team that writes this sort of shit logic clearly shows they are incapable of learning a new one probably...
They are already script kiddies... Don't need them to become babies...
rant