But there is no "privacy policy" on the Samsung keyboard about page.
The Samsungs privacy policy on the web states this:
Samsung Keyboard information: The words that you type when you enable “Predictive text”. This feature may be offered in connection with your Samsung account to synchronise the data for use on your other Samsung mobile devices. You can clear the data by going to the “Predictive text” settings.
I wouldn't doubt if it's changed a few times. The phone was a 2016 Galaxy J3 V. I no longer remember the name of the 3rd party they were using for predictive text at the time, but I know that in the past they've used SwiftKey and Grammarly
I would recommend Crunch's webapp accountancy software (which I used a lot) but also hire someone to handle it for you (which I did not and wish I did).
Have you tried any indirect hunting tactics? Going to a tech meet-up and seeing who's hiring? Talking to people in the sector can also put your mind at ease when you relate to people with similar problems.
Might also be worth looking at University job boards if there's any Uni's in your town. I worked an academia job part time because it was all I could find, but I learned a lot and the work felt great compared to most office jobs. Might be a good stop gap for you, as they tend to be fixed term contracts I think.
I'm a developer of 10 years, and use the command line for Git, Brew and a few other things, though I'm normally an IDE developer. I believe the CL is as powerful as everyone says, but what are some useful things I can use it for? I use Zsh on a Mac some of the time.
- CLI encourages automation (shell commands are easier to repeat/parametrize then GUI steps)
- shell instructions are more git friendly than screenshots (even if a process can't/shouldn't be automated. Commands are easier to document in a reusable/updatable way)
- CLI can be used to run tests in a way similar how CI does it (more reproducible)
Command line tools are easier to extend/combine with existing pipelines (rg,jq,xargs): read input from stdin/write output to stdout, report on stderr, return non-zero code on error. It enables you to create adhoc tools that you wouldn't bother otherwise (unrelated: LLMs also have this property by making your skill set much broader (though very shallow with current LLMs)).
Shell also has Forth-like property (compose with: retry, timeout, setuid, exec, xargs, env, ssh, etc) https://www.oilshell.org/blog/2017/01/13.html
Rename hundreds of files at a time. Find stupid errors in GB sized csv/json/.. data files. Automate git bisect. Automate workflows by writing a short loop or 3 commands in a row you can easily repeat. Down/upload big datasets. Convert text files any way you can think of.
For #2 once you’ve got a command you like, maybe one that generates a metric, you can now re-run it with ease from your history, saved text file, or an alias. You could also share it with teammates.
Please correct me if there are other ways to achieve the above, shell is the only way I know
Colorful prompt with context information, powerline glyphs, autocomplete, command highlighting, easy navigation through strings, plugins and a plugin ecosystem that extends your shell like crazy
I strive to speak multiple languages, but I think it still worthwhile to be really good at my primary language of English.
Same with computers and servers. I interact with a lot of them, but my primary computer that I use >80% of the time is worthwhile to optimize with some tooling that's not available on all the others.
Some folks grew up on systems that could fail at any time and leave them with nothing but the tools in /sbin to fix it with. No /usr, no bash/zsh, just sh and vi if you were lucky. You learn to love the cool new things, but you still have a mental bag packed with fsck and ed in case you need to bug out.
It's silly, really because no systems are like that any more, but the things you learned at 2am when you were 22 tend to stick with you.
As we're in a zsh story, I'll point out it comes with a clever file renaming interface out of the box¹. It allows full access to all the advanced glob operators zsh provides too².
On the second one - if that’s in code than a good IDE will not only do it with a single keypress, but will also (optionally) do it intelligently eg change only in the code, not the comments, show you a browseable preview, and offer undo should you get it wrong.
I like the shell but I also think IDEs are underrated.
You bet wrong, because naturally approaching 50y, I have my tools for quite some time, for the stuff I care about, not random examples on the Internet.
A UNIX shell is a very bad approximation of a real programming language REPL.
It is no accident that sh scripts turn into Perl, Python, Tcl, Lisp,... when one wants to keep sanity.
