From experience, if you are applying for a job on the West Coast you will look more believable if you do NOT wear a suit. The rest of the world most likely will expect you to dress up as usual.
So if I just get interviewed by a nurse that will enter my "symptoms" into the diagnosing computer I could game the system to prescribe pain medication and opiates...
Well I understand the negative reaction. We have to accept that programming has become a profession. What this should mean is that there should be a career/education path commonly accepted to achieve this. Unfortunately this path now requires years to learn and practice.
The negative reaction is when people think they can just "pick it up" and probably in a few months start cashing some pay cheques. Is like saying you helped to cure your grandson from a bruise and placed a bandaid and now you are thinking of becoming a doctor. Comments from doctors would be similar.
But even among seasoned programmers they find it hard to accept they are professionals and don't realize that the specialized knowledge they have came from years of practice and research. Many professional programmers get kicked around by their managers because of this perception of programming being just banging the keyboard until something comes out.
My response to the original poster is to do some research first and decide in what he/she wants to specialize. I don't think anything today can compare to QBasic and MS Dos batch files, code complexity is the norm and data privacy responsibilities have legal consequences. So either he is trolling or was lazy and just figured the easiest thing was to fire a question to trusty old Slashdot.
Working to death is a bit harsh. What is more realistic is working past our "retiring" age. With no retiring savings and possibly almost no pension to support us even with a frugal lifestyle, we will be forced to work hoping that our mind and body remain healthy.
Perfectly said but, when you are giving away the keys you are trusting your cloud provider 100%.
When your boss asks you, are we 100% sure that we can trust the cloud what would you say?
The government/hacker group can come to your cloud provider and shut you down base on something done without warning. Usually done by one of your employees, or the cloud provider employees. Probably they were hosting something illegal/controversial in your cloud space without you knowing. How do you recover? How do you setup gigabytes of data and code on another server in a short time?
Wow I'm 40ish and using Java so I guess I'm with the in crowd. Where are those cute female java coders? I want to teach them how to catch exceptions properly
When working on a new project I set the objectives and the architecture and then force my way through looking how to design and implement it. Sometimes is PHP, sometimes is Java but I know when something has to work and I just research/google the missing part.
Keeping an open mind and making the right design decisions comes with experience.
True, but I worked with some great math people that wrote terrible code. Almost like trying to make java look like fortran. It was hell maintaining their code.
Amazingly there are a lot of procedural programers out there that still have to bend their minds around Object Oriented Development. You can take the courses for java, C# and other OOP languages but you will be left wondering why all the trouble to apparently do the same thing.
You need to read "Object-oriented Software Construction" by Bertrand Meyer Written at the beginning of the OO methodologies (circa 1998)
It was required reading when I was in University and many concepts he explains in his book are very valid today.
Slashdot Mirror
But... are you saying he is wrong?
I would need to do some serious googling to confirm it...
Or he trolled harder than you?
+1
I've been using PDFCreator for years now.
I'm another clueless slashdoter in agreement with the parent post...
*shrugs*
Well said... is not what we want to hear but the truth is we need to "align" our resumes for an easy match past HR
From experience, if you are applying for a job on the West Coast you will look more believable if you do NOT wear a suit.
The rest of the world most likely will expect you to dress up as usual.
The other question is if this AI "Doctor" be required to purchase malpractice insurance.
Who is liable? The owner of the AI or the maker/designer?
So if I just get interviewed by a nurse that will enter my "symptoms" into the diagnosing computer I could game the system to prescribe pain medication and opiates...
Profit!!
Well I understand the negative reaction. We have to accept that programming has become a profession. What this should mean is that there should be a career/education path commonly accepted to achieve this. Unfortunately this path now requires years to learn and practice.
The negative reaction is when people think they can just "pick it up" and probably in a few months start cashing some pay cheques.
Is like saying you helped to cure your grandson from a bruise and placed a bandaid and now you are thinking of becoming a doctor. Comments from doctors would be similar.
But even among seasoned programmers they find it hard to accept they are professionals and don't realize that the specialized knowledge they have came from years of practice and research. Many professional programmers get kicked around by their managers because of this perception of programming being just banging the keyboard until something comes out.
My response to the original poster is to do some research first and decide in what he/she wants to specialize. I don't think anything today can compare to QBasic and MS Dos batch files, code complexity is the norm and data privacy responsibilities have legal consequences. So either he is trolling or was lazy and just figured the easiest thing was to fire a question to trusty old Slashdot.
+1
Working to death is a bit harsh. What is more realistic is working past our "retiring" age.
With no retiring savings and possibly almost no pension to support us even with a frugal lifestyle, we will be forced to work hoping that our mind and body remain healthy.
Indeed
+1 Interesting
+1 Well said
Perfectly said but, when you are giving away the keys you are trusting your cloud provider 100%.
When your boss asks you, are we 100% sure that we can trust the cloud what would you say?
The government/hacker group can come to your cloud provider and shut you down base on something done without warning. Usually done by one of your employees, or the cloud provider employees. Probably they were hosting something illegal/controversial in your cloud space without you knowing. How do you recover? How do you setup gigabytes of data and code on another server in a short time?
So... you stick to java?
Wow I'm 40ish and using Java so I guess I'm with the in crowd.
Where are those cute female java coders? I want to teach them how to catch exceptions properly
You sound young!
So true.
When working on a new project I set the objectives and the architecture and then force my way through looking how to design and implement it.
Sometimes is PHP, sometimes is Java but I know when something has to work and I just research/google the missing part.
Keeping an open mind and making the right design decisions comes with experience.
Or if they think assembler is perfectly fine compared to all those sugar coated languages.
If I may borrow that metaphor then as long as the Rolling Stones are still touring...
Come on Mick, one more gig!!
lol
Cool story... bro.
Reads.
Wipes eyes.
Re-reads....
75 years old?? O.o
Well said.
True, but I worked with some great math people that wrote terrible code. Almost like trying to make java look like fortran. It was hell maintaining their code.
Amazingly there are a lot of procedural programers out there that still have to bend their minds around Object Oriented Development.
You can take the courses for java, C# and other OOP languages but you will be left wondering why all the trouble to apparently do the same thing.
You need to read "Object-oriented Software Construction" by Bertrand Meyer
Written at the beginning of the OO methodologies (circa 1998)
It was required reading when I was in University and many concepts he explains in his book are very valid today.