Do some cool shit that I’ve always wanted to do.

- learn more about machine learning and computer vision
- learn C / C++ / rust
- learn embedded systems / programming
- learn more EE centered stuff

I started to get interested in programming at the age of 13. I was started spending a lot time in our school library and read mostly technical books (beginner/hobbyist stuff) about electronics.
Some book was about Quick Basic (hence my username).
On Windoze 95 in a DOS mode IDE I started trying stuff out and soon I had my first tiny console game.
A bit later I started with HTML and CSS stuff, made a website about ongoing jokes in our class and some rants, later I got into VB6 (I hate VB nowadays!) and wrote for a personal school project a learning software (relatively simple one) to learn vocabulary for foreign languages.

At about 15 I started with C++ and later C# .NET, which I liked the most, and started on some new Windows.Forms stuff, created some small websites.

Now I'm working parttime as a professional developer (mostly web, but VR & .NET too) and studying EE at a university.

My parents had no experience with computers at all, so I learned everything myself an with the help of the allmighty internet (the black box with the red dot on top).

That's my story. ;)

Insert your rant about this below this line:
-----------------------------------------

This may be a dumb question, but are there any benefits in learning c instead of going straight to c++ for microcontrollers? I'm in my first ee semester and wondered, because we are learning c and java (next semester), but not c++

Not bragging, when I was in EE Engineering dept, programming with C grade was A1. When I realized I was terrible at ee and wanted to switch to a new dept, I have choosen comp eng because sw dev would give me the most money for the least effort.

TLDR: GREAT MONEY, LOW EFFORT.

Guys...watch the cppcon21 keynotes.
That is good stuff.

The insights and ideas in these talks are not just for c++. They apply to CS in general.

The presenters have done a phenomenal job with the content. There is a good deal of philosophy for what it means to code and how it should look like (not specifically in c++). Most of it is distilled insights collated right from the times when computer science was a domain of mathematicians and ee majors to the modern age.
It is like Dr.Dobbs but in video. Even book like. Certainly very dense.