HN user

gte910h

5,630 karma
Posts12
Comments3,298
View on HN

Supervised release often lets you move AFTER you find a job from what I understand via a friend who had an unfortunate intersection with the law as well.

I'd imagine federal probation is related to that program and has similar standards?

A petition to move to a larger job market (SF, Atl, or Austin) might start a discussion which opens other options to you.

1> Do you have a "Real" CS degree?

If not, doing a good portion of the exercises in some books on [compilers](http://www.amazon.com/Compilers-Principles-Techniques-Tools-...), [DFAs/State Machines](http://www.amazon.com/Introduction-Theory-Computation-Michae...), Algorithms (http://www.amazon.com/Introduction-Algorithms-Thomas-H-Corme...) and theoretical programming (https://mitpress.mit.edu/sicp/full-text/book/book.html) can give you some common foundational lenses with which to see these articles

2> Learning the history of your field

Nothing informs the current state of the field more than how we got here! Learn the foundation of your field from people who lived it. The podcast [Debug](http://www.imore.com/debug) is Guy English (Creator of Napkin and other apps) along with Rene Ritchie interviewing people about the history of Cocoa and CocoaTouch

I found [this episode about AutoLayout and Key Ferry illuminating](http://www.imore.com/debug-33-ken-ferry-auto-layout-passbook...).

3> Go through early versions. Few systems START complex. Look at OLD books for EARLY versions of systems, and why old php made such silly choices is obvious (hint, they weren't that silly for what it was doing). Read books and commentary through the timeline. Understand the history of what's happening to the language, then you'll understand why you are where you are.

4> Go DOWN the stack. Understand the bottom of Objective C by reading [the open source implementation of Core Foundation and more](http://www.gnustep.org/). Also available elsewhere (and I think somewhere on Apple's Site still).

5> Do what you shouldn't! Don't ship it, but really use those implementation details to do something awesome and amazing. You'll learn tons about what's happening.

PS: To the mods, those aren't affiliate links

Right now you only have the choice of a transaction with chargeback guarentees and other credit card niceities.

With something like bitcoin as an option, you have the option to drop that fraud overage charge, when you aren't worried about the other party (like in a repeated business scenario, such as amazon, or for a tiny purchase, or other things of that nature).

Harassment laws should be enforced on twitter as much as anywhere else.

"Generally, criminal harassment entails intentionally targeting someone else with behavior that is meant to alarm, annoy, torment or terrorize them. Not all petty annoyances constitute harassment. Instead, most state laws require that the behavior cause a credible threat to the person's safety or their family's safety. - See more at: http://criminal.findlaw.com/criminal-charges/harassment.html...

"I'm going to rape/kill/etc you" should probably end up with you in front of a prosecutor in many states.

Swift is not 12 years ago

These appear to be in line with unoptimized swift. mpweiher, can we have some gists of the proj or something for these numbers?

u. No, deleting your emails programatically because you haven't got around to reading them is not a good idea

Archiving them is. You can't have more attention than you have. If people try to get more attention then you can give, you have to triage. Backloads of email are huge piles of stress, and you realistically will almost never get to them

Once you've done the emails you've chosen to handle, use a mail client with some form reply to process some things which that's amenable to handling, and archive that which isn't important beyond that.

You should ALSO work directly to stop getting CCed on so many things and to communicate with fewer exchanges on more important topics. Get co-workers to not bury the lede, and to get items which need your decision or action to very prominently feature that in the title and first line of the message.

Google didn't bring Clojure to Android, some 3rd party did, and slowly. Scala appear to have the same story I think? (Large startup lag?)

If you want functional on Android, I'm betting F# is the premiere method today performant enough to write real apps in.

Cocoa, the API behind iOS and Mac Objective-C, is the hardest part, and is still there.

I suggest going through some detailed tutorials on building an X, so you get the feel for how views, view controllers, objects and everything all interact.

The new playgrounds look EXCELLENT for doing that! Best of luck

I suggest http://www.raywenderlich.com/ and his fantastic books with examples. While I actually think I've been doing Objective-C longer than most of his writers, when there is some area I haven't worked in yet they usually have a high quality, simple to follow example on how do do a thing that's a great jumping off point to getting going and then understanding further once you get the main thing in front of you.

Every single AAA studio uses C++ to write the smallest portion of their game they can in C++.

Then they put a sane, modern language on top of it many places, Actionscript at EA, Python at many other places, LUA at others, C# at others, and write in a high level language that doesn't leak abstractions like a nut milk bag.

Objective C is head and shoulders better to program in than C++.

It's still got the same C warts that C++ does in a lot of place, but it is far simpler and less leaky than C++.

C++ is still faster and more cross platform, than objective-c

  --Have done both professionally

I'd say "Bring Scala to Android" would be more comparable? Bring Clojure and I'd say you're stealing a lot of developers away who think Swift is a half measure.

Could you go over the good solutions then? I have always heard there are about 4-5 "good but complicated" systems, none of which are easily shown to be best due to strategic voting and haven't seen clear "we should do this one because it beats all those for sure" type recommendations.

Sci-Fi is commentary on the present, or the near future.

Even Star Trek (TOS was 60's era Apollo optimisim, ST:TNG was 1980's "Communism is falling"/We're getting okay with Russia/The Economy is booming/Roddenberry said so!)

The reason why today's SciFi isn't hopeful is that there are lots of very easy to see bad ways today turns into tomorrow, and not very easy to see good ways.

I honestly think self driving cars will make life crazy better for instance. But there isn't Sci-Fi to write about that is interesting enough to publish or make a show about with that premise. Or for 3d printing. etc

Friend of mine had to get gammaglobulin shots for a few years (8 or so years ago): The stuff supposedly cost about 10k a vial, because it was filtered out of the plasma of many of people per vial and put through several complicated processes to isolate and sterilize it.

So...if we had considerably larger plasma donations, maybe?

I lack 'deep', real knowledge and am desperate to acquire this mythical stuff before it's too late.

I mean, there are books on this stuff? Read them, do their exercises, and you will be fine.

I will say, most of this stuff now functions mostly as mind training. The specifics about low level computer systems, Big (O), parsing and compilers is the only part I see repeated use in my day to day.

So knowing this, how would I best use say 8-12 hours a day, every day, to learn this stuff?

You should audit courses at a CS program taught near you. This stuff is chunky and the books are designed mostly for a classroom setting