Recent submissions

Comment · 12 years ago
This feels like a way to export money from China.
Comment · 12 years ago
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.

Comment · 12 years ago
I want to use Xamarin like http://www.remobjects.com/elements/hydrogene/ remobjects c# works.

(Well, I guess I'd prefer to use it in F# too).

How well does it work to ignore the .Net parts and just use the nice IDE/Packaging/Not java story?

Comment · 12 years ago
Comment · 12 years ago
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

Comment · 12 years ago
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).

Comment · 12 years ago
Comment · 12 years ago
Comment · 12 years ago
Yes, the types.

Strong types are far easier to optimize.

Comment · 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?
Comment · 12 years ago
>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.

Comment · 12 years ago
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.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton