jmakeig

24 ms·

1.
by jmakeig 8y ago
This took me a while to figure out, but it’s incredibly powerful once you get it. As others have suggested, I was working on a Redux-based interpreter.
2.
by jmakeig 8y ago
REST allows for clients and servers to evolve independently. If you can constrain that you can probably design something significantly simpler. That’s not a shortcoming of REST, though. The channel between your mobile client and your backen
3.
Elasticsearch SQL(elastic.co)
1 points by jmakeig 8y ago|0 comments
4.
by jmakeig 8y ago
HATEOAS is designed so clients and servers can evolve independently, like on the open web. If you control both ends, HATEOAS is probably overkill. (And that’s ok.)
5.
by jmakeig 9y ago
The problem isn’t the schema, it’s that you must have exactly one at all times. Sometimes you need zero, sometimes you need many. Having a fixed schema in production reduces unpredictability and provides optimization opportunities. The jour
6.
by jmakeig 9y ago
Only? Many of the early MongoDB employees came from MarkLogic. Several have returned too. (Full disclosure: PM at MarkLogic)
7.
by jmakeig 9y ago
Or your data is…you know…mark-up. Imagine a biology textbook, or legal contract, with inline citations and entities. There’s lots of marked-up human text around, even if that’s not what you’re sending to a JavaScript front-end. (Ironically,
8.
by jmakeig 9y ago
If you control both the client and the server, there are lots of shortcuts you can take. As you say, that’s not the problem that REST was trying to solve, though.
9.
by jmakeig 10y ago
That is clearly an invitation to Netflix and chill.
10.
by jmakeig 10y ago
This was nothing but a ring-kissing ceremony only to boost Trump’s own ego. The entire Trump campaign has been a sophomoric revenge fantasy exacted against the (actual) elites who have excluded him his entire life. Trump is not interested i
11.
by jmakeig 10y ago
Argh! They didn’t charge for the component of their offering that was most valuable. Period. Good software doesn’t pay for itself. Consulting and training are difficult to scale, mostly because they require adding people. As such, the margi
12.
by jmakeig 10y ago
This is a cultural problem not a technical one. The social contract in a dev team should strictly enforce no cowboy commits to master…ever. If Bob thinks that’s OK, there are more issues than a UI warning is going to solve.
13.
by jmakeig 10y ago
I'd love some backstory on this too. I (kind of) understand JSX for HTML, but declaring routing rules seems very far from that.
14.
by jmakeig 10y ago
This looks really cool, but I still don’t understand how Rethink plans to cash out their VCs, though—~$12M, according to Angel List. Cloud hosting is trending toward zero and support/consulting only scales with people. I’m not to tryin
15.
by jmakeig 10y ago
I created a quick code generator[1] for async action scaffolding just for this reason. [1] https://github.com/jmakeig/redux-thunk-scaffolding/blob/mast...
16.
by jmakeig 11y ago
ACID transactions in a highly available distributed system are hard and often fail in subtle ways when done wrong at the edges. Any implementation will take years to mature in the lab and in actual production usage. This isn’t a knock on th
17.
by jmakeig 11y ago
And it’s a database with indexes and caches.
18.
by jmakeig 11y ago
OK, I'll bite: What is "fair"? Isn't allocated to the users who value it most fair?
19.
by jmakeig 11y ago
Maybe "efficient" would have been a better word than "good". I have no doubt that Uber is pricing to benefit their shareholders, not the public good. That's why the taxi fare regulations are there in the first place
20.
by jmakeig 11y ago
"Couldn't afford" is a loaded term. I can afford a helicopter ride home, but I don't value its utility enough to pay what's being asked. Isn't that how prices are supposed to work?
21.
by jmakeig 11y ago
Great read and thorough approach. However, it's worth noting that Uber provided the data for this study. I'd imagine they had an idea as to its conclusions before they provided it. The findings are intuitive and validate that surg
22.
by jmakeig 11y ago
http://developer.marklogic.com/features/javascript (Full disclosure: I work at MarkLogic)
23.
by jmakeig 12y ago
[Full disclosure: I’m a product manager at MarkLogic.] MarkLogic can handle all of these requirements with aplomb. You can think of MarkLogic as a database built with search engine technology. It uses a document data model (text documents i
24.
by jmakeig 12y ago
Looks like a FLWOR statement in XQuery.
25.
by jmakeig 12y ago
Yes, MarkLogic includes a full HTTP client and server so you can create and consume web services. In XQuery this would look like: xdmp:http-get("http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary
26.
by jmakeig 12y ago
REST, as Fielding described it, is good for decoupled systems that can (and need to) evolve independently, like web browsers consuming HTML and JavaScript. If you can relax the decoupling or independent evolution constraints, RPC over HTTP
27.
by jmakeig 12y ago
http://explainshell.com is what you're looking for.
28.
by jmakeig 14y ago
Parsing and accessing are two different tasks. Even if you have an entire JSON (or XML) data structure in memory, getting to the right pieces can be difficult. “Return all of the order entries contained in an a shipment of type ‘Billable‘ w