|
How does the other one feel about that?
|
|
|
|
|
I've never asked, he's never offered an opinion
|
|
|
|
|
Maybe you haven't even told him that his brother is named "My best son" or "The son at my right hand" 
|
|
|
|
|
Seems like they would be declared as an array of type Benjamin, named Ben(0) and Ben(1).
|
|
|
|
|
MKJCP wrote: declared as an array of type Benjamin, named Ben[0] and Ben[1].
FTFY! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Thanks. That's newfangled. Today I am writing in Fortran and VBA. Someone's gotta do it.
|
|
|
|
|
|
One starts with a "C", the second with a "D", the third with a "P". 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
|
When I started out it was the systems analysts who did the design and logic. All the programmer needed to do was to convert the English instructions into lines of code. So it was a fairly basic function and any idiot (me) could do it. Since then the job has developed in line with ever more sophisticated hardware and software. So now, the 'programmer' has to understand much more and use his/her skills to develop products rather than be a 'code monkey'.
|
|
|
|
|
Exactly. 
|
|
|
|
|
You are not implying that there's anything wrong with being a 'code monkey'. .
I am implying that I like being a 'code monkey'. .
modified 8-Nov-19 9:07am.
|
|
|
|
|
Of course not. Be true to yourself, do what you enjoy and enjoy what you do.
|
|
|
|
|
Every team needs some code monkeys and I've never seen a successful large project (in this century) that did not have a good balance of analysts, developers, and code monkeys; not to mention some kicka$$ QA people.
JW
|
|
|
|
|
Being ancient enough to remember the System Analyst days, I'd modify that a little:
The profession started as Programmers - that meant we understood the mystic language of computers (COBOL, Algol, Fortran etc) and could translate detailed pseudo code into something that actually worked. In the modern parlance this is also referred to as Coders.
Software Engineers - an evolutionary step where the programmers were actually trusted with writing their own pseudo code and doing some design. Of course letting the business people actually meet the coal face workers was still frowned upon.
Developers - The current evolutionary step where the code jockeys actually can influence how the business should be using the software, rather than being told what to write.
An opinion is an opinion, it's my right to be wrong.
|
|
|
|
|
I guess it has to do with the image people have of each.
A programmer is someone who is anti-social and types code all day, not rarely for evil intent.
A coder is pretty much the same, but without the evil, maybe? It sounds more akin to script kiddies.
A developer sounds a lot more friendly. We're developing, rather than destroying.
I know I prefer the term developer because it sounds like I do more than just type code.
As a developer I also create UI's.
Or what about an engineer? I think I've had that title in the past.
In the end they're all the same, but managers rather hire developers than coders.
Put full-stack or cloud somewhere in your title and you'll do well among managers and recruiters 
Sr. full-stack cloud architect 
|
|
|
|
|
Sander Rossel wrote: do well among managers and recruiters
Who wants to do well with them? They did their best to drain all life out of me and now I have come back to scare them to death.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Looking at the progression of Programmer => Developer => Engineer...
Quote: A sanitation engineer is responsible for the proper handling of sewage and wastewater, as well as the sanitary treatment of wastewater and sewage. They use their skills to perform random sample testing of water in local streams and soil to make sure that the local environment remains safe from contamination.
The analogy should be clear.
|
|
|
|
|
I wonder what would be "the improper handling of sewage". 
|
|
|
|
|
When you forget your gloves & face mask...
|
|
|
|
|
Marc Clifton wrote: Programmer => Developer => Engineer => CodeWraith
You forgot the last step
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
You forgot the precedent to programmer of hack.
Some people never get beyond that. Unfortunately, they work here.
|
|
|
|
|
agolddog wrote: Unfortunately, they work here.
They may use the forums, but they certainly do not work here.
|
|
|
|
|
No, no, "here" is where I am. Not your "here".
Also realized it's an iterative thing, not linear. Start out as a hack, think you've got a pretty good handle on things and have moved up.
Then, a year later, you look at the code you developed when you thought you were getting a pretty good handle on things and think, "what a hack".
Of course, there are some who never endeavor to improve and think they're decent developers, but really just stay on the hack level.
|
|
|
|
|
Ah, thanks for the clarification. in mitigation see the third sentence at The Lounge[^].
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
