Comments by "Traveller" (@traveller23e) on "Fireship"
channel.
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
Not quite, he missed out on bitfields, several of the keywords (static, register, inline, volatile...depending on C version), and completely omitted mention of the CPP which is pretty important to say the least. Also, he didn't mention all the datatypes, nor go into some of the more complex topics like integer promotion, which overflows are undefined behavior and which are defined, and the challenges of having potentially different byte sizes on different platforms.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
OOP languages tend to be good, but if someone tells you to stick to strict OOP principles ignore them. Like any other tool in programming, use it when it makes sense. If your code would be better with a lambda expression somewhere or whatever, do that. The strict OOP cops will tell you not to use inheritance ("antipattern") or static methods, for an example of how over-the-top some of the stuff gets.
My controversial opinion would be that it's best to just stop worrying about it and just write code that's readable, low-effort, uses the best tool for the job, and (if applicable) efficient. If the best way forward involves a goto, then fuck it and stick a goto in there. Just double check it was the best way first, and choose a more laid-back coworker to do the peer review.
Also, side note: given the choice of C# and Java, go with C#. It's virtually the same, except generics aren't broken in all the core methods ;)
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1