If your organization thinks they will look worse by releasing their data, it is OK to explain to them how it looks to not.
@j_houg no, I mean given multiple options, do something like:
options.filter{_.worstCase > threshold}.maxBy{_.bestCase}
-
-
@avibryant I don't think there is a special word for that. I do think you want to filter on inputs, and then optimize the result. -
@avibryant I've been pondering on how to distinguish jobs + offers, kinda thinking of actually building a model now.
End of conversation
New conversation -
-
-
@avibryant Dude, put some white space in your code! You had plenty of characters left.@j_houg -
@peterseibel@avibryant@j_houg Just like you were back at the middle school dances, man. Give it a little room for jesus. -
@sritchie@peterseibel@j_houg look, I put spaces around the > and I totally didn't have to. -
@avibryant@peterseibel@j_houg maxBy(_.bestCase), no sharp corners to catch yourself on -
@sritchie@peterseibel@j_houg I just can't get behind the parens for closure params. My Ruby is showing. -
@avibryant@sritchie@j_houg That and the fact that there seem to be a lot of situations where scalac actually chokes on ()s where {}s work. -
@avibryant@sritchie I should also like to say that while we've dragged this off to nerd comfort zone,@j_houg's original point is legit. -
@peterseibel@avibryant@sritchie Thanks! On my tombstone I want "Loud, but not wrong." - 1 more reply
New conversation -
-
-
@j_houg eg, for jobs, as long as you're ok with all the salaries assuming options are worthless, pick the offer with the highest upside.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.