JavaScript and other plans
This post was written 8 years ago.
Fri, 28 Oct 2016
It is very late now, but I suddenly feel this urge to write down those plans I have (carrying on from previous longwinded post which was all about just getting ready to make plans). I just want to make it very brief!
So basically, for let's say the next year, I have these two objectives:
1, Organise at least 5 events/workshops in the coming year, where the unifying principles are:
- The format: Probably 2.5 hours in the evening as a default, but could also be a whole Saturday 9 - 5 or something like that
- The topic: It should in some way help newcomers, and it could be something that you don't necessarily find in every tutorial; for example how to use the unix commandline, dev tools etc. It could also be 'soft' topics like how to organise yourself when you freelance, or how to keep physically and emotionally well; I actually have a list of topics in my head (have had that for a long time). Need to start asking people!
2, Improve full-stack web dev and in particular JavaScript as well as I can. I will measure this by hours, i.e. I will set myself a target of how many hours I'll learn. But I will measure the outcome by other objectives. There will be certain endpoints: a, Can I contribute to open source projects? b, Do I feel comfortable teaching others (formally or informally) and c, Can I build stuff without this being a massive and time-consuming pain? (Relatedly, do I manage to stick to a project and finish it off before I start a new one) I am aware that these goals don't look measurable, still to me they are hard endpoints, because I know how I feel when I've grasped something, and I know how it feels when you need just the right effort for something.
So either I will manage to achieve one or more of these endpoints, or I won't. It's an experiment. If I succeed that would be fab, because then I could really teach and could properly help people - and possibly build cool stuff! . But I am a bit skeptic whether that will be the case. The important thing is that I'll allow myself any possible outcome. As long as I stick to my plan of doing a certain number of hours a week, there will always be an outcome worth talking/writing about. And hopefully there will be some improvement. And I have to say that from when we starte our JS group a bit less than two years ago, my JavaScript has really got so much better!So basically, for let's say the next year, I have these two objectives:
1, Organise at least 5 events/workshops in the coming year, where the unifying principles are:
- The format: Probably 2.5 hours in the evening as a default, but could also be a whole Saturday 9 - 5 or something like that
- The topic: It should in some way help newcomers, and it could be something that you don't necessarily find in every tutorial; for example how to use the unix commandline, dev tools etc. It could also be 'soft' topics like how to organise yourself when you freelance, or how to keep physically and emotionally well; I actually have a list of topics in my head (have had that for a long time). Need to start asking people!
2, Improve full-stack web dev and in particular JavaScript as well as I can. I will measure this by hours, i.e. I will set myself a target of how many hours I'll learn. But I will measure the outcome by other objectives. There will be certain endpoints: a, Can I contribute to open source projects? b, Do I feel comfortable teaching others (formally or informally) and c, Can I build stuff without this being a massive and time-consuming pain? (Relatedly, do I manage to stick to a project and finish it off before I start a new one) I am aware that these goals don't look measurable, still to me they are hard endpoints, because I know how I feel when I've grasped something, and I know how it feels when you need just the right effort for something.
If I only could always see it like that! Right, I just will from now on. - The 'full stack' aim is also interesting. I sometimes think I need to make a certain switch in my mind if I really want to succeed there. I guess the main thing is to actually believe that I can learn certain things. I took one significant step years ago, which was switching to Linux as my OS and running my own server to host things. I cannot say how glad I am that I did that. But when things become a bit more proper devopsy, that still feels like a bit of a barrier. It is difficult to say what makes sense there, should I not specialise on the front-end and PHP programming? But then, it does all interest me, and people used to do it all, and the way things are set up at work makes it possible to learn at least the basics of the different technologies you need to have a server up and running, keep it secure and sites performing well. I think I (and others) perceive it a bit as a 'guys' thing. I wonder if it's something of a cultural thing where as a woman you have been conditioned to be more careful with everything, not break things ladida. (My fear of breaking things has in the past years gone down quite a bit already though ;) )
Don't know. But as we are on this topic, here's another thing I am going to stop doing. Looking out for, or thinking too much about whether something someone said or ways in which they behaved is sexist (or agist, anti-foreigner? haha, how unusual can I get - and still, I am the urban 'cosmopolitan' middle-class and the people around me are, too, this is so far probably still the one decisive factor to make me compatible, but maybe shouldn't be?). It is such a fine line, and in the end, it is mostly history and people's habits that can lead to situations where you might feel treated differently as a woman. It is not directly anybody's fault. I do think it can become toxic, it depends very much on where you are. But it seems to me that currently, in my personal life, any subtle thing that might happen in this regard, is far outweighed by the opportunities I've been given, the super-flexible work contract, knowing so many great people in Bristol's tech community, being able to learn from others and so on. Besides that, in some regards, when it comes to the gender topic, there are things that have been problematic from my side. This has only gradually become clear to me, and it pains me somewhat, because I fear it has been a bit destructive. But that again, it is a historical thing why I behaved in certain ways, and there is no point in beating myself up about it. Main thing is, I am aware of it now.
This post was written 8 years ago, which in internet time is really, really old. This means that what is written above, and the links contained within, may now be obsolete, inaccurate or wildly out of context, so please bear that in mind :)