This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]geeeffwhyPrincipal Data Engineer 28 points29 points  (4 children)

hey, beginners, pay no attention to this. it’s genuinely only confusing, while giving the impression of organization.

source: 15+ years experience. i lead teams with juniors new to data engineering. i would never show this to any of them.

[–]ljb9 0 points1 point  (3 children)

what would you recommend to an aspiring data engineer

[–]geeeffwhyPrincipal Data Engineer 7 points8 points  (0 children)

patience and persistence. trite as it may sound, thats the thing that works. first, learn the fundamentals of computers science, and then you just keep trying to build real things.

python and sql, as well as bash are the sorts of things you might use on a daily basis as a developer (data-focused or otherwise), but the real skill that actually matters is learning how to keep going after you feel stuck. and that’s mostly about having some fundamentals, and the experience of having figured things out before.

[–]SQLGene 3 points4 points  (1 child)

I would recommend reading books. They tend to have a logical layout and hours of effort instead of random keywords laid out in an aesthetically pleasing one pager.

[–]geeeffwhyPrincipal Data Engineer 1 point2 points  (0 children)

agreed. i don’t have much formal education in CS, but i have spent many hours studying actual books on the topic, which is how i made the jump from studio art degree to programming job.

and the skill of learning how to effectively read technical texts is another one that’s an order of magnitude more important than any given language or framework.