3 ms·
Sounds like the criteria you outline for using a library can be learnt in a second. Why is it then a differentiator between junior and senior? I have been thin
by auggierose 5y ago
Sounds like the criteria you outline for using a library can be learnt in a second. Why is it then a differentiator between junior and senior?
I have been thinking about Rust, but it has too much stuff like ownership I rather don't want to think about on top of the already complicated things my code does.
A compiler from Swift (or a subset of Swift) to TypeScript would make it a viable option for me. Maybe I write it myself.
- CactusOnFire 5y agoIt's a differentiator between junior and senior because senior people need to make "the call" on using a technology, juniors don't. There's a couple of other heuristics for whether or not something is worth using on a project (like complexity of learning, and context within a larger stack), but suffice to say it's about looking past a specific problem and on to subsequent problems down the line.
- bluGill 5y agoJuniors often make the call too. Seniors make the call on major things, but there are a lot of little things juniors get to decide, and some of them become bigger over time.