@Elendil yes you can. You just give notice applicable to your contract. I also mean start the job if needs be and continue to look then.

Take the job and then look for something better. If you don't find a better thing then you have something to fall back on. Best time to be looking for a job is when you have one

@Coffe2Code The sophistication of a language doesn't mean it is better at handling sophisticated scenarios. I find web services don't get too complex anyway. If they do then break them up. Devs can make crap of anything without testing, review and direction. What are the skills of the team and senior devs at present. Take that into account obviously. Also look at how easy it is to attract talent

Remove php from job description. Honestly even the risk of me doing php would make look elsewhere.

I was a Java dev for years and Co-architected a multi service (microservice) platform in Java. I would chose node. Developing node is far faster because devs don't waste their time on making code overly typed with verbose generics and overly pretty patterns etc. These are fallacies which cost time especially in early days when requirements are fluid. In Node devs just think in flexible json. Json in json out. Free and fast. Java has a fairly hard scale ceiling and a memory hog. Both are good choices though.

@RememberMe. Maybe. However Ive worked in very large enterprises and medium sized ones. In both places developers just ignored the licence types and downloaded intellij community free edition. The business didn't know or seem to have opinion. Just my experience though.

@RememberMe sorry I was prob a bit cryptic there. Lol. I mean once you use intellij eclipse instantly becomes completely irrelevant and you never use it again. You don't complain about irrelevant things do you? You move on

People who complain about eclipse have just never heard about intellij. It's even better for java than visual studio is for c#. Visual studio has a good debuuger but intellij pips it overall as it has a great emphasis on keyboard use, leading to rapid developing. Please Stop complaining and take the time to look at intellij.

I suspect that they didn't reject you for that answer. That would be ridiculous.

Doesn't matter which one (I use gitlab) , just don't bother hosting your own. It will only be time and effort to setup, maintain, keep running and will need to be back up anyway to the cloud unless you want to risk losing your repos if hard drive fails. Cloud all the way. Most small companies do this. Only big companies host their own usually

In a nice-to-work-for company it's when you stop climbing or growing or being valued. In a not-nice company: as soon as you can find something better

Thank the gods for jodatime

I've used it lots to dynamically infer the class which is implementing a certain interface. The interface described a DB connection object and the various classes which implemented it each handled different schemas. We needed to find which was the most appropriate version for given schema of the DB and then create it

I'm a software and product director and have been a software manager. In my professional opinion... This guy is not just incompetant but is actively impeding development. Formally request a change to the policy in a strongly worded but respectful email. If that doesn't work then leave the company and do them a favour by informing them why in an exit interview

An infinite number monkey's on an infinite number of typewriters cannot exit Vi

This is so fucking true its uncanny

Component composition and abstractions are how unscalable human brains can manage the scale-less complexity of computer systems. We all move up the stack.

I have worked on both. SSR is a poor separation of concerns. It's about guiding devs to work towards scalability and reusability. In SSR Devs end up wrapping data access and rendering in a tightly coupled ball. Scaling suffers and when you find you need a nice reusable REST API later which describes your business its too late