3 ms·
The story of the senior Java developer is startling but plausible. If you work on legacy applications for 15 years and you're never the originial author who st
by YourAnMoran 9y ago
The story of the senior Java developer is startling but plausible.
If you work on legacy applications for 15 years and you're never the originial author who starts from scratch, it is very possible that you'll never write a main method. You always have one already.
- Quarrelsome 9y agoyeah but how the hell do you even start to grok a code base without knowing how to identify the main entry point? This is what disappoints me with MS technologies like WPF where they go out of their way to hide the static void main.
- haltingthoughts 9y agoYou can abstract out how things are setup. If you have an inversion of control framework that creates all your objects and makes sure services get started in the correct order then you don't really care about the exact details.
- Quarrelsome 9y agoyeah but where do you initialise the IOC container? ;) Also sometimes the magic breaks and you need to know how it works to fix it.
- andyjohnson0 9y agoI'd still expect such a person to have written standalone utilities and throw-away test applications.
- Joe-Z 9y agoEven then, this is stuff that the IDE simply generates for you. Why would I memorize the signature of a method I will probably never use?