4 ms·

99.98% of all "programming" is CRUD and line of business _applications_ (the clue is in the name). It is not realistic to turn a CRUD job into a low level / "c

99.98% of all "programming" is CRUD and line of business _applications_ (the clue is in the name). It is not realistic to turn a CRUD job into a low level / "challenging" systems engineering job. If you want a job doing those things, you need to be qualified, apply for, and be hired for such a job, and CRUD experience won't get you very far. No amount of flight attendant experience will get you a pilot job. No amount of nursing experience will get you a doctor job. Same thing applies here, even if companies doing CRUD work like to interview as if and otherwise pretend that their jobs are a stepping stone to such things.

closeparen 5y ago
If CRUD work is so monotonous then why haven’t you automated it away yet? The classic counterpoint here would be e.g. DHH creating Rails.
- jackling 5y ago
  Past few years we automated much of the more common problems. Making the platform highly configurable to the customer so a lot of use cases, especially when it comes to data generation, can be met. But due to the nature of the industry (regulatory software), there's always obscure rules and needs that require new features. So the work isn't completely monotonous, but it is relatively simple.
jackling 5y ago
Yea, my question may have been too vague and poorly worded. I agree with your statement, I was wondering if there was any steps I can take right now to transition into a more technically challenging role. >It is not realistic to turn a CRUD job into a low level / "challenging" systems engineering job. Are you implying that this goal is not realistic, and I should just stick to the current work? Appreciate your response!
- tacostakohashi 5y ago
  You cannot "transition into a more technically challenging role". Of course such roles exist, but you cannot "transition" into them from CRUD. If you want such a role, you just have to stop doing what you're doing now, look at the requirements for whatever role you want, and meet those requirements. CRUD experience is not one of them.
  - jstx1 5y ago
    Sounds like they can transition into a more technically challenging role.

closeparen 5y ago

If CRUD work is so monotonous then why haven’t you automated it away yet? The classic counterpoint here would be e.g. DHH creating Rails.

jackling 5y ago
Past few years we automated much of the more common problems. Making the platform highly configurable to the customer so a lot of use cases, especially when it comes to data generation, can be met. But due to the nature of the industry (regulatory software), there's always obscure rules and needs that require new features. So the work isn't completely monotonous, but it is relatively simple.

jackling 5y ago

Yea, my question may have been too vague and poorly worded. I agree with your statement, I was wondering if there was any steps I can take right now to transition into a more technically challenging role. >It is not realistic to turn a CRUD job into a low level / "challenging" systems engineering job. Are you implying that this goal is not realistic, and I should just stick to the current work? Appreciate your response!

tacostakohashi 5y ago
You cannot "transition into a more technically challenging role". Of course such roles exist, but you cannot "transition" into them from CRUD. If you want such a role, you just have to stop doing what you're doing now, look at the requirements for whatever role you want, and meet those requirements. CRUD experience is not one of them.
- jstx1 5y ago
  Sounds like they can transition into a more technically challenging role.