HN user

denzil

88 karma
Posts0
Comments47
View on HN
No posts found.

So yes, it mostly gets done for (components of) planes, spacecraft, medical devices, etc.

I have to disagree here. All of these you mentioned have regularly bugs. Multiple spacecraft got lost because of these. For planes there's not so distant Boeing 737 MAX fiasco (admittedly this was bad software behavior caused by sensor failure). And medical devices, the news about their bugs semi-regularly pop up. So while the software for these might do a bit better than the rest, they certainly are not anywhere close to being bug free.

And same goes for specifications the software is based on. Those aren't bug-free either. And writing software based on flawed specification will inevitably result in flawed software.

That's not to say we should give up on trying to write bug free software. But we currently don't know how to do so.

Unlike the car question, where you can assume the car is at home and so the most probable answer is to drive, with the machines it gets complicated. Since the question doesn't specify if each machine makes one part or if they depend on each other (which is pretty common for parts production). If they are in series and the time to first part is different than time to produce 5 parts, the answer for 100 machines would be the time to produce the first part. Where if each machine is independent and takes 5 minutes to produce single part, the time would be 5 minutes.

I wonder, if these problems aren't Ubuntu fault, since it forces snap version of Firefox on you. I had Firefox crashing repeatedly on me with the snap version. Maybe switching to Firefox apt repo would help? (I tried the repo, but before I had chance to test it properly, I found I could use Debian instead of Ubuntu and reinstalled immediately.)

I wish. If you live in any country that uses more than ASCII, then certainly not since forever. I mean, just for my language there were 7 different encodings (according to Wikipedia, possibly more) before Unicode era. When you want to read these it's solvable problem, but still it is extra work to deal with it. Now that we have UTF-8 as de-facto standard, it is much better, but there are still problems. Like when you use Japanese and it gets displayed as Chinese (same characters are different glyphs depending on language).

I have been working in my spare time on Japanese vocabulary learning app and just yesterday finally convinced myself to publish the sources: https://github.com/d3nzil/gaku

Be warned it's in early stages, difficult to use and code is big ball of mud. But the basic functionality works, so maybe it will be already useful for someone. And I have been using it and working on it consistently, so hopefully it'll only get better.

IrfanView 2 years ago

Windows now have OpenSSH client (and server) available as optional features. Together with the new terminal the ssh client seems to be working fine. Personally I usually opt in to use the ssh in WSL as I keep it installed on all my Windows machines.

Coastline paradox 3 years ago

Of course, if you are using tape to measure your weight, you are using the wrong tool for the job.

The satellite orbited at 320 km. At that altitude the atmosphere drag is non-negligible, so it had to burn fuel to stay there. So the life was limited by how much fuel it had and that is limited by launch vehicle capabilities. If the launch cost get lower, I imagine refueling might become option, but we are not there yet (except for ISS, but that is different case).

Even that is not needed. There is enough people that want open source ChatGPT clone to create the dataset from scratch by themselves. The Open Assistant community actually already created enough training data for the initial model training and the data will be released under open source license. And from what I played with the initial model, it looked promising (though not anywhere close to GPT 3.5 yet).

My usual strategy is to ensure that the lengthy parts are executed only once. So for example one of the lengthy parts is environment setup for me too. So what I did is to put as much as possible on the docker image I build and then I start tests from image mostly ready to run. Of course something similar can be done during runtime. If starting the software you test takes long time, you could set it up only once and run multiple tests without tearing down the setup. Of course this has disadvantage of having possibly tainted environment and there is risk of making the tests depend on previous state. On the other hand this could also help discover problems that are hidden by always running tests on clean slate, so it's a tradeoff. And I have to note that I mostly do integration testing, so the long parts are probably in different places than for unit testing.

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...

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.

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.