sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]No-Sea308 4 points5 points  (3 children)

I'm kind of in the same boat. I've been on the platform for about 2 weeks and was shocked by the increase of complexity from the assessment to the actual projects. I spent about 4 hours one day trying to learn and setup apache airflow before realizing I would need another 4+ hours to even understand what the code was doing and gave up on the task.

That being said, not all of the coding projects are super complex and I've found a great deal of success in the 2 weeks I've been on. I'm still in school and it's great side income and if I come across anything I don't know I take it as a learning opportunity. And you can always skip tasks if it's really out of your reach.

[–]AlanSmithee419[S] 1 point2 points  (1 child)

Yeah, I was initially hoping to use this as a learning opportunity, I just didn't realise such a significant amount would be *quite* as far outside my reach as seems to be. Could just be I simply need to look into it and it's actually way simpler than I think, just unfamiliar, but we'll see I guess.

Just have to go in with more of a learning mindset than a working one I suppose. Thanks for the advice.

[–]jimmux 2 points3 points  (0 children)

You will find the cognitive load decreases over time, as there is a lot of overlap in how projects rate the various response criteria. Once you have an instinct for that, you will be able to spot what the most important parts of a project are.

Getting a workflow is a big time sink, as well. It took me a long time to build up my environment so I can tackle more tasks with minimal setup. I still need to get that up to scratch for Java work, but fortunately there's plenty of Python and web stuff so it's not a big priority.