programmer

Even if you aren't a fan of it, that is a pretty ridiculous statement. It is easy enough for almost anyone to use at a basic level, is incredibly extensible, and is efficient and complete enough that it runs most of the commercial web (at least on front end - and its growing on back end.)
 
Some of its features like falsyness, duck typing, and global scope are double edged swords that cause weird errors and library collisions - but every language has trade offs (though I'll admit that "0 == false" causes headaches). It is the rare language that can be used to throw together a simple script or tool in a few minutes to something that can power massive web applications.
 
If you struggled with it then spend some time to learn about its architecture (it has different underlying assumptions from the C family languages.) If your complaint is bad code - inexperienced coders do that in every language.
 
Most of all, don't judge languages that aren't your schtick based on how much easier you find your languages.

Single page apps are going to be heavy in JavaScript and use a a framework like Angular or React. Although the site might be visual, its going to to have more of an emphasis on data and your going to need to connect to a back end (where your data will be secured and served from), learn to handle authentication (thankfully, there are many drop in options for this now), and be more about interacting with the client in their browser.
 
A slick product/corporate page is designed to maximize conversions, funnel users to certain parts of the sites, and drive sales/action. It is going to have well designed hero images, slick animations, need lightning fast load times (at least as the user percieves them), SEO, and likely a responsive design (scales well on both mobile and desktop browsers.) This is a much more design oriented skill set with less emphasis on JS and much more on HTML, CSS.
 
Doing both is great - but learning one well will do more than sorta learning both - so choose a place to start off.
 
Also, working on enterprise CRUD web sites for things like managing bank accounts and flagging suspicious behavior, handling logistics, or moving insurance information around pays just as well if not better. It tends to be contractor dominated and use older technologies like JSPs and long dead JS frameworks. It isn't as much fun, but there is a lot more of that sort of work in the world than the customer facing stuff.

So, I doubt anyone on the forum is going to sink huge sums of time into proving you wrong - it would be an extremely pyrrhic victory when that time could have been used to do something more useful or enjoyable. If you are convinced of something without any underlying theory to support that notion, and are not interested in doing the work to find out whether it is true, then that ignorance is your own burden to bear.
 
I will also say that it speaks to a kind of arrogance that will, I imagine, eventually lead you into some painful repercussions. When I was younger, I did a variant of the same thing and on more than one occasion and was humbled and bloodied for my behavior. It wasn't until I lost friends and jobs and felt the pain and humiliation that I brought on myself that I learned how much I had to learn.
 
Of course, its possible you are just trying to troll - if so I pity you because that is the habit of a person who instead of doing something useful just tries to tear others down. It will not only bring you no lasting joy but leave you useless and aimless while those around you do learn and grow. It is a sure way to lead a lousy life and achieve nothing of note.
 
As a final point, in the time you've spent on this thread you could have started learning something new and useful - the seeds to a profitable career, the foundations of some great endeavor, or perhaps just an amusing project. Imagine if instead you had asked for help in finding the answer yourself - where to start and what to do - how much more you would now know.

Not to insult you, but please read about the dunning kruger effect. You have been making certain statements about something you don't understand very well. That doesn't make you a bad person, but it is a bad habit and will put people off who would otherwise be interested in helping you. Be more curious than certain and accept that the world is full of things you don't know. There is nothing wrong with not knowing, nor in deciding something won't bring you enough value to be worth learning, but there is in asserting the nature of things without having spent the effort to learn about them first. The wisest of men are awestruck not by the amount they know, but the vastness of the things they don't.
 
If you want to make AI then do enough research to ask concrete questions. Both deterministic and learning based AIs are going to be hard to write and I doubt anyone on the forum could simply "give" you the knowledge. If you already know how to program, go watch some videos on youtube that explain it in more depth. If you decide you want to write your own, a good course would give you a good foundation - there are classes on Udemy and other sites. Determine what exactly you want your AI to do, how much work it'd take you (at a minimum it will be a lot), and start learning.

I honestly think paying for a class with a high rating on somewhere like Udemy is a good idea for a greenhorn - when you pay you have some motivation to use the class and the fact that it costs money ensures that the course materials work. A lot of tutorials become out of date or are incomplete, and having a single good starting point to learn from is better than trying to cobble everything together yourself.

Probably too late - but I'm guessing the issue is that you don't have a column for REFERENCES animal(animalno) to apply to.
https://www.w3schools.com/sql/sql_foreignkey.asp

I would use json
 
{     Data: [         { name: 'LTT', price: 25.67},         { name: 'YoutTube', price: 35.67}     ] }  
You can data.toString()  the json to sent and then JSON.loads it the other side.
 
That's json from JavaScript I think python requires all keys to be quoted too.

Java for a back-end or using JSPs/JSFs is still valid but please don't try to use applets, they were always a terrible technology and user experience.
 
Hacking together a Java back end is pretty easy and it's heavily supported within big companies. I know PHP is supposed to be popular but of the more than a dozen clients I've had, not a single one used it - is it popular as a hobbyists/creatives?

Java for a back-end or using JSPs/JSFs is still valid but please don't try to use applets, they were always a terrible technology and user experience.
 
Hacking together a Java back end is pretty easy and it's heavily supported within big companies. I know PHP is supposed to be popular but of the more than a dozen clients I've had, not a single one used it - is it popular as a hobbyists/creatives?

So, C is great if you already understand programming and need to create something close to the hardware - but it's far from trivial to write apps and applications in it. Its like saying assembly is simple - which is technically true, but being simple doesn't mean easy to learn or use.
 
Each tool is good for its own things. A high level OO language is good for representing things like UI's elements and actors in a game because their behavior and state are object like. HTML is excellent for representing a static text document (and awful for most things the web does today without tons of JavaScript thrown in.) C is, if well written, a way to write very fast/efficient code and is a great choice to work with mechanical things. I don't think I would want to program a robot in JavaScript or C# - but if I made an abstraction layer then those languages might let me do all sorts of orchestration easily. Use the right tool for the job.

Cordova is primarily JavaScript, HTML, and CSS and is a cross platform option for developing apps. You can make Java Android plugins but I don't think they can be used on iPhone, only the normal JS, HTML, CSS.

I don't hate C# but I hate Microsoft's stewardship of it (almost as bad as Oracle's efforts to poison Java) and their licensing terms on Visual Studio. Compared to the *free and open* nature of web standards (*really free, not that GPL communist garbage), I hope that .Net and JVM both die in a fire and that some flavor or flavors of ECMAscript/JavaScript with frameworks/libraries on top become the de facto language of everything. If Electron/Cordova apps become efficient then you could write desktop, web, mobile, and server code all in JS - oh what a day, what a lovely day.

I find oracle to be the lesser evil compared to Microsoft. Both have open sourced implementation like openJDK and mono but for cross platform, java runs circles around C#

As developer jobs vary wildly in complexity, technology stack, and domain, there is no set "level" and skill sets aren't nearly as transferable as people make it out. One thing I have learned is that companies have no idea how hard tasks are...and if they don't know, there is no way you can know until you interview and get an idea of what they want. In a first role just try to learn as much as you can, do the best job you can, and remember that getting fired/rolled is par for the course and just another part of the learning process.
 
I'd agree with M.Yurizaki that you should be able to make at least simple, useful apps/sites/programs before applying.

I think there's a difference between "We think higher education should do a better job of teaching real and practical coding standards" and "Higher education is just a gateway to the industry and is useless beyond that"
 
The biggest thing you lose if you ignore academia is the breadth of knowledge. I went to college and took a bunch of classes that are not directly applicable to my current job, but I still am very glad I know them. Things like the machine learning, statistics beyond just the basics, how the internet works, how a CPU works/writing in assembly, etc.
(note these are things I know from college that *I* don't use, obviously there are plenty of jobs that do use some of these but even then a person in that job might have a different set of skills they learned in college they don't use but are glad to know)

In addition to my actual job, I also mentor new engineers in our onboarding program (~2 months time) and I absolutely wish colleges offered a few courses that were industry focused. An "industry primer" class if you will, taught by person who has relevant industry experience. Things like writing proper unit tests, satisfactory documentation, modularity and reusability, writing cohesive interfaces, etc.
 
tl;dr Colleges could absolutely do better, but I still think they are very valuable and don't exactly blame most companies for requiring degrees. (though the price for college in the USA is still stupid and i'll be paying back loans for way longer that I am comfortable with).

If you can get a programming job right now, do so. It will give you real world experience and money. If you can afford to get a degree, consider starting courses. You may or may not learn, you may or may not finish, but the odds of it being a good investment are favorable - unlike a liberal arts degree, a bachelor's in computer science should be able to pay for itself fairly quickly assuming you didn't pursue courses at an exorbitantly expensive college. Get scholarships, get grants - spend the time and effort to get that free money.
 
It is fair to think of a degree as an insurance policy - if you can't get a job without it then its well worth it, if you get a job and didn't need it it will still likely increase you salary enough to pay for itself, and if you land something awesome and never end up needing to complete it - then you can afford the wasted dollars. But the main thing is to start hustling and looking for roles early - it takes several years, possibly painful ones, to ramp up and start climbing the compensation ladder and the longer you wait the more it will suck especially as your life priorities change.

Anyone can write code, the difficult bit is writing good code. Yes you can come up with some projects and put them on GitHub but who is to say the code is actually good?
 
I graduated University ~4 years ago in the UK, started in an entry level role and now lead a team of software engineers in a FTSE 100 company. Truthfully when I'm interviewing we will rarely have anyone in without a qualification of some kind, a personal portfolio is a welcome addition but I've seen some awful stuff in some personal GitHub accounts but we have a few within our department who didn't get a software engineering degree and either started at a small company or started in a different department and learnt what they needed to move into Technology.
 
As others have mentioned as well its not just about writing code, there are a number of other skills you need. I posted this list before but when interviewing I'm looking for all of these things:
 
Code standards - Learn what good code is and stick to it Frameworks - Don't try reinventing the wheel. Cover front-end and back-end Databases - You need somewhere to store data. Look at query optimisation & replication Linux - You're going to be connecting to a Linux server using SSH at some point Security - Do not forget this! Know how to write secure code, stay up to date on the OWASP Top 10 and know what encryption is suitable and when to use it  Software Development Methodologies Software Development Life Cycle Testing - Unit & Functional Continuous Automation / Delivery / Deployment Version Control - Git Other Standards - e.g PHP-FIG PSRs  

Try to either bullet or put punctuation between your responses, it makes them easier to understand 
 
You will need use a program to take Bell's email data and take action whenever an email is recieved. Assuming you're using Bell Canada, this page looks like it has the relevant information: http://support.bell.ca/internet/email/how-to-use-bell-mail?step=5#displayStep And assuming the above link is to the right mail provider, you need to buy/build a IMAP or POP compatible email solution. Do you plan to do this on a single computer, on a server, or on the cloud? Do you have a programmer to work on this? If so, what technologies is he/she familiar with (so I can link a relevant example), if not do you know what programming stack this will use?  
For part 2, it depends on how you are going to get the data. Do you have a web service you can call or do you need to log in get the data? Do you have permission from the data source to get that data? What are you planning to use the data for? Insurance data is rife with personal information which if mishandled can land you in legal trouble (I am not a lawyer, always consult someone who is.)   
For Part 3, do you have any of this site up and running? There are multiple possible architectures you could use to import the data from a web service to a scanning a storage folder with result files. Another option is having somebody manually get the data and enter it into your site.

First projects should be achievable and relatively throwaway - so writing an OS, programming language, or library are not great first choices. Instead, try to add a single new feature to an open source program you like, write a website, or make a simple game. Try to choose projects with reasonable scope - struggling through many small projects (many of which will be failures) will teach more than one giant project.
 
If there was something you wanted your OS to do, ask about how that one feature could be achieved instead.