danielheath

91 ms·

1381.
by danielheath 7y ago
ActiveFacts (the hard formalism parts are done and working, but almost none of the quality of life stuff is implemented yet) Core idea is to start from a human-authored formal domain model (sample models: https://github.com/
1382.
by danielheath 10y ago
If an i-device breaks on the first day and you take it to an Apple Store, the tech fixing it has: * A repair manual * Parts * Tools * The ability to replace your device on-the-spot with a new one if they brick it
1383.
by danielheath 10y ago
There is absolutely no reason to expect volunteers to owe you their time or responses. I don't mean to denigrate you, but I must be candid here: demanding work from others without putting in the hard yards yourself is simply not accept
1384.
by danielheath 10y ago
The killer feature (and only reason I use it) is being able to render the same templates with the same data on the server (isomorphic/universal/whatever). The result is a webpage that can do lightening-fast transitions client-side
1385.
by danielheath 10y ago
That's a hell of a reach from what she said, to put it mildly. To justify your inference she would need to be asking for extra money for dealing with any men, ever.
1386.
by danielheath 10y ago
Perhaps because without nothing is useful if you don't know where to find it?
1387.
by danielheath 10y ago
It's common for programs to embed a database engine. Informally, you're doing this every time you write any structured data to a file. Baking a database into your application drastically simplifies distribution/deployment a
1388.
by danielheath 11y ago
https://github.com/ask-izzy/ask-izzy/
1389.
by danielheath 11y ago
For that you would need * An STM implementation (ruby doesn't have one afaik) * All network services you connect to (eg databases, APIs etc) would need to support transactions for write operations
1390.
by danielheath 11y ago
I don't think baked-in is a great idea unless the data layer is really good. There are plenty of data-layer implementations that work with react, but none are good enough yet (imo) to be the canonical way to do it.
1391.
by danielheath 11y ago
Main dev on the project here (I work for rea-group.com who run www.realestate.com.au, but they've given me a years secondment to the project). Back in 2013 a team at our hackday implemented the precursor to this app, and the leadership
1392.
by danielheath 11y ago
I tend to think of systems which don't sandbox each process effectively as 'toys' since I can't meaningfully trust them to run code I haven't audited.
1393.
by danielheath 12y ago
Tomorrows headline: "Googler claims AI is evil, and also definitely not real" :troll:
1394.
by danielheath 12y ago
"a senior/lead software engineer with only about 2 years of professional experience" Has the term senior lost all meaning?
1395.
by danielheath 12y ago
It's natural that most public code panics on error, even though it's bad practice. Error return values (e.g. go) are better for building large systems where stability & predictability are important (that is, cost to maintain).
1396.
by danielheath 13y ago
The problem is stunningly difficult and widely believed (but not proven) to be intractable. However, there's good work advancing the state of the art in this field. Look at Object Role Modelling implementations like ActiveFacts ( http