292 karma · joined April 17, 2014
It was so bizarre it took me a while to decide if they were insane or just incredibly rude. Upon reflection, they were both.
The first type of excommunication you're talking about is the automatic kind. If you commit grave (not venial) sins and haven't been to confession yet, you cannot receive Communion without committing a sacrilege. No formal decree from the bishop is necessary for this. In fact, no one even needs to know you committed a sin, for you to be in this state.
A formal excommunication is a public announcement intended to shame a sinner into amending his life and re-entering a state of grace by repentance and confession. I believe in some cases it requires a public act by the sinner, to let the community know that the public charge of excommunication has been answered. So, to contradict your position, a public excommunication is not a shunning but rather is meant to bring the sinner back into the community.
It might be a useful practice for the Church to do more of...
In your case, maybe you learn computer science and you apply it to some problem in art or the humanities.
Part of the reason I think this area is hot is that it's harder to do than apps. Every "app" I can think of has already been done, and in fact there's probably a dozen versions of it languishing in app stores. Manufacturing is harder, and is often geographically local, so there are fewer competitors and more niches.
Another leading indicator for me is the general rebellion of young people against the fact that "shop class" has been taken out of schools. Lots of kids are trying to find ways to be "makers". In my state, when I was in school the "dummies" were pushed toward taking vocational classes in plumbing, welding, etc. Now (20+ years later) the vocational classes are the most competitive, prestigious classes that students fight to get admitted to.
If I had to guess, the new manufacturing is going to be smaller scale, extremely high quality, locally sourced materials, with some kind of digital "twist" on the business models.
So it's certainly feasible for an advanced race to build a star empire; the question is why they'd want to do it. If we're talking about humans you might say ambition or imagination. If Vulcans, maybe they'd think it logical to pre-emptively become stronger than any potential aggressors.
The big surprise line is that there's no one on earth who knows how to make a pencil. (It therefore serves as testimony in favor of free enterprise and against the idea of a centrally planned economy.)
Something more recent: Martin Fowler's great introduction to NoSQL: https://youtu.be/qI_g07C_Q5I Not so technical, this is a great overview of the reasons why (and when) NoSQL is valuable. He crams a lot into a short speech, so it's one of the rare videos I've required students in my database classes to watch.
Now, really getting away from the technical, I have to recommend watching the IDEO shopping cart video: https://youtu.be/taJOV-YCieI This is the classic introduction of Design Thinking to the world, in 1999. If you're using the Lean Startup or an Agile method, but have never heard of IDEO's shopping cart, you may be able to get along fine at work, but you should be kind of embarrassed like a physicist who's never read Newton.
The big idea of the book is that Einstein isn't wrong about C being the speed limit. Therefore, to be a starfaring race requires the ability to make commitments and hold to them over extremely long timespans. The connection to game theory is that, as in the Prisoner's Dilemma, the only way you can really make predictably right decisions in cooperation with other entities is if your decision-making formulas are spelled out mathematically in advance; so all can predict how you will act. The first book begins with mankind discovering the galaxy's "rules" on a kind of signpost at a nearby star.
Read the books!
I don't think there's ever going to be a point when a race has "enough" and doesn't want to explore or build any more. Our ambition should grow with our capabilities. Once you can control a star, why not work on a galaxy?
Where it becomes extremely impactful is when a database is distributed or sharded across a cluster. If the various tables (article, author, comment) are stored on different servers, it takes time for the database to reassemble them. Moreover, modern web apps often have content that's written once, read many times: blog posts, photo posts, status messages, news articles, advertisements, catalog listings, etc. Why re-do that work of assembling the content every time people want to look at it? When documents are rarely or never edited, the relational model's defenses against "anomalies" become less relevant. Far better to use a document store like MongoDB, which stores a piece of content as an integrated whole at a single place in the database.
In teaching programming, I've found that often the hardest thing to learn is how to break down problems logically, not how to write code. For example, if I assign students to write a function that takes an average (mean) of a series of numbers, very few will fail because of syntax errors. Many more will fail because they've never thought about how to take an average!
Therefore, my latest thinking is that the first few programming lessons should be about basic mathematical problem solving. How to compute an average. How to estimate a square root. That sort of thing in a "math" class is assumed given. To a mathematician, the square root of two is "the square root of two" and no computation is necessary. I want to convey to my students that computers have to be taught a process, not an answer.
I'll find out next semester if that's a better approach. I hope you find it helpful or at least interesting.
Compare this to an RDBMS-based web app, where to display a blog article for example you'd need to make multiple queries of different tables: first the "article" table to get the text, then the "author" table, then all the comments, tags, images, or whatever. The NoSQL way is much easier to code for this sort of thing. The lack of ACID doesn't matter so much because these kinds of data are usually written just once, read many times, edited rarely, so there are few opportunities for inconsistencies to creep in.
On the other hand if a human is reading your resume, creativity may be a plus. So that might apply to small businesses, start-ups, etc.
When considering a PhD, the best thing to do is look at the advisor(s) you'd be working for and their repertoire of projects. Looking at the "discipline" isn't precise enough; there's a wide range of stuff happening within fields like information systems or computer science, everything from very theoretical to very practical.
You're just going to have to "grin and bear it" for 3-4 years before people will start listening to what you think. In the mean time, focus on showing up every day on time, wearing a clean shirt, using your manners, and learning to do whatever they're asking you to do, really well. Those things will distinguish you from the other fresh graduates more than you'd think.
Heroku gives you a PostgreSQL database with one click, but you could easily integrate a MongoDB database if you wanted to try NoSQL. In Mongo, you'd actually store and retrieve your data in JSON, so it's even easier than writing SQL.