/u/xyz
+85
+32
+85
+32
Joined:
2019-10-02
Last Online:
Unknown
About:
Nothing Yet
Weren't you interviewing for a C-related job?
If it's any consolation, I don't think you're only the only person. As things move on, I'm always second guessing myself about my decision of majoring in Computer Science. Nowadays even getting an internship (as a student) is a complete ordeal; I've been trying myself and I've had no luck at all.
A few days ago I came across this article and it does a better job at describing the state of affairs of jobs in the tech industry than I could ever do. I wonder if things were always like this.
I am giving away this first version of the book for free. I do reserve the right to print the book and sell it. You are free to distribute the pdf file or print it. You are also free to distribute printed copies, but you may not get paid for it.
Feel free to use the code samples, either as they are or as inspiration for your own work. Attribution would be nice, but isn’t required.
I will be grateful for feedback, and do so at the Github page for the book – or by email to the address shown in the book. I intend to publish a revised version of the book if I receive feedback that warrants an update.
More about the book on here.
I think the "black magic" might eventually fade away as you gain more intuition but I was referring specifically to those instances for which there is no precedent and somebody come up with a novel idea and a different way of attacking a particular problem.
Yeah, good books that explaining things thoroughly without boring you down are far and between. First, I picked up K&C's The C Programming Language and their expositional style didn't jibe with me. Then, I found Prata's C Primer Plus and found it to be the right fit, so to speak. I recently began reading Chapter 12. What was the book you started with it?
I could search stuff online as I go along but I prefer the structured approach that a good book provides. Then, after I have some of the basics down I can start looking in other places.
Well, that sounds horrible, especially the part about setting up a dev environment. Don't books usually place this type of stuff in the appendix?
Yeah, this might turn out to be true for almost languages that descend from C. Thus, the idea of control statements for looping and branching, functions, etc. might still be the same and you might not have to spend the same amount of time as someone totally new.
Edit: Sorry. I deleted the previous comment which was posted as mod. I wonder if there's there any way to default all posts as non-mod.
Create Post +
.Raku kept the sigils given they're quite useful. As for references, Raku doesn't have them anymore. BTW, sigils are now invariant in Raku. So for instance:
my @fruits = 'orange', 'apple', 'mango'; my $orange = $fruits[0]; # Perl 5 my $apple = @fruits[0]; # Raku
I myself find the distinction between singular vs plural distinction when accessing single and multiple elements quite interesting. However, it can get hairy in some situations so in Raku, the sigil for positionals (
@
) doesn't vary.BTW, does "Manual" refer to the dynamically-allocated memory in the image?
I'm reading about storage classes in C and before that, the author discusses about scope (block scope, function scope, function prototype scope, and block scope), linkage (no linkage, external linkage, and internal linkage), and storage duration (static storage duration, thread storage duration, automatic storage duration, and allocated storage duration). Then, C uses them in combination for different storage classes (automatic variables, register variables, static with external linkage, etc.). Quite the mouthful if you ask me.