The code monkeys are invading!
-
Hi Scott, I was talking about blogs in general and certainly meant no disrespect toward you or your blog. The blog comment was pretty tongue-in-cheek. As for my opinion on your one blog entry - no big deal. I'm pretty sure it doesn't matter what I think one way or the other. If I reread it again now, maybe I'd feel different. I think on that topic I live in blissful denial as much as possible. I could go off on a soapbox rant about how hard it is to find good programmers (I do it occasionally with my business partner :)) Regardless of education and work experience, it's next to impossible to find programmers with any problem-solving skills. Maybe there should be more courses in how to use MSDN or how to find what you need with Google. I don't expect anyone to have the SDK or .NET framework memorized. I don't expect anyone to already have a solution to every situation/problem that comes up. I do expect programmers to know how to research a solution though. Why is that too much to ask? :) Cheers! Mark
Mark Salsbery Microsoft MVP - Visual C++ "Go that way, really fast. If something gets in your way, turn."
Mark, It has been pointed out that I am (obviously) a little too close to the topic. I completely agree with that point, and while I try to be objective in my reading of and responses to the comments here I don't always succeed.
Mark Salsbery wrote:
I think on that topic I live in blissful denial as much as possible. I could go off on a soapbox rant about how hard it is to find good programmers
I think all of us could do the same and probably have very similar rants. :) As you said, it is very difficult to find people with good problem-solving skills, but even harder to find people with good research skills. I've worked with people before that could never find relevant answers on Google no matter how hard they tried.
----------------------------- In just two days, tomorrow will be yesterday.
-
Chris-Kaiser wrote:
Nah, you're too close to the subject. This is the hazard of reading and responding to feedback on one of your works.
I'm definately close to the subject, :) but you are right, it is one of the hazards of reading and responding to feedback on something I wrote.
Chris-Kaiser wrote:
Every post you've made so far has been defensive. They are discussing and maybe attacking, the concepts and position, not you. You've got to get over that if you want you're views in the public and discussed.
You are absolutely right and thank you for the constructive criticism. I do try, but (obviously) don't always succeed.
----------------------------- In just two days, tomorrow will be yesterday.
Scott Dorman wrote:
You are absolutely right and thank you for the constructive criticism. I do try, but (obviously) don't always succeed.
No worries...
-
I'm 74. I got my only degree, in physics, in 1960. I have been programming since 1962, when I fell in love with an IBM 1620. In May 2007 I accepted a full-time programming position writing embedded systems software. As Shakespeare said, "The fault, dear Brutus, lies not in our stars ..." You can't lift yourself up by putting the other guy down.
Jim, amazing! You still working? I didn't beging writing serious software until I learned CP/M on a 3rd-hand Osborne "portable." Before that I only learned what a hassle it was to code in machine language on Texas Instruments and DEC minis. Flip a row of switches, then flip the "enter" switch. I never learned to program card readers, but we had one in our field service office.
-
Jim, amazing! You still working? I didn't beging writing serious software until I learned CP/M on a 3rd-hand Osborne "portable." Before that I only learned what a hassle it was to code in machine language on Texas Instruments and DEC minis. Flip a row of switches, then flip the "enter" switch. I never learned to program card readers, but we had one in our field service office.
When I interviewed, the 1620 they showed me had paper tape input and output. By the time I reported for work they had removed the tape and added a card reader/punch. Hard copy was produced by running the cards through an accounting machine. We got a line printer a while later. The fun part was modifying the Fortran compiler and run-time package to work with the printer. Those were the days!
-
So says this article[^], citing none other than our CP forums as an example. What do you guys think, are newbies taking over software development?
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Back From Vacation The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
The sky is falling! The sky is falling! Everything is falling apart! All the jobs are going overseas! No one cares about quality! ....and man look at the music that kids listen to! It is ruining the morals! And their teeth! -------------------------- Now in my world the last two cell phones that I had still work. I got new phones because the technology was old, it had nothing to do with the manufacturing nor the 'intent' of the manufacturer. How exactly were they supposed to add a camera into it 15 years ago? What exactly was the battery life then? And my last two TVs still work as well. Contrast this with the TVs that I had as a kid which seldom lasted more than three years. And "lasted" is a stretch since that involved literally banging on the top and the sides until the picture maybe worked given the exactly 7 (up from 4 initially) channels that were possible where I lived. How exactly long was a warranty on a car in 1960 when one drove it new off the lot? I have no idea. I doubt it was 5/10 years. I have worked for exactly one company that has successfully outsourced. And that entire company had every possible advantage in succeeding out outsourcing. There are much larger companies that would fail miserably even if they attempted it. And no that has nothing what so ever to do with quality that other countries might have or have not. And not to mention from the point of this original thread that I started programming in high school and I can certainly remember having problems figuring out how arrays worked and I had no idea what a hash was. That didn't mean that I didn't attempt (at least dream) of making money doing it. Not to mention that although I learned about one way hashes in college I certainly didn't remember anything at all about that particular class (and one part only of that class) when I finally encountered later one. And why shouldn't one ask a question about it? After all we have huge thread here which probably has no actual technical content in it at all and which was based on a reference blog which is just an op'ed piece. Given all that verbiage surely someone can explain what a hash is and how to use an array.