doug1001
>I’m not from the South and don’t talk as if I were. Most telling, and the other guys can sense this somehow, I do not for a moment think I’m a symbol of some bygone ideal of Wild West American freedom or any other half-mythic, half-menacing nugget of folk nonsense.
"Some Dart users really dig a functional style and appear to be playing a game where whoever crams the most work before a single semicolon wins."
sort of the Dave Eggers of software engineering
i am
fire up the redis server--you'll see some ascii art there
i suspect that, to capture the full value of J, one needs to already know the array-oriented paradigm (or at least have a strong motivation to learn the two in parallel)
knowing the AOP paradigm also helps understand the programming patterns as well as the syntax
still, the dense syntax has extraordinary power
for instance, n-queens in J (from Rosetta Code) is just 4 short lines:
perm =: ! A.&i. ]
comb2 =: (, #: I.@,@(</)&i.)~
mask =: [ */@:~:&(|@-/) {
queenst=: comb2 (] #"1~ mask)&.|: perm
line 1: create the 2D array (n x n chessboard)
line 2: populate the array with candidate solutions
line 3: eliminate invalid solutions ('mask' them)
also NumPy, and Nd4j via scala bindings
of course NumPy and Nd4j are libaries
i strongly recommend Julia as an array-oriented programming language
particularly because it has quite a few other features to recommend it
Julia follows the Matlab syntax conventions more closely than NumPy (or R) which i think was a good design choice
(which honors the convention of expressing a dual using "co-" and indeed co-product is the dual of product)
aside from that, python has a separate ordered dict class
it's a beautiful country, but for a start-up? I have my doubts.
i have also lived in the Bay Area; live here now in fact.
Norway is the most expensive country i have ever lived in or visited--more than SF, more than Manhattan, perhaps about the same as Tokyo, although i have only made brief visits there for work.
Taxes are insanely high: income tax is on the level as Switzerland; VAT is 24.5%. Petrol prices are the highest in any country i have ever driven in.
lastly, working start-up hours (or even normal hours) is not easy during the months of October through February when daylight's non-existent or negligible
the term "triage" means to order items (patients, originally) according to urgency
this paper has nothing whatever to do with sorting a bug list according to urgency
the paper describes a model to assign a particular bug to the developer who can resolve it most efficiently
to me this is "assignment" not "triaging"
but at least you can see how a supervised learning technique is a good fit for the problem they actually describe
so one row in the training set is a set of attributes relating to the bug itself--where in the codebase it resides, etc
the class labels are of course the developers assigned to fix the bug
what actually is presented in this paper might be useful--although i have my doubts that the net value of such a model (optimum assignment of devs to bugs). In other words, even if the model can generate assignments better and more efficiently than manual assignment, the developer time required to write the code to convert the raw data to model input (to train/test/validate the model) is not small--for intance, look at how much unstructured text is involved
i doubt i would go to the trouble--mapping devs to bugs is nothing something we do poorly at my shop, and even when i get it wrong, the devs sort it out by swaping out tickets
not nearly as useful as an automated bug triaging sytem--ie, a system that would auto-sort our bug list based on urgency, but again, that's not the subject of this paper, title notwithstanding.
developer to Minister: "ideal use case for Machine Learning--i'm on it"
to argue that the meaningful rubric of effort ought to be a "product", he creates a straw-man called a "project"
the much more meaningful comparison is to compare products versus "platforms" and "tools/infrastructure"
if he had done that, then he i bet that he would conclude that all three rubrics of effort are necessary, and preferring one vs the other is a question of priority, not "do one instead of the other"
ie: some things you built to sell; other things you build so you can build those things better and more efficiently; and still others you build for use as reusable or modular components across multiple future products, so you don't have to build the same component over again for each product that requires it
"tools", eg: the 250-developer-hours spent on a "project" to create an automated testing & deployment pipeline, will likely net out in a few months and result in higher quality products almost immediately
"platform": a "project" to factor out code common across many workflows in a typical web app, and re-implement that code as microservices having endpoints available to any of the multiple data flows that need them (for instance, "user-login & authentication", "user-profile fetch", "re-ordering user-search results using learning-to-rank algorithm" etc
a project to build such reusable utility micro-services obviously don't result in a "product", and yet such a project is usually cost-justified (in CFO terms) even over short-term periods (< 90 days)
"a word [or phrase] is the skin of a living thought"--not sure who said this, i think it was Oliver Wendall Holmes
does this seems like another instance of the annoying practice in our field of someone giving a name to a thing because they think it's new, though it's not (ie, source-to-source compilers have been around as long as source-to-bytecode compilers)--no need to re-name them
wish they would just stop it and get the hell off my lawn
building the model and packaging it for deployment are two completely different sets of tasks, are they not?
much more useful, again in my experience, is a tool like vagrant, which allows a production environment to be provisioned onto a VM; said VM is then run from the data scientist's desktop (eg, so they can do their work with the same versions of the same tools available in prod)
a tightly defined, clearly written question with a single correct anwswer?
Rejected: RTFM
a question with more than one correct answer (but which almost certainly has a "best answer" which a community like SO is in the obvious best position to judge)?
Rejected: subjective; opinion-based
no axe to grind here--i used to participate in SO (50K rep, and one of the highest rep-to-post ratios)--i honestly just find it too difficult to navigate that narrow straight