[overtomanu]

It's not that easy to do Java+enterprise CRUD job. Even though there might not be much to learn technically, you will be expected to learn about functional/business rules related to the application. ERP software can be one of the most complicated soul sucking job. It is in here where stuff gets tough, in that you have to deal with legacy codebase, poorly documented rules, bug would have become feature etc.

If you don't bring more value to the table and just coast off without learning anything, you will not get hike and effectively be taking demotion year after year. You will not have any bargaining power since they can replace you with a new grad anytime.

[anonzzzies]

I agree somewhat, but we were talking about maximising money without caring about the work; that, at least to me, means I am working as a company for a company, not in a traditional job. Contracting as a company means I can deduct almost everything I buy and/or charge it to the client which means more money. It also means multiple clients and work from ‘my office’ (which looks a lot like my home) has been allowed forever as if you are a company they cannot dictate where you work. Demotion does not exist; they can just tell me they don’t need my services anymore: I have too many clients so I have to say ‘in 6 months’ anyway and get offers all the time for more.

And yes you are right about the learning but that happens automatically when you are building ERP stuff. But that’s always the case: my point is: if you chase the newest tech crap, you are not focusing on making max money as you don’t need to update your tech knowledge. No one cares about that outside the tech realm. For both old and new tech, the business rules you learn by doing and you start to see patterns fairly fast so the next project will be similar to the current. I don’t want to think how many times I implemented almost identical employee benefits self service portals…

[overtomanu]

Yes, I was talking from the POV of employee. If I am going through the trouble of setting my own company and doing contracting job which involve similar work, then to maximize money for work, I would be thinking of offering some SaaS service via the company. If so many companies want a similar thing, then there is some gap in the market.

[anonzzzies]

Different budgets (in a lot of companies they don't have to do paperwork for a project that fits in the assigned budget, but monthly contracts have to be improved higher up and with the IT dep etc) and one doesn’t exclude the other; once I built it for that company I can recreate it and try to sell if I believe it's worth it. My first SaaS company actually was created (in 2001) when one of my enterprise clients said I was allowed to not only sell the solution we built for them but they would actually encourage their competitors to use it so they get new features without having to start a new project themselves. But we kept selling custom/from scratch implementations as well because some companies simply want to own things. The company still exists and sells the same product (very much changed over the years). Was built in Java.

[overtomanu]

yes that makes sense