I use nano all the time for production linux services. Its simple, effective and works really well in a shell session over a satlink connection. The key combinations make it a lot easier to not f*k up in those kinds of sessions.
The mobile operator 3 have upped their prices on pay as you go. They had a "123" PAYG plan that was 1p/MB 2p/Text and 3p/Min. They now are changing it on Feb 16th to 5p/MB 10p/Text 10p/min. They claim "Some of our international roaming rates are also increasing. This is to keep them in line with domestic standard rates and not a result of brexit"
I guess you're from the US? In the UK that picture alone would hardly be an issue, in the context of an article it would get no more than a glance from co-workers.
I think Bill is answering in such a way to be politically neutral. Other questions he has in his post here read as if they are politically biased and well to be honest, in this global pandemic there shouldn't really be any political tension.
Most of the software I have written for work has no near on no functional / unit tests. It is industrial process monitoring software that runs 247 on remote machines thousands of miles away. Simple fact is it has to work, no if's but's, even when there are faults in its environment.
This does not mean to say that the software has not been tested.
Testing is subjective to a softwares use. You could have 10000 tests and still have a series of bugs.
Testing for my work comes as two categories, "Tested by design" and "Environmental Testing". "Tested by design" involves developing your software by which the designing and writing the software inherits the tests as you go. When I go about designing a feature, I expand on a chosen solution of that feature and then methodically branch out on the uses of that feature, build a map of dependancies, scenarios, outcomes, consequences etc for that feature. These become the basis of how I write the code for that feature because I have inherantly put in mitigations for everything I have considered before hand. There is no point in testing something excessively if you can and/or have garanteed by code that it will perform exactly as designed. That may seam a contraversial thing to say.
With "Environmental Testing" we simulate the environment which the software is put into with real external factors. This is particular for the software I write. This is not always the best for another software project.
I've written my works software from scratch 3 years ago and it has had various incremental additions and changes. Yes there have been bugs. I will admit that entirely. However the key thing with work's software is that is has rarely crashed or rarely faulted while containing those bugs. Most faults that have been found have been configuration errors/issues.
I would be interested in how others approach testing strategies for the software they have written.
It may be the size on the page, or glyph rendering artefact but this font doesnt look... consistent. Dont get me wrong the font is brilliant, however atleast for me there are some points at which the rendered glyphs are over cut. Another way id describe this is the antialiasing is not consistent. Its like layering the same text on top of the other multiple times.
Every time I look at fork lightning of any kind, it keeps reminding me of natures version of a depth first search algorithm. If you ever watch a high speed capture of a fork lightning youll see it spray out and as soon as it gets a link to ground, the energy backtracks up that path.
