Isn't Java a PITA? Like, couldn't someone who learned Java go on to learn C++, and then C, for example? If they're smart enough to learn to deal with Java, I mean. I know I find C to be a lot more scrutable.
Once you have access to a debugger like gdb, remember to build with debug symbols, and have tools like valgrind or even electricfence. Then C becomes a lot easier. Once you have what I call a debugging-friendly environment for C, you can make headway on unit tests.
This might be my own bias, but I think going from Java to C is a smaller step than going from Java to C++. There are a lot of new concepts in C++, and the syntax is not always obvious. C is a bit more primitive and the main new skill is learning n
Monoculture of language? (Score:2)
The lack of diverse programming experience in your country is not something to be proud of.
Re:Monoculture of language? (Score:2)
Who cares? As long as it pays the bills and works as intended.
Re: (Score:2)
Short term planing doesn't usually lead to long term success.
Re: (Score:1)
Isn't Java a PITA? Like, couldn't someone who learned Java go on to learn C++, and then C, for example? If they're smart enough to learn to deal with Java, I mean. I know I find C to be a lot more scrutable.
Re: (Score:2)
Once you have access to a debugger like gdb, remember to build with debug symbols, and have tools like valgrind or even electricfence. Then C becomes a lot easier. Once you have what I call a debugging-friendly environment for C, you can make headway on unit tests.
This might be my own bias, but I think going from Java to C is a smaller step than going from Java to C++. There are a lot of new concepts in C++, and the syntax is not always obvious. C is a bit more primitive and the main new skill is learning n