It depends on the job. I’ve had jobs where you couldn’t get approval to take a week off and a week off at my current job is no big deal. Generally PTO is more generous as you become harder to replace.
Legacy of the Wizard on NES. It was sort of an RPG precursor with multiple characters and different abilities that you would needed to use to make progress through a dungeon. I was too young for the game and never finished it but I’ve always wondered what happened at the end. Obviously I could look it up but I don’t mind it being a mystery. The box art was cool and the soundtrack still sticks with me today.
In all seriousness, I use to work on a large web app written in C and it was fine for CRUD, but I would never use it for a greenfield project when there are so many other options.
Where I live in the US any kind of fresh herbs except for maybe parsley and cilantro costs more than a box of mac and cheese. My kids eat it occasionally (maybe once a month) because they like it, it's cheap, and takes about 10 minutes to make. Still, >90% of what we eat is home made from scratch. I don't know anyone who eats processed foods for the majority of their diet, though I'm sure some people out there do.
I'm wrapping up my second to last class for Georgia Tech's OMSCS. Here are some thoughts from my experience in no particular order:
- The program is suppose to be the same as on-campus, so the degree is the same (MS).
- It's dirt cheap as far as master's degrees go. My employer is paying 2/3, so that sweetens the deal even more.
- Since it's online and inexpensive, the program is growing a lot. I think in a few years it would be safe to assume that if someone has an MSCS from GT that it was obtained online.
- I've learned a lot of things that I wouldn't have otherwise been exposed to.
- The workload hasn't been bad, but it definitely can be if you're not somewhat familiar with C, C++, and Python since most of the classes are project based. The workload exceptions have been ML and RL which are pretty time consuming. For context, I work full-time and have two toddlers.
- I honestly don't think the online program is the same as on-campus. Maybe the topics are the same, but I very rarely had to study anything outside of the lecture videos, which are almost always very high-level, and the classes have been much less rigorous than my undergraduate classes (from a different university). Additionally, the online demographic is substantially different than on-campus (I imagine anyway). I think this translates to less stimulating discussion and larger grade curves.
- Expanding on the previous thought, the program has definitely been a "what you put in is what you get out" type of thing. You can coast and still get decent grades, so getting the most out of the program requires some discipline to study stuff that isn't required to get the A.
- There is almost no interaction with the professors, but there is an instructor and TAs for each class who may or may not be helpful in answering your questions.
I'm glad I did the OMSCS program overall. I wish that I had the opportunity to get a master's in-person at a top school, but I don't want to quit my job, move, or pay out the nose, so I'll take what I can get. I don't think that the degree will result in higher compensation, but I've thought about maybe one day teaching at a community college or something like that and I figured I'd get the credential just in case.
I honestly don't think very many, if any, employers will care about the ranking of the school you got a course-based master's degree from. I think it matters more if you're doing a thesis based master's and want to do research.
I've used the Teensy 3.1 and it's more or less an Arduino (including uses the Arduino IDE) but lower cost and more powerful processor. There is also a way to build C/C++ code and run it on the Teensy. ESP is similar but has WiFi built in and Raspberry Pi is closer to a full blown general-purpose computer than an embedded platform. Software on the Teensy runs on bare metal, software on the Raspberry Pi usually runs on an operating system (Linux) and is not real-time.
The author points out a poor abstraction and blames the object oriented programming with its secret methods and private code happening behind the scenes, when the issue was just poor documentation or a flawed implementation. Would functional programming really have prevented all bugs?
I've never met someone who hates on OOP like this and has also spent time working in a multi-team setting on a large codebase. Given enough code it's impossible to grok everything that is going on and some kind of abstraction is necessary. This is where OOP really shines; OOP is great exactly because it abstracts away data so I don't have to think about it. Sure, multiple inheritance and deep class ancestry can make OOP code hard to follow, but it's just as easy to write bad code functionally. This post is just comparing the worst of OOP with the best of FP without doing the reverse.
At Google (the original audience of the "rant") tools like Moma and Code Search make it much easier to find the relationship between commit messages and code, so it makes more sense to avoid duplicating information in comments. Finding the commit message for a line of code literally takes one press of a button.
If it's really tedious to find relevant commit logs then I think the right answer is to improve the search process rather than compensate with more comments.