gte910h
Joined 17 years ago
Joined 17 years ago
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.
(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?
You've escaped the Dunning Kruger effect for now: http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
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
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).
"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.
Strong types are far easier to optimize.
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.
If you want functional on Android, I'm betting F# is the premiere method today performant enough to write real apps in.
http://www.hackernewsers.com/users/gte910h.html