|
Sounds like me, though I am down a tooth.  One thing you left off your list of resources was codeproject. I guess it is a given though because we are all here, aren't we?
|
|
|
|
|
Good Point! Oversight on my part. I think that I take Code Project for granted, it's just there.
I would be at a loss without my regular email shots from CP. It's not only helped with codeine etc., but I've got some blummin' good applications for free.
|
|
|
|
|
Glad I am not the only one!
He funny thing is though, despite this, we produce great products. Focus. Maturity. Keep it simple. All the attributes of experience I think.
|
|
|
|
|
I'm 68, down several teeth (my dad never left me anything but his crappy brittle teeth), and teaching myself C# as I convert my VB6 code to it. It does not get any better.
Getting old is hell, but it does beat the alternative...
|
|
|
|
|
I thought I was the only one here that fits this description... glad for the company!
|
|
|
|
|
There's a lot of us out here.
the not so silent majority...
|
|
|
|
|
At 75 I thought that I was the oldest coder in the World. I tell my clients "I can still do it.. if I just didn't look so old."
|
|
|
|
|
At 75, you probably are the oldest. I'm only 68.
|
|
|
|
|
I'm the Chief Bit-Byte-Blob Combobulator in my company (of one
Technically, a "Software Engineer" might not do any actual "Programming" - maybe just designing/architecting. So I don't think it's always an equivalency. $0.02
|
|
|
|
|
After 52 years of writing computer programs in various languages across various platforms, I still get the same kick out of watching code run as I did when I started. I'm proud to be a "Programmer" although I moved into "Consultancy" and "Management" for the sake of my career. I never stopped writing code or learning new languages and concepts and I believe I'll be writing code as long as I can see and type. (I still have all my own teeth, but I invested a lot of money in crowns over the years...) Programming is about an attitude to problem solving and being determined to make something work; it doesn't matter whether you call yourself a "software engineer", a "programmer", a "code jockey" or a "computer geek"; if you will visualize a process and create it in working code, you are a "programmer".
Pete Dashwood
|
|
|
|
|
Jeremy Falcon wrote: Chances are you're just getting old then brother. 
Hey! I resemble that remark! 
If you think hiring a professional is expensive, wait until you hire an amateur! - Red Adair
|
|
|
|
|
Jeremy Falcon
|
|
|
|
|
Engineer is one who can see the "big picture" and build an application, since an application is the inter-workings of hundreds of algorithms, a programmer is one who can code the algorithms that are needed to work together to build the application. We find we can find a lot of good programmers, but, it is very hard to find people that are good engineers...start with a blank canvas and build something.
As for age, the good news is everything is online today! If you forget a function and how to use it, simply use Google and up pops the solution and hundreds of examples. It is much easier to be a programmer these days because you simply don't have to remember anything. I remember 20+ years ago we would even give quizzes to prospective programmers to see how many commands and functions they knew, using the logic that the more they knew the faster the could work since they wouldn't have to constantly look commands up in a reference book. But, today, it simply doesn't matter...in fact it is actually good when they look up things on Google because it shows them command they are searching for and algorithms that use the function in ways they maybe hadn't thought about.
|
|
|
|
|
Instructors in schools and universities need to realize this. I agree completely.
|
|
|
|
|
Realize that where all getting old?
|
|
|
|
|
The Klingon kind of.
|
|
|
|
|
|
Today is a good day to code!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I think of myself as Pete, don't really care about the job label.
This space for rent
|
|
|
|
|
Just Pete? Not Pete O'Hanlon?
"Hi. My name is Pete, Pete O'Hanlon. You can call me Pete".
|
|
|
|
|
 Same here. You get an email from me it says Joe. I get one from someone sitting 5 feet from me I get a 10 line email signature, chain or not.
|
|
|
|
|
Software Engineers design and implement entire software application systems. Programmers/developers take those designs and code individual units of work from those designs/specs. Programmers/developers rarely design.
So, if you are designing things, then you are an engineer/architect, if you are strictly just coding to someone else's designs/specs, you are a developer/programmer.
Simples.
Edit: Semantics. Some would argue that "developers" develop software, similar to engineer/architect. With that said, I guess the word "developer" is interchangeable here. - depends on your employer.
modified 8-Nov-17 5:00am.
|
|
|
|
|
Ok, so far. Let's add that you ar a manager or a wizard if you get things done by waving your hands.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
True, of course, but I have never worked in a situation where the two were separated. In all my roles the engineers designed and coded the product.
|
|
|
|
|
Yep. My experience as well, and seems to be the current trend. IMHO, I think it has to do with more shops are going "agile" so to speak, and there is less up front time spent purely in design. So, your "coders" have to know design as well (design & code as you produce and deliver). That is my high level opinion about that - don't know if it is accurate or not.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
