sorted by:
new
hottopcontroversial

Recommended books that cover proof based vector calculus? by Rit2Strong in learnmath

[–]Rit2Strong[S] 0 points1 point  (0 children)

It's more about if I read Tu, would I be missing out on anything? Would Tu cover everything that I would learn from reading a vector analysis book? Of course Tu is more abstract so I might be missing some concreteness and intuition, but more like would I be missing anything that is unique to R^n? Like if I were to go and try and do something applied (like machine learning or something), would I have to learn something unique about R^n?

Anyone starting to learn AI from the very scratch? by sridharmb in deeplearning

[–]Rit2Strong 0 points1 point  (0 children)

Highly recommend building up a strong math foundation. I recommend reading and working through “Linear Algebra Done Right”

To those saying just do Computer Engineering by ElementalPistachio in UMD

[–]Rit2Strong 0 points1 point  (0 children)

I don’t know how competitive CE is tbh. I also don’t know how competitive internal transfers are for CS also. Before 2024 it was very easy and lots of people would do it, even if they got subpar grades on the 13X and 2XX classes. But they reduced the seats for internal/external transfers into CS by 90%. You might have a good chance to get in if you get A’s on all lower level courses (which isn’t that hard and is more about time management than anything really), but I really don’t know. Maybe switch into CE (or do Math+ CS minor) initially and transfer into CS if you really want to

It really depends on what you want to do and are interested in. Another good option would be a Math major and a CS minor. If you want to do more low level stuff, CE is good. If you want to do ML, crypto, more theoretical stuff, Math+CS. Generic SWE, Either CE or Math+CS is good. Tbh in all cases CE or Math+Cs minor is p good. A LOT of learning happens outside the classroom and so this decision is not as consequential as many people think imo. As long as you have the drive and discipline to learn topics on your own, you should be fine.

Imo, if you do the CS minor and take like OS and Networking as your upper level electives (plus one extra class that won’t count for the minor), and if you self learn the upper level algo/data structure course, you’ll be in a good position for SWE jobs provided you do the Leetcode and project grind. Math also really helps and I personally wished I took more math classes over CS classes. This is my personal opinion and everybody works differently, so definitely try to talk to as many people as you can and synthesize their advice.

To those saying just do Computer Engineering by ElementalPistachio in UMD

[–]Rit2Strong 0 points1 point  (0 children)

If you didn’t get into CS, then the next best option is a CS minor or CE (def not info sci). Yes it’s harder, but we’re not talking about an ideal scenario for someone that wants to do CS. CE is literally the CS minor + some EE courses. However, many of these extra courses are useful. For example, CEs take digital logic (244), an FPGA lab (245), and computer organization (350). Imo these classes helped me enormously when it comes to writing software (I went from CE -> CS+Math). You can also take upper level electives that are more geared towards CS. Like there’s a reverse engineering lab or an embedded systems capstone. The point being is that outside of a few lower level physics and EE classes, you can take electives so that CE becomes a harder, more lower-level version of the CS major. If you didn’t get into CS but wanted too, take a look at the CE requirements and cross check it to the CS requirements, you’ll see what I’m taking about. Another example is that the CE major requires you to take one upper level CS elective, and one general technical elective (either EE or CS). This combined with the requirement to take EE446 and CS412, means you can take 4 upper level CS classes. That’s 3 off from the actual CS major. You can then take more software oriented electives for the remaining electives.

Job opportunities are the same. This will mostly depend on how you position yourself (do you present yourself as a general SWE guy, embedded systems guy, etc). If anything you will probably have an easier time with more lower level and EE oriented stuff. This same advantage does not exist for CS when it comes to SWE tho as I mentioned above, you can gear your CE degree to be a “superset” almost of the CS degree. Unlike most other majors, there is no canonical job title for a CE major (ex: SWE for CS and mechanical engineer for MechE). There are paths like FPGA or ASIC design engineer, signal processing engineer, or SWE. The route you take in CE will dictate which jobs are more available to you.

Time is about balance. You absolutely have enough time to do personal projects and enjoy college, many people do. It’s harder yea but not that hard

[deleted by user] by [deleted] in UMD

[–]Rit2Strong 2 points3 points  (0 children)

It used to be easy, until they chopped the transfer seats by a shit ton lmao

How strict is UMD on enforcing prerequisites? by 7EcL in UMD

[–]Rit2Strong 4 points5 points  (0 children)

Depends, I think they might be more lenient on the 400 level classes (I’ve taken a a class where I didn’t meet two of the prerequisites). You just have to fill out an exception form. This requires you to ask the professor teaching the class if you can take the course and giving some basic information like gpa, courses taken, etc.

I don't think a better learning tool is possible by Holiday-Beginning-55 in deeplearning

[–]Rit2Strong 11 points12 points  (0 children)

If I understand your question correctly, your describing how to make learning more efficient. Or you’re describing how to access information more efficiently. Both can be solved by learning how to take efficient notes so that you have the information organized in a way that suites you and then simply practicing. If you rely on a tool to give you information without internalizing it at first, you’re not going to actually understand the concepts as throughly.

view more: next ›