This is a prepost of a reddit self.learnprogramming post.
There are a lot of conversations going on about the future of digital literacy, and some people think everyone will be a programmer at some point however soon, or else live in abject poverty.
I tend to agree that the basics of loops, arrays, etc are good for most people to have a handle on, but some people dive in with the idea that they're going to be an amateur application developer in a month, and I think this is bad. An amateur application developer is a full time application developer. You can't be in this field and not give tremendous time to reading docs and fixing bugs, and if you don't have the time, IMO it's a dead end.
But Bash, even with all its flaws, gives a lot of reward with just a little effort. As I have learned Bash over the last several years, I started out writing scripts that just looked like what one would type at the shell (and hey, they worked!), and gradually learned how to make them more stable by checking error codes and setting options etc. For a long time I didn't even know Bash had arrays. I think Bash is the best language to learn with just a bit of time here and there. And you have curl for rest apis, SQLite when you need more structure, jq for managing json, xmllint for xml, each with a manual.
The biggest point is that Bash is designed for managing the computer you're on. It's personal, and a newb can do things that are meaningful and useful pretty fast, use those tools they built daily, and build on them incrementally. You don't need Git, an IDE, a web framework, etc etc. It's all preinstalled on your mac.
Personally I'm a Java programmer who won't touch MySQL when PostgreSQL is in the picture, and with PostgreSQL I don't see much point in using SQLite, and I'm writing this post on a Fedora 20 install. But I recognize I am a number of standard deviations removed from the middle of whatever bell curve, and I think a lot of advocates of digital literacy make the mistake of saying to someone with budding interest, "Do what I do, it's great!" while somehow forgetting how many hours of sleep they've lost obsessing over stack traces.
I also think using the shell a bit on a regular basis gives one appreciation for the Unix philosophy: a thing modern web development deviates from in big ways. I hope future generations reverse this trend, so that's another motive of mine.
So if you have budding interest, open up your terminal and type 'man apropos', and if you're an advocate, consider your audience.
This is a prepost of an attempt to reach out to the librarians subreddit for a discussion about applications for BaseParadigm.
Everyone knows libraries have been having increasing trouble since Google took over most indexing tasks. Why is it that the web hasn't created equivalent roles for librarians in online contexts as they already have in physical libraries? Is Google so good that librarians aren't necessary? (I don't think so, or I wouldn't be posting.)
I want to see better curation of information online, not just pinterest boards and tumblr blogs. I want a question and answer framework that can't be dominated by a corporate entity (like yahoo/quora/stackexchange). I want everything to be easy to archive and file (not 'share' through other services, and not 'export' to the file system). I'm building what I hope to address systemic issues like this.
I know that I want to serve the community of librarians. I understand you to be a crowd for whom openness and democratized participation are important. I think you want to curate information spanning domains and apps and free free information from the framework with which it was published without cutting ties to its context and author.
I'm here to find out what pains you most. What you long for. What you need to make your best impact. I can promise you that I'm writing free software, and there isn't a greedy startup behind my plea for input (though I can't guarantee anything about who else is on reddit, of course).