I write all of my queries, and I read any existing queries before updating/changing them.
Each time a co-worker tries to use an LLM for a query, it gets something wrong, and I end up having to correct it.
Not sure if a more visual inspection would help.
What I have found to help, is a more hands on inspection. Forcing co-workers to actually run the queries they write, and verify the expected outcome.
Virtual tables, and test tables are cheap and easy, there is very little reason not test what you write(or even test what an LLM writes, if you are that lazy,as most seem to be.)
I care. I use a generated email address at my domain for every account/service/website.
I store the account info in keepass, they all have generated passwords too.
I can see when email comes in who abused the email, was compromised, or sold it.
If an email starts getting spam, i block receiving to that address. if desired, I update the account to have another generated email, but usually if I'm getting spam to that email I don't want to do business with them again.
Cool to see this posted. I've always liked, and now miss PDAs.
The picture marked as NX70V is actually an NR70, which you can tell from the rounded camera, and rounded power button. The NX-70V was square.
The NR70 also lacked the compact flash card slot.
I have an NX-70v, and specifically got it for the CF card slot. The slot was only intended to be used with a wifi card that Sony released, but with an OS patch, you could use regular CF cards, which were much cheaper than Memory sticks. So I bought a third party memory stick Wifi card, and used the CF for storage.
Looks super awesome.
I've been slowly working towards building pretty much the same thing, but haven't had enough time to finish.
I added myself to the wait list. Intend to purchase 3 if I'm able to. Getting everything into such a nice packet is very cool.
The limitation is mostly in the software of the base band modem, which is separate from the OS.
iDEN Direct Talk is the closest thing I'm aware of. It used the FHSS on the 900Mhz ISM band. If you get phones(probably off ebay) that have SIMs that were previously activated, it is still possible to use Direct Talk.
I haven't personally used these since the iDEN network was shutdown, but there are a number of videos on youtube.
I do have some Motorola DTR radios, which use the same FHSS on 900mhz ISM (didn't keys, so they are not compatible) Performance I see is about 1 mile through buildings/tress, but not large hills.
They work extremely well.
This is just radio to radio, there is no relay, so messages/voice isn't forwarded, though this could be done with software.
Which gets back to the modem software. On phones, this is different than the OS, and in most cases very locked down, you aren't allowed to alter the firmware. Cellphone companies specifically don't want non-authorized(locked down) modems on their networks.
Next thing to keep in mind. Cellphones all operate on the license of the Cellphone network operator(Verizon, AT&T, and T-Mobile)* In the US, you are required to have a license for most Radio transmissions. So if you were to somehow modify the modem firmware to work as desired, you wouldn't be operating in the way the license holder wants, and they could send the FCC after you.
In the US there are a few bands that are open to use without a license(though there are restrictions.) CB(No data/encryption), FRS(No data/encryption), and ISM( 900mhz, 2.4Ghz, and 5.8Ghz), and CBRS(requires you to register, and check a Database controlled by google before you can actually transmit).
2.4ghz and 5.8ghz are used by Wifi. 900mhz is used by the Motorola DTR, LoRa, and a few other things, less common, but usage has been picking up a lot recently thanks to LoRa. Of these, the 900Mhz.
CBRS(3.5ghz) was extremely promising, but thanks to the lobbying of the Cellphone networks, including google, you can't just use it, there is a complicated process and spec you have to abide by in order to do so, which is out of the reach of most citizens, despite that being the original intent of the band being opened up.
* As mentioned above, cellphones operate on the frequencies that the cellphone networks have paid for, the exception to this is CBRS. A lot of newer phones have support for CBRS because the carriers themselves intend to take advantage of this frequency.
CBRS is probably the easiest to move forward with using existing cellphones. The downside, would be the requirement of checking the google DB, and getting the permission to transmit before doing so, which complicates the whole p2p, and off major network problem. There is base station hardware available, though I don't if you could install custom software on it. Most of it is from the Helium crypto/cellphone network.
I also want to comment on this: "They are stronger, in terms of bandwidth and throughput." In most cases the cellphone radios are not any more powerful than Wifi, or BT. The main difference is the frequency(Simplified: lower frequencies reach further with the same power), and that the Cellphones communicate with raised towers. Most radio communication is line of sight, or close to line of sight(though there are exceptions such as bouncing off the atmosphere.) With the DTR radios I mentioned above, I have reached 4 miles(the longest line of sight I could get in my area). They are 1 watt. Most phones are limited to 1 watt.
I use Watts when talking about power, but the FCC regulates transmit power based on effective isotropic radiated power (EIRP), which is a combination of the antenna and power you use. so sometimes the transmit power will be higher or lower, depending on the antenna used. Most wifi usage falls within the same range as cellphones.
For p2p stuff, I could encourage you to looking into LoRa devices. Meshtastic [https://meshtastic.org/docs/introduction/] is the software most are using. It is great for text messaging, but doesn't support voice(yet)
This was a long comment, hopefully it was useful, if you have additional questions I can try to answer if I know, feel free to reach out.
Right now i'm using what was manjaro, but has become more Arch after all the changes I've made. It was installed 4 years ago. I've been looking at getting a Freebsd install setup for laptop use, but haven't gotten it working enough to make the switch.
There is the Unihertz Titan Slim.
The keyboard layout is a bit different, and the specs aren't that great compared to current gen phones.
I am typing this on a Blackberry Key2le.
Not new, or on the market anymore, but it still works well.
"To anyone who claims they can land a plane without experience, in an imaginary or real scenario, Venhuizen issued this challenge: “They should go give it a shot some time in a simulator.”"
https://github.com/nhn/tui.editor Might be close to what you are after.
The only thing I don't think it does is the @mentions, but there is probably a way to address that.
This month I have programmed in the following languages:
D, ECMAscript, python, php, bash, c/c++, Java, powershell, and groovy.
There are other langues I use. as for how? Most of what to do in each language is the same, the Languages just change how you go about doing it. Most of the difference is the keywords and syntax. the tasks you are writing out are the same or similar, with some features of languages making certain parts easier.
- The First had the Rom chip and ram removed from it and has a bit of wear.(by a goodwill that likes to strip computers)
- The second is in near mint condition, as if it has never been used. It works without issue. I had to find a power supply for it, since neither came with one.
I have been contemplating replacing the guts on the one missing the rom chip, since I have no idea where to find one of those. It should be able to fit a raspberry PI inside, alone with a much higher quality screen, but I don't really feel like figuring out the keyboard/trackpoint connections/software.
Each time a co-worker tries to use an LLM for a query, it gets something wrong, and I end up having to correct it. Not sure if a more visual inspection would help. What I have found to help, is a more hands on inspection. Forcing co-workers to actually run the queries they write, and verify the expected outcome. Virtual tables, and test tables are cheap and easy, there is very little reason not test what you write(or even test what an LLM writes, if you are that lazy,as most seem to be.)