- Nov 9, 2013
- 1,515
- 419
- 136
I first studied programming in 1994 -- Wordperfect, Lotus 1-2-3, Microsoft FoxPro (which I use on a daily basis). IMO, boasting is never a good look. TBH, I explain to people that I program because I wouldn't be the same person if I didn't program. For the last 15 years I've done it for myself, I use code to manage my own data.It's commonplace right now. There is no need to boast about it. This isn't 1994.
Elementary students are being taught Python now.
I'm watching this cool video of a speech by Warren Buffett. He talks about 3 people who started with close to nothing and made themselves into paragons of success. The first is Rose Blumkin who came to America and couldn't speak a word of English. She had a kid who taught her words by and by. Her whole life she couldn't read or write. But she had ambition, started a used furniture business that she eventually sold to Buffett for $60,000,000, died at 101.Back in the day, those that couldn't read or write were also basically peasants who never went anywhere in life.
Now a days there is a lot more than programming that can get you ahead in life.
So I'm going to say no.
I love programming in FoxPro. It's an extremely powerful 4th generation language. I started in it before the object oriented versions started coming out, and after Microsoft had bought Fox Software. It's an xBase derivative. I program for myself these days, so I only program when I am motivated to, which is a lot. I've taken the simplest of procedures (my own that I used in a tech support capacity at a software company) and morphed it over the years into a behemoth of flexibility and functionality for my own use. I learned a lot of state of the art programming techniques when I careered in it in the middle to late 1990's and into this century a bit. Did a bit of Y2K work at one point. More than anything it's why I work in Windows. Microsoft stopped supporting it mainly because it wasn't a great revenue source for them. If they'd developed it in the first place, I'm sure it would have been, but they inherited its xBase platform and couldn't turn it into the cash cow type of thing that SQL Server is.I think some it is because it's boring. At least it is for me. If I'm not solving a problem I find useful, it's just work. Not sure what problems school kids could solve to keep the ones like me interested.
I'll bet that a lot of them don't understand it, either. They used to teach Basic programming when I was in high school, and there seemed to be a pretty even split in the class between those who completed the assignments early and those who needed instructor help to get the minimum requirements complete.
Coding is a lot like advanced math. You either "get it", or you don't.
As someone in the industry, people don't really refer to themselves as programmers or coders. It's usually developer or engineer. I call myself a software engineer because there is quite a bit more than the whole coding side of it. That is just part of it, but a major part of it.
Actually, Ford and GM does that to cars all the time. Altnernator under the car, shitty metal, no stopping of the production line. Where Toyota innovated in car manufacturing is that they DO stop the lines if there is a quality defect.i use developer because engineer sounds pretentious
plus almost all software development isn't real engineering - it's "do this as fast and cheap as possible to deploy to production, then we'll fix the bugs and add stuff people want later"
like, you couldn't engineer a building or a bridge or a car or a rocket like that
Software development is part of a software engineers job. I am glad I have the ability to actually engineer stuff from scratch. And I'm constantly re-engineering stuff too and am a huge fan of refactoring.i use developer because engineer sounds pretentious
plus almost all software development isn't real engineering - it's "do this as fast and cheap as possible to deploy to production, then we'll fix the bugs and add stuff people want later"
like, you couldn't engineer a building or a bridge or a car or a rocket like that
I've mostly told people that I'm a programmer for a long time, because that was enough for people to understand and they generally don't care much beyond that (a popular response in the Midwest was "haha, I hate computers"). Being in the greater Seattle area now I do tend to use software engineer more, because everyone here knows what that means.As someone in the industry, people don't really refer to themselves as programmers or coders. It's usually developer or engineer. I call myself a software engineer because there is quite a bit more than the whole coding side of it. That is just part of it, but a major part of it.
I lament the loss of a B.A.S.I.C. curriculum in schools these days. It really was a good teaching / prototyping language.I'll bet that a lot of them don't understand it, either. They used to teach Basic programming when I was in high school, and there seemed to be a pretty even split in the class between those who completed the assignments early and those who needed instructor help to get the minimum requirements complete.
I lament the loss of a B.A.S.I.C. curriculum in schools these days. It really was a good teaching / prototyping language.
(That's Beginner's All-purpose Symbolic Instruction Code to you, buddy.)
Pick a number between one and five.i wrote so many dumb games in QBASIC lol