|
Earlier days:
Machine level language -> Middle level language (C) -> High level language -> HTML controls in ASP -> ASP.NET controls -> ASP.NET(MVC) (Back to HTML Control again ) -> Again going towards to native language
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
Build tools are great in software industry, but I am a student so I will whine about bad academics and bad teaching practices. Sorry.
Stupider in the sense that we are getting lazy, we are leaving everything on the shoulders of programs, such as compilers and build tools. A few problems of today are:
- We apply hacks until the problem fades away, or turns into another one.
- We lack knowledge of "the way computers work", we just press F5. Rest is history.
- Stuff like cross-platform native web applications — yes, you got me right, I am talking about JavaScript being used as native language — is making beginners lose their efficiency. In my times, only adults were allowed to lose it.
- Beginners are introduced with "good" tools that keep them from learning how the software industry works actually. Then they use beginners as a good investment and to do the monetization for the company.
- Bad coding practices. Can you imagine, Turbo C++ is still being taught in academics?
I don't want to start a debate or discussion, but, in my opinion every software developer must be taught about the low-level concepts. Not assembly, but at least C or C++ (if you are a fan of Object-oriented programming, anyways). I face students (my class fellows actually) who lack understanding of how a programming language works, but they do know how to cram an output of a loop with 5 as counter variable. That's sad.
Finally, if a developer know what a build tool is, they would be able to use Gradle, Ant or any other tool. If they are unaware of the core concept (as in today's era) they are going to end up using these tools in a very bad manner. I agree I am very bad at Gradle and that is exactly why I am learning the build tools procedures and until then I am trying to stay away from that build.gradle file in my Android applications.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Good speech
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
This is very true.
One reason for this "way of doing things" are websites like stackoverflow. Don't get me wrong - it's a great help if you have a problem.
But many beginners (I see it day by day with my daughter and class mates of her) who just try to develop Android Apps by doing more or less a "copy-paste-session" from answers to different questions on SO and are then unable to determine why something isn't working as expected.
Because they all lack knowledge of the BASICS.
Yes, it's simple things like "how to navigate through folders or copy files in a shell". that basic-basic-basics. fundamentals. Things you "just need to know about how a COMPUTER works" before you think of "how a programming language works".
how shall one, who has no understanding of a filesystem work properly with folders/files and management of the local app folder, user profiles, etc... if this is "just words" for that beginner.
The tools are "too good" today. More like an end-user app like word or excel. Devtools do not require ENOUGH knowledge about the technology. It's too easy. And thats why you can see a worldwide trend of website getting worse and worse... simple login-windows often fail with strange errors today. Refreshed don't work... Apps keep consuming cpu in background. Simple games requre 85% of your device's cpu while in background...
Many of the today's newcomers lack basic knowledge. And this is a hard decrease in the overall software quality worldwide.
You know nothing, Jon Snow.
|
|
|
|
|
Be that as it may, I encounter a lot of old folk, who, according to you, should have the understanding of how a programming language works, yet write code like it's 1960...
If your teachers don't get it, then why should other people get it?
I don't know why, but it seems there are indeed very few programmers who really understand what's going on.
That doesn't really have anything to do with the tools though.
Well, there's the old geezers who simply refuse to learn anything new after VB6... They may code .NET, but they write it like it's VB6 (or worse).
And those are the people that have to learn the newbies.
When you really understand programming it doesn't really matter what language you write in, it's all more or less the same anyway. There's a few core concepts, like memory management (garbage collection or no), object oriented principles, functional programming principles, database principles (SQL and NoSQL)...
The more tools at your disposal the better (if you can correctly use them)!
|
|
|
|
|
Well, being active in the QA forum has made me realize that not even pressing F5 is common knowledge, or at least not put in a breakpoint in relevant places and also use F10 and F11.
|
|
|
|
|
Please, can you visit every school in your country (and any others you can get to) and explain this. Not to the students, but to the teachers.
|
|
|
|
|
I just did during my class of "Introduction to Programming" as well as "Object-oriented programming". I tried to fix them in a few areas where they were lagging. The result was I just got lucky to get an A grade in the first course, in second one teacher gave me a B grade.
So, I came to conclusion that you cannot teach your teacher as long as you are their student. No matter what.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
I've been doing this for almost six years and to me it became easier.
But that may be because I gained a lot of knowledge and skills in those past five years (coming from zero).
There ARE a lot of tools and languages, but so were there five years ago (I just didn't know them yet).
I remember a time when JSON sounded arcane to me. I thought this was some framework all the "big players" used because it was so profound
Anyway, the more I know the more I know I don't know
|
|
|
|
|
Why?
However, I really agree to your claim of JSON. I remember I also got confused with that notation of data storage. But things seem to be easier, or maybe, I started to learn them. And yes, the chain continues, you learn one framework and then you start learning 5 more and with each of that one... The cycle continues.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Once we had to worry about pointers, memory, optimization, architectures.
Now we have to worry about memory, sometimes optimization, architectures, idiosyncrasie of the various frameworks (particularly .NET which is fairly dumb for a number of applications) and skipping useless technologies which will die in a couple of years.
It's just easier to get scammed but back then there were many dubious programming magazines which... scammed a lot of wannabe-developers, so I guess it's just the same situation with a different dress.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
|
|
|
|
|
I find it easier to create something to start playing with because of the amount of tools and frameworks that allow you to create a sketch.
The final product will be harder than before because the requirements are every year more precise and challenging.
|
|
|
|
|
I think some aspects are easier but this is off set by being able to do more trickier, powerful stuff and varied things which makes it harder to get my head round.
|
|
|
|
|
More is not necessarily better.
Peter Leow
https://www.amazon.com/author/peterleow
|
|
|
|
|