Does Anyone Know Why Are These Positions Listed Under Football Administration | Page 2 | FinHeaven - Miami Dolphins Forums

Does Anyone Know Why Are These Positions Listed Under Football Administration

Because they typically don't have any direct interaction with the players. They're simply there to analyze film based on specialized situations.

"Assistant coaches" don't always coach the players. Nowdays, everything is specialized. A lot of times you basically have two coaches at every position.

For example, in college football you're only allowed to have so many coaches on staff - coaches that are allowed to actually interact with the players, and recruit. But there's no limit on the number of "analysts" you can have. Because they're not coaching the players. They're simply walking, living, breathing databases that are earning a paycheck charting statistics.

It's similar to how Saban hired former head coaches like Lane Kiffin or Butch Jones or D.J. Durkin as analysts to be on his staff when they needed a job. The best coaches are always on the cutting edge of evolution.

Conversely, the other side of it is how Brian Flores and the Dolphins hired Coach Farrell away from Saban and Alabama a few months ago. Farrell was assistant special teams coach/offensive analyst under Saban. But he couldn't recruit or interact with the players on the field. However, Saban and Flores felt that he was ready to take the next step in his coaching career and begin teaching techniques. A lot of young coaches and/or former players might not have teaching skills yet - but they understand the ins and outs of playing a specific position. In a lot of ways, it's just a way to get former players into coaching. It's kinda what used to be referred to as a GA (graduate assistant) back in the day. That's how you got your start into coaching in my day. You didn't have analysts.

Thanks. This does address what I saw as a "dislocation" of job and accountability.
 
Based on what I've been able to put together concerning apparent coaching staff in the Football Administration department I've updated my Dolphins Coaching Organizational chart. Please let me know if you have any suggestions or recommendations for this chart.

upload_2019-6-24_11-15-47.png
 
Good discussion. Maybe they are looking at other coaches (head and coordinators) preferences, tendencies, and histories in a given situation?
 
Based on what I've been able to put together concerning apparent coaching staff in the Football Administration department I've updated my Dolphins Coaching Organizational chart. Please let me know if you have any suggestions or recommendations for this chart.

View attachment 21313

Awesome Ray!!!

Are you by chance involved in database development, as a career?
 
Awesome Ray!!!

Are you by chance involved in database development, as a career?

No.

I was basically an electronics technician, then a non-degreed electronics engineer and finally a Quality Control Manager in a large industrial electronics repair facility with about 50 to 70 electronic repair technicians.

I did get a BS in Computer Information Systems when I was 64, but I never made much use of it. I remember taking the final exam in advanced programming on my 64th birthday and decided that I had all the fun in college that I was going to get and it was time to give it a rest.

I liked relational data base development but thought that the seven levels of abstraction they tried to design to was, to an extent, like fine tuning a turd. It had to do with the extent of cross referencing types of data and data keys. You could extend the level of keys and data references until everything was tied to everything instead of just grouping like data. It always seemed to me that making a multi- dimensional array would have had the same effect and been more effective. People get so tied to certain methods of rigorous refinement that they "can't see the forest for the trees".

This is kind of like many posters here who get wound around the axle with position terminology. An example is Ends. There are really only two types of ends and they are mirror images of each other; the left end and the right end.

Now watch and see if this statement doesn't generate a lot of "but what about Wide Receivers vs. Tight Ends etc. etc. etc.". Actually there are really only receivers and then, they are only receivers when they catch the ball. The rest of the time they are blockers or decoys. I don't care if you want to call them Running Backs or "Tackle Eligible". Those "specialist" terms are all a bunch of self serving nomenclature that keeps tripping over itself when you have to use a combined term, then your back to a receiver like a "dual threat" receiver.

OK, I'm done ranting. I feel much better now. Back to programming.

I always liked flow charts and programming, but by the time I finished my degree, programming was pretty much a case of using a specialized menu to create screens and did not take a lot of thought or imagination. I liked programming in some of the earlier languages like FORTRAN II and Fortran IV, BASIC, FORTH and computer assembly languages which were commonly used in manufacturing on dedicated machine tools. I also programmed a little using relay logic which was tied to Industrial Control Systems.

I hope this answers your question.
 
No.

