Pierson Prioleau

Pierson Olin Prioleau [PEER-sun PRAY-low] (born August 6, 1977) is a former American football safety. He was drafted by the San Francisco 49ers in the fourth round of the 1999 NFL Draft. He played college football at Virginia Tech. He received a degree from Virginia Tech in interdisciplinary studies, graduating on May 14, 2011.

Pierson Prioleau
No. 23, 25, 20, 31
Position:Safety
Personal information
Born: (1977-08-06) August 6, 1977
Charleston, South Carolina
Height:5 ft 11 in (1.80 m)
Weight:188 lb (85 kg)
Career information
College:Virginia Tech
NFL Draft:1999 / Round: 4 / Pick: 110
Career history
Career highlights and awards
Career NFL statistics
Tackles:360
Sacks:6.0
INTs:1
Player stats at NFL.com

Prioleau has also played for the Buffalo Bills, Washington Redskins, Jacksonville Jaguars, and New Orleans Saints.

College career

Prioleau played college football at Virginia Tech. As a freshman, he appeared in 11 games on special teams and as a reserve cornerback and finished that season with 24 tackles (15 solo). As a sophomore, he started every game at rover position, appeared in 809 total plays and finished with 71 tackles (41 solo). As a junior, he was named first-team All-Big East and third-team All-America by Sporting News. He posted 81 tackles (41 solo) and two sacks that year. As a senior, he started every game for the defense that led the Big East with only 12.9 points per game allowed. He finished with 61 tackles (41 solo) and two interceptions.

Professional career

San Francisco 49ers

Prioleau was drafted in the 1999 NFL Draft by the San Francisco 49ers. While with the 49ers for the 1999 and 2000 seasons, Prioleau started 11 of 28 games he played in as a safety and corner, accumulating 81 tackles and one interception.

Buffalo Bills

Prioleau signed with the Buffalo Bills on November 7, 2001 but was inactive for first three games after joining the team. Prioleau was impressive when he saw action in the final six games. In his first full season with the Bills in 2002, Prioleau started all 16 games at free safety for the first time in his NFL career. He finished fifth on the team with a career-best 86 tackles and also had 10 stops on special teams. In 2003, Prioleau appeared in all 16 games with six starts in his second full season in Buffalo. He posted 37 tackles, .5 sacks, four quarterback pressures and one forced fumble. In 2004, Prioleau played in all 16 games with two starts in final season with Buffalo. He totaled 37 tackles on the year.

Washington Redskins

In his first season with the Washington Redskins in 2005, Prioleau played in 15 games, had 43 tackles, three sacks, and a forced fumble.

On opening day 2006, while playing in a game versus the Minnesota Vikings, Prioleau injured himself during the opening kickoff and spent the rest of the season on Injured reserve.

Jacksonville Jaguars

On April 29, 2008, Prioleau signed with the Jacksonville Jaguars.

New Orleans Saints

Prioleau signed a one-year deal with the New Orleans Saints on March 26, 2009.[1] He re-signed with the Saints on March 5, 2010[2] and again on July 29, 2011. He was released on September 3, 2011.

Personal life

Prioleau and his wife, Alicia, have three sons: Pierson Jalen (P.J.), Parker Jayden and Pace Jordan.[3]

gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.
gollark: That doesn't mean it's actually always what happens.
gollark: Legally, yes.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.