- Training – There simply isn’t the budget and will to allow staff to develop skills by attending conferences out of the province or country, training sessions and courses on a regular basis. Fortunately, there is now Google and an abundance of on-line courses so I can maintain my skills, but a good portion is at my own expense and time. I can’t imagine how staff 20 years ago maintained their skill set. In fact, I can see that a lot of staff hasn’t. This is particularly short-sighted initiative from the government. You don’t know what you don’t know and the only way to learn things is to see what other people are doing, including in other provinces and countries. It’s one thing to sit around a room and discuss things, but the conversations that happen at conferences are probably where I’ve learned the most. I’ve also made some great connections, which means when I get stuck with something I can email someone I met in Las Vegas or Montreal and ask what they do in the same situation.
- Speed – The rate of change in government is extremely slow. For someone like me, with not a huge amount of patience, waiting 6 months for the latest version of software or getting a new piece of software is extremely frustrating.
- Collaboration – There really is a lack of collaboration within government, with respect to people working together. I’m not sure why this is, or if it’s just the ‘culture’ where I’ve happened to work. I can definitely say the best places I’ve worked, have emphasized collaboration. When collaborating, there’s always someone to say well-done and why did the hell did you do that. Those simple checks can go a long way in accomplishing projects.
- Lack of bonuses – The base pay within government is not bad, but there are no incentives to work harder. There isn’t any options to reward staff who’ve done well, even with a day off, an extra something in the pay check. If you’re lucky you’ll get a beer and some wings.
- Mandatory union and pension contributions – The upsides of being in a union and pension are definitely weighed down by the expenses, specifically the pension contributions. I take home less than 60% of my actual pay check but live in the province with one of the lowest tax rates. A large portion goes to the pension contribution. When I’m just starting out, I’d probably prefer more to put on my mortgage and get a new car, but I don’t get the choice. In the long run, I’m not sure this is bad, but right now its a pain in the ass.
5 reasons that its nice to work in government:
- Job Stability: I belong to a union. The odds of being laid off are very slim, once I past probation and unless your a total idiot they generally work with you or find a position that fits your skill set.
- Contribute to Society: the things I work on have an effect on peoples lives. I can help make decisions that improve peoples lives and future well-being. Most of the time this effect is visible in the short term, though once in a while it will take years to see the effect.
- Work – Life Balance: Rarely do I have to work overtime, and if I do, I get the time back. Additionally, I work a very regular 8-4:30 schedule that leaves me time to schedule life. Also, I’m on a alternate work arrangement schedule that allows me to work a little extra every day and then take every third Friday off. That means at least one long weekend every month, in addition to the mandatory statutory holidays. It also means that second jobs are manageable.
- Defined-Benefit Pension: Retiree’s today from the governments defined benefit contribution plan have a very healthy payback. This means that you can save less in an RRSP. The contribution levels are high, about 11%, and it remains to be seen if the plan is in place when I’m ready to retire. Assuming I stay with government for that long.
- Low Expectations: Let’s face it, the best and brightest rarely go in to government. The salary and opportunities are lacking. There isn’t a lot of competition to be the best in your field or area. This could equally be nice or bad so I’m gonna call it a tie.
- Variability: Depending on what Ministry or area your workload shifts as things become popular. This means priorities can shift at a moments notice, but it also means you get to work on different and interesting things.
When doing Logistic regression in SAS there are several procedures that you can use:
- Proc Logistic
- Proc Genmod
- Proc Surveylogistic
- If you’re using survey weights then you need to use SurveyLogistic to have your variance and confidence intervals calculated appropriately.
- For categorical variables, use a CLASS statement and specify PARAM=REF to use referential coding. If you use EFFECT coding (the default option) then your p-values may not align with your odds ratio confidence intervals.
- Use the ODDSRATIO statement to get odds ratio for specific variables or to compare different levels.
- /EXPB after your model statement will allow you to have the ratios included in your output.
- Check the event selection that is modelled in SAS. By default SAS models the event Y=0, when you usually want Y=1. You can modify by specifying the event in your model statement.
So that are some quick heads up regarding using proc logistic in SAS.
I have a Masters in Statistics. This means I spent at least 6 years studying statistics at some university (University of Alberta) and know a few things about stats. All of this allows me to label myself a ‘statistician’. However, in the past 9 years that I’ve been working I don’t believe my job title has ever been a statistician. I have been a:
- Risk Analyst
- Resource Analyst
- Business Intelligence Analyst
Biostatistician is the closest title to statistician; all of the positions were very numbers oriented and all of them taught me very different things that have come in useful in my career. I will say, that even though all of them were numbers oriented, one thing they all required was clear and concise communication skills. Something I’m still working on.