Unless of course they invent their own WhatsApp, as many other regions have done. I mean, WeChat anyone? Chinese people refuse to use anything but that.
>But suggested for a new project ? I'm seeing this a lot. If you browse the site the article's on you'll find some more examples. The moral of the story is that "we" all think Java EE is very enterprisey and that it's…
I agree with what you say. Certainly would have had a bit more value if the article had elaborated on whether they used anything else. I feel the interviewer should have asked about that. Even a "no, we didn't" would…
> I think it just lacks a new MVC module as an alternative to JSF. In Java EE 8 such a new MVC framework is indeed coming. From the same startup the article uses as an example: https://mvc.zeef.com/manfred.riem That…
>setting thresholds on method / class sizes seems quite arbitrary and potentially harmful. Splitting a method into n different ones, none of which is called more than once is setting up the code for opportunistic reuse…
>Variable names: foo or bar are probably not useful method names for data structures. e is similarly not useful when compared to exception. Be as verbose as you need (depending on the language). Expressive variable…
Unless of course they invent their own WhatsApp, as many other regions have done. I mean, WeChat anyone? Chinese people refuse to use anything but that.
>But suggested for a new project ? I'm seeing this a lot. If you browse the site the article's on you'll find some more examples. The moral of the story is that "we" all think Java EE is very enterprisey and that it's…
I agree with what you say. Certainly would have had a bit more value if the article had elaborated on whether they used anything else. I feel the interviewer should have asked about that. Even a "no, we didn't" would…
> I think it just lacks a new MVC module as an alternative to JSF. In Java EE 8 such a new MVC framework is indeed coming. From the same startup the article uses as an example: https://mvc.zeef.com/manfred.riem That…
>setting thresholds on method / class sizes seems quite arbitrary and potentially harmful. Splitting a method into n different ones, none of which is called more than once is setting up the code for opportunistic reuse…
>Variable names: foo or bar are probably not useful method names for data structures. e is similarly not useful when compared to exception. Be as verbose as you need (depending on the language). Expressive variable…