a_lieb
Joined 10 years ago
Joined 10 years ago
The stats on the CIRR site across schools did always seem a little... odd to me, with differences in outcomes too big to believe at times. Sounds like I would have found the same thing if I looked at any individual school over time, as the rules and practices changed.
I think you're talking about either the Council on Integrity in Results Reporting (CIRR) [1], or Course Report [2] (both still up). CIRR is a body run by the code school industry itself to monitor its own results; Course Report has over 50k reviews by students as well as articles with tips about how to pick a code school, "top x code schools for y" lists, etc.
CIRR seems to be reasonably rigorous and honest. Their reports are easily available on the site. I've poked around in their reports, and there's a huge range of results, from less than 50% employment at 6 months to 80%+. There seems to be little to no correlation between the reputation of a given school and the actual outcomes (some of the most reputable schools had employment rates of 50%-60% at 6 months).
A big trend I noticed was that the schools with the highest employment rates were relatively low-profile schools teaching unsexy technologies that are low in SV buzz but nonetheless have high demand, like Java and C#.
If you're the head of a successful OSS project and you believe it's helping your career in the way of industry notoriety, good demo work to show potential employers, etc.—then give a cut to cover the project's expenses, or even hire folks for freelance work.
There might be stretches when you're not going to make any extra money from the project; say you've reached the point where the project isn't a top line-item in your resume and is probably not responsible for your next salary bump. You can still honor what you've gotten from the project by voluntarily investing back a portion of the money. It has a "benefit corporation" flavor.
If this sounds like too much generosity to expect of people, consider people like Thibault. He's very, very deep into the "generous" side, in that pretty clearly he could work on the project _far_ less and still get a dream job. What I'm describing is a way to make an overall profit and still feel like you're giving back to the world by nurturing the project you've built.
Obviously, this is an overwhelmingly common thing in practice already, whether it's someone who made an OSS project to get a good job and then continued to work in their spare time to maintain it, or language BDFLs who maintain the project on a volunteer basis, but as a result of founding the language they have amazing and well-paying day jobs. But so far I've never seen it described as an actual business model, where you can feel great about helping to keep up your project, but still come out ahead overall.
There have been many attempts at a chromatic music notation, but nothing has caught on so far [1].
Things are a little better with solfege -- there is "chromatic fixed do" solfege, where every note has its own name, rather than only having a name for the "white notes," which leaves you to mentally calculate the sharps and flats.
It's a minority thing--maybe 5-10% in Europe? Even regular fixed "do" is rare in English-speaking countries, so I would assume the chromatic fixed "do" is almost unheard of in the US, Britain, etc.
At any rate, there're are at least seeds of hope for a chromatic fixed-do solfege to catch on more. I use it for my own learning.
It turns out that when you make a language like that, you end up something where your code looks and feels like a list of commands (much like a shell script) but is also capable of doing "real" programming stuff where needed without much pain.
The test suite for SQLite is (still!) written in Tcl, I think partly for this reason. You probably wouldn't want to write a test suite in bash, but you don't quite get that feeling of "it's just a list of commands."
Nice easter egg from the source code:
<!-- <audio autoplay="autoplay" controls="controls"><source src="topgun.mid" type="audio/mpeg"></audio> -->
[1] http://www.alexliebowitz.com/ [2] https://www.vikingcodeschool.com/ [3] https://www.thinkful.com/