DEADB17

15 ms·

1.
by DEADB17 2y ago
https://git-scm.com/docs/git-check-ignore is useful to diagnose why a file is ignored
2.
by DEADB17 5y ago
In the "Fundamentals"[1] course they use a table format for the design recipe that makes the correspondence between data and functions more obvious, and perhaps the JSP inspiration more evident. [1] https://course.ccs.n
3.
by DEADB17 6y ago
The techniques are not mutually exclusive, it depends on the context. When you don't have a clear idea of the requirements starting "front to back" helps to understand and gather them while building something that validates t
4.
by DEADB17 6y ago
Most of the complexity comes from state management and tracking data dependencies, not dom manipulation. If you like keeping things light this library gives you a lot of bang for the buck: https://github.com/MaiaVictor/
5.
by DEADB17 8y ago
if you enjoyed this you might also find “A confession”[1] by L. Tolstoy interesting. I did. [1] https://en.wikipedia.org/wiki/A_Confession
6.
by DEADB17 8y ago
off topic, but HN is the last place I'd would expect to find a reference to Rudolf Steiner :)
7.
by DEADB17 9y ago
plantuml is also text based and supports many types of diagrams: http://plantuml.com/gantt-diagram
8.
by DEADB17 10y ago
There are tests to validate IE support. The intent is clearly there. Circumstantially this design decision is not met, but it is clearly a bug not some fundamental lack of support. Please consider how your feedback might affect the people g
9.
by DEADB17 10y ago
Sorry @taeric, I can't reply to your post directly. I do think that the intent of the producer is being communicated (unsafe to upgrade, safe to upgrade with new features, safe + automatic improvements). I'm not disagreeing that &
10.
by DEADB17 10y ago
I don't know about maven, but in NPM you can keep both. If you take away the limits of a particular implementation, I think that semantic versioning is a useful convention for the producer of an artifact to convey intent to the consume
11.
by DEADB17 10y ago
Being screwed would be the case if the consumer of the artifact is forced to upgrade. i.e.: if versions cannot coexist in a code base. Otherwise I think the information that they convey is useful: PATCH: improvement or correction that does
12.
by DEADB17 10y ago
Wouldn't changing the MAJOR version be equivalent to changing the namespace without altering the human memorable identifier of the package? Understanding that changes in MINOR.PATCH are backwards compatible, is the difference between N
13.
by DEADB17 10y ago
I don't understand why he says semantic versioning does not work. In my experience (with NPM, not maven) it is very useful, adding meaning of intent by convention: Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR vers
14.
by DEADB17 12y ago
I think that contrasting OOP with FP brings too many implicit assumptions to the discussion. The value of immutability, for example, seems to be orthogonal to the technique used to structure a computation and is more closely related to the
15.
by DEADB17 12y ago
After using browserify for a while now, I recently came across webpack ( http://webpack.github.io/docs/what-is-webpack.html ) which I'm finding more convenient and as efficient. Advantages: - requiring and pre-prose
16.
by DEADB17 13y ago
It is, let me know if you want more info
17.
by DEADB17 13y ago
> which isn't really possible if you're rendering html in the server. You can have a front-end web server that is also a client of the API server and keep the separation as if it were any other API client. This is the approach