a pattern I think I’m noticing is that - if you’re results-oriented as a developer then the best move is to use something very big and complex to do a lot of the work for you. like a web framework, a GUI framework, a game engine, an SPA framework, etc.

and because of that, getting hired to write code generally also involves learning (at least on a surface level) several of these Big Complicated Things. because corpos are very results-oriented of course

what I’d expect is that amateur* programmers avoid Big Complicated Things because learning them takes a long time and none of that time is fun for them. but actually it seems like amateur programmers are more split on whether they use BCTs or not. and I find that interesting. I wonder if:

• some amateur programmers enjoy the process of learning BCTs
• some amateur programmers enjoy getting results faster than if they didn’t use BCTs
• a third reason?

* amateur: doing something out of pure passion and love - with no need to be paid for it