Plaid spanked by 2018 Escalade

[dvarapala]

Originally Posted by Yadkin

I learned to write code in high school, then again in college. That's not engineering.

If actual licensed engineers made the errors that software writers publish routinely, planes would fall from the sky, cars would always break down, and buildings would collapse on top of each other.

Originally Posted by sublime1996525

I am sure the code writing you learned in high school and from your community college 50 years ago is totally similar to what’s being done now.

Every airplane Yaddie has ever flown in has 100% of its software written by unlicensed engineers, but none of them fell out of the sky. Every line of code in his precious Macan was written by unlicensed engineers, yet his SUV hasn't crashed.

Funny how Yaddie's fantasy world matches up to Reality. Or doesn't.

[Yadkin]

Originally Posted by sublime1996525

I am sure the code writing you learned in high school and from your community college 50 years ago is totally similar to what’s being done now.

I didn't go to a community college. But if I did, I wouldn't be ashamed of that.

[Yadkin]

Originally Posted by dvarapala

Every airplane Yaddie has ever flown in has 100% of its software written by unlicensed engineers, but none of them fell out of the sky. Every line of code in his precious Macan was written by unlicensed engineers, yet his SUV hasn't crashed.

The code writers were supervised by licensed professionals.

[Onebadcad]

Originally Posted by Yadkin

I didn't go to a community college. But if I did, I wouldn't be ashamed of that.

In my hood growing up, it was either community college, the military, or a life of crime.

[Yadkin]

Originally Posted by Onebadcad

In my hood growing up, it was either community college, the military, or a life of crime.

I'm always amused by education snobs.

[Tikiman]

Originally Posted by Yadkin

I learned to write code in high school, then again in college. That's not engineering.

If actual licensed engineers made the errors that software writers publish routinely, planes would fall from the sky, cars would always break down, and buildings would collapse on top of each other.

I had to take a semester of Fortran. On punch cards.


A lot of truth to your last paragraph. Where I worked, they would dump new releases for our software programs at night. The first thing you would get in the morning was an email telling you to click on the icon to update the relevant program. I would ignore it and start working using the non-updated program. Sure enough, about 9:00 when enough people had come in and updated, the grumbling would start. Nobody could do anything because there was a bug in the new feature set. My buddies would stop in to my office and find me working and they would say, "How are you able to still be working?" I would just grin and respond, "Oh, I never update my software until you guys have and I see if it works or not."

[snide]

Originally Posted by Yadkin

The code writers were supervised by licensed professionals.

Wrong.

[dvarapala]

Originally Posted by Yadkin

The code writers were supervised by licensed professionals.

Wrong-o.

We can add the DO-178C software development process to the long list of things you are ignorant about.

[dvarapala]

Originally Posted by Yadkin

I'm always amused by education snobs.

Almost as amusing as licensing snobs.

[dvarapala]

Originally Posted by Tikiman

Where I worked, they would dump new releases for our software programs at night. The first thing you would get in the morning was an email telling you to click on the icon to update the relevant program. I would ignore it and start working using the non-updated program. Sure enough, about 9:00 when enough people had come in and updated, the grumbling would start. Nobody could do anything because there was a bug in the new feature set. My buddies would stop in to my office and find me working and they would say, "How are you able to still be working?" I would just grin and respond, "Oh, I never update my software until you guys have and I see if it works or not."

So you worked at Microsoft?

[Steve_R]

How were airplanes built before computers and software existed? How about bridges? Nuclear reactors and weapons? Etc. Etc. Etc.

Inquiring minds...

[GTOguy]

Originally Posted by Yadkin

I didn't go to a community college. But if I did, I wouldn't be ashamed of that.

In general, I have much more respect for tradespeople and creative people than I do with institutionalized academics. The more letters behind their name, the more clueless and helpless they are in the real world. I used to respect that crap. Then I grew up and opened my eyes.

[dvarapala]

Originally Posted by Steve_R

How were airplanes built before computers and software existed?

Ah, so you're saying that Yaddie is so old he used to fly on airplanes that used bicycle chains to spin the propeller?

Good point.

[GTOguy]

Originally Posted by dvarapala

Ah, so you're saying that Yaddie is so old he used to fly on airplanes that used bicycle chains to spin the propeller?

Good point.

That bald-pated, dried-up old popcorn fart is bound to outlive all of us. It's the Yadkin Way.

[GrandSportC3]

It's shocking how little people seem to know about the software life cycle.

1) The product person (or engineer) requests a certain feature
2) The Business Analyst and Development leads meet with the product person to work on requirements for the software to be built. They create a business requirement document.
3) Development lead and business analyst meet and determine what programs or routines have to be created. This is to be discussed with the development team. The work is broken down and each component is assigned to developers. If this is a larger undertaking, each developer has to create a technical design which is then reviewed with BA and the tech team. Once all agree that the tech design is good, each developer will work on their piece and unit tests their piece.
4) once code and unit test is peer reviewed, it is moved to the QA team (Quality Assurance). All the programs for thr project are tested together. A SIT (System Integration Test) is performed and all potential scenarios are run through the system. If all the test cases are closed and successful, the software will then implemented in production or in case of car software, sent via update to the cars.

I've been a Software Engineer for like 35 years. I work for a huge financial institution and I know very little about banking, yet, I write programs for the bank. I don't need to have banking knowledge. That's what we have the BA's for.

[Egnalf]

talking about people or things "spanking" each other on the internet speaks of low character.

[Steve_R]

Originally Posted by Egnalf

talking about people or things "spanking" each other on the internet speaks of low character.

[Raazor] Solid input. [/Raazor]

[Egnalf]

Originally Posted by Steve_R

[Raazor] Solid input. [/Raazor]

Be nice, he sent me a decent bottle of wine to the condo in vail a few years ago. might have been two bottles, i was drunk.

[GTOguy]

Originally Posted by GrandSportC3

It's shocking how little people seem to know about the software life cycle.

1) The product person (or engineer) requests a certain feature
2) The Business Analyst and Development leads meet with the product person to work on requirements for the software to be built. They create a business requirement document.
3) Development lead and business analyst meet and determine what programs or routines have to be created. This is to be discussed with the development team. The work is broken down and each component is assigned to developers. If this is a larger undertaking, each developer has to create a technical design which is then reviewed with BA and the tech team. Once all agree that the tech design is good, each developer will work on their piece and unit tests their piece.
4) once code and unit test is peer reviewed, it is moved to the QA team (Quality Assurance). All the programs for thr project are tested together. A SIT (System Integration Test) is performed and all potential scenarios are run through the system. If all the test cases are closed and successful, the software will then implemented in production or in case of car software, sent via update to the cars.

I've been a Software Engineer for like 35 years. I work for a huge financial institution and I know very little about banking, yet, I write programs for the bank. I don't need to have banking knowledge. That's what we have the BA's for.

I have zero software knowledge. I don't need any. Never did. Never will. Glad I have none, as it doesn't interest me in the slightest.
It's shocking how little people know about Waterman's hard rubber fountain pens of the eyedropper fill era. Horrifying, in fact.

[Yadkin]

Originally Posted by Tikiman

I had to take a semester of Fortran. On punch cards.

BTDT. A half-hour or so of writing code, pencil and paper. Then hours spent typing on that machine, making cards. Wrap up the stack with two rubber bands and paper with your name and account number, drop it off at the window where the big main frame lives. Come back the next day to find a 1" thick printout of continuous, folded paper where you made an error on the third card and the rest is pure gibberish.

Then the personal computer came out and the world changed. You could write a few lines of code, test it, and then write some more in real time.