3 ms·
1. Learn C. It is the mother tongue of everything. ESP32 projects are as good as anything else. No cheating with the VS code tool chain, understand how all that
by zer00eyz 3y ago
1. Learn C. It is the mother tongue of everything. ESP32 projects are as good as anything else. No cheating with the VS code tool chain, understand how all that gets put together before taking the short cut.
2. Get a CCNA, or at least take all the prep for one. So many devs dont understand the network.
3. Learn about database design: DO you know your normal forms? There is more math and logic in a good DB than most can grasp.
4. Statistics: some of the most important math you're going to take will be here.
5. Daily drive linux, for at least a year. You want to know the OS up/down/sideways. Bind (see CCNA), LDAP (see open ldap)... don't just install them understand them.
6. Play with hardware. If you can spend 50 bucks and get a couple of Rpi' zero2's and build little clusters, and client server toys do it. Cameras can make this fun.
7. Pick an open source project and contribute. Or roll your own and maintain it. You're going to learn more dealing with your first bug than you will in your first year of classes.
8. Java is fine -- play with go, and zig or rust. Build a tiny app in each just for fun (cli).
9. Have fun and never stop playing. Dont take any of the things your doing based on this advice that you no longer enjoy them. If you have to walk away and take a break do it.
- eholli23 3y agoHi, thanks for your response! 1. Would you say the main benefit of getting a CCNA is the knowledge obtained or the certificate itself? 2. My database instructor in HS stressed that SQL is an underused/misunderstood language and is fundamental to understand. Would you agree? Also, is an oracle SQL certificate worth the investment or are there other forms of database languages that I am unaware of? 3. With how competitive the computer science field is, do you have any basic tips on how to stand out? Thanks for your reply :)
- zer00eyz 3y agoCCNA > just do the course work, it's a good networking foundation. It's sql all the way down. The book database design for mear mortals remains the best foundational text on the topic that I know of. After that anything vendor specific is just that... your better off knowing the features of mysql/postrgres than oracle If you were graduating today, I would just tell you "do what ever job you have to to survive and keep working on what every you can on the side". IN a few years when you graduate the market will likely be different. It's going to take you YEARS to close the gap with Sr. engineers, just keep after it and keep growing. I find that people who have a passion for computing or see it as a place to "play" tend to fare the best over time. If you enjoy it, make sure you dont loose that ever. It shows.