I was basically an electronics technician, then a non-degreed electronics engineer and finally a Quality Control Manager in a large industrial electronics repair facility with about 50 to 70 electronic repair technicians.

I did get a BS in Computer Information Systems when I was 64, but I never made much use of it. I remember taking the final exam in advanced programming on my 64th birthday and decided that I had all the fun in college that I was going to get and it was time to give it a rest.

I liked relational data base development but thought that the seven levels of abstraction they tried to design to was, to an extent, like fine tuning a turd. It had to do with the extent of cross referencing types of data and data keys. You could extend the level of keys and data references until everything was tied to everything instead of just grouping like data. It always seemed to me that making a multi- dimensional array would have had the same effect and been more effective. People get so tied to certain methods of rigorous refinement that they "can't see the forest for the trees".

This is kind of like many posters here who get wound around the axle with position terminology. An example is Ends. There are really only two types of ends and they are mirror images of each other; the left end and the right end.

Now watch and see if this statement doesn't generate a lot of "but what about Wide Receivers vs. Tight Ends etc. etc. etc.". Actually there are really only receivers and then, they are only receivers when they catch the ball. The rest of the time they are blockers or decoys. I don't care if you want to call them Running Backs or "Tackle Eligible". Those "specialist" terms are all a bunch of self serving nomenclature that keeps tripping over itself when you have to use a combined term, then your back to a receiver like a "dual threat" receiver.

OK, I'm done ranting. I feel much better now. Back to programming.

I always liked flow charts and programming, but by the time I finished my degree, programming was pretty much a case of using a specialized menu to create screens and did not take a lot of thought or imagination. I liked programming in some of the earlier languages like FORTRAN II and Fortran IV, BASIC, FORTH and computer assembly languages which were commonly used in manufacturing on dedicated machine tools. I also programmed a little using relay logic which was tied to Industrial Control Systems.

I hope this answers your question.
Oddly enough, I started out in electronics, and electrical engineering, as well. Fortran, and COBAL are what I was forced to learn.

I eventually became a machine tool programmer, which I enjoy, because you can see, and hold something "tangible" at the end of the process.

I've kept up with some of the modern languages, Python, PHP, etc, but really only as a hobby.

Your flowchart just reminded me of some SQL dbase projects I worked on a couple lifetimes ago. Awfully dry, and boring work. Pays well though.

Anyway, I agree some folks tend to over complicate the game of football.

There's a reason coaches only use a handful of symbols when the draw plays on a whiteboard......lol
 
Interesting thread Ray. Enjoyed your background disclosure and philosophy...

Perhaps you're familiar with the "concept" of Maya?

Joseph Campbell elaborated on it a lot -- referring to "it" as the trap of
intellectual categories (i.e., thoughts) which bind us in our own mind...

In that way ALL WORDS are highly imprecise and simply abbreviations of "meaning."

Oh yea -- and great job with the chart!

:)
 
Because they typically don't have any direct interaction with the players. They're simply there to analyze film based on specialized situations.

"Assistant coaches" don't always coach the players. Nowdays, everything is specialized. A lot of times you basically have two coaches at every position.

For example, in college football you're only allowed to have so many coaches on staff - coaches that are allowed to actually interact with the players, and recruit. But there's no limit on the number of "analysts" you can have. Because they're not coaching the players. They're simply walking, living, breathing databases that are earning a paycheck charting statistics.

It's similar to how Saban hired former head coaches like Lane Kiffin or Butch Jones or D.J. Durkin as analysts to be on his staff when they needed a job. The best coaches are always on the cutting edge of evolution.

Conversely, the other side of it is how Brian Flores and the Dolphins hired Coach Farrell away from Saban and Alabama a few months ago. Farrell was assistant special teams coach/offensive analyst under Saban. But he couldn't recruit or interact with the players on the field. However, Saban and Flores felt that he was ready to take the next step in his coaching career and begin teaching techniques. A lot of young coaches and/or former players might not have teaching skills yet - but they understand the ins and outs of playing a specific position. In a lot of ways, it's just a way to get former players into coaching. It's kinda what used to be referred to as a GA (graduate assistant) back in the day. That's how you got your start into coaching in my day. You didn't have analysts.
Makes sense to me...
 
Back
Top Bottom