Fossil's also very easy to put online, needing at a minimum a two-line bash file to function as a CGI script.
Maybe more relevant to private data, the builtin wiki makes a good personal knowledge database.
The next version of fossil will have a forum (seen already at https://fossil-scm.org/forum/forum ). With the time sorting for threads, that might be good for temporal data that you wouldn't want to put in a wiki.
oh wow, power is very fluid. it's easy to break into power anywhere now. You don't have these awful elites preventing you from doing whatever you want to do.
1. a request to return org-mode data (or for requests to contain it in a mechanically distinguishable manner, an option if your normal output is org-mode plus some JavaScript that renders the page from org-mode)
2. some Emacs code to populate a buffer with org-mode data extracted from an HTTP request
That's it. Neither of those are technically difficult. Although there's lots of room for improvement, and that's where people might start to get interested. For example, you could develop org-mode as an alternative to Jupyter notebooks.
> 3. Not speaking Swahili. If your boss is from Swaziland, then you need to know everything there is about Tanzania or Kenya.
Ha ha, pretty good. They snuck a serious-sounding joke item into an otherwise good list.
> 14. Writing an open letter to your boss.
Needs to go on a separate list, titled something like "Fun Ways to Quit Your Job"
> BONUS: Being a jackass outside of the work place.
Needs to go on a separate list, titled "The author of a list tells you how he vindictively sabotaged someone's career for expressing mild annoyance in a way the author did not care for."
Replace it, on this list, with "having a social media account".
Yeah, there's no amount of bigoted "Haskell uber alles" posturing that can replace a simple, supported argument. None of the reading you think you've done, and I haven't, has succeeded in distinguishing your output from that of a complete poser.
1. avoid metrics. Ask during the interview how they gauge your work performance, how people get bonuses, etc. As a rule you'd much rather be judged by a person, your direct manager, than by an Excel sheet. Yes, hostile managers can be a source of stress, but they'll be that in any case. Metrics are simply an additional potential source of stress.
2. avoid having to deal with backups. Think of all the warnings about test coverage. Or about advocacy for compile-time checks, and for more thorough checks, for information in the editor as you're coding. Backup systems are all about finding out that shit's broke after it's too late and when you most urgently need it. They are an incarnation of stress. And if you do it well, nobody will ever even know. It's not "heads - bonus, tails - no bonus", but "heads - you can come into work tomorrow for the same pay, tails - you can't".
^ everybody remember this line for when it's given in response to an angry Congressman.
I imagine another line will be "it's marginally better than statistical human shooting, according to three studies!"
And then in the 'big house' people will refer to you as "Butterstats" or something. Because you were screaming "marginally better" the first night they left you in your cell.
> I don’t want you to have to sign up to Wordpress just to leave comments and communicate with me.
Then don't restrict your comments like that. WordPress pages don't gather 8000+ spam links because it's only capable of accepting wordpress users' comments.
WordPress is flexible enough and rich enough in plugins and themes that I wouldn't it an alternative to "building my own website", but rather as one technology you can use to do that.
> Let's say a technology could be developed that allowed your government (wherever you are) to kill any person with almost zero cost and no chance of detection.
oh yeah, I remember that Hitman mission.
"Would it be morally justified for an assassin to kill me?" is a good question to add to the project-acceptance checklist.
It's really not, as people by themselves don't pose much of a military threat. What you really want to do is break all the stuff that lets those people actually threaten you.
Granted, much of that stuff is arranged in the form of compounds that contain people, or is stored on such compounds.
There are a few steps to "deciding who is innocent", but the big steps are Step 1: the President decides that the military can start making spot decisions like "that guy just shot me" within a specific set of circumstances. Step 2: "that guy just shot me! I'm shooting back!"
Better military technology improves step #2. It also improves subtler cases like "can I shoot this guy" / "does he have a weapon?" / "yes he totally does [false]" / "ok shoot him" -- by allowing the supervisor in this case to confirm what he's being told, before he gives the go-ahead.
But step #1 is the biggie. As soon as the President says that the military can go to a place and kill people, it gets very dangerous for the people there. Apart from turning the entire planet into a panopticon, I don't think technology can change this much.
If you put the most valuable thing in the universe inside a box that can't be opened or permeated by any force in the universe--then that thing is no longer valuable. Go find the former #2. If you have a programming ideal and that ideal requires laziness--then you've messed up. You have to conclude that there was something flawed about the ideal.
I'm a lot more confident about laziness being bad than about what you're thinking of as "a pure immutable language" being bad, but part of the problem about laziness is that it's a feature apart from the language it's in. If you implement a cache with a hash table in any normal language, then you can later on check and see how much data you have cached, keep track of your cache hit rate, empty the cache, pre-load your cache from a previous run, and so on. To work with your cache, you have the language itself at your disposal. If you implement a cache with a lazy list in language X, then language X can't help you. You'll need to hope that whatever Gods dangled laziness before you, also have some tools dangled elsewhere.
1. child porn
2. steganography
if I were the dev I'd add a 'list all' just to avoid anyone thinking the above were a good plan.