I would strongly recommend building up a portfolio of cool side projects and making them publicly available on github. I think more and more tech interviewers are starting to look at candidates' github accounts and taking it seriously. Even better if you can host your side projects somewhere so they can easily check it out.

Counting cards in poker? Say what? The deck is shuffled between every hand.

Unless you're referring to the basic skill of determining odds to make a certain hand based on your hole cards and the common cards?

That's true for hold'em, but in stud variants you need to keep track of the cards held or folded by other players.

But that's a very different skill from counting cards.

It's the same idea: predict future draws based on used cards.

In one you have you remember the attributes of the cards in the other you just have to maintain a running total. They are very different skills.

For a product like this, the extra weight is a good thing.

For a product like this, so is the extra cost.

I dunno, the classic Sound On Sound "synth secrets" covers all this and more, in a lot more detail IMO

http://www.soundonsound.com/sos/allsynthsecrets.htm

Yeah, a lot of this information is pretty low-value relative to the Sound On Sound stuff. What good is it to know the difference in how a square wave and triangle wave look, if you don't understand how they sound different and why you might prefer one to the other? The "synth secrets" series is much more technical and showing its age, but it's comprehensive.

It also helps to have a real or soft synth in front of you so you can tweak knobs and play around as you go If you don't have anything, my recommendation is ZynAddSubFX. It is an amazing free synth with enough knobs to do almost anything

Another (much more expensive) "standard" reference for synthesis algorithms is Curtis Roads' "The Computer Music Tutorial" http://www.amazon.com/Computer-Music-Tutorial-Technology/dp/...

This is THE STANDARD

Almost 6 years old and still referenced everyday. Amazing documents. I would love to see more added to it.

Nit: The first articles in the series came out in 1999, so more like 17 years old :)

Thank you for the link! :) I've recently gotten a MIDI controller to finally take some first steps into electronic music (I'm used to playing "regualr" keyboard) and this is what I was looking for!

Yep, it's closed source. I dream of a day where they open-source it, but IIRC the creator has turned down various monetary offers so as to retain complete control of the game, so it seems unlikely that he'd ever release the code.

Interesting read, thanks for posting this. I was flabbergasted to see that he had only been diving for 4 years when he made the attempt.

Two points in this article really rang true to me in particular:

- the tendency for divers to speed through increasingly more advanced dive certifications. Often I'll be at the dive shop waiting on a tank fill, and I'll overhear somebody talking about how they had such a fun time during their beginner open water certification that they signed right up for advanced and divemaster courses. There's nothing wrong with educating oneself, but I think the false sense of mastery instilled by these courses is clearly a potential danger. The material learned in the class must be complemented by real-world experience for the concepts to become second-nature. The dive shops make money on this mindset too and so share lots of the guilt.

- going deep for the sake of going deep. There's always that one guy (it's always a guy in my experience) whose goal is to get deeper than everybody else on the boat. As far as I can tell, it's pure machismo. Not only does it lead to accidents like this, but you have less bottom time, worse visibility due to lower light, and in most places the richest animal life is not at the deepest part of the dive. So it's stupid. This article seems like that mindset taken to the extreme.

I don't want to speak callously of the dead, but this guy appears to have had it coming. And I think the dive shop that sponsored him should bear a big chunk of the responsibility for this accident, as outlined in the article.

This is a good step in the right direction, but this piece is still incredibly insensitive. Using words at all is literacy privilege. The author really needs to start thinking about people who either can't speak, or have lost the ability to speak. Not to mention the fact that there are millions of infants and mentally disabled people on this planet who can't even read, let alone speak. Sorry if I have offended you with this harsh response, but I'm still feeling extremely triggered by the brash insensitivity on display in this post.

I had never thought of this before, but now that my eyes have been opened and I have spent a good fifteen minutes absorbing my new reality, I shall go forth to lecture the great unwashed masses about what bigoted jerks they are.

do you mind articulating what you think is actually wrong with the post?

I really want to want one of these but I have no idea what I'd use it for, and not enough space in my euro rack to risk on it.

I'm so glad that we live in a universe where this exists, though.

It is still worth watching. It's about the journey, not just the destination.

Life before death, strength before weakness, journey before destination.

It's been said before, but in the opinion of many would-be DF players, it's really the interface that could use a massive amount of love. The ascii graphics may not be your cup of tea, but at least they would be functional if, IF the interface/controls/menu systems weren't all so horrible and obfuscated and totally inconsistent with each other. I've come to the conclusion that the developers get some sort of sick joy out of putting this incredible, tantalizing core out there but making it completely inaccessible to the average player. Maybe that's their strategy to weed out non-diehards until "it's ready".

All software is of the highest craftdwarfship.