Also think of your target audience. All of them can program in JavaScript more or less, not all of them will want to learn Perl to do something they can do without learning a new language.
I'm fairly disappointed with this release. My read through of a tutorial in it went something like this:
* Oh you're sticking with that confusing % for hashes, @ for arrays then $ for everything else... maybe maybe classes have been sorted out though.
* Hmm, why is the syntax for defining a class totally different to defining functions and variables everywhere else
* Well they can't have made anything WORSE. Oh fields can have minuses in them?? Packages exist and you can define them but you're not supposed to anymore?
* Well at least you can't totally rewrite the language in some arcane way which means every bit of perl you come across is totally different and unreadable for 45min while you work out what the custom DSL does. looks at phasers, Meta operators, fix'es sigh
Great that this has finally been released, but it really doesn't solve the problems that Perl always had that it is TOO expressive and too customisable, meaning it'll always be vastly different project to project. On top of that it doesn't have the things that people are really excited about now, which is channels, selects and other things that make async easy. I think that this would have been an amazing release when Ruby was getting popular, but I think it's a few years too late.
Manual testing is basically a 0 skill job. Can you click around this website and tell me when you see a bug. This is the most common form of QA but adds very little value that can't be added with more reliability using automation.
Given this QA can still bring value. The two roles that they really add value in are a Test developer specialist writing non-flaky automated tests, and a BA type role where they have conversations that expand a product owner's idea into an implementable feature.
Given that neither of these roles require manual testing, if a QA team has over specialised on manual testing, there's little value in keeping it.
So I develop PHP. The reason I don't use Debian stable is because the latest version of PHP on there is 5.4.41, which is behind the "old stable version". That means security fixes only.
No bug fixes that resolve problems, or modern functionality (that release is over a year old), and will be EOLd in 1 month. That means a big delta of change that will be needed to handled when debian finally does get round to upgrading. Large deltas of change mean lots of risk.
It's much better to stay further up the crest of the wave and handle more regular updates, to minimise the size of the risk I'm bringing into my code at each release, than it is to stick to an old version and not handle the stream of new functionality that's coming in as it arrives.
This happened to me. It was related to work stuff, but also there were some things that made it worse (I'm transgender, and I hadn't started my transition at the time).
* It got so bad that twice I day I'd think I was having a heart attack.
* I wasn't sleeping (like not even a little bit) (I watched like all of Colombo during this time)
* Couldn't walk home without freaking out all the time (that person is staring at me, do they hate me, I don't even know them, are they following me, etc)
In the end I quit my job, and moved town, so I was lots closer to friends. This got me about half way to being normal. Later started my transition, which got rid of /so/ many issues, and got me more or less the rest of the way.
Looking back I wonder how I managed to live with my mind being that messed up.
A lot of people recommend getting medical help. However, just a warning, GPs (in the UK at least) aren't all brilliant with mental health. I got medical help for what I thought was heart attacks, and while my GP suggested it may be stress, they never recommended a therapist. (I have since been told that if you ask, you will get one though, I didn't really know to ask.)
The reason I wanted to post was to point out how it can creep up on you. I certainly didn't notice becoming more and more stressed out, I felt normal. It just felt like life was harder.
So watch out for the things you read in these posts, and be sure know that this can happen to you too.
Whenever you read, watch and listen to content you want to support, you simply flattr it. Remember that you can flattr as many times you want during a month, as you never will exceed your chosen budget.
At the end of each month, we divide your budget into as many pieces as you made flattrs. For example 25 flattrs will divide your budget into 25 pieces. With a 10 euro budget, each piece is 40 cents.
I think this technology might be even more useful for trans men, where unlike trans women there's less flesh available to sculpt the structures you want.
It's only different in that, unless you're contracting, they're fairly uncommon.
Meetings and code reviews happen every day (or at least a few times a month), so you're well versed in their protocol.
Make yourself well versed in the protocol of interviews and they won't be any more stressful than any other type of meeting.
I find its helpful to think of people in a similar situation: door to door salesmen (possibly they're more disadvantaged, than you will be in an interview, I mean you know you've got the skill set or you wouldn't be there, they might get turned away just for being salesmen). Now a door to door salesman doesn't get terribly nervous selling something at the door of their house. Why? Well they do it hundreds of times a day, and before that the practice their marketing spiel, and techniques for getting the customer on side.
Practice questions, practice those body language techniques, practice telling jokes, and generally getting the interviewer to open up. When you do into do the real thing it won't be a big deal at all because you've practically done hundreds of them.