Why coding is kinda... addicting?

The novelty wears off...

I'm actually studying stuff similar to that! I really disliked coding at first but people kept telling me "just stick with it, you'll love it by the end." They were totally right (as people usually are in those cases).

What kind of work do you do, if you don't mind me asking? I just really like talking to other people who work with data.

@cauliquackers my work is basically crunching data from Facebook, Instagram, and adobe analytics. I work at an advertising agency. Although I have a senior position, the job's difficulty feels lighter than business data analyst jobs. Due to abundance of time, I ended up studying during my working days, and only work when I need to, it's usually the first week of the month and only took me 3 days the latest, a week if I procrastinate.

Are you aspiring to be a data scientist too?

@eriol33 I'm more math/statistics but job-wise the skills I need overlap a lot with those of data scientists.

Your job sounds really cool!! For me, I'm hoping to get into something healthcare-related, like pharmacy or clinical trials

I think you will do great, I met so many biostatisticians on LinkedIn who work as a data scientist

It's true what they say. Programming isn't for everyone, but it's something it just gets to you. I mean I realized I was born to code when I was 4 y old, and I inmediately realized "magic" drove electrical circuitry, and then, controlled circuitry-behaviour through relay states.
TBH that was just the beginning, since I never really managed to tie together electrical engineering with programming, that, of course, until mad scientists such as most research interns of 1970-2000 managed to create analogue behaviour through maths. (such as controlled sound channels, serial-to-serial realtime interaction, data "crunching" (which is what most video game consoles do when executing code), and also the research & development of machines and new ways to do stuff with it.

Do note that programming can't fix hardware, so you need a background in electrical engineering to see "outside the software layer". Nowadays it isn't even really required to know low level stuff to be a good programmer. But I think good programmers are always capable of resolving stuff by thinking outside the box. That undoubtely will lead to a new finding, result and you'll learn invaluable methods from that.

And yeah stay away from the Big O notation because that malform programmers. (it forces you to think how to measure data by density and by possible combinations), that is literally baby steps for a "real programmer". There are much more interesting math approaches to use when tackling black-box scenarios. (hacking)