3,862 reputation
21648
bio website connjur.uchc.edu
location Connecticut, USA
age 27
visits member for 2 years, 8 months
seen yesterday

I work in a scientific computing group on the CONNJUR project, providing open-source software for NMR (Nuclear Magnetic Resonance) spectroscopy.

Check out some of my work on github:

  • NMRPyStar: an API for accessing archived NMR data files in the NMR-Star format used by the BMRB.

  • Miscue-js: validation of JSON files to deal with obnoxious and tricky interoperability issues such as number overflows and duplicate keys

Some technologies that I've used and like:

  • Python
  • git
  • Javascript
  • Haskell
  • Java
  • MySQL

Jun
27
revised Named output parameters vs return values
'language agnostic' means nothing
Jun
27
comment What did Rich Hickey mean when he said, “All that specificity [of interfaces/classes/types] kills your reuse!”
What do you mean by discoverability? Is it similar to this?
Jun
25
comment Is it a good practice to wrap all primitives and Strings?
@maple_shaft the OP explicitly said in a comment that he hadn't read the paper. This was before I posted my answer. See programmers.stackexchange.com/questions/202663/…
Jun
25
awarded  Cleanup
Jun
25
revised Is it a good practice to wrap all primitives and Strings?
rolled back to a previous revision
Jun
25
comment Is it a good practice to wrap all primitives and Strings?
-1; Mr. Client now needs the software to work for his associates in China/Brazil/India/etc. who don't all speak English. Mr. Client, who is a bit of a software engineer himself, is dismayed to find that display logic is embedded within domain objects, making it extremely difficult to add support for other languages.
Jun
25
answered Is it a good practice to wrap all primitives and Strings?
Jun
25
revised Make a flowchart to demonstrate closure behavior
added 113 characters in body
Jun
24
comment What does scannerless parsing have to do with the “Dangling Else Problem”?
@Giorgio no, it's off topic.
Jun
24
comment What does scannerless parsing have to do with the “Dangling Else Problem”?
@Giorgio that is a good question and I would love to answer it; however, it should be a separate question as it's off-topic from the OP here.
Jun
24
revised Make a flowchart to demonstrate closure behavior
added 618 characters in body
Jun
24
revised Make a flowchart to demonstrate closure behavior
added 31 characters in body
Jun
24
answered Make a flowchart to demonstrate closure behavior
Jun
24
comment What does scannerless parsing have to do with the “Dangling Else Problem”?
@Giorgio yes.
Jun
21
comment Is it a good idea to read compiler source code?
I am truly amazed that all the answers say "no, don't do it". I couldn't disagree more with those answers. In addition to reading source code, you might enjoy and benefit from reading academic papers describing parsing algorithms and compiler architecture. +1 for a good question and good luck.
Jun
21
comment Finally block for methods - is it a bad idea?
Cross-posted: stackoverflow.com/questions/17223949/…
Jun
18
comment What does scannerless parsing have to do with the “Dangling Else Problem”?
@Giorgio ... um. That example doesn't really help me. Scannerless parsers could be implemented like that, but there's much easier/safer/clearer/simpler ways of doing it. But I guess if that's the point the wikipedia page was making ...
Jun
18
comment What does scannerless parsing have to do with the “Dangling Else Problem”?
@RobertHarvey a common way to define languages is using a context-free grammar, plus a bunch of rules which disambiguate the grammar, if necessary.
Jun
18
comment What does scannerless parsing have to do with the “Dangling Else Problem”?
@Giorgio I am confused by your comment: 1) why does a scanner-less parser need a more complex grammar? The grammar is independent of the implementation. 2) heuristics? Isn't there a well-defined answer to the dangling else problem -- no guessing required?
Jun
18
asked What does scannerless parsing have to do with the “Dangling Else Problem”?