Subscribe to Blog via Email
Join 296 other subscribers-
Recent Posts
Recent Comments
- Wlodzimierz Kuczynski on Vamvakaris: The flood
- opoudjis on Which Indian states are well known in other countries?
- Test Test on Which Indian states are well known in other countries?
- opoudjis on Karamanlis and their food
- Stazybo Horn on Karamanlis and their food
Archives
- July 2023
- June 2023
- May 2023
- February 2023
- June 2022
- November 2021
- October 2021
- March 2019
- February 2019
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- September 2015
- February 2011
- January 2011
- November 2010
- July 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- July 2008
- June 2008
- November 2006
- October 2006
Categories
Meta
How do you know that you are doing your job well? I’m looking for specific examples.
Interesting. I’ve been in a series of jobs and/or avocations where it is very hard to know, because there haven’t been straightforward quantitative metrics. A lot of what I’ve been doing has been government sponsored culture change (promoting IT interoperability), and that is slow.
- Writing policy papers: well, I dunno, I write the papers, the papers get drafted and redrafted, the papers go out. The board and the stakeholders say OK, but policy is normally a marathon; change is incremental, and there’s always another government department and another vendor to try to get on board.
- Writing IT standards: if you don’t get many requests to update the model, you may have done your job right in anticipating the requirements. Or then again, you may not have promoted the standard to the people that would stretch it into new domains. Getting a request for update is also a success, it means they’re paying attention.
- Promoting IT standards: less pilot projects. Thank god. The concept, it is proven, we don’t need to prove it any more. At least not with those clients.
- Writing software. The client tells you that it does what they want. I’m starting to get that freelancing. It’s hard to get in pilot infrastructure programming (e.g. messaging systems), because it’s pilot, and it’s infrastructure (not visible), though we’ve got ourselves a good instant-validation niche. It was hard to get in an unmentionable past job where the boss kept me completely barricaded off from all users, so I made up my own metrics. And was pretty happy with them.
- Scholarly papers. If you get feedback, at least they’re paying attention. If you get recognised in conferences, you just hope it’s because it was a good bunch of papers, and not because you were a fun drinking buddy last conference.
- Lecturing. Anonymous quantitative student evaluations can kiss my hairy arse: I filled those in as a student, and I remember giving the lecturer a 4 out of 5 so they wouldn’t get too uppity. What mattered to me as a lecturer was the qualitatives. One student saying “never allow Dr Nicholas to take a course again”, and three or four saying I was the best lecturer they had in their undergraduate career. University administration had no time for someone polarising like me. And screw them too.
The kids that said that? They got it. And by that, and by polarising them, I knew I was doing something right.
Leave a Reply