[hasyimibhar]

I completed OMSCS with 2 kids (both preschool), taking 1 class per semester from Fall 2019 to Spring 2023. It was possible thanks to having full remote job and a very supportive wife. I learned a lot, but I probably wouldn't do it again, it was extremely unhealthy, especially for certain classes like Distributed Computing (CS7210).

[Jesus_piece]

Why was it extremely unhealthy? The work load? The lack of sleep with work, kids, and school? Asking because I’m sorta in the same position

[hasyimibhar]

Mostly lack of sleep and having to sacrifice a lot of weekends to work on the assignments. I took OMSCS with the goal of learning as much as possible since I did not have a traditional CS degree, so I took all the hard classes in the Computing Systems track (DC, Compilers, ISL:BE, IHPC, etc).

CS7210 (DC) is the hardest class I took. We had to write a correct Paxos implementation, then use it to build a distributed sharded KV store. I remember having to spend 10+ hours on a single day during weekend. It was worth it though, learned a lot about distributed consensus, and how difficult it is to get right (there were test failures that were fixed after hours of debug, and the fix was literally changing the order of some code lol).

[dannyfreeman]

That's one of the classes I would really like to take. If I end up doing it the kids might spend a lot of time with grandma that semester.

[legerdemain]

Specifically CS7210 is demanding because of its assignments. The assignments come from UW's CSE452, have very little direct connection with the course lectures, and require you to implement a Paxos-like system correctly, basically in one shot, in an environment that is very difficult to debug. So the projects turn into 60-80-hour slogs where students change parameters semi-randomly until something starts working. CS7210 shares that aspect with a number of other courses in the program.

[kingkongjaffa]

is there a decent list of omscs courses to avoid on this basis?