You can actually try adding "and indicate what security vulnerabilities are present in the code, if any" or something to that effect to the prompt, by tweaking the `EXTRA` global variable defined near the head of the script. My experience with this so far is that it tends to spew out infosec truisms that aren't closely connected with the code, and that most interesting vulnerabilities require a bit more contextual awareness to notice than this tool has available to it, but ymmv, and it's definitely worth taking a bit of time to see if you can massage the prompt to finagle useful bughunting output from the tool.
Having had worked with both Pytest and Robot, I have to agree. And to expand on that, Robot framework had multiple disadvantages for us. (Note that this is about 2-3 years, so maybe things improved).
It was pretty slow, just rewriting the same test using Pytest sped it up by about 50% on average and that was despite our test environment being the slow part.
The Robot language was quite error prone as it uses spaces inside single keyword as well as to separate parameters. And the IDE support (VSCode in our case) wasn't particularly great. We ended up having to write custom static analysis tools, to catch some of the more common Robot problems.
And pretty much every time something more complicated was required, it was easier to switch to Python to do it. So in the end two languages were required instead of one, making maintenance more painful.
That is not to say that Robot doesn't have its good points. For example retrying on error was much easier than in pure Python. But in the end it was much more work than just using pure Python with Pytest as testing framework.
My experience with trying to use Cucumber for tests pretty much shown me that it doesn't work there. But one thing that I played a bit and seemed that it might work was using Cucumber for writing requirements. At least for when the requirements are written by not technical people, it could give them better structure and for me as a tester make it easier to spot possible problems in them. But I haven't had to chance to try this more, so it might up end not working just like tests themselves...
We didn't had access to that book then on, but it was described in various .txt files from demo groups, though I've found them later (like arround assembly 93 or 94 came out)
From what I read in EU the pay is considered personal information and is thus is protected by GDPR. If your employer wanted to share it with 3rd party for something like this, he would need your explicit approval for it.
The issue as I see it is, that they put the people, who have to rescue them in unnecessary danger as well as potentially drawing them from other places they might be needed at.
There are other ways to grow, that don't put others in danger, so I personally see this as something quite stupid.
I don't agree with this line of reasoning. Every time you take your car, you put pedestrians and bikes in danger, and when a car hurt them it take EMTs away from the heart attacks at home (which I guess it the societal goal). Truth is, accidents individually happen so rarely that we just think that it's ok to drive a car. Here is the deal: as seen from the EMTs point of view, there are freaking people hurt every single day and it's a nightmare out there.
Same with hiking in remote places, it's a bit more dangerous, but still most of the time you don't die (I'd venture to argue that the average number of death per person is only one), so the averaged risk is quite low still, but every time you slip on a rock, cross a sketchy river, etc. You gain experience that will further reduce the risk.
When people drive, we expect them to have a certain level of competence and for their car to be in good working order - there are unavoidable risks to driving, but society expects people to take reasonable steps to mitigate those risks. It's the same principle if you're going into the wilderness. Going into the back country without the right training and equipment is just stupid and selfish.
Well, there is risk taking and risk taking. If you take a calculated risk taking into account weather, skills, environment etc.. and then something happens that's what you have first responders for.
If, on the other hand, you take risks you are not equipped to handle and judge due a lack of skill and ability and you need than first responders you are acting irresponsible. You might also end up in much more dangerous situations then the above mentioned group of people again increasing risk for first responders. You always hear about people unable to judge risks in the Alps.
Here is the deal: when people die in the back country, they will always be judged by wether they lived there or not. If they were from somewhere else, they will be insulted in death as careless tourists, and if they were local, it will be deemed a terrible act of god. Nobody is able to access the skill level and preparedness of dead people across a news article. It's a buffet of prejudice. They will tell you of careless tourists walking somewhere they shouldn't in sneakers, but a local climbing in sneakers will deemed skilled.
I have seen mountaineering guides going solo in ice climbing higher than their clients, going in the mountains in sneakers (which I'm not sure is stupid in the circumstances, but imagine a news article describing a dead tourist with sneakers on their feet).
And you can be criticized in many ways: calling for help to early (that was not very dangerous), too late (you didn't recognize the subtle beginning of a crisis and you let it unfold), too much, not enough. It's all about the identity of the dead and the "angle" journalists will have chosen.
Your second paragraph is describing exactly what I meant. Mountaineering guide =\= tourist. One has the experience the other doesn't.
And journalists usually get it wrong anyway because they cannot judge the risks themselves properly. And those few that do, locals or not doesn't matter, write different articles.
And just by the way. Assuming all locals have experience in their wilds is such a fallacy. Generally speaking the average level of knowledge might be higher, on an individual level you will always have your locals, e.g. the Alps, who are unable to climb, judge avalanche risks or even just zhe weather.
Feeling quite similar and only a little bit younger than you. I just rediscovered LessWrong (because of Pokemon fanfiction) and I think it might be worth for you to have a look at the Hammertime series: https://www.lesswrong.com/s/qRxTKm7DAftSuTGvj
LessWrong has it's problems, like lots of jargon, but this series seems like good tool to clean up life a bit. Especially I recommend having look at the Aversion factoring and Goal factoring, those two seem to be the most useful ones to deal with having lost some kind of "life purpose". Though I have to admit I still haven't found my solution, so take my post with a grain of salt. But at least I feel like I'm working on it in the right direction.
