This is a really interesting read from Monzo about a recent incident they had. I really enjoy reading their incident management writeups because they show a tonne of detail, yet are stakeholder-friendly.

It's always interesting to see how other banks deal with issues like this, and what they would do to make things better next time.

This is a super interesting thread from Justin Garrison about the importance of words, using Disney as an example. It's always amazing to see examples of how these seemingly small changes can make huge differences.

This is a nice look back at the first year in Women in Tech York - great to hear and looking forward to many years to come!

As with 'You Guys', this is another great view into why using inclusive phrases are incredibly important.

This is one of those posts that sums up why the Nottingham tech community is so amazing - it's well worth a read, especially if you're not from Nottingham!

Ashley's talk was all about how to find out what you're really worth, and some top tips to make sure you're getting what you deserve.

Ashley spoke about how she runs a workshop all about helping negotiate for a better deal, and how difficult it can be finding your worth when comparing yourself against a London salary. Since running the workshop, she's had no one come back to say that they've had negative reactions to negotiation. But if you're in a company that you're worried it'll be held against you (asking for something reasonable) then maybe that says something about whether you should stay there.

Ashley's tweet the day before the event (https://twitter.com/TuffersTests/status/1136227900225708032) was used them to shape some of the talk, talking about the common worries people have with negotiation.

Ashley mentioned that only 20% of women attempt to negotiate salary, but the number of men is much higher. I personally have in the past, as an entitled white-ish man who's been advised in the past to try it where possible.

Instead of "trying to fix the women", Ashley wants to fix the system - a much better idea. Ashley noted that it's been found that women will negotiate if it's *explicitly clear* that negotiation is an option.

Sometimes the company may just not be aware you need a raise, or some other compensation, such as pregnancy parking, because it's the first time they've been made aware of it.

Because it can be uncomfortable to talk about your performance, we had an uncomfortable activity to talk about a recent accomplishment. We learned to talk about ourselves some more - because *it's not bragging if it's a fact*! Prepping for the negotiation is important, taking notes and being ready to talk about your worth.

For the next activity, we were asked to write our salaries, and a generic job title (i.e. instead of Software Quality Engineer, I put automation tester) and threw them across the room.

This was a good exercise to make people think about how they feel about what they get paid - a few people refused to join in, and most felt very uncomfortable. I didn't share it on the night, but I was quite happy with it - as a white-ish male I already have a headstart in confidence, and I'm also very well compensated at Capital One so am fairly proud of what I earn.

Some of the interesting responses were "I need to learn to code!" from some non-tech folks, and "I don't want to share even with people I work with".

A number of comments were along the lines "I'm not sure I'm worth what I'm paid". One view was that the role is quite vague, so "why am I being paid so much? What am I actually being paid for?". And another comment was "I'm not sure I should get paid that much, but other people doing the same job do, so why wouldn't I take it.

It was interesting to hear someone saying how they were happy with what they get paid, in isolation, but if they were to find that "the guy next to me" gets paid more, doing same role, why wouldn't that be a problem.

Ashley shared that in Nottingham, the average non-techn salary is £24500pa, but in tech it's £45000pa. This made a lot of people in the room be like "oh wow, why am I being paid what I am?" This again leads to the question - how do you know what you could get? It's all about keeping an eye on what market rate is by looking at online salary checkers, checking out jobs in your area, and asking friends, family and colleagues.

When negotiating - remember not to panic! Take some time to think about the number, and _go away and think about it_. Do not immediately reply, and feel the urge to take whatever number it is.

But what if they say no when you negotiate? Ashley had a great tip:

> Ask for the criteria that they use to make a decision

They will likely immediately panic and agree to the offer - yay! Because it was likely an opinion, lacking true reason so if they have to try and explain it they'll find it easier to rightfully buckle.

But if they still say no, you could seek a compromise, or really consider your options - is it actually just time to walk away if they won't give you what you deserve? Somewhere else will, so maybe it's worth going somewhere who will appreciate you better.

Ashley noted, on fear, that the physical manifestations of fear is very similar to excitement - so take it as a challenge and be excited by it!

When having the conversation, be yourself, as the best way to convince someone you're an awesome person is to be that authentic, awesome person! It also really helps with confidence if you just be yourself.

One of the questions was "what if it's in our contract that we can't talk about our salaries?" Ashley replied that you need to query this with your HR department and find out what the harm would be if you discussed it. One of the ladies I sat next to spoke about how her company (in Derby) did not want her promoting any meetups because it may expose them to recruiters. Both these defences are short-sighted because if someone wants a better deal or to move on, they will.

Speaking about organisations where there are strict bands of compensation, where you aren't explicitly told you can negotiate, it's still worth a try. And if you're at the top of the band, try and find a role you can move into that has a bit more headroom.

And obviously, money isn't everything - if you're enjoying the work, and able to live comfortably, that's the most important thing. *But* if you find out you've been underpaid for i.e. 5 years in that super enjoyable role, wouldn't you want to know? Wouldn't you want that money.

This was a great, interesting, funny, and thought provoking talk from Ashley, and I look forward to my next opportunity to negotiate!

This is a great post by Jon about Firefox Containers and the power they can hold.

I lazily use them as a way to have i.e. multiple email accounts logged in, or at work having several AWS accounts logged in at once but have also got some pieces in place to containerise certain privacy-infringing companies' attempts to track me.

This is another post you really need to read, if you haven't already, as it makes you really think about the way you communicate.

I know a lot of people who use the term 'you guys' as a gender-neutral term, but after reading this article it really helps persuade you that the term is actually not as inclusive as you think.

For a couple of years now I've been making an effort to use gender-neutral ways to address groups, and I hope after reading this you will too.

As I've embraced indie post types, such as reposts, I've noticed that actually I've been using them wrong.

Looking at https://indieweb.org/bookmark#Repost it appears I've been conflating a "retweet" on Twitter with a "repost", thinking they were the same. Alas, they are not, and it makes more sense to be a bookmark.

I've since updated the posts using the wrong type and will get things right next time!

Being able to write semi-readable written text with technical terminology is a huge skill, and makes such a difference compared to not being able to write it.

I've found that since blogging more, my written language has gotten a lot better, and significantly makes my job easier.

I've worked with a number of brilliant engineers who can't explain themselves as well in written forms, which means commit messages and core pieces of documentation are difficult to understand.

Remember that you're never going to be the only person reading something, so make your content well thought out, re-read it and ask someone else to read through it to check it's OK.