3 ms·
Exactly. The code isn't the hard part. The hard part is abstract thinking and logic. I created an email escalation notification system that was manipulated w
by ldiracdelta 5y ago
Exactly. The code isn't the hard part. The hard part is abstract thinking and logic.
I created an email escalation notification system that was manipulated with graphics in a flow diagram. My users couldn't handle the precise logic for doing the escalation chain and always asked for help. Turns out, _that's_ what I'm good at. Logic and abstract reasoning.
- oneplane 5y agoI see the same thing in most ticketing and planning systems, they all have some logic to decide what next steps are allowed and to edit those steps you modify a graphical representation of a state machine. You don't need to write code to modify it, but if you have no knowledge of flows or state machines or logical succession of events you simply can't solve the problem. It's not hard, but no-code isn't going to make it less hard either.