Cool History and Facts that aren't important to learning how to be a Database Enginner


History

Even before the internet data enginering has taken many forms for hundreds of years, previously people would manually compile and store information using tabulating machines.

In around 1970 Edgar F Codd began refining the database model using new technology to supercharge effectivity.

In 1980s Data engineering went "mainstream", becoming the optimal way to store and format data.

Pros and Cons

Pros

Cons

Why I want to be a Data Engineer

I want to be a data engineer because I’m pretty interested with how information travels across the internet to make stuff happen. I first got interested when I realized that every time I like a video or buy a new skin in a game, a massive amount of data has to be organized and moved around behind the scenes. I love solving puzzles and building things, so the idea of creating "pipelines" that act like digital plumbing for big companies sounds super cool to me. I think it would be awesome to be the person who makes sure that data doesn't get stuck or messy, because without clean data, even the smartest AI or the coolest apps wouldn't work at all.

Another reason I’m shooting for this career is that I want a job where I can use my brain to help people make better decisions. I know that data engineers are like the behind the scenes heroes of the tech world who set everything up so that data scientists can do their magic. I really enjoy working with computers and learning new coding languages like HTML, and I feel like being a data engineer is the perfect way to turn my hobby into a real professional path. Plus, I know that they get paid pretty well and can work from almost anywhere, which means I could keep my simple lifestyle while still being a tech wizard.