I think there's more an aspect of, "When people are getting a paycheck, they care less." Part of it's because following what your boss wants is not very fun.
ESR is not fashionable these days, but he has some good points about programmer motivation in the open source world.
. We give them a reading list, and require them to spend about four hours per week doing professional reading and studying on their own time. The books include "Clean Code", "Programming Pearls", "The Pragmatic Programmer", several books on algorithms, code complexity, and books on software engineering such as "The Mythical Man-Month" and "Joel on Software".
So, question........how do you ensure that they actually read them?
Oooh, insults. I can do that too: you're an ignoramus, know nothing about WebAssembly except what I've told you, and most likely your knowledge of GC is almost as bad.
If they are new programmers, probably they need more than just programming skill, they need skill acting like a professional. The Clean Coder does a really good job with that.
For programming skill, I'm going to suggest Zero Bugs and Program Faster. That book tries to change the way people think about code.
On the practical side, there's no substitute for looking at good code. Assuming you're a good programmer, this would mean code review is one method. Have him review your code and find mistakes. He'll think he's trying to catch you, but he'll learn a lot doing it. Then you can review his code, too.
Another good mentoring technique is unit tests. They show you the kinds of things the programmer is thinking about when they test. So you can look over the tests in code review and say, "hey, you forgot to test this aspect." Ideally you'll want him/her to be thinking of every possible test case, even if he/she doesn't actually write out the test.
Another thing is to treat the younger person with respect. Sometimes if you say, "Oh you did that wrong" they will automatically assume, "he hates me" and put themselves in an adversarial stance, which is not helpful for anyone. Look for things that they do that you really respect, and point them out.
People are going to be upset when they realize that they will lose an hour of sun in the summer evenings, instead of gaining an hour of sun in the winter evenings.
In fact, I do not think such primitives exits in any assembler dialect,
Well get ready, because you're going to see it in WebAssembly.
GC is not something an execution platform supplies and it does not need to have "primitives" for it.
WebAssembly is going to have it whether it needs it or not. That's the plan. In your confusion about the exact definition of assembly language, you seemed to have missed the point. Languages with GC are not likely to be ported to WebAssembly because in a few years, it will be much, much easier to port them.
WebAssembly will likely never be more secure than Javascript is now, because the people who are implementing it are the same ones who implemented Javascript.
The big thing people are going to start talking about is types in the browser. You'll hear it all over the place, "Use language X because it has types it's better than Javascript." Beyond that, even Crockford is insulting Javascript now, so its usage is probably going to decline.
Lovely argument. Anyone who prefers Visual Studio does so because they are stupid.
No, no. But anyone who claims they prefer Visual Studio without having an understanding of the alternatives, has absolutely no basis for judgement. They merely prefer the only thing they know.
Right now WebAssembly doesn't have primitives that support it. You could hypothetically write your own garbage collector and port it over (so when people load your web page they also have to load a C# runtime or whatever), but I don't think anyone is going to do that since it would become outdated soon.
So Visual Studio is only an advantage to people who prefer Visual Studio, and yet your proof that it wasn't a major advantage of Windows before 2005 was because one person didn't prefer Visual Studio.
I didn't think this was controversial lol. I don't know anyone who understood both Visual Studio and the unix stack who thought that VS was better before 2005.
Even setting up project files in the GUI was painful (where is that compile option I want? How do I link to a shared library?). With gcc it was pretty obvious where the compile option was, and where you had to put it in the Makefile. Of course, if you didn't understand makefiles, that would seem confusing to you, but in that case you're one of the people who didn't understand the unix stack.
you should just have replied with proof about vi's autocomplete.
Here you go, but if you're having trouble using Google I can't imagine the confusion autocomplete will give you. Maybe you need to put down your beer in the cupholder on your computer and clear your mind.
It's still going to be a few years. Right now, you can't even access the DOM from Webassembly.
Eventually it will be in there, and eventually they will be adding hooks so garbage collected languages can run in WebAssembly, too. They're taking it slow though, because they don't want to make the world suffer by making it too miserable. CSS and HTML might be getting an overhaul too, but the whole process could go on until 2030. For right now, we still have to write web pages using lousy frameworks.
Slashdot Mirror
diaf
Were you one of those people who couldn't figure out why your makefiles didn't always work?
I don't think so, setting up a project was a pain in VS for anything non-trivial.
Which one?
Just name every variable 'i.' If he complains, rename them all to 'codebase_lacks_organization.'
You can start reading up on it here. If you had done a little research before typing, you wouldn't have an egg on your face right now.
I think there's more an aspect of, "When people are getting a paycheck, they care less." Part of it's because following what your boss wants is not very fun.
ESR is not fashionable these days, but he has some good points about programmer motivation in the open source world.
These are self-taught people that passed a rigorous interview process consisting mostly of coding. They want to learn.
Good point.
. We give them a reading list, and require them to spend about four hours per week doing professional reading and studying on their own time. The books include "Clean Code", "Programming Pearls", "The Pragmatic Programmer", several books on algorithms, code complexity, and books on software engineering such as "The Mythical Man-Month" and "Joel on Software".
So, question........how do you ensure that they actually read them?
Around here even with the change It's dark by 5:30 in the winter.
It's still going to be dark at 5:30 in the winter, mate.
Oooh, insults. I can do that too: you're an ignoramus, know nothing about WebAssembly except what I've told you, and most likely your knowledge of GC is almost as bad.
If they are new programmers, probably they need more than just programming skill, they need skill acting like a professional. The Clean Coder does a really good job with that.
For programming skill, I'm going to suggest Zero Bugs and Program Faster. That book tries to change the way people think about code.
On the practical side, there's no substitute for looking at good code. Assuming you're a good programmer, this would mean code review is one method. Have him review your code and find mistakes. He'll think he's trying to catch you, but he'll learn a lot doing it. Then you can review his code, too.
Another good mentoring technique is unit tests. They show you the kinds of things the programmer is thinking about when they test. So you can look over the tests in code review and say, "hey, you forgot to test this aspect." Ideally you'll want him/her to be thinking of every possible test case, even if he/she doesn't actually write out the test.
Another thing is to treat the younger person with respect. Sometimes if you say, "Oh you did that wrong" they will automatically assume, "he hates me" and put themselves in an adversarial stance, which is not helpful for anyone. Look for things that they do that you really respect, and point them out.
People are going to be upset when they realize that they will lose an hour of sun in the summer evenings, instead of gaining an hour of sun in the winter evenings.
In fact, I do not think such primitives exits in any assembler dialect,
Well get ready, because you're going to see it in WebAssembly.
GC is not something an execution platform supplies and it does not need to have "primitives" for it.
WebAssembly is going to have it whether it needs it or not. That's the plan. In your confusion about the exact definition of assembly language, you seemed to have missed the point. Languages with GC are not likely to be ported to WebAssembly because in a few years, it will be much, much easier to port them.
WebAssembly will likely never be more secure than Javascript is now, because the people who are implementing it are the same ones who implemented Javascript.
The big thing people are going to start talking about is types in the browser. You'll hear it all over the place, "Use language X because it has types it's better than Javascript." Beyond that, even Crockford is insulting Javascript now, so its usage is probably going to decline.
Lovely argument. Anyone who prefers Visual Studio does so because they are stupid.
No, no. But anyone who claims they prefer Visual Studio without having an understanding of the alternatives, has absolutely no basis for judgement. They merely prefer the only thing they know.
It will happen as Windows becomes less and less of Microsoft's revenue. There are signs all over the place.
Right now WebAssembly doesn't have primitives that support it. You could hypothetically write your own garbage collector and port it over (so when people load your web page they also have to load a C# runtime or whatever), but I don't think anyone is going to do that since it would become outdated soon.
Hilary didn't (she looked tired the entire time) and that lack of campaigning cost her the election.
That's good point. I haven't seen anyone make that connection yet. If she had spent more time out on the campaign trail, maybe she would have won.
So Visual Studio is only an advantage to people who prefer Visual Studio, and yet your proof that it wasn't a major advantage of Windows before 2005 was because one person didn't prefer Visual Studio.
I didn't think this was controversial lol. I don't know anyone who understood both Visual Studio and the unix stack who thought that VS was better before 2005.
Even setting up project files in the GUI was painful (where is that compile option I want? How do I link to a shared library?). With gcc it was pretty obvious where the compile option was, and where you had to put it in the Makefile. Of course, if you didn't understand makefiles, that would seem confusing to you, but in that case you're one of the people who didn't understand the unix stack.
you should just have replied with proof about vi's autocomplete.
Here you go, but if you're having trouble using Google I can't imagine the confusion autocomplete will give you. Maybe you need to put down your beer in the cupholder on your computer and clear your mind.
It's still going to be a few years. Right now, you can't even access the DOM from Webassembly.
Eventually it will be in there, and eventually they will be adding hooks so garbage collected languages can run in WebAssembly, too. They're taking it slow though, because they don't want to make the world suffer by making it too miserable. CSS and HTML might be getting an overhaul too, but the whole process could go on until 2030. For right now, we still have to write web pages using lousy frameworks.
GDB is very, very good. If you were "not impressed", then you did not get how to use it.
What are your favorite (lesser known) features of GDB? I'm not saying you're wrong, just want to improve my knowledge.
You are absolutely out of your mind
What an erudite, informative, and intelligent thing to say. You are so convincing. I expect nothing less from Windows lovers.