hashtree

Would love to be fast tracked, if possible. Thanks for doing this.

Docker ID: rockymadden

SEEKING WORK - Remote and Boulder, CO

I help early stage startups deliver on their technical milestones with progressive development and solid communication/project management. I'm an FP-oriented JavaScript developer with direct influences from Scala, Haskell, and Clojure. My passions lay in the lower-end of the spectrum, with particular emphasis on microservices, stream processing, machine learning, natural language processing, and expert systems. I'm also a data science practitioner with a heavy background in both frequentist and bayesian statistics. Currently focusing on freelancing with React/React-Native/Flux-like frameworks to develop unified web, iOS, and desktop experiences.

https://github.com/rockymadden

https://dribbble.com/rockymadden

https://rockymadden.com/

hn@rockymadden.com

Very neat idea, reminds me of the Gatherer add-on from WoW (http://www.curse.com/addons/wow/gatherer).

Functional programming in Scala, one of my favorite functional programming books if you take the time to do each and every exercise. Coupled with it's solid Github repo (https://github.com/fpinscala/fpinscala) and companion book (https://leanpub.com/fpinscalacompanion), it's a winner.

OVH, SoYouStart, and KimSufi with Dokku Alt (for quick apps) or custom Ansible/Docker deployments (for big apps). Since OVH created their North American DC I took the leap and have been very very happy. Knowing just how cheap the hardware/ops game is, I just can't bring myself to spend anything more than what these guys do:

  - $115/mn for a 64GB ECC, 3x Intel SSD, Xeon E51620v2, 500Mbps, etc
  - $50/mn for a 32GB ECC, Intel Xeon W3520, 4TB SATA
  - $15/mn for a 4GB RAM, Atom N2800, 1TB HDD

- From the creators of nothing you've heard of

- From the creators of this site and its previous version

- After being compared to Duke Nukem Forever

- "I’ve never agreed to having my face used on the itemz website"

- "There are millions of task management apps. Creating another one is just stupid."

- "I don’t use this app and I‘m not planning to start"

Despite OP saying otherwise in this thread, this has to be a joke.. right? Every page/video seems to have things like this. OP, if you are serious get a native english speaker (you said you weren't one) to go through the site.

I really hope there is a joke in there I am missing, besides the obvious irony in relation to the article content.

Having done much with districts in the past, I observed the same push to collect data and then make use of it in the classroom and at the district level. In the districts I encountered, there was plenty of data collection and there were even some basic reports each system might provide, but beyond that, very little thought went into `what to do with this data to turn it into actionable knowledge`. Districts would blindly throw hundreds of thousands of dollars at the problem of data collection with very little, and often none, at the actual analysis portion of the problem.

Districts often face even more fundamental problems, such as each software system being a silo to it's own data and being very hard to cross reference with other systems. SISes, LMSes, HR, and dozens of smaller systems existing in their own world. Many questions one might want to pose needs data from two or three of these. So, questions like `is Steve a much more pronounced risk of dropping out of high school` are hard/impossible to ask (depends on the software systems and data collection practices).

Another approach you might consider is:

  - 4 to 6 hours of dedicated/uninterrupted work per day
  - 6 to 7 days per week
  - Wake early, say 05:30, and start work right off the bat

Exactly, the only thing I might add would be homebrew cask (https://github.com/caskroom/homebrew-cask) as well to install gui based applications.

This should be at the top of the article to hush folks like myself who might be curious from the get go why another approach wasn't taken and why the Mac Pros were selected. Thanks for the insight as to the why.

Having been on CodeMentor for a few weeks now (as a mentor), I have some mixed feelings on the experience. I was hoping that I'd be talking with folks doing interesting things or helping fledging developers on a solid path. You do get that (and it is wonderful when it happens), however most of what it seems to be is `do my homework for me`, `fix my old jquery site`, and stackoverflow type questions answered in realtime. Overall, it has been a positive experience but just not exactly what I expected. I believe in what they are doing and expect things to improve over time if the brand can be grown.

Lastly, there does seem to be a mindset of `I want a stellar developer to talk with but don't truly value their time` (e.g. the $10 for 15 minutes of their time you mentioned). Not always the case, but it is definitely not common to see freelancing type rates. So, you end up donating your time, which isn't always possible to do from a fiscal standpoint.

In order (which is actually very hard to find):

  - Mission which truly helps people and focuses on the end-user and not simply the bottom line
  - Working with extremely smart/talented people, who don't take themselves too seriously
  - Robust development practices, to the point you can feel proud of your work and allowed to be the best in your field
  - Treats employees as adults and also truly value their work/life balance (i.e. happy employees are good employees)
  - Money

Rather than giving you a specific laptop, I will give you a strategy I have used for a number of years that has worked well for me. It allows you to have brand new equipment each year for less than what you pay buying a laptop and replacing every 3 to 5 years. I've only tried with Apple products.

  - Create an Amazon seller account in which you have absolutely stellar reviews and customer service. A perfect five stars is what you are aiming for, which is pretty easy to accomplish if you try (e.g. with roughly 50 sales over the years, I only have one 4 star review and all others are 5 stars).
  - Purchase the Mac product(s) you want.
  - Ensure you keep good care of the laptops and also keep the original boxes and accessories.
  - When Apple comes out with a new version, immediately buy the new version(s).
  - Sell your old version(s) via your Amazon seller account.

You will find certain product lines hold their resale value better. For instance, iPads, 13-inch rMBP, and both Airs hold their value well. On the other hand, iMacs and Mac Pros don't hold their value very well. In the middle you have iPhones, 15-inch rMBPs, and Minis. Customized add-ons (in which you can't go into a store and buy) are a huge no-no with this approach. The depreciation cost is just too high.

SEEKING WORK - Remote/Colorado

Heya, I'm Rocky. I'm an avid open source developer, mentor, and lead developer with over twelve years experience. I'm an FP-oriented JavaScript developer with direct influences from Scala, Haskell, and Clojure. My passions lay in the lower-end of the spectrum, with particular emphasis on machine learning, natural language processing, expert systems, and other forms of artificial intelligence. I'm also a data science practitioner with a heavy background in both frequentist and bayesian statistics.

Currently focusing on freelancing in:

  - React/React-Native
  - Flux/Reflux/Fluxible/Fluxxor
  - Electron
  - Unified web, iOS, and desktop solutions

-----

https://github.com/rockymadden

https://dribbble.com/rockymadden

https://rockymadden.com/

Love the final sentence, and thanks for the fresh viewpoint. On the bullets, we differ in opinion on some (maybe I truly am a stick in the mud):

- React/Flux: It IS super new, I just assumed if a company choose/moved to it and are actively coding with it that they would know the basics of it. Certainly wasn't expecting core contributor knowledge by any means, just that fellow devs have read the docs and avoid plainly stated bad patterns in said documentation.

- Functional Programming: Again, I only mentioned FP because they are core concepts for React/Flux. They are also highly encouraged/required in certain scenarios: https://facebook.github.io/react/docs/advanced-performance.h...

- Security: There is no reason security needs to slow down a project dramatically, if done right. End-user security should be taken seriously and not be something to be tossed aside because it is "hard". Basics get you a long way.

- CS: Good idea on the premium. Though it is often beyond a simple conversation when the concepts of recursion and basic data structure performance/usage is an exotic topic.

- Devops: Solid points, however I wouldn't say it is anything close to a bankrupt concept. Ansible and Salt for a day or two and you have completely manageable, repeatable, and solid approach to your infrastructure.

We agree on what the biggest concerns are. Oddly, I often see nearly everything missing, those being of the most concern.

SEEKING WORK - Colorado/Remote

Functional JavaScripter seeking React/React Native/Flux work with technically strong and collaborative teams. Twelve years as a developer, served as dev lead for top US trafficked sites, additional background in machine learning/AI, bayesian/frequentist statistics, data science, horizontal scaling, micro service architectures, Scala/Haskell/Clojure, etc. Successful react projects with a couple VC backed startups, wanting more.

  GitHub: https://github.com/rockymadden
  Dribbble: https://dribbble.com/rockymadden
  Personal: https://rockymadden.com

A concrete example of how I saved a few hundred thousand dollars over the AWS by building quarter rack colocation setups with SuperMicro servers: https://gist.github.com/rockymadden/5561377

With Ansible, I spend no more than an hour a week, amortized, maintaining both the hardware and administration. I assume nodes for any specific role will fail, I only scale horizontally, I always have redundancy for every role, I stay off disk as long as possible (heya 512GB RAM redis cluster), etc.

Simply personal preference. I'd like to use the same supporting tools, UI, zero context switching between products, etc. Funny enough, I use some of the social features (issues/milestones/wiki) for project management, even for my own projects.

I really wish GitHub only counted private repos that have more than one collaborator. If you are like me and have dozens and dozens of smaller repos that only you yourself work on, it makes the GitHub model a non-starter (and I'd love to be GitHub only, rather hosting my own server or using bitbucket).

Oddly enough, I have two Dell PowerEdge 1850 servers for anyone interested in the Fort Collins, Colorado area. They have been sitting on a bread rack for a while now and could use a good home.

You might try Kaggle: http://www.kaggle.com/

Ha, I didn't and I am on it (though I don't deserve to be, IMO).

The original concept was to scale via the open and self-administered community itself while keeping a hands off approach to all other aspects. Truly just a simple network of solid folks and not a product trying to solve every problem (though I imagine it could be productized). The hope was that by only letting in solid freelancers that these items could be handled by the freelancers themselves without too much worry about getting screwed over or hassling one another.

You bring up a valid concern about the race to the bottom, which is exactly one of the things I want to avoid. The thought around the minimum rate information was to inform others about what type of level of compensation one would need to even consider work. I think I might rework this right now and also inform folks that only developers with rates above XYZ are allowed.

OP here: I, like many others, experience times of great abundance and shortage of freelancing work. The idea of having a vetted/endorsed network of freelancers I can trust to send overflow work was something that appeals to me on both sides. I thought using GitHub as the vehicle for maintaining such a community was an open and hacker-friendly way of doing it.

I welcome any feedback on the concept!

With io.js coming on to the scene, I've recently revisited my thoughts on using JavaScript for scientific/statistical computing. With ES6, V8 Turbofan coming down the pipe, and enough support for serious functional programming (e.g. fantasy land, transducers, ramda, etc), I've decided to shift from using Scala/Haskell/R to JavaScript. I think there is a bright future in these areas and a lot of room for devs to make a name for themselves doing this kind of development. R is particularly easy to beat on the performance front, from the libs I have rewritten to JS to date.

Daily Rituals (book) which covers the work habits of ~160 famous writers, artists, philosophers, scientists, and mathematicians. Nearly every single one had a strict schedule to force work into specific time slots rather than letting inspiration strike, they tended to be morning people, and they tended to work shorter days but worked everyday. While still anecdotal, an interesting read on how many great minds spent their work days; nearly each one seemed to follow this same notion that you favor discipline over motivation.

https://www.goodreads.com/book/show/15799151-daily-rituals

MITM certainly can see everything, and employers do it: http://it.slashdot.org/story/14/03/05/1724237/ask-slashdot-d...

Examine DNS lookups, examine URLs, MITM potential to read everything, all sorts of things they could do on just the network level.

The other comments are solid, and this is one of those questions whose answer probably won't help much in solving your problem (due to its nature, not for a lack of good answers). However, I can offer you some time and insight if you want a technical person in the ML/NLP domain to bounce your ideas off of before you get too far into it. Contact information is on my profile, if you so wish.