Hacker News new | ask | show | jobs
by fendy3002 2250 days ago
First, the are smaller number of smart developers than you think.

Then see the project's scope. Big project's architecture may not works well for small scoped project, and vice versa. As long as it pays well, small, quick, with duct typing projects are worth to develop.

Usually the problem is small project with tight budget, which makes the margin small and causing you unable to improve / improving your tools.

If that's the case, you may look for other company which have higher margin and pay-to-work hours ratio. It does not necessarily means bigger companies.

Now for the paths:

- front end knowledge is valuable even if you don't aim to be front end devs or full stack, so more or less knowing how they work is useful. Afaik react devs are in high demand and highly paid. However front end grows very fast compared to backend.

- machine learning is good, but I lack the knowledge in this topic. My concern is the tooling today may be very different with the tooling in following years, CMIIW.

1 comments

Thank you for the comment. Do you have some advice on how to see the mode of working within a company during the interview process? Or how to choose a company before sending an application.
For me, I especially avoid companies which take and create multiple projects for clients, or outsourcing companies.

If you love quality, look for companies that have / makes product(s), or companies that use their own product (such as SAAS).