Henk Nienhuis

Henk Nienhuis (11 August 1941 – 18 February 2017) was a Dutch footballer and manager. He spent the major part of his career at BV Veendam, hence his nickname Mister Veendam.[1]

Henk Nienhuis
Personal information
Full name Hendrik Evert Nienhuis
Date of birth (1941-08-11)11 August 1941
Place of birth Nieuw-Buinen, Netherlands
Date of death 18 February 2017(2017-02-18) (aged 75)
Place of death Veendam, Netherlands
Playing position(s) Midfielder
Youth career
VV Nieuw Buinen
Senior career*
Years Team Apps (Gls)
1963–1973 Veendam
Teams managed
1984–1989 BV Veendam
1993–1994 BV Veendam
* Senior club appearances and goals counted for the domestic league only

Playing career

Club

Nienhuis played in midfield for BV Veendam from 1963 to 1973, after joining them from hometown amateur side Nieuw Buinen.[2] He made his debut for Veendam on 25 August 1963 against Excelsior.[3]

He attracted interest from Feyenoord and was called up for Netherlands U-21 in November 1964,[3] only for a severe injury to spoil his chances.[4]

Managerial career

Nienhuis managed Veendam during the second half of the eighties, clinching promotion with them to the Eredivisie twice. He later worked as a director at the club, as he did at FC Groningen.[1]

Personal life

He was honoured as a Knight of the Order of Orange-Nassau in 2000 for his services to football in the Netherlands.[5] His son Evert-Jan also played for Veendam.

Nienhuis died in February 2017 of prostate cancer.[6]

gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.

References

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