Its not bad.
Just remember to make your code easy to understand to others.
Also try not to repeat yourself. You are calculating 3 times the where the half is.
Instead you can make a specific variable for it at the beginning solving both of your problems.

a good solution, but it wont work if y try add comma, because punctuation can be between words
"Pig, latin is cool" result = "Pig, atinlay siay oolcay"

Is the type casting necessary or best practices?

Someone can give me feedback about my solution?

I think your solution is way less efective, and in this top rated solution is problem with creating String s (it's redundant) we should just return new string from substring and that is it. Clear effictient and without redundancy :).

Love this solution. Interested one

The only thing different I'd do here is make the 48 a descriptive constant to avoid it being a magic number. I'd make the constant follow what @boyarkogc explains is the reason why 48 is there. I.e. CHAR_TO_INT_CONVERSTION_NUMBER or something better.

It's bad practice! Because every use of the substring method creates a new string. Hence we pollute the string pool. See mine....

Extremely disappointed that this did not work. I had to take the long long long way around.

https://www.cs.cmu.edu/~pattis/15-1XX/common/handouts/ascii.html
(A little late, I know...)

String s is unnecessary. Just directly return word.substring(...).

beautiful...?

Why are you importing java...Collectors if you r not using Stream API? :D

Why people are voting "Best Practice" to a String concat loop